Possible Speed-Bug in Hybris

[SailorSat]

Hi.
I'm currently trying to setup my Amiga emulation system and I think I've stumbled about some bug in WinUAE.

I've selected an Amiga 500 with OCS Chipset and Kick 1.3 in Quickstart.
The compatibility/speed slider is set to most left position.

The game that triggers the bug is Hybris, the Quartex-cracked version actually (CRC = 6E B0 8E 74) and the "AGA fixed" one (for some reason WinUAE doesn't show a CRC?!)

Actually the game runs way too fast ingame, sometimes "flashing" the whole screen.

This Disk works fine on my real Amiga 500 and on my real Amiga 600.

I'm running WinUAE Fullscreen+VSync in 720x288 50Hz on two systems, and on 1600x1200 85Hz on the third.

Also the problem seems to disappear if I set the compatibility slider in the second position OR if I run it in Window Mode.

System1 - Core Duo T2050 (1,6Ghz, 2GB RAM), Radeon xpress 200m, XP32 SP3.
System2 - Core2 Quad 6600 (2,4GHz, 4GB RAM), GeForce 9600, XP32 SP3.
System3 - Core2 Duo E2160 (1,8GHz, 2GB RAM), GeForce 9500, XP64 SP2.

I've only added Logs for the first System, as the others say pretty much the same.

P.S. Don't know exactly when this bug started to happen, I think I noticed something like that with 1.5.4 already but didn't have time to tinker around.

[TCD]

Hi SailorSat and welcome to EAB!

Originally Posted by SailorSat

Also the problem seems to disappear if I set the compatibility slider in the second position OR if I run it in Window Mode.

If you change the slider from the leftmost position, you disable 'Cycle exact' for the chipset. As Toni has explained several times these changes for the chipset timing can be important for the game to work as expected. So it's not really a bug

[SailorSat]

Hm okay that sounds logical though I thought more compatible meant more like the real thing (but using more CPU time).

[Ironclaw]

Yeah, always try to disable/activate Cycle-exact when a game isn't behaving like it should. Alot of people posting errors in a lot of games, bug reports etc... all in vain when in alot of those cases no one thought of trying the Cycle-exact (lack of knowledge)

[TCD]

Er, it actually works when disabling cycle exact IC.

[SailorSat]

Now that I think about it.
If thats the problem, why does it work in window mode?

[Ironclaw]

Originally Posted by TheCyberDruid

Er, it actually works when disabling cycle exact IC.

Yeah, the same thing goes the other way too.. if a game isn't behaving like it should and u have Cycle-exact ticked, try without.

In my experience, way more games need it ticked than not.

[TCD]

Originally Posted by SailorSat

If thats the problem, why does it work in window mode?

Slightly different timing for windowed vs. fullscreen mode. If it works in fullscreen (or fullwindow) with cycle exact disabled, it's still fine. Might always change in the next version

Originally Posted by Ironclaw

Yeah, the same thing goes the other way too.. if a game isn't behaving like it should and u have Cycle-exact ticked, try without.

Okay, got your point

[Retro-Nerd]

Match A500 speed it the point here. If you switch to adjustable settings Hybris fluctuates in speed. And for faster Amigas: There is a WinUAE speed patch in the WHDLoad version.

[TCD]

Originally Posted by Retro-Nerd

Match A500 speed it the point here.

Hmm, for the A500 quickstarts 'Match A500 speed' is always enabled, no matter what 'compatibility' option you choose.

[Retro-Nerd]

Of course, Quickstart (= cycle exact) auto-switch to A500 Speed. But as you already said, it works without. In this case you have to make sure that "A500 speed" is enabled.

[TCD]

If you choose any of the A500 quickstarts with any compatibilty it is always enabled, no matter if you selected something else for the CPU emulation speed before.

[Retro-Nerd]

You miss the point. Anyway, the game has no speed bugs with a proper/working config.

[TCD]

Originally Posted by Retro-Nerd

You miss the point.

Guess so Anyway with an A500 quickstart and cycle exact disabled it works flawlessly

[Retro-Nerd]

Mmh, i thought quickstart A500 enables "Cycle Exact" by default since ages. Obvisously not. I'm getting old.

[Toni Wilen]

To everyone who answered: it is good idea to read the whole OP before answering... (it obviously has nothing to do with CE mode if it works in windowed!)

Originally Posted by TheCyberDruid

Slightly different timing for windowed vs. fullscreen mode.

What? This is totally wrong too

OP: Does it stop flashing if you disable vsync? (if you had it enabled). AFAIK it can only cause incorrect (fullscreen-only) speed, another possibility for problem is vsync being disabled in display driver's control panel. Anyway, try without vsync first.

Works fine here in ce-mode, even in fullscreen.

[SailorSat]

Hi Tony.

It also happens in Fullscreen without VSync.
VSync it set to application controlled on all systems.
I can even capture it to AVI.

I've completely deleted my configurations directory just to get sure it's nothing set wrong anywhere.

Steps I take to reproduce...
1. Start WinUAE.
2. Select Amiga 500, 1.3 Rom, OCS, 512+512...
3. Set Slider to the most left position.
4. Select my Disk Image.
5. Switch to Host/Display. (which is default 800x600 16Bit)
6. Select "Native Mode" -> "Fullscreen". (Not VSync)
7. Just let it run.

The game is constantly "jumping" and sometimes "flashing" forward ingame.

For some reason I haven't figures out yet, it SOMETIMES (like 1 of 5 tries) works fine.

If there wasn't the fact I can reproduce it on at least 3 systems here... Oh well.

Actually I'm pretty clueless whats happening. And WHY it is happening.

[SailorSat]

I've just uploaded an AVI (XVID Codec) showing whats happening over here.

You can clearly see the background "jumpin" forward, flashing sometimes, and getting slower when enemies enter the screen.

[Galahad/FLT]

Which AGA fixed version?

[SailorSat]

Hybris (1988)(Discovery Software)[cr QTX][f AGA Orb][t +2 DLT]

Though I have been told there are others around. (WHDLoad)