Physical Game Speed faster than normal?

[3 Ducks in a Trenchcoat]

Hello, just a real quick question and/or concern. I edited the fallout ini's command line that reads iPresentInterval and changed the value from a 1 to a 0. I understand this removes the v-sync built into the engine, but it seems like the game speed itself is running faster, such as animations, speech and combat itself. I guess this is the reason, as when I switched back everything was normal. Is there any way to uncap the framerate without causing the actual game speed clock to increase with it?

Thanks in advance.

Edit #1:
So while I didn't figure out a way to uncap the framerate without changing the game speed with it, changing iPresentInterval back actually did nothing. Turns out the speed issue was because I have my monitor set to 144hz, and when I reverted it back to 60hz everything was fine.
This engine is next-level stupid.

[sqμeaky]

I have my monitor on 144hz but I downloaded rivatuner to cap the fps to 60 (with ingame vsync off so i dont get the ♥♥♥♥ mouse delay). It's stupid but sadly there's no other way. Bethesda treats it's PC customers like 2nd class citizens

[TehSpoopyKitteh]

Originally posted by Yes Man:

Hello, just a real quick question and/or concern. I edited the fallout ini's command line that reads iPresentInterval and changed the value from a 1 to a 0. I understand this removes the v-sync built into the engine, but it seems like the game speed itself is running faster, such as animations, speech and combat itself. I guess this is the reason, as when I switched back everything was normal. Is there any way to uncap the framerate without causing the actual game speed clock to increase with it?

Thanks in advance.

Edit #1:
So while I didn't figure out a way to uncap the framerate without changing the game speed with it, changing iPresentInterval back actually did nothing. Turns out the speed issue was because I have my monitor set to 144hz, and when I reverted it back to 60hz everything was fine.
This engine is next-level stupid.

I typically try to put the value to -1

[3 Ducks in a Trenchcoat]

Originally posted by angry boi:

I have my monitor on 144hz but I downloaded rivatuner to cap the fps to 60 (with ingame vsync off so i dont get the ♥♥♥♥ mouse delay). It's stupid but sadly there's no other way. Bethesda treats it's PC customers like 2nd class citizens

there's mouse delay?

[3 Ducks in a Trenchcoat]

Originally posted by The Spoopy Kitteh:

Originally posted by Yes Man:

Hello, just a real quick question and/or concern. I edited the fallout ini's command line that reads iPresentInterval and changed the value from a 1 to a 0. I understand this removes the v-sync built into the engine, but it seems like the game speed itself is running faster, such as animations, speech and combat itself. I guess this is the reason, as when I switched back everything was normal. Is there any way to uncap the framerate without causing the actual game speed clock to increase with it?

Thanks in advance.

Edit #1:
So while I didn't figure out a way to uncap the framerate without changing the game speed with it, changing iPresentInterval back actually did nothing. Turns out the speed issue was because I have my monitor set to 144hz, and when I reverted it back to 60hz everything was fine.
This engine is next-level stupid.

I typically try to put the value to -1

what does the -1 do?

[TehSpoopyKitteh]

Originally posted by Yes Man:

Originally posted by The Spoopy Kitteh:

I typically try to put the value to -1

what does the -1 do?

It syncs the previous frame rather than the outgoing one. Used a lot back in teh DOS days with double buffering. It fixes the supposed 64Hz bug.

Originally posted by Yes Man:

Originally posted by angry boi:

I have my monitor on 144hz but I downloaded rivatuner to cap the fps to 60 (with ingame vsync off so i dont get the ♥♥♥♥ mouse delay). It's stupid but sadly there's no other way. Bethesda treats it's PC customers like 2nd class citizens

there's mouse delay?

Very slight. It can be fixed by easily by turning off Mouse Acceleration and smoothing. If you are a NVIDIA user, use NVIDIA control pannel to set the "maximum allowed prerendered frames" setting to 1 for the FO# profile.

[3 Ducks in a Trenchcoat]

Originally posted by The Spoopy Kitteh:

Originally posted by Yes Man:

what does the -1 do?

It syncs the previous frame rather than the outgoing one. Used a lot back in teh DOS days with double buffering. It fixes the supposed 64Hz bug.

Originally posted by Yes Man:

there's mouse delay?

Very slight. It can be fixed by easily by turning off Mouse Acceleration and smoothing. If you are a NVIDIA user, use NVIDIA control pannel to set the "maximum allowed prerendered frames" setting to 1 for the FO# profile.

