Turbo Mode in WinUAE 1.6.0 with Fullscreen+Vsync 100Hz not working?

[rsn8887]

I think I found a couple bugs in WinUAE 1.6.0 regarding Fullcsreen+Vsync 100 Hz, Turbo mode, and the "remove interlace artifacts" option:

All tested in "A500 quickstart most compatible" + 800*600 100 Hz PAL + Fullscreen+Vsync + On screen LEDs on

1. Turbo mode (END+PAUSE) is not functioning when cycle exact is enabled in Fullscreen+Vsync 100 Hz PAL. Turbo ON or OFF makes no difference in this case.
2. Turbo mode seems to be capped at a maximum 100 fps when remove interlace artifacts is NOT checked and an interlace image is being displayed (regardless of cycle exact).
3. Display and animation of interlace displays in Fullscreen+Vsync 100 Hz PAL is very slow in general if remove interlace artifacts is NOT checked

EDIT: I should add that it looks like none of these problems are there in windowed mode. It is definitely a fullscreen specific issue.

[Toni Wilen]

I don't have any 100Hz capable displays anymore, can't test

(perhaps when real 100Hz LCDs that accept 100Hz signal via DIV/HDMI/whatever are available..)

[rsn8887]

Thanks for the interest in this, Toni.

I just checked this on a different computer again: At least problem no. 1 seems to be reproducible in any "Fullscreen+Vsync" mode, not just 100 Hz!

To reproduce it:
- select A500 quickstart, most compatible, eject the floppies. Select a "Fullscreen + Vsync" display mode (I just tested with 800*600, 70 Hz) and turn the on screen LEDs on.
- Go into turbo mode by pressing END+PAUSE
- The fps will stay at whatever refresh rate you selected for your display mode, for me it was 70 in these tests.

Compare this with selecting non-vsync fullscreen or windowed display modes. There the fps will be around 400+ for me once I turn on Turbo.

As soon as I turn cycle exact off, turbo mode works again as it should with Vsync on.

I suspect the other problems that appear when "remove interlace artifacts" is not checked also happen at other refresh rates, not just 100 Hz, but I will have to test that at home.

EDIT: I just tested it again, and it looks like turbo mode won't work even in non vsync fullscreen modes if cycle exact is on. It is always capped at the refresh rate of the display resolution? Only turning off cycle exact makes it work. Window mode works fine, though, as I said earlier.

[Toni Wilen]

Originally Posted by rsn8887

EDIT: I just tested it again, and it looks like turbo mode won't work even in non vsync fullscreen modes if cycle exact is on. It is always capped at the refresh rate of the display resolution? Only turning off cycle exact makes it work. Window mode works fine, though, as I said earlier.

Confirmed. In fullscreen modes "do not wait for vblank" flag wasn't set in turbo modes. In non-ce modes it still worked (more or less) because turbo also sets update only every 10th display frame