Short description of the bug:
When running the game on Windows 8, limiting the framerate at 100 FPS drops the actual framerate around 90 FPS and the game microstutters considerably. Other FPS limits are also working weirdly, see screenshots below.
Sample screenshots:
1. No FPS limiter enabled smooth gameplay, no microstuttering
2. Limiter set to 100 FPS results in 90.9 FPS
3. Limiter set to 83 FPS results in 83 FPS
4. Limiter set to 50 FPS results in 47.6 FPS
5. Limiter set to 30 FPS results in 29.4 FPS
Also, the game runs in full screen at around 170 FPS, but when I run it windowed, I'm hitting the hard coded fps limit at 300+ FPS, not sure if this is related to the bug or not. Tried running SLI enabled and disabled, no change. Also tried forcing maximum power setting instead of adaptive in drivers, no change.
System & software:
Rampage IV Extreme
i7-3930K
16GB RAM
2x GTX 680, reference models in SLI, 306.97 WHQL Driver
Windows 8 Pro 64-bit, legit
LFS - Tested both 0.6B and the 0.6B10 test patch, problem occurs on both releases
If this is just a driver problem, I'll update the title.
When running the game on Windows 8, limiting the framerate at 100 FPS drops the actual framerate around 90 FPS and the game microstutters considerably. Other FPS limits are also working weirdly, see screenshots below.
Sample screenshots:
1. No FPS limiter enabled smooth gameplay, no microstuttering
2. Limiter set to 100 FPS results in 90.9 FPS
3. Limiter set to 83 FPS results in 83 FPS
4. Limiter set to 50 FPS results in 47.6 FPS
5. Limiter set to 30 FPS results in 29.4 FPS
Also, the game runs in full screen at around 170 FPS, but when I run it windowed, I'm hitting the hard coded fps limit at 300+ FPS, not sure if this is related to the bug or not. Tried running SLI enabled and disabled, no change. Also tried forcing maximum power setting instead of adaptive in drivers, no change.
System & software:
Rampage IV Extreme
i7-3930K
16GB RAM
2x GTX 680, reference models in SLI, 306.97 WHQL Driver
Windows 8 Pro 64-bit, legit
LFS - Tested both 0.6B and the 0.6B10 test patch, problem occurs on both releases
If this is just a driver problem, I'll update the title.