MathemagicianJJ

MathemagicianJJ

Joined Member # 7020532
0 Posts 0 Replies 28 Reputation

I'm using CPU-Z and RealTempGT. When I start the multiplicity processes listed above, it happens. When I stop them, it stops. Regardless of anything else. This happens on two different PCs (identical hardware) whenever they are the server, even if there are no connected clients. I've tried disabling audio sharing and no impact. Same for holding the mouse still, reducing report rate on both mouse and kbd to 125Hz, and closing the Corsair and Logitech apps.

18 Replies 11,428 Views

It happens only on the server side. Both client and server are i7 9700K (which does not have hyperthreading while your i9-9900k does... might be a factor) with Logitech mouse and Corsair keyboard. G Hub and iCUE are both installed and I tried turning both down to minimum polling with no effect. I also tried closing both of those completely with no effect. <span style="font-size: 16px; background-color:

18 Replies 11,428 Views

That is a good suggestion if you are using Process Lasso anyway. But, to pay for a second app to wrangle a poorly behaving paid (and relatively expensive) app into "mostly" behaving is rather unsatisfying. Much better to simply request a refund and pay once for something that works and behaves well.

18 Replies 11,428 Views

You can mitigate this issue by setting the affinity of "MP2Control.exe" and "Multipl2.exe" to a single CPU core. In this way, only that core is stuck at maximum speed. The rest will behave as normal. This is a real pain to do every time Multiplicity launches. Anybody know a way to make this setting permanent?

18 Replies 11,428 Views