Natural Selection 2

Natural Selection 2

View Stats:
boolean 8 Jan, 2019 @ 12:14pm
FPS in game won't go above 60 [NOT IN MENUS, IN GAME]
I KNOW ABOUT THE MENU FPS CAP, THIS IS NOT THE CAUSE. I'M MEASURING FPS IN GAME WITH R_STATS.

Latest Manjaro Linux distrib. GTX 970 on proprietary driver 415.25. AMD Ryzen 1700 processor.

Three monitor setup: Main monitor an LG 144hz monitor connected via displayport and set to 144hz in X server settings. Second monitor an older ASUS 1600x900 60hz panel. Third is an AV reciever for sound output set to 1080p 60hz in x server settings.

I run NS2 on the LG panel with a maxfps command setting my maxfps to 289. There is clearly a software limit on my FPS as it never deviates above 61 or below 59, staying exactly at 59.99 to 60.01 95% of the time. Why?

I've tried unplugging EVERY OTHER DISPLAY ON THE SYSTEM to isolate the problem to only the 144hz panel and it still REFUSES to output above 60fps. WHY?
< >
Showing 1-3 of 3 comments
Ghoul  [developer] 8 Jan, 2019 @ 12:23pm 
Hi,

make sure vsync is disabled in your gpu driver settings. A number of ppl did run into the same issue with linux. See https://www.reddit.com/r/ns2/comments/a1eznv/linux_tip_for_users_with_nvidia_capped_at_60fps/ for details.
boolean 8 Jan, 2019 @ 12:38pm 
Originally posted by Ghoul:
Hi,

make sure vsync is disabled in your gpu driver settings. A number of ppl did run into the same issue with linux. See https://www.reddit.com/r/ns2/comments/a1eznv/linux_tip_for_users_with_nvidia_capped_at_60fps/ for details.

My bad not posting this in tech support to begin with.

Vsync was already off, but disabling Sync to VBlank fixed it. You're a legend, responding in 5 minutes with the solution.

Don't know why my googles didn't find that reddit thread, only a red herring about HDMI monitors potentially limiting max fps.

Just saw your post in a thread on UWE forums from around 4 years ago too, I'll see if I can't get some backtraces of my crashes. They're MUCH less common since I came back to this game a couple weeks ago, so that's nice, but they still happen. Pretty sporadic, but hopefully I'll get one while I'm mindful enough to have GDB attached
Last edited by boolean; 8 Jan, 2019 @ 12:39pm
Ghoul  [developer] 8 Jan, 2019 @ 1:20pm 
Originally posted by rest in pasta roni:
Originally posted by Ghoul:
Hi,

make sure vsync is disabled in your gpu driver settings. A number of ppl did run into the same issue with linux. See https://www.reddit.com/r/ns2/comments/a1eznv/linux_tip_for_users_with_nvidia_capped_at_60fps/ for details.

My bad not posting this in tech support to begin with.

Vsync was already off, but disabling Sync to VBlank fixed it. You're a legend, responding in 5 minutes with the solution.

Don't know why my googles didn't find that reddit thread, only a red herring about HDMI monitors potentially limiting max fps.

Just saw your post in a thread on UWE forums from around 4 years ago too, I'll see if I can't get some backtraces of my crashes. They're MUCH less common since I came back to this game a couple weeks ago, so that's nice, but they still happen. Pretty sporadic, but hopefully I'll get one while I'm mindful enough to have GDB attached

Great to hear you could solve the issue. Actually we added a proper crash reporter to the game some time ago. So you don't even need to attach gdb yourself anymore. If you want me to look into a perticular crash of yours make sure to copy the dump id from the crash reporter interface.
Last edited by Ghoul; 8 Jan, 2019 @ 1:21pm
< >
Showing 1-3 of 3 comments
Per page: 1530 50