-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
[REQUEST] Will donate money for this feature. The Saboteur Fusion Fix, uncap FPS. #1651
Comments
Try this build, but don't forget to disable vsync. |
Is there somewhere specific I'm to disable Vsync? I did it in the config files of the game, in "%USERPROFILE%\Documents\My Games\The Saboteur™\SaveGames" I set vcync to 0. FPS is still capped to 59, but the fusion fix is definitely working since I can see the FOV adjustment. I'm using the Steam build of the game |
Might be that it needs windowed mode disabled as well. |
Vsync for me is disabled, I also did a fresh install on steam. I know it's disabled since I get screen tearing. What does your config files look like? I have my game config looking like this, changing the refresh rate to higher than 60 causes the game to render at 640x480. DisplayProfile 0 and my Fusion Fix config looking like this [MAIN] |
Redownload the archive above and try again. |
I downloaded the archive and extracted the TheSaboteur.FusionFix.asi into the scripts folder. Using the public Fusion Fix for the Dinput.dll file |
Launching in 640x480 is fixed there, that's why I said redownload. It wasn't fixed the first time I posted that message. |
So I set in the launcher 144hz, and the 640x480 bug is fixed, but it's still capped to 59 FPS. I'm not sure what specifically I'm doing wrong. I downloaded the zip file you linked above and I'm using that ASI script with the dinput.dll from the public release. |
Seems to be working on the GOG version for some reason? Very strange |
Ah, it's probably because the code is executed too late on steam version. Give me a moment to work around this. |
Does this make any difference? |
If not, then try this |
Seems to make my game not want to boot up at all, but I'll try a fresh steam install again. |
Nevermind, second zip file is working on Steam |
Working meaning fps is not capped at 60 as well? If so, that's the best I can do at the moment. Maybe will look into how to uncap fps with vsync later. |
Yeah, FPS isn't capped with your fix. You can use Nvidia control panel to cap it now. Surprisingly minimal issues running uncapped, some slight collision bugs possibly, will need to do more testing. But at least at minimum we can have proper frame times running at 60 FPS if we choose to. 120 FPS seems to work well for minimising collision issues. Physics issues aren't your fault though, just how the game engine is. Will send a donation your way. For future reference, this is how I have my config, and the windowed option also needs to be disabled in the fusion fix config in the scripts folder. Use something like borderless gaming to make the game full screen in borderless mode. DisplayProfile 0 |
Are you planning on updating fusion fix to include the updates you just did? You could also edit the PCGW page to say it can run above 60 FPS. |
I updated dev build just now, can update a release on GitHub as well if you want. |
I think it would be good to make the fix as public as possible, anyone looking to play above 60 FPS should be able to find it easily |
Updated. |
Hello,
As the title says, I'm willing to donate some money for this feature. I believe the Saboteur can run at a higher FPS than 60, as you can run it through an emulator (Xenia/RPSC3) and get a high FPS (has graphical issues, but that's beside the point).
I've posted on forums and have got no responses, and I was told that you might be the person to come up with a solution, since you have knowledge of DirectX API.
I think the game is running at a forced cap of 59.94 FPS, it can go slightly above 60 if you use the speed hack in CWcheat and halve the speed. I've tried finding memory addresses and all I've found are addresses that calculate the FPS.
The text was updated successfully, but these errors were encountered: