DisplayLink Forum

DisplayLink Forum (https://displaylink.org/forum/index.php)
-   Windows Software (https://displaylink.org/forum/forumdisplay.php?f=28)
-   -   No Mouse cursor with 8.1 (and workaround) (https://displaylink.org/forum/showthread.php?t=64975)

Marc H 12-04-2016 10:38 AM

No Mouse cursor with 8.1 (and workaround)
 
Hello,

I am facing the issue, that there is no visible mouse pointer at all (I had extra big mouse pointer "inverted" as my initial setting) on the DisplayLink display.

I have Windows 10 Pro 64-Bit on a Dell D830 (8GB, Core2Duo T9300) with extra USB 3.0 ports in the ExpressCard slot, where the DisplayLink is connected to.

I tried all available mouse-pointers, but the cursor remained blank.

The only way I could get the mouse-pointer to show was to switch on the "mouse trail" in the windows settings (with the shortest possible mouse trail setting available). Then also all the available Windows mouse pointers all work.

Maybe this is some problem with the initial different settings (extra big, inverted), that I had?

Speed of the Mouse pointer with 8.1 Alpha is almost back to pre Anniversary Update speed :-), probably still a little bit slower.

Marc H 12-08-2016 08:36 PM

Updated to Alpha 8.1 M0
 
Update worked fine - but I still see the mouse only with activated trail.
Speed (for my surely outdated config with Core2Duo only) is still more laggy than with the 7.x drivers before the Anniversary Update, but at least somehow useable now.

Tue-Tue 12-22-2016 11:35 AM

No Mouse cursor with 8.1 M0 Driver
 
As others users reported with 8.1 Alpha version of the driver http://www.displaylink.org/forum/showthread.php?t=64975 I have no mouse pointer after installing the new driver.
As they said, the only way to show the mouse-pointer is to switch on the "mouse trail" in the windows settings.

Two months waiting for the update that solves the mouse lag and it is unusable :(

AlbanRampon 01-12-2017 11:15 AM

Hello,

I missed your message, I am sorry.
Would you please be able to provide the log files as described in my signature (3rd link) and post the ZIP file from the Customer Support Tool?

In order to progress, we need to setup a reproduction in house.
Could you try to add the following registry key, if you know how to do this?
I would like to gauge the impact.

Code:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\DisplayLink\Core
Value: LowLatencyMouseCursor
Data: false
Data type: REG_SZ

Kind regards,
Alban

Tue-Tue 01-13-2017 08:54 AM

It works. Mouse is still laggy but adding this registry key solves the cursor visibility problem.

Thanks a lot, Alban

Quote:

Originally Posted by AlbanRampon (Post 82433)
Hello,
Could you try to add the following registry key, if you know how to do this?
I would like to gauge the impact.

Code:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\DisplayLink\Core
Value: LowLatencyMouseCursor
Data: false
Data type: REG_SZ

Kind regards,
Alban


AlbanRampon 01-13-2017 09:18 AM

Thank you for testing this.
This key simply disabled the work done to change the way the mouse cursor was handled.

I am very sorry this was not developed properly. We did test it internally before we released the change, and I don't yet know why this doesn't work for some machines when we did not have the missing cursor on any internal machine we tried on.

Would you please be able to generate ZIP file of your logs with our Customer Support Tool as described in the last link in my forum post signature?
We need to reproduce the issue to understand what is going wrong and selecting a machin as close to yours as possible will be key.

Kind regards,
Alban

Tue-Tue 01-13-2017 01:00 PM

I've sent you a PM

Quote:

Originally Posted by AlbanRampon (Post 82442)
Thank you for testing this.
Would you please be able to generate ZIP file of your logs with our Customer Support Tool as described in the last link in my forum post signature?
We need to reproduce the issue to understand what is going wrong and selecting a machin as close to yours as possible will be key.

Kind regards,
Alban


AlbanRampon 01-13-2017 04:21 PM

Tue-Tue,

Thank you for the logs. It has helped us select the machine to setup the reproduction.
Once I have an update from the engineering team, I will share it here.

Kind regards,
Alban

AlbanRampon 02-02-2017 09:57 AM

Hello,

Root cause has been found.
Some graphics cards put the wrong depth (they set it to 0) on the surface.
Instead of simply using the depth value given, we will gather it from somewhere else if we're told it's 0.
We're implementing the change and will have to test it.

Kind regards,
Alban

AlbanRampon 03-01-2017 11:41 AM

Hello,

The fix for that is now available from 8.2 Beta onwards.
http://www.displaylink.org/forum/showthread.php?t=65140

Kind regards,
Alban


All times are GMT. The time now is 12:35 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.