Feels like mouse filtering or something weird was turned on. My movements don't feel that reactive. I have filtering turned off. Tried raw mouse input as well with no results.
Yeah... the weird movement I get from the mouse messed up my aim. I thought it were to fast moving in a way so have been slowing down the sensitivity in-game, but it's to slow when I play aliens kind of, haha. So need to change every time I change team.
For the mouse, head into the options, turn on mouse acceleration and turn off raw input
Apply and close, then reopen the options, turn off mouse acceleration, turn on raw input.
That fixed the mouse issue for me.
Might as well give your basic system information with posts confirming that you are experiencing the problem. So they know what setups are having the issue.
why do they feel like the need to revamp movement everytime they update...everytime i get use to it there is another update... seems like a waste of resources
Lower your settings, or go lower than before. The mouse input jerkiness/lag was connected to performance for me. If you're not getting more than 70-80 FPS it'll probably not be good. Hoping for a quick fix.
I've noticed enabling triple buffered vertical sync smooth out the framerate and the mouse lag. With it disabled it feels like there's latency on mouse input (even with the raw input fix) and when moving fast it also have this stuttering feeling even the framerate is high.
I hope they get the performance back they had in 251.
Everyone playing has input lag/delay right now as far as I know (including every person I talked to on my friends list), anyone who doesn't notice it simply isn't aware/caring of input
I'm sure they're working hard on a fix, I personally couldn't play with it because it felt like I was running v-sync (which you should never use in a competitive fps game.. ever)
edit: the current mouse delay will probably feel worse with lower frames, but I tested in a closed room @ 200 fps and the delay is still present so there's an actual issue with input, framerate low or high doesn't matter (even though it will feel worse if your framerate is dropping below your refresh rate)
I agree, with high FPS it still doesn't feel like before, but it's much better than with low FPS.
Fundamentally, there's some problem with input (linux... somebody said they changed the input method for compatibility reasons), so hopefully it'll be fixed sometime. Kind of unfortunate when they're asking for money tbh. -_-
Everyone playing has input lag/delay right now as far as I know (including every person I talked to on my friends list), anyone who doesn't notice it simply isn't aware/caring of input
I'm sure they're working hard on a fix, I personally couldn't play with it because it felt like I was running v-sync (which you should never use in a competitive fps game.. ever)
edit: the current mouse delay will probably feel worse with lower frames, but I tested in a closed room @ 200 fps and the delay is still present so there's an actual issue with input, framerate low or high doesn't matter (even though it will feel worse if your framerate is dropping below your refresh rate)
I...really am not feeling the input lag, at all. Didn't even have to do the settings toggle fix.
EDIT: Also the only fps loss I got was swapping to DX11 (but it feels smoother so w/e), although sometimes when I first get into a map it's UNBELIEVABLY choppy for about 20s before it comes good.
SamusDroidColoradoJoin Date: 2013-05-13Member: 185219Members, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Gold, Subnautica Playtester, NS2 Community Developer, Pistachionauts
Problem has been found (hopefully this is the only cause). Fullscreen is NOT true fullscreen. It is fullscreen windowed or very close to.
I have a fully backed up 249, I threw Biodome on there, and well...
Problem has been found (hopefully this is the only cause). Fullscreen is NOT true fullscreen. It is fullscreen windowed or very close to.
I have a fully backed up 249, I threw Biodome on there, and well...
I knew it!!, check your alt tab Working like window screen and before there was memory flush when you go to windows and console flood "Error: Couldn't initialize the render device."
Problem has been found (hopefully this is the only cause). Fullscreen is NOT true fullscreen. It is fullscreen windowed or very close to.
Hmm yeah I remember I had this same kind of input lag when I tried windowed fullscreen a couple of patches ago. Hopefully they can fix this soon, as currently the game is unplayable.
Problem has been found (hopefully this is the only cause). Fullscreen is NOT true fullscreen. It is fullscreen windowed or very close to.
I could never run NS2 in a window/windowed fullscreen in any build. It had to be in exclusive fullscreen mode or it would stutter and exhibit input lag. Now it's like that either way, so this makes some sense.
Alt + enter (makes game fullscreen) in menu Works for me, no input lag
Nope doesn't work here. Maybe you're just imagining it?
I can't understand how such a serious bug got through the playtesting group..
Just because something 'gets through' doesn't mean we missed it. We in fact found it in 252 and it's been difficult to track down for the Devs (especially with Max away at the moment). A number of things were tried to improve the situation and for a few people on certain configurations it's better. Others not. Sometimes fixes are elusive or hard to fix and take time to fix properly.
The input lag and microstuttering is apparently caused - at least in part - by using aero in windows - windows doesn't allow the game to automatically use the resources properly, even if it's full screen. The workaround is to find the executable and "disable desktop composition" in it's file properties here;
Comments
On a diff topic, my HD sounds like a Tibetan Throat Singer when loading and while playing ns2. Fine with every other game. Starting to worry me.
dam damm DAAAAMMMMM
Apply and close, then reopen the options, turn off mouse acceleration, turn on raw input.
That fixed the mouse issue for me.
I hope they get the performance back they had in 251.
I'm sure they're working hard on a fix, I personally couldn't play with it because it felt like I was running v-sync (which you should never use in a competitive fps game.. ever)
edit: the current mouse delay will probably feel worse with lower frames, but I tested in a closed room @ 200 fps and the delay is still present so there's an actual issue with input, framerate low or high doesn't matter (even though it will feel worse if your framerate is dropping below your refresh rate)
Fundamentally, there's some problem with input (linux... somebody said they changed the input method for compatibility reasons), so hopefully it'll be fixed sometime. Kind of unfortunate when they're asking for money tbh. -_-
I...really am not feeling the input lag, at all. Didn't even have to do the settings toggle fix.
EDIT: Also the only fps loss I got was swapping to DX11 (but it feels smoother so w/e), although sometimes when I first get into a map it's UNBELIEVABLY choppy for about 20s before it comes good.
I have a fully backed up 249, I threw Biodome on there, and well...
249 fullscreen http://imgur.com/a/lwckS 249 fullscreen windowed http://imgur.com/a/lyRbv 254 fullscreen http://imgur.com/a/DogFK
Look at 249 fullscreen windowed and 254 fullscreen. Almost identical.
Hmm yeah I remember I had this same kind of input lag when I tried windowed fullscreen a couple of patches ago. Hopefully they can fix this soon, as currently the game is unplayable.
I could never run NS2 in a window/windowed fullscreen in any build. It had to be in exclusive fullscreen mode or it would stutter and exhibit input lag. Now it's like that either way, so this makes some sense.
Nope doesn't work here. Maybe you're just imagining it?
I can't understand how such a serious bug got through the playtesting group..
OK, it doesn`t work for me too ( Just smaller lag, but still too big.
Now that I can actually play the game, I'm starting to realize how shitty move it was to nerf the AV..
Just because something 'gets through' doesn't mean we missed it. We in fact found it in 252 and it's been difficult to track down for the Devs (especially with Max away at the moment). A number of things were tried to improve the situation and for a few people on certain configurations it's better. Others not. Sometimes fixes are elusive or hard to fix and take time to fix properly.
C:\Program Files (x86)\Steam\steamapps\common\natural selection 2\NS2.exe
Thanks to Samusdroid (Orphan Black) for picking up on this ! :-)