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 9 hours ago 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 9 hours ago 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 1 hour ago by sleighzy