Disabled “software mouse” cursor for Windows 11 insider?
-
Is there any more information on the nature of this change and whatever the problem was?
I ask because with build 26058, released last week, there is a major issue with the mouse cursor, so bad that I had to revert the build.
The problem was that artifacts of the mouse cursor were left everywhere you moved the mouse cursor on the screen. There seemed to be heavy CPU use, too. It made doing almost anything very difficult.
Since it was still not normal in safe mode, it never occurred to me that anything I was running could be involved, though in safe mode the artifact effect did change somewhat. Better but still not usable.
If f.lux was somehow involved, it might explain why so few people reported the problem.
-
@rseiler sure - we have a "software mouse" option in f.lux (that defaults to off, btw).
To implement this, we were using a "mouse trails" setting that has worked until now to force software drawing of the mouse. This forces the mouse to draw as a layered window rather than using a hardware overlay, which avoids bugs with GPUs that don't color correct the cursor. On this update, apparently the setting we use makes it draw 'infinite' mouse trails rather than 'none'...which should not be possible as it really has no purpose!
4.133 and later basically force this setting off to prevent it, but we hope it will get a MSFT fix in the future.
-
Had this issue also. Didn't even cross my mind that f.lux could be behind it, but now that you mention it, it's worth looking into.
