Mini-hitching/Stuttering
NikolaiLev
Join Date: 2012-11-01 Member: 165658Members
Join Date: 2012-11-01 Member: 165658Members
When I look around I get this hitching that pauses my turning. It's seemingly not the same as an FPS drop, though it might be a drop related to looking around (for some reason). Unfortunately, I do not know if this started happening because of Build 240, or because I installed Windows 7.
Specs:
Intel Core 2 Duo E8500 3.16GHz
Radeon HD4890 1gb
4gb DDR2 800
Windows 7 SP1
I've always had mediocre frames running on all low, but this never happened. With this bug, the game is virtually unplayable as it becomes excessively difficult to track where I'm actually aiming. I've attempted turning on texture streaming, messing with raw input, but nothing seems to really affect this (the gaps between hitches seems worse the lower my frames are, though).
Thanks in advance.
Edit: Bewilderingly, turning up the in-game mouse sensitivity (while lowering my mouse's DPI to compensate) mitigates this problem. However, it still exists. It seems 240 or Win7 has overall reduced my performance. Hopefully there's a way I can eliminate this problem, or at least help others with the same one.
Specs:
Intel Core 2 Duo E8500 3.16GHz
Radeon HD4890 1gb
4gb DDR2 800
Windows 7 SP1
I've always had mediocre frames running on all low, but this never happened. With this bug, the game is virtually unplayable as it becomes excessively difficult to track where I'm actually aiming. I've attempted turning on texture streaming, messing with raw input, but nothing seems to really affect this (the gaps between hitches seems worse the lower my frames are, though).
Thanks in advance.
Edit: Bewilderingly, turning up the in-game mouse sensitivity (while lowering my mouse's DPI to compensate) mitigates this problem. However, it still exists. It seems 240 or Win7 has overall reduced my performance. Hopefully there's a way I can eliminate this problem, or at least help others with the same one.
Comments
If it's the latter, check r_stats and net_graph to see what's happening, waiting for render thread? Waiting for GPU? Perhaps choke?
Anything weird going on in the console? (~)
Give us some stats and we'll look in to it.
I've checked r_stats and while waiting for GPU never occurs, waiting for render thread flickers between 0 and some two digit number. It seems to be correlated with the hitching. Given this occurs in explore mode, net_graph doesn't seem to apply here.
Nothing in the console.
Hope this is enough!
Also be sure to disable any Vsync
Still occurring?
All tested. No effect.
Logitech G700. However, I doubt this is the cause of the issue, as I was using the G700 before I installed Win7/played B240. It's also worth re-emphasizing that the turning hitches coincide with spikes in "waiting for render thread."
I always knew my CPU was not up to par for the game, but it ran playable without this issue before the aforementioned occurrences.
* wireless mouse. batteries ok? tried for testing with a wired mouse?
* tried without the mouse macros?
* how big are the render thread spikes?
* tried closing more and more programs before you run ns? (as a side note, you would be amazed how many stuff out there is insanely badly coded. browser plugins, printer programs, some mouse control programs.
It can be a combination of factors.
I'll see if I can link you to an earlier post of mine explaining how. (http://forums.unknownworlds.com/discussion/comment/2074238/#Comment_2074238)
Profile would show the culprit in this case I believe
Also check your video settings and look for "max buffered frames" or "pre buffered frames" (not sure what it is for Amd cards) and please report what you find
Edit: you switched to win 7 recently? What are your os mouse settings? Try polling rates as mentioned in here as well
Edit2: Have you confirmed your in game gfx settings are the exact same? Do you have texture streaming enabled?
Puzzlingly, this helped. It heavily mitigated the issue, though it's still slightly there, and I still need to test what happens in a real match (this was in Explore Mode).
In the interest of actually getting to the bottom of this issue rather than bandaging it, I'll answer most of the questions here. AMD does not have any options related to max buffered frames or so. I could download ATI Tray Tools for this sake but those have always given me problems in the past. Graphics settings were all the same, especially considering I've tested different settings.
This is profile at 125 polling rate.
http://steamcommunity.com/sharedfiles/filedetails/?id=131137373
This is profile at 1000 polling rate, moving to another part of the map to get lower frames (which makes the issue more apparent. And yes, people joined my Explore Mode game and killed me; I still need to suggest they be excluded from quick join).
http://steamcommunity.com/sharedfiles/filedetails/?id=131137411
I hope a fix can be found for this issue, as it seems to be confined only to NS2 and no other game (I've never encountered this issue before). Good luck!
Edit: I forgot to mention that I've always had my mouse on 1000Hz polling rate, so there's still something odd about Win7/B240. Further, I've played in a real match and it's quite playable. Unfortunately, my performance in general has taken a hit as well, but that's not quite related.
maybe your cpu goes into some kind of energy saving mode until you move your mouse, which can produce some kind of stuttering too. try to deactivate "intel speed step" in bios and/or use the "high performance mode" of energy saving options in windows (i dont know the correct translation in english).
The keyword is by spec. Depending on motherboard & drivers many usb can deliver more power then spec indicates, and some produce less.
I would start by checking your USB ports & drivers