View Single Post
Old 12 October 2013, 18:42   #179
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,524
Quote:
Originally Posted by amilo3438 View Post
A500 confirmed (OCS), ECS = very corrupted display because it triggers chipset bug (bitplane DMA can end too late on ECS and AGA causing DMA cycle conflict), this does not happen in emulation (effect looks like some kind of line delay scrambling..) but I added log warning.

Quote:
Hammer's Mini Intro by Anarchy

A500 OCS ... same here but only on OCS (pic.3)!
I think this depends on memory configuration and more, could be some kind of sprite emulation problem too. This is not good test case.

Quote:
Originally Posted by amilo3438 View Post
FYI...
Deja Vu by Anarchy

A500 OCS/ECS ... worked fine with b8, but with the 2013-10-10 winuae.exe there's an error on the sphere part! (as shown on pictures below)
I can't duplicate it working using b8 or any other version..

Quote:
Originally Posted by amilo3438 View Post
Yea, I know ... I found it while testing Anarchy demos/intros so decided to mention it here again just for the info/record.

But to me it looks more like the demo problem then an emu problem.
Are you sure it doesnt happens on a real A500?!
Yes, it is A500 confirmed. This kind of "effect" is very common when "something" takes too long or is too quick and program requires very good timing and is "racing the beam". (Similar to Deja Vu above). If for example bitplane clearing is too fast, it may clear scanlines that are not yet output = cleared empty data is visible at the bottom part of display, not old and correct data.
Toni Wilen is online now  
 
Page generated in 0.06374 seconds with 9 queries