ok so i'll probably do the -1 thing, and i am a nvidia user so i guess that makes it easier,
cheers mate

[TehSpoopyKitteh]

Originally posted by Yes Man:

Originally posted by The Spoopy Kitteh:

It syncs the previous frame rather than the outgoing one. Used a lot back in teh DOS days with double buffering. It fixes the supposed 64Hz bug.




Very slight. It can be fixed by easily by turning off Mouse Acceleration and smoothing. If you are a NVIDIA user, use NVIDIA control pannel to set the "maximum allowed prerendered frames" setting to 1 for the FO# profile.

ok so i'll probably do the -1 thing, and i am a nvidia user so i guess that makes it easier,
cheers mate

While yuou are at it...you can increase the number of exterior cell buffers...the default value is 36...I set mine to 81.

[sqμeaky]

Originally posted by The Spoopy Kitteh:

Originally posted by Yes Man:

what does the -1 do?

It syncs the previous frame rather than the outgoing one. Used a lot back in teh DOS days with double buffering. It fixes the supposed 64Hz bug.

Originally posted by Yes Man:

there's mouse delay?

Very slight. It can be fixed by easily by turning off Mouse Acceleration and smoothing. If you are a NVIDIA user, use NVIDIA control pannel to set the "maximum allowed prerendered frames" setting to 1 for the FO# profile.

This is just not true at all in my case. Anything with Vsync still enabled had a terrible (im talking like 100-200+ms) mouse delay.

[TehSpoopyKitteh]

Originally posted by sneaky boi:

Originally posted by The Spoopy Kitteh:

It syncs the previous frame rather than the outgoing one. Used a lot back in teh DOS days with double buffering. It fixes the supposed 64Hz bug.




Very slight. It can be fixed by easily by turning off Mouse Acceleration and smoothing. If you are a NVIDIA user, use NVIDIA control pannel to set the "maximum allowed prerendered frames" setting to 1 for the FO# profile.

This is just not true at all in my case. Anything with Vsync still enabled had a terrible (im talking like 100+ms) mouse delay.

Weird....Are we tlaking cursor movement? Shooting? Both? There are several ways around this actually. Keep in mind I am using a Toshib 40L52000U TV as my monitor...with game mode on (which runs it at 60Hz).

For cursur movement you might have to mess with the FALLOUT.ini file. Adding the following lines under [Control] or altering them migh help a bit.

fForegroundMouseAccelBase=0
fForegroundMouseAccelTop=0
fForegroundMouseBase=0
fForegroundMouseMult=0

Also, make sure your monitor is running at 60Hz. The game caps the frame rate at 60FPS

[3 Ducks in a Trenchcoat]

Originally posted by The Spoopy Kitteh:

Originally posted by sneaky boi:

This is just not true at all in my case. Anything with Vsync still enabled had a terrible (im talking like 100+ms) mouse delay.

Weird....Are we tlaking cursor movement? Shooting? Both? There are several ways around this actually. Keep in mind I am using a Toshib 40L52000U TV as my monitor...with game mode on (which runs it at 60Hz).

For cursur movement you might have to mess with the FALLOUT.ini file. Adding the following lines under [Control] or altering them migh help a bit.

fForegroundMouseAccelBase=0
fForegroundMouseAccelTop=0
fForegroundMouseBase=0
fForegroundMouseMult=0

Also, make sure your monitor is running at 60Hz. The game caps the frame rate at 60FPS

is it worth doing those command lines for me as well?

[TehSpoopyKitteh]

Originally posted by Yes Man:

Originally posted by The Spoopy Kitteh:

Weird....Are we tlaking cursor movement? Shooting? Both? There are several ways around this actually. Keep in mind I am using a Toshib 40L52000U TV as my monitor...with game mode on (which runs it at 60Hz).

For cursur movement you might have to mess with the FALLOUT.ini file. Adding the following lines under [Control] or altering them migh help a bit.

fForegroundMouseAccelBase=0
fForegroundMouseAccelTop=0
fForegroundMouseBase=0
fForegroundMouseMult=0

Also, make sure your monitor is running at 60Hz. The game caps the frame rate at 60FPS

is it worth doing those command lines for me as well?

Couldn't hurt. The place to put those code lines are right below [Controls] in the FALLOUT.ini file. The file can be found in "Documents\my games\Fallout3"

:-)