Slown down UAE!! Please!!!!

[pulsecode]

Hmm...probably a seriously dumb question but..here goes!

I`m running WinUAE 0.8.21 R4 on a P4 1.9 Ghz machine.
I`ve looked everywhere, several times in the menus of UAE to find some kind of speed restrictor...but..well,maybe i`m blind, but i cant find anything!
I could REALLY do with slowing it down to a respectable speed, cause right now its running at arround 150+ fps...which is mighty scary!!

Any ideas?

[Paul]

Try turning Vsync off.

[pulsecode]

It`s allready off..! :^\

It`s quite bizzare, the older UAE i was running ran at a fairly normal speed, but for some reason the new one flys!!

[Ian]

Turn vsync on then;)

If your GFX card can handle 100 hz (or 50 hz) modes.

In 100hz mode there are a few games/demos that run twice normal speed, but everything else will be fine;)

And you think ~150 frames per second is bad, I was trying to play Alien Breed - Tower Assualt yesterday at ~500 Frames per second, not easy;)

[pulsecode]

HAHA yeah, i know what you mean!
I said 150 as an average, but yeah, it does climb to ridculous speeds on certain games!

Ok, i`ll give it a try!
Tho it IS quite funny seeing Turrican scamper about benny hill style! ;)

[§ane]

500 FPS ?! Begesus !!

I do think this is a bug.

if((!currprefs.gfx_vsync || !currprefs.gfx_afullscreen))
do_limit_FPS_stuff();

Now in English:

VSync and Fullscreen = (0 || 0 = 0) = No FPS limit!
VSync Disabled and Fullscreen = (1 || 0 = 1) = Fixed FPS
VSync and NOT Fullscreen = (0 || 1 = 1) = Fixed FPS
VSync Disabled and NOT Fullscreen = (1 || 1 = 1) = Fixed FPS

Why is the if() statement even necessary? Although maybe this was intended, perhaps required for custom refresh rate to work.. but doesn't.., Toni?

[Toni Wilen]

Why is the if() statement even necessary?

Because in vsync-mode DX_Flip() handles fps limiting, non-vsync or windowed modes use framewait() for fps limiting.

pulsecode: does it run ultra-fast in windowed modes too?

[§ane]

Originally posted by Toni Wilen
Because in vsync-mode DX_Flip() handles fps limiting, non-vsync or windowed modes use framewait() for fps limiting. As I thought, but it doesn't appear to be working too well for everyone.

EDIT: Before you ask, yes my drivers vsync is enabled through RivaTuner, plus I know it's functioning properly because I don't get any image tearing with it turned on.

[§ane]

I think a combination of both framewait() and the DirectDraw wait is in order.

I just did a little test removing the if() statement, oddly enough the FPS will now match the refresh setting, 50hz and you get 50 FPS, 72hz and 72 FPS.. etc, this is in full screen mode obviously.

[pulsecode]

Yeah, same crazy speeds whilst windowed! i mainly run games windowed, cause i like to be able to quickly switch between the games and Internet Explorer / ICQ, so infact i run it windowed nearly allways, i only use full screen for D-Paint ;^)

[Drake1009]

How about the slider under CPU options? The adjust speed I've noticed can speed things up unnescesarily much, which is why I usually never select this option because I can't find the right speed.

[pulsecode]

It doesnt seem to affect it too much, it DOES slow down a little, but nowhere near as much as required!!

Something strange...i set it to "aprox a500 speed" and it ittered, as if it was trying its hardest to go 1000Mph, but was being held back....after about 1 min of this jittering it hung! :^\
Odd indeed..i`ve never ever EVER had UAE hang like that before!

[Toni Wilen]

I think a combination of both framewait() and the DirectDraw wait is in order.

nope, DirectDraw wait is needed because recent WinUAEs use triple-buffering (removes tearing) in fullscreen modes. Older versions used framewait()-style waiting in all modes.

§ane: either your display driver is buggy or it does not have enough display RAM for triple buffering and WinUAE falls back to doublebuffering mode that seems to be buggy.. Do you see any interesting messages in log?

pulsecode: unfortunately I don't have any solutions, but at least your problem can't be caused by vsync code because vsync code is not used in windowed mode.

[Ian]

Pulsecode: I think you must be using the Chipset slider, try using Fastest possible, but Maintain Chipset timing instead on the CPU settings tab.

[7-Zark-7]

Gee,I dunno you coders's & power user's amaze me!
Most people with machines like PII,III,Celeron's etc. have enough fun trying to get WinUAE running fast enough to be functional in modes like 800x600!!
Talk about making the "plebs" feel inferior!! :D ;)

[§ane]

Originally posted by Toni Wilen
§ane: either your display driver is buggy or it does not have enough display RAM for triple buffering and WinUAE falls back to doublebuffering mode that seems to be buggy.. Do you see any interesting messages in log?Latest 29.42 WHQL certified detonators, 32MB video memory and 256 of 1536MB system memory available via the AGP bus, though I suppose that is only for textures.

Nothing in the log that would indicate a problem.

Okay, I know what is wrong now, I had the custom refresh rate set to 50Hz, expecting to get 50FPS, but my display driver nor monitor driver for that matter does not support this value, so it defaults to 60Hz, same as if I were using NTSC mode, the game appears substantially faster than normal.

[pulsecode]

Yeah Toni, i`m sure its not a bug of any sort, i think i`m just being stupid and missing something somewhere, i`ve played about with all sorts but to no avail...

i`m gonna start from scratch and go through every option to make a new config and see what happens...

Oh yeah..Ian, nah its nothing to do with that, i tried messing with that, and it DID slow it down a little, but not enough. ANd as i said before, if i checked aprox A500 speed it went a bit scatty!