You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just locked up during a Cut Scene and it's because I play at 60 fps. I thought since this addon already does all the work to track when you're in/out of a cut scene already, it might be easy to implement an option to limit the fps to 30 while in a cut scene while reverting back to an fps divisor of 0 or 1 afterwards.
I realize that I might have locked up during the scene for another reason and I don't really have concrete evidence about this specific instance. I do think it's a common issue though and mentioned in some of the mission guides. I've experienced the same lockup in the past before during cut scenes and always just assumed it was the fps issue.
The text was updated successfully, but these errors were encountered:
Yeah lockups during cutscenes can happen, though only on specific ones. Very likely due to something assuming a certain frame rate and the positions or something overshoot and miss a marker or something like that.
As you say, since this addon now knows when you're in a cutscene we could auto adjust the framerate. I'll take a look over the holidays and see if I can sneak it in early Jan!
I just locked up during a Cut Scene and it's because I play at 60 fps. I thought since this addon already does all the work to track when you're in/out of a cut scene already, it might be easy to implement an option to limit the fps to 30 while in a cut scene while reverting back to an fps divisor of 0 or 1 afterwards.
I realize that I might have locked up during the scene for another reason and I don't really have concrete evidence about this specific instance. I do think it's a common issue though and mentioned in some of the mission guides. I've experienced the same lockup in the past before during cut scenes and always just assumed it was the fps issue.
The text was updated successfully, but these errors were encountered: