

If you tried to go even higher than 60, cars would stop braking at all, effectively making the game unplayable. Fixed car brakingĪnother drawback of using the 60 FPS patches was that cars would brake a lot slower. Please make sure to report the problem on the Steam forums, ModDB comments, or via GitHub issues so that we can work on a fix. If you encounter such an issue, disable the FPS unlock in the config file (lanvp.ini in the game folder), restart the game, pass the current section, re-enable the FPS unlock in the config and restart the game again. However, it's better than anything else available currently )ĭisclaimer: Some missions or activities may still be unbeatable when playing with a high framerate.

Of course, the fix is not perfect, since some things in the game logic are still tied to the framerate. It doesn't matter if you are running 60 FPS or 160, the game will always run at the correct speed. This means that you can now run the game at any framerate. Then, in order to make the game run at the correct speed, I hooked a small function which updates the game speed according to the current frame time. I ended up patching out the frame synchronization logic, which had the effect of totally uncapping the framerate. or even better, removing it all together. Therefore, I looked for a new method of increasing the frame cap. And since the game can often drop below 60 FPS even on a fairly good setup, you would get occasional slowdowns.
#L.a. noire iso Pc#
This means if you set your frame cap to 60, but your PC could only produce 30 FPS, the game would run at half the right speed. Since the value used to cap the framerate was also used for game logic, in case your PC could not produce a constant 60 FPS, the game simulation would run slower. However, this method had a big disadvantage. Usually, raising "the cap" would be done by increasing a value in the game's memory, that would have the effect of increasing the frame limit. Not only that, playing with these fixes would sometimes make the game run slow if you happened to drop a few frames below 60 FPS. The biggest drawback of all available fixes for me was the fact that they would only raise "the FPS cap" to 60 frames per second. Features Total FPS Uncap (60+ FPS) & Variable Framerate Later in development it became clear to me that what I had made was worth publishing for others to use. With this fact in mind, I started to search for fixes, only to learn that most of them sucked.Īfter determining that all the available fixes were either unintuitive to use for the average user or lacking in features, I sought out to make my own patch, mainly looking to tackle the 30 FPS cap and the aspect ratio limitations. This project is not affiliated with Take-Two or Rockstar GamesĪ while ago I wanted to replay L.A Noire on my new setup, only to find out that the game was locked to 30 FPS and didn't support my monitor's aspect ratio.
