Feedback about driver v3.0 beta 2

[rudders]

I've pretty much stopped using the displays on my Hub as the CPU impact was typically 50% on a MBP i7 (Previous model). Anyone else finding CPU consumption an issue.

Driving two DisplayPort Dell Monitors @ 1920 * 1080 and MBP @ Retina.

[Carlo]

Originally Posted by rudders

I've pretty much stopped using the displays on my Hub as the CPU impact was typically 50% on a MBP i7 (Previous model). Anyone else finding CPU consumption an issue.

Driving two DisplayPort Dell Monitors @ 1920 * 1080 and MBP @ Retina.

Hi yes we discovered this issue too. It's worse the more monitors you have connected.

We definitely want to fix this for the final 3.0.
I'm trying now a build that resolves this issue, seems to be working fine so far.

Best regards,
Carlo

[Carlo]

Originally Posted by Alyson

I recently got a docking station to use with my MacBook operating Sierra. I was using the driver 2.6 and it was working fine but with a little keyboard lag. One day it completely stopped working (nothing would show up on monitors when plugged in), so I upgraded to the new beta even though there was the warning against performance issues. I didn't seem to have a choice.

Now I am semi-operating but with some severe issues that make it so that most of the time I would rather just work from my laptop. Any advice on either of my major issues listed below? At this point I think I need to switch to another brand as this is majorly cutting into my work productivity...

1. SEVERE keyboard and mouse lag (wireless Logitech). Mouse lag seems to slightly improve if laptop is open instead of closed, but keyboard connection is very intermittent and sometimes will work fine then sometimes will not work for up to 3 minutes then come back fine.

2. 2nd monitor plugged into HDMI port is completely not available as a display (tried gather windows, detect displays, etc). This monitor was working fine before the beta update, and works fine if I plug into the DVI port with an adapter.

Alyson I'd suggest to write to our support including the logs: http://support.displaylink.com/knowl...to-displaylink

Please also try to install 2.6 again to see if it behaves better, from what you wrote it looks some kind of hardware issue and the logs may be able to confirm it.

Regards,
Carlo