Thread: Whdload demos
View Single Post
Old 23 December 2017, 11:47   #6
StingRay
move.l #$c0ff33,throat
 
StingRay's Avatar
 
Join Date: Dec 2005
Location: Berlin/Joymoney
Posts: 6,863
Quote:
Originally Posted by chip View Post
I still don't understand which way an OCS prod can run under AGA machine
By simply patching the problematic parts (see Ross' reply) to work properly. Real world example: Demo works fine on 68000 but has buggy graphics display on faster machines. This can be caused by missed blitter waits (68000 is slow enough so blitter has finished before next operation starts) which then need to be added for the demo to run properly on 020+ machines.

However, there can also be problems that are not so trivial, demo has blitter waits but there still are bugs on 020+? This can be timing related problem, some code is executed while blitter clears the screen, code is executed faster on 020+, blitter is still clearing the screen which can lead to weird visible bugs.

It can be a matter of some minutes to make code run properly on all machines or it can take MANY hours (Desert Dream and Hardwired are good examples of the latter).
StingRay is offline  
 
Page generated in 0.24925 seconds with 11 queries