

As we've said before, hardcoded framerate caps are a relic of a bygone era and need to go away. The way I see it, if a game engine can handle 20-120 fps without problems, that same code can be adapted to handle 20-240 fps as well. Hopefully, the ultimate solution is to provide PC gamers with the ability to run with an unlocked framerate, at least up to a suitably high ceiling line 240fps, for those 240Hz display owners. It could be that Bethesda will lock out INI file edits, or put in a hard-coded FPS cap. however in places where your framerate is below 60FPS the game physics will slow down. Bethesda, speaking with Polygon, has confirmed it's aware of the issue but doesn't expect a fix until the game launches on November 14. Browse to your Fallout New Vegas installation directory. Dubbed "speed hacking," this is a bannable offense in most multiplayer games. I noticed framerates of nearly 200fps inside some buildings during the beta, and as with Fallout 4, that caused things to speed up (here's some evidence of that in video posted to Streamable). Bethesda will need to ensure everything works properly and that everyone runs the game calculations at the correct rate, as you can't have a multiplayer game where some people are able to move faster and break the physics.
