Centroid Community CNC Support Forum

Chaz wrote: ↑Mon Aug 11, 2025 1:49 pm Out of interest, what was 'fixed'?

Using the original MPGClient.exe file resulted the PC's CPU being bogged down. Win Task Manager was showing 90%-100% total load, and MPGClient.exe was using 60%-75% continuously while CNC12 was running (but idle) with no other programs open.

Mouse, touchscreen, and keyboard were a bit laggy. Opening a window (such as selecting a file to run) resulted in a noticeable delay in mouse responsiveness when trying to select a file or move/resize a window.

Sorry, I understand it was improved. What was actually done to improve it is my question.

I used to get odd issues with the MPG years ago, not something I see often anymore, just keen to understand.

To my understanding the MpgClient.exe is checking every so many milliseconds while idle for inputs, like turning the handwheel etc.
By default it's checking I believe every millisecond.
These other options Liviu posted change that to check for inputs every 50, 100, or 200 milliseconds while idle.
So going from every millisecond to every 200 milliseconds is of course a massive difference in performance.

CentroidFrog wrote: ↑Mon Aug 11, 2025 3:45 pm To my understanding the MpgClient.exe is checking every so many milliseconds for inputs, like turning the handwheel etc.
By default it's checking I believe every millisecond.
These other options Liviu posted change that to check for inputs every 50, 100, or 200 milliseconds.
So going from every millisecond to every 200 milliseconds is of course a massive difference in performance.

Yeah, but why is every ms using only 6% CPU with USB 3.1 on WIN 10 and 90% with USB3.2 on WIN 11?

Sounds like more latency for less performance...

Even worse like the short tuner joke "serial performance almost achieved"

Uwe

for 5.4 we are going to parameterize the refresh rate so you can change the MPG client refresh rate via a CNC12 parameter (rather than copying files)
then we are going to look further into Windows 11 USB code for a better solution as the CPU usage on some of these win11 machines should not be this high.