Overview Features Coding ApolloOS Performance Forum Downloads Products Order Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
Please visit our Apollo-Discord Server for support.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Documentation about the Vampire hardware

Graphical Glitches?

Tony Day

Posts 62
05 May 2016 23:17

Quick question. I have an A600 with a dying floppy drive. It only loads about 20 - 30% of my floppy discs. I know its not the disks as my A500 loads them all.

  Recently got a Vampire2 card and I've tried playing a few games.

  Example of games that I actually got to boot:

  Speedball 2 and Chaos Engine - Fine

  Final Fight - graphical glitches appear sometimes when scrolling

  Stunt car racer - Flickering road when driving straight?

  FINAL FIGHT VIDEO HERE: (Glitch on right of screen):
EXTERNAL LINK

  With the above information do you think that the problem lies with the Vamp2 or the floppy and discs?

  Thanks


Michal Warzecha

Posts 209
06 May 2016 07:32

It's not floppy for sure. Some Vampire problem I think. If You remove Vampire from board problem dissappear? Do You run Vampire with latest core?


Nixus Minimax

Posts 416
06 May 2016 12:17

It's probably bad programming on the side of the game programmers. There are a lot of games and demos that have problems with processors much faster than they ever expected. Usually you can check this in UAE with maximum speed CPU settings.



Tony Day

Posts 62
07 May 2016 12:40

The Vampire is running with the latest core. I would like to know why this happens with some games and not others.. once I get WHDload on the CF ill see if Final Fight has the same problems.

As for the Vampire. Im not going to disconnect the thing again. I had a lot of trouble in that department and fixing FF is not that important :)


Nixus Minimax

Posts 416
09 May 2016 13:35

Tony Day wrote:
I would like to know why this happens with some games and not others.

Bad programming. The most common problem is the programmer assuming a blitjob will be done after some CPU time and restarting the blitter for some new blitjob not expecting the CPU to be so fast that the blitter couldn't finish its work in time.

posts 5