High mouse polling rate causes stutter

[SharpeXB]

Setting a higher polling rate for the mouse causes stuttering. Logs attached, one with and one without. The effect seems to occur randomly.

DxDiag.txt dcs no stutter.log dcs stutter.log

[Furiz]

18 hours ago, SharpeXB said:

The effect seems to occur randomly.

Yeah I can confirm this, yesterday it was working fine with pooling rate 1000 and day before that I had to lower it to 250, cause 500 was stuttering as well.

at the moment of posting this, 1000 pooling rate was the cause of stutter, when I lowered to 500 it was ok.

Mouse stutter pooling rate 1000.trk

[silverdevil]

@SharpeXB  and  @Furiz when you notice the stuttering, and go into mouse polling settings, are they set correctly? meaning, do the settings seem to revert to a different rate than what you set? i wonder if the settings are sticking?

interesting suggestion here is to change to a different mouse to  test.

 

Edited October 1 by silverdevil

[SharpeXB]

25 minutes ago, silverdevil said:

@SharpeXB  and  @Furiz when you notice the stuttering, and go into mouse polling settings, are they set correctly? meaning, do the settings seem to revert to a different rate than what you set? i wonder if the settings are sticking?

interesting suggestion here is to change to a different mouse to  test.

 

I kept the rate at 1000 in both those logs. The stuttering doesn’t always happen. Those two logs were made with the same mission and settings. After I restarted DCS the stuttering didn’t happen. 

Edited October 1 by SharpeXB

[Furiz]

6 hours ago, silverdevil said:

@SharpeXB  and  @Furiz when you notice the stuttering, and go into mouse polling settings, are they set correctly? meaning, do the settings seem to revert to a different rate than what you set? i wonder if the settings are sticking?

Setting didn't change, but as SharpeXB said sometimes it is ok and sometimes its not good and we have to change settings, DCS restart helps sometimes, and in some cases I even restarted my PC and it didn't help, I had to change pooling rate to fix the stutter.

Its variable, I wish it isn't it would be easier problem to solve.

[sleighzy]

Couple of things from your log file:

You have core parking enabled. Use software like ParkControl https://bitsum.com/parkcontrol/ (or there is instructions here for doing via the registry: https://www.dannymoran.com/windows-cpu-core-parking)

Secondly, the stutter log file contains the following which is spammed through the startup and not consistent with the other log, don't know if they were from different missions, or something else going on:

2025-09-30 22:12:54.792 INFO    LUA-MISSIONGENERATOR (Main): loadMissionNodes: "missionNodes"
2025-09-30 22:12:54.793 INFO    LUA-MISSIONGENERATOR (Main): loadMissionNodes: 1 : "1-SW-Gali-1"
2025-09-30 22:12:54.793 INFO    LUA-MISSIONGENERATOR (Main): 		redTemplates: "Red Offensive - Large 1"
2025-09-30 22:12:54.793 INFO    LUA-MISSIONGENERATOR (Main): 		redTemplates: "Red Defensive - Large 1"
2025-09-30 22:12:54.793 INFO    LUA-MISSIONGENERATOR (Main): 		redTemplates: "Red Offensive - Large 2"

Your log file shows two Razer Wolverine V2 Pro 2.4 being connected. Is that correct, 2 of them? EDIT: I'm assuming so as I notice now the UUIDs for them are one digit different.

I'd recommend trying without all those peripherals connected, ie. the controllers and the Razer Tartarus V2 gamepad. Just strip it right back to basics. If you also have the world's most basic mouse try that as well. It may be that there is a bunch of I/O stuff happening. Might not be, but can at least rule it all out. Test over time to see if it does make a change then slowly reintroduce them again to see what happens.

This is the full list of stuff connected, thought maybe a mouse would have shown up unless I overlooked it.

