Photon
24 November 2004, 16:24
Hi!
Getting nostalgic, so I'm coding an A500 demo in WinUAE. I'm worried because even though I've set 'Cycle Exact CPU and blitter timing' WinUAE doesn't really have any configuration settings for bitplane DMA stealing blitter cycles. At least I seem to recall that both the blitter and the bitplane DMA used even cycles, so that the more bitplanes you had on, the longer it took for the blitter toblit. Am I wrong?
However, this is not the case when I emulate my demo in WinUAE. Regardless of the number of bitplanes used, the blit takes the same amount of time. NOW: here's the problem: the point of programming A500 demos is the challenge of making the fullest possible use of the available raster time, without overdoing it so that the demo staggers.
How can I make sure that a demo developed in WinUAE won't stagger when it's transferred to Amiga? (I.e., how do I stop WinUAE from telling me that I have all this time available, when on a real Amiga, I don't?)
I have WinUAE 0.9.91.
Thanks for any help
Getting nostalgic, so I'm coding an A500 demo in WinUAE. I'm worried because even though I've set 'Cycle Exact CPU and blitter timing' WinUAE doesn't really have any configuration settings for bitplane DMA stealing blitter cycles. At least I seem to recall that both the blitter and the bitplane DMA used even cycles, so that the more bitplanes you had on, the longer it took for the blitter toblit. Am I wrong?
However, this is not the case when I emulate my demo in WinUAE. Regardless of the number of bitplanes used, the blit takes the same amount of time. NOW: here's the problem: the point of programming A500 demos is the challenge of making the fullest possible use of the available raster time, without overdoing it so that the demo staggers.
How can I make sure that a demo developed in WinUAE won't stagger when it's transferred to Amiga? (I.e., how do I stop WinUAE from telling me that I have all this time available, when on a real Amiga, I don't?)
I have WinUAE 0.9.91.
Thanks for any help