O Up to 34% performance increase in Prototype with antialiasing enabled O Up to 10% performance increase in Far Cry 2 (DX9 version) with antialiasing enabled O Up to 14% performance increase in Fallout 3 (indoor scenes) with antialiasing enabled O Up to 50% performance increase in Call of Juarez: Blood in Bound with SLI enabled O Up to 8% performance increase in Batman: Arkham Asylum with GPU PhysX enabled O Up to 12% performance increase in ARMA 2 version 190.62 drivers (results will vary depending on your GPU, system configuration, and game settings): The following are examples of improvements measured with version 191.07 drivers vs.
The suite provides driver and system software support for all current NVIDIA GeForce graphics products, GeForce 6-series and above. What this means is you _MUST_ keep your in-game fps below 60 at all times in order for the game to work properly.A little over two weeks after releasing its previous 190.62 WHQL version of its GeForce drivers, NVIDIA released its brand new GeForce 191.07 driver suite, signed by Windows Hardware Quality Labs (WHQL). FPS below 60 doesn't seem to alter building speed. Anything above 60 fps will increase building times and potentially speed up enemy spawns (unconfirmed, but suspected). So it seems like that old bug is fixed.Ĭonclusion: The game's in-game timing system for building speed and probably other things (enemy spawns, quest triggers), is roughly tied to in-game fps. I also tested things both at 1x and 5x speed and there was no difference in how many in-game days it took. If you don't do this your building times will be up to 4 times longer than originally intended.ġ20hz refresh rate, vsync off both in-game and in control panel, 240-270+ in-game fps, took 8 days to build a guard tower and upgrade it one time.ġ20hz refresh rate, vsync on in-game, capped 120 fps, took 4.5 daysġ20hz refresh rate, vsync off in-game, vsync forced 'on' in control panel, capped 120 fps, took 4.5 daysįorced 60hz refresh rate, vsync on in-game, capped 60 fps, took 2.5 days to build a guard tower and upgrade it one time.įorced 60hz refresh rate, vsync off in-game, vsync forced 'on' in control panel, capped 60 fps, took 2.5 daysġ20hz refresh rate, vsync off in-game, vsync forced on but set to 'Adaptive (half refresh rate)' in control panel, capped 60 fps, took 2.5 daysįorced 60hz refresh rate, vsync off in-game, vsync forced on but set to 'Adaptive (half refresh rate)' in control panel, capped 30 fps, took 2.5 days ++I would also recommend using something like fraps that shows your in-game fps to make sure you're staying under 60 fps at all times. If you're using a 120hz monitor, force vsync on for majesty2.exe (manege 3d settings -> programs settings -> select majesty2.exe) in your GFX control panel BUT you MUST use adaptive at half refresh rate, so your monitor is still set to 120hz but your fps is capped at 60fps. If you're using a 120hz or 144hz monitor, set your monitor to 60hz globally (or you can have something like Nvidia control panel change it automatically whenever majesty2.exe is running) and then turn on the in-game vsync.
If you're using a 60hz monitor, be sure you have either vsync turned on in-game or vsync forced on in your graphics card's control panel. What you need to do to fix this is one of the following: I also suspect other in-game timings are tied to your FPS as well, such as enemy spawn timers as i also noticed i was getting about 2-3 times more enemy spawns than them too (but i didn't thoroughly test this though). See the bottom of this post to see how i tested this, but the short version is your building times can be 4 times longer than intended with uncapped fps. Turns out that the time it takes to build a building is roughly tied to your in-game fps. They were building 4-5 buildings before being attacked whereas i couldn't build a single building before i had waves of enemies in my base already. It seemed like my building times were at least double that of various youtube video guides.
0 kommentar(er)