025-09-30 22:17:29.596 INFO    INPUT (Main): created [Keyboard]
2025-09-30 22:17:29.597 INFO    INPUT (Main): created [CH PRO THROTTLE USB ] with full id [CH PRO THROTTLE USB  {2796EE60-F354-11ef-8001-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.629 INFO    INPUT (Main): created [Razer Wolverine V2 Pro 2.4] with full id [Razer Wolverine V2 Pro 2.4 {B4B0A250-F43A-11ef-8001-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.630 INFO    INPUT (Main): created [Razer Wolverine V2 Pro 2.4] with full id [Razer Wolverine V2 Pro 2.4 {B4B0A250-F43A-11ef-8002-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.630 INFO    INPUT (Main): created [Joystick (Razer Tartarus V2)] with full id [Joystick (Razer Tartarus V2) {7ABE3B90-F352-11ef-800B-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.633 INFO    INPUT (Main): created [CH FIGHTERSTICK USB ] with full id [CH FIGHTERSTICK USB  {2796EE60-F354-11ef-8002-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.633 INFO    INPUT (Main): created [T-Rudder] with full id [T-Rudder {AB553AC0-859B-11f0-8001-444553540000}], ForceFeedBack: no
2025-09-30 22:17:29.648 INFO    INPUT (Main): created [TrackIR]

 

Edited October 2 by sleighzy

[SharpeXB]

4 hours ago, sleighzy said:

You have core parking enabled.

I’d rather not mess with that. It’s easier to just Tab out to GHUB and change the polling rate whenever this happens. I run other things besides DCS and changing things like that every time I run it is too much work. 

5 hours ago, sleighzy said:

Secondly, the stutter log file contains the following which is spammed through the startup and not consistent with the other log, don't know if they were from different missions, or something else going on:

The mission was the F-4 Marianas Cold Start both times.

5 hours ago, sleighzy said:

Your log file shows two Razer Wolverine V2 Pro 2.4 being connected. Is that correct, 2 of them? EDIT: I'm assuming so as I notice now the UUIDs for them are one digit different.

I only have one. The other ID might be from a previous Windows install. That device was turned off during this session. 

5 hours ago, sleighzy said:

I'd recommend trying without all those peripherals connected, ie. the controllers and the Razer Tartarus V2 gamepad.

The Wolverine was powered off and disconnecting devices continually is a pain. Again it’s easier to just Tab out and change the polling. 
 

[Furiz]

6 hours ago, sleighzy said:

You have core parking enabled. Use software like ParkControl https://bitsum.com/parkcontrol/ (or there is instructions here for doing via the registry: https://www.dannymoran.com/windows-cpu-core-parking)

We shouldn't be using software for some game to run, game should run on non modded windows.

[Mr_sukebe]

Agreed that the issue exists.

I did however get the impression that it was an issue with Windows, not just DCS.

I've certainly included a comment to review that in my recommendation on VR performance:

 

[SharpeXB]

11 minutes ago, Furiz said:

We shouldn't be using software for some game to run, game should run on non modded windows.

Right, players shouldn’t have to mess with Windows to run the game. I don’t think core parking matters one way or the other though. 

[silverdevil]

6 minutes ago, Furiz said:

We shouldn't be using software for some game to run, game should run on non modded windows.

i think everyone agrees. yet here we are helping people with stuttering. which, btw, does not happen to everyone. do you or @SharpeXB have TACVIEW running? i have seen other posts that this caused stuttering. many moons ago, i had similar problems and discovered having my windows desktop backgrounds rotating every 5 minutes or so. stopping that stopped my stuttering.

when users call for help in forums, i believe it is best to follow the advice of those that take time away from enjoying the sim; if only just to test. empirical data will help if we keep track of changes and the effect of those changes on the system.

[Furiz]

6 minutes ago, silverdevil said:

i think everyone agrees. yet here we are helping people with stuttering. which, btw, does not happen to everyone. do you or @SharpeXB have TACVIEW running? i have seen other posts that this caused stuttering. many moons ago, i had similar problems and discovered having my windows desktop backgrounds rotating every 5 minutes or so. stopping that stopped my stuttering.

when users call for help in forums, i believe it is best to follow the advice of those that take time away from enjoying the sim; if only just to test. empirical data will help if we keep track of changes and the effect of those changes on the system.

I know you guys are trying to help, and thanks for that. I also help here from time to time.

But I think the suggested app is not a valid solution.

 

I don't use any mods, or tacview or any programs that alter or mine data from DCS,

only program outside DCS that both me and SharpeXB are using is Logitech G HUB, maybe that is related to this problem?

[silverdevil]

12 minutes ago, Furiz said:

Logitech G HUB

i was not trying to be crass. so i apologize if i came off that way. 

i use G HUB too. i have 11th gen i9 which does not have P/E cores. only 8 cores which are like P cores. lots of users have 14th gen (which i believe @SharpeXB has). there are many of these users with various problems. keep in mind that it is intel. they have been perceived for many years as managerial oafs. i bet they are cutting corners with chip production.

back to G HUB. i have two mice. one is for DCS. it is on a desk mounted tray in the center of my desk and chair position. i use my left hand to operate in DCS. both are set as below. note that the DPI speeds matter too. DCS is not an FPS so who cares. 

Edited October 2 by silverdevil

[Hiob]

38 minutes ago, Furiz said:

I know you guys are trying to help, and thanks for that. I also help here from time to time.

But I think the suggested app is not a valid solution.

 

I don't use any mods, or tacview or any programs that alter or mine data from DCS,

only program outside DCS that both me and SharpeXB are using is Logitech G HUB, maybe that is related to this problem?

In my mind, G-HUB is an absolute crap piece of software that shouldn't be running if possible. Other's milage may vary.

Only thing it is good for, is to keep the rainbow puke on my mouse at bay, but for that I'm not willing to compromise my DCS experience.

Edited October 2 by Hiob

[Furiz]

30 minutes ago, Hiob said:

In my mind, G-HUB is an absolute crap piece of software that shouldn't be running if possible. Other's milage may vary.

Only thing it is good for, is to keep the rainbow puke on my mouse at bay, but for that I'm not willing to compromise my DCS experience.

It is not giving me trouble with any other game, software or whatever other than DCS, but we don't know for sure its G HUB. 

[SharpeXB]

3 hours ago, silverdevil said:

do you or @SharpeXB have TACVIEW running?

No

2 hours ago, Hiob said:

In my mind, G-HUB is an absolute crap piece of software that shouldn't be running if possible

The problem can still occur with GUHB off, but I have it on in order to change the polling if I need to. 

[silverdevil]

2 hours ago, Furiz said:

It is not giving me trouble with any other game, software or whatever other than DCS, but we don't know for sure its G HUB. 

agreed. with the data we have available, there are users with other brands of mice, that do not use G HUB, that have the stuttering problem. and in our case, G HUB cannot be singled out as the culprit. as far as my system is concerned, i do not have stuttering, and i use G HUB.

check out this link if you have not already.

https://www.wikihow.com/Change-Mouse-Polling-Rate

[SharpeXB]

3 hours ago, silverdevil said:

note that the DPI speeds matter too. DCS is not an FPS so who cares.

I just find changing the rate to feel clumsy especially if it has to be 125. I would change it back to 1000 after exiting DCS

[sleighzy]

@Furiz Can you also attach your DCS log file after replicating this issue.

[MoleUK]

Just to add, some users report that it happens inconsistently on DCS start. ie starting the game up 5 times in a row will result in mouse polling above 125hz causing problems 3 or 4 times out of 5.

Also, reducing the polling rate to 125hz does not entirely "fix" the problem. You will still see the frametime react to mouse movement at 125hz, just not in a way that impacts overall visuals at that point.

[fagulha]

41 minutes ago, MoleUK said:

Just to add, some users report that it happens inconsistently on DCS start. ie starting the game up 5 times in a row will result in mouse polling above 125hz causing problems 3 or 4 times out of 5.

Also, reducing the polling rate to 125hz does not entirely "fix" the problem. You will still see the frametime react to mouse movement at 125hz, just not in a way that impacts overall visuals at that point.

Same here. Sometimes DCS starts normally but sometimes in need to restart it 2 times before the issue goes away (i´m using mouse polling of 500hz).

[SharpeXB]

I would say this happens to me perhaps 1 out of 5 times. Not very often. 

[Marco Schaap]

I'd like to report that with my both Corsair mouses with 1000hz polling rate I don't have this problem. Might narrow down the problem.

[Flia]

I have never ever has this problem in DCS with any wirless Logitech mouse. G 305 and now G 502X. Both without this issue.

Edited 9 hours ago by Flia

[silverdevil]

I also use two mice on the system. I did change polling rate for both to 500. I never change it. Though previous poster mentioned wireless. My two are wired. I wonder if that affects the problem. I am old school and have never used wireless in gaming.