Displaylink driver 8.0 M.0 Mouse & Keyboard Lag

[AlbanRampon]

Hello Bert,
Could you tell me how you gauge the lag?
Is it whilst playing video when you notice an issue with lipsync or is it just the mouse pointer, or something else?
Kind regards,
Alban

Originally Posted by Bert Jansen

Just upgraded to M2 with W10 Anniversary version. I do see a noticeable difference in screen lag: I've 2 screens connected using displaylink, on the 1920x1200 screen the lag is not there, on the 3440x1440 screen there's still a noticeable lag, although it's workable. This lag was not present with the 7.9 and previous windows 10 version, so there still seem to be a need for performance improvements with the anniversary update.

If it helps I can provide debug information, just let me know.

[Bert Jansen]

Originally Posted by AlbanRampon

Hello Bert,
Could you tell me how you gauge the lag?
Is it whilst playing video when you notice an issue with lipsync or is it just the mouse pointer, or something else?
Kind regards,
Alban

It's the mouse pointer and general screen refresh...it's a bit slower then it used to be...still workable though. Actually today performance seems to be better, so let me try a few more days first, maybe there's other factors in play.

[mag]

Tried 8.0 M2 drivers today, still lagging, support tool output attached (EDIT: later removed).

I reproduced it with all external USB devices disconnected, only external display (in the Replace display mode - Show only on 2) and Ethernet cable connected to the dock.

Restarted Windows, logged in, moved around with the cursor (using the builtin touchpad) - the occasional lag was there (cursor stuttering on the display). Similar lag also visible when typing on the keyboard.

Back to 7.9 M7 with no lag.

[AlbanRampon]

Hello mag,
Then similar reasons to everyone else. Don't use replace mode until Microsoft sends the Windows Update fixing the OS. You need at least one monitor on the primary graphics card to be switched on for Windows not to put it to sleep and DisplayLink to have to wait for it to wake up to get pixels.
I'll post here when I know it's on its way.
Kind regards,
Alban

Originally Posted by mag

Tried 8.0 M2 drivers today, still lagging, support tool output attached.

I reproduced it with all external USB devices disconnected, only external display (in the Replace display mode - Show only on 2) and Ethernet cable connected to the dock.

Restarted Windows, logged in, moved around with the cursor (using the builtin touchpad) - the occasional lag was there (cursor stuttering on the display). Similar lag also visible when typing on the keyboard.

Back to 7.9 M7 and no lag.

[mag]

Do You know whether the fix is already in the works/testing at least (so there's a good chance it won't take several months for it to be released)?

[AlbanRampon]

@Mag,
The fix is done and verified fixed in Redstone 2. A few big companies have asked for a backport as I flagged earlier in the thread.
In the meantime, activate all monitors.
If you keep 7.9 M7 and get new Intel/nVidia/AMD/Exotic graphics drivers with WDDM 2.1, then you may not be able to use your computer anymore. Up to you, of course.

@Bert,
Thanks for the details. There is something in the backlog for the mouse pointer scheduled for 8.1 later this year.
That's only a first step to keep improving the new driver architecture.

Kind regards,
Alban

[DougG]

I have activated all monitors (laptop now open (previously closed), and two external monitors connected) and my mouse and keyboard lag seems to have disappeared. Just confirming the workaround.

Originally Posted by AlbanRampon

@Mag,
The fix is done and verified fixed in Redstone 2. A few big companies have asked for a backport as I flagged earlier in the thread.
In the meantime, activate all monitors.
If you keep 7.9 M7 and get new Intel/nVidia/AMD/Exotic graphics drivers with WDDM 2.1, then you may not be able to use your computer anymore. Up to you, of course.

@Bert,
Thanks for the details. There is something in the backlog for the mouse pointer scheduled for 8.1 later this year.
That's only a first step to keep improving the new driver architecture.

Kind regards,
Alban