Game becomes too fast during AAF scenes

[Vel W]

Howdy, 

 

So, I just got a new computer which runs many games at 120fps with a 240Hz display. While all the mods work (including AAF), I notice that animations play too fast (about 1.5~2 times faster). 

 

After some research, I have found this article. Essentially, if for some reason the fps goes above 60, weird things happen. The game runs too fast, and everything runs too fast.

Because the game speed is completely fine outside AAF animations, I wonder if AAF has something that unlocks framerates and creates this bug.

 

Your thoughts? 

[dagobaking]

Not sure if it's related. But, you might try modifying the animation_timescale setting in AAF_settings.ini

[Vel W]

17 hours ago, dagobaking said:

Not sure if it's related. But, you might try modifying the animation_timescale setting in AAF_settings.ini

@dagobaking Thank you for the quick response. Using in-game FPS counter, I tracked the issue down to the 240Hz display refresh rate. When not playing AAF, the game's fps caps at exactly 61, while with any AAF animation playing and when starting AAF up by pressing [Home], the fps fluctuates between 120~135. This fluctuation then caused everything in the game world to act weird, as the game engine uses fps cap to count time. I assume this might also be what AAF and F4SE have to work with. It is possible that something in the scripts removed the FPS cap.

 

Changing the display refresh rate from 240 to 60 Hz resolved this issue.

Is there another solution?? Is there something in AAF setting that can be adjusted to maintain the 60 FPS cap, like everything else in the game??

[dagobaking]

6 hours ago, Vel W said:

@dagobaking Thank you for the quick response. Using in-game FPS counter, I tracked the issue down to the 240Hz display refresh rate. When not playing AAF, the game's fps caps at exactly 61, while with any AAF animation playing and when starting AAF up by pressing [Home], the fps fluctuates between 120~135. This fluctuation then caused everything in the game world to act weird, as the game engine uses fps cap to count time. I assume this might also be what AAF and F4SE have to work with. It is possible that something in the scripts removed the FPS cap.

 

Changing the display refresh rate from 240 to 60 Hz resolved this issue.

Is there another solution?? Is there something in AAF setting that can be adjusted to maintain the 60 FPS cap, like everything else in the game??

I can't think of anything that AAF does that would affect this other than maybe the timescale setting (which defaults to no effect anyway).

 

AAF may be a red herring here.

[Vel W]

On 10/27/2020 at 12:04 AM, dagobaking said:

I can't think of anything that AAF does that would affect this other than maybe the timescale setting (which defaults to no effect anyway).

 

AAF may be a red herring here.

Late response but yes you're right, AAF is a red herring here.

 

The cause of this issue turns out to be ENB series' key bindings in the enblocal.ini file

In short, ENB binds a feature to unlock FPS limit to key 36 which according to O'Reilly's doc is the Home key ---- the same key that initiates the AAF interface.

That is why whenever AAF is called, the FPS goes wonky on machines with display refresh rates above 60Hz.

 

Editing the enblocal file and changing ENB Local's key 36 to key 145 (Scroll Lock) resolved this issue for me. Sharing it here in case anyone else is curious.

[dagobaking]

6 hours ago, Vel W said:

Late response but yes you're right, AAF is a red herring here.

 

The cause of this issue turns out to be ENB series' key bindings in the enblocal.ini file

In short, ENB binds a feature to unlock FPS limit to key 36 which according to O'Reilly's doc is the Home key ---- the same key that initiates the AAF interface.

That is why whenever AAF is called, the FPS goes wonky on machines with display refresh rates above 60Hz.

 

Editing the enblocal file and changing ENB Local's key 36 to key 145 (Scroll Lock) resolved this issue for me. Sharing it here in case anyone else is curious.

Thank you for following up to clarify. It will be good to note this for future troubleshooting.