Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Improve Loading Times Further #302

Closed
RecklessGlue540 opened this issue Dec 9, 2023 · 1 comment
Closed

[Feature Request] Improve Loading Times Further #302

RecklessGlue540 opened this issue Dec 9, 2023 · 1 comment

Comments

@RecklessGlue540
Copy link

Is your feature request related to a problem? Please describe.

In-game loading times seem to depend on the frame rate. Because of this, capping the game at 60fps or less will make the game stay more in load screen compared to an uncapped framerate (FusionFix's FPS Limiter always uncaps the framerate during load screens to combat this, however, using external FPS Limiters on top, such as RivaTuner will have the behavior described.)

Describe the solution you'd like

Make the in-game loading times frame rate agnostic, without uncapping the frame rate on loading screens.

Describe alternatives you've considered

Not much else...
Fixing this issue will make the existing implementation a bit better:

  • Animated UI elements such as the Rockstar logos, loading bars, police cars and helis on the minimap will run faster at higher framerates than 30;

Additional context

Good examples are when loading the game's Benchmark Tool and Starting A New Game:

Starting A New Game:

30 FPS:

30FPS.mp4

60 FPS:

60FPS.mp4

Uncapped:

Uncapped.mp4

Benchmark Tool:
30 FPS: Infinite Load (Probably Bugged)
60 FPS: Infinite Load (Probably Bugged)
Uncapped: Same as above Uncapped. But still takes some time to load compared to it.

You can see a difference of 20sec between all of them...

@RecklessGlue540
Copy link
Author

Could be closed as unplanned rather, but it's actually a vanilla game issue and I'm wondering if it has something to do with any .sco script related to the starting a new game scenario. As we know, they changed between versions and this behavior carried on from 1080.
I may test scripts from multiple versions to see anyways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants