Zool AGA WHDLoad issues

[hexaae]

Gfx issues with Zool AGA WHDLoad 2.0:
http://mantis.whdload.de/view.php?id=5755
vertical line on the left border, horizontal line with flashing pixels in the upper part, horizontal short blue line on the right border



The strange thing is that the problem goes away activating and deactivating subpixel emulation OR gfx scale (TV, auto integer...) so it looks like a possible WinUAE issue...
Just to be clear: if you run the game without subpixel emulation or fullscreen auto it will still show these gfx glitches, 'till you change them again. Will also happen again every time you start a new game.
If someone could test this also on a real A1200 it would be interesting...


It also has another issue:
try to run the game with Music a pair of times (you can quit in-game pressing P, and then Q) and you'll notice the small intro with Zool flying kicking from right to left has randomly no sound... It happens with sound fx only too if you start a new game enough times.

P.S.
Before you ask: yes, also ross 3.1beta slave is still affected

[elessar84]

I confirm everything @hexaae wrote.
To be clear, it's not WHDLoad's fault, because the floppy version works with the same graphical bugs.
I also checked the CD32 versions under WHDLoad (A1200 configuration), and the CD32 versions with the disc image (CD32 configuration) and these work without graphical errors. Something is wrong with Zool AGA emulations on Winuae.

[Toni Wilen]

Much better if disk version does same. Statefile please

[jotd]

I remember the game using a lot of self-modifying mode too. Not the best for compatibility.

I also remember that on my real machine (A1200/060) the main character is glitchy (not the case in the ECS version, and I don't remember about the CD32 version). Doesn't happen on winuae.

[elessar84]

I'm testing Winuae version 4.10 right now and it seems that the graphics bugs are gone (at least in the WHDLoad Zool AGA version).

[Zarnal]

I can't reproduce with a " simple " Quickstart A1200 + Fast + HD ( slave version 2.0 ) and subpixel actived/desactived. Area 1-1 ( pic 1 ).

Maybe it's only related with high ends configurations and/or Whdload related ?

Note : simple configuration.

Note 2 : i can't test with IPF 1655 because i don't have " Code Window " ( protection ).

[hexaae]

Tested with new 4.10 public and the upper screen corruption is gone indeed, but the half-pixel (subpixel glitch) vertical line on the left border is there (whdload thing... same minor non-issue have been fixed in the past for a few other games but I can't remember the thread where ross, wepl, and Toni discussed about it...), and on the right the short horizontal blue line is still visibile using as video filter: Fullscreen (Max) or (TV), or Integer scaling.
Is not visible using Default or some other filter scaling combos... but this could be an original game bug in the end, not visible on older TV color.

BTW, the flying kick animation bug starting a new game, randomly without audio, is something whdload could fix in the future... To reproduce it you can start a new game and then quit (P pause, and then Q quit) again and again, especially after you changed from game options between Music/Fx.

[hexaae]

Just tested 4.10.1 beta 0 (latest winuae.7z), and the upper screen shows again the issue fixed by public 4.10 (it was just a pure coincidence?).
Probably Zool AGA slave needs some more fixes, independently from WinUAE emulation accuracy...

P.S.: another old thread about Zool AGA issues...

[hexaae]

In the meanwhile I've found these custom settings to fix Zool AGA boders:

SLAVE=ZoolAGA_ross.slave
PRELOAD
ExecuteStartup=
ExecutePostDisk=UAE-configuration cachesize 0 cpu_speed real chipset_subpixel false gfx_filter_autoscale standard gfx_filter_vert_zoomf 88 gfx_filter_horiz_zoomf 88 gfx_filter_vert_offsetf -200 gfx_filter_top_border 90 gfx_filter_left_border 290 gfx_filter_right_border 1564 gfx_filter_bottom_border 600
Custom1=0
NoCache
PreloadSize=1796960

Notice I've forced restricted screen borders (black bands) from top, bottom, left, right (gfx_filter_top_border 90 gfx_filter_left_border 290 gfx_filter_right_border 1564 gfx_filter_bottom_border 600) and works like a charm on my 1920x1080 fullscreen.
Maybe
a) WinUAE calculates wrong border limits when using filters?
b) devs in the good old days didn't set up borders properly since TV always cut out those portions, now visible using WinUAE?