![]() |
|
|
|
|
#1 |
|
Member
Join Date: Oct 2014
Posts: 43
|
Ditto of above post. Performance is much better with this version but I am also seeing the visual glitches a lot more. I am running 10.12.2 beta (16C60b) on a mac Mini 2012 core i7/16gb ram. I have DL3.0 beta installed from "DisplayLink Installer 77739.dmg" and my device is a "Plugable USB3-HDMI-DVI" that uses the DL3500 chipset I believe.
I am attaching a couple of pictures I took with my phone to show the artifacting. Hoping that these visual glitches can be improved... ![]()
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Dec 2016
Posts: 1
|
New user to the forum just to add feedback on the Beta drivers. Mouse latency is much MUCH better. Thank you for addressing this.
I'm experiencing the exact same artifacting as the above 2 posters so I wanted to make sure to add that feedback for your team. I can deal with the artifacts as a trade off for the mouse latency being better. It's a huge help in my workflow that's for sure! |
|
|
|
|
#3 |
|
Member
Join Date: Jun 2015
Posts: 32
|
I've just updated to 10.12.2 - seems great so far. Mission Control is finally working properly! This together with the new beta driver is delivering a vastly superior experience compared to the older builds.
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Dec 2016
Posts: 7
|
I updated to Mac Sierra 10.12.2 and I still have this annoying issue:
![]() If I directly connect the Display to my Mac, it works fine. I use HDMI. |
|
|
|
|
#5 |
|
Junior Member
Join Date: May 2014
Posts: 13
|
Like Vasile, I am also getting weird artifacts left behind by moving the cursor when using Chrome on my DisplayLink connected screen after updating to macOS 10.12.2.
Attempting to capture a screen shot of the affected Chrome window results in the window getting wiped completely for a few moments. Scrolling seems to clear all artifacts until it begins to happen again a few seconds later. |
|
|
|
|
#6 |
|
Junior Member
Join Date: Mar 2015
Posts: 8
|
3.0 beta made my display link screen completely unusable.
2.6 was still working more or less fine after the upgrade to macOS 10.12.2. after installing 3.0 i got massive repaint problems on the display link screen. white windows and desktop background, cursor artefacts, windows in the front erasing windows in the background and more. after going back to 2.6 the problems remain and the displaylink screen is unusable. |
|
|
|
|
#7 |
|
Junior Member
Join Date: Dec 2016
Posts: 1
|
Display Link driver v3.0 beta 1 stability compared to v2.6 is much improved running on macOS Sierra. On v2.6, my extended displays would become unresponsive and only a reboot would restore functionality. Something as simple as moving windows around the displays would crash the driver and require a reboot. This hasn't happened nearly as often with v3.0 beta 1.
Thanks for the continued development!
|
|
|
|
|
#8 |
|
Junior Member
Join Date: Oct 2016
Posts: 4
|
Used the beta drivers for the first one today on OSX 10.12.2 beta 5 and they worked quite well. Granted I really only use that monitor for iTerm to ssh to Linux servers, but I did drag winded around in it and it worked well. I didn't notice any issues with the Windows being black when dragging them to the DisplayLink monitor. So for me, it's been good overall.
|
|
|
![]() |
|
|