Feedback about driver v3.0 beta 2

[luckman212]

Originally Posted by Carlo

We found what the trigger is [...] To see all these issues you have to disable "Displays have separate Spaces" in the Mission Control system preference.

That is great to hear!

We'll open a bug with Apple immediately. As for the other defects already fixed in 10.12.1 and 10.12.2, the priority of this issue can be raised by opening more bugs with Apple at bugreporter.apple.com. We'd be grateful if you could open bugs there as well.

Would be happy to open a case, but could you guys post somewhere the details or wording that you'd like us to use, so we can be sure all of the cases are linked together properly to generate the higher priority?

you may want to enable separate spaces, currently the default setting in macOS. You won't be able to show windows across displays but there are quite a few advantages.

I haven't tried in a while but I remember not liking this setting when I first encountered it. What are some of those advantages?

[Carlo]

Originally Posted by luckman212

That is great to hear!

Would be happy to open a case, but could you guys post somewhere the details or wording that you'd like us to use, so we can be sure all of the cases are linked together properly to generate the higher priority?

I haven't tried in a while but I remember not liking this setting when I first encountered it. What are some of those advantages?

Hi luckman,

About the separate spaces bug simply describe the issue as you see it, attach your system profile and mention our own bug ID: 29825934

Off the top of my head some advantages of the separate spaces:
- Menu bar on all screens
- Full screen video on one screen does not blank all others
- Easier to keep all window contents in one screen

I'm sure the are advantages to the Spaces feature but I'm not using it enough to notice really. Maybe others can share their impressions.

Regards,
Carlo

[phrogg]

So I switched that preference and it makes the second screen really work pretty well! Overall I like that configuration and I'm not sure how I ended up with that choice turned off!

So things are much better in most respects. The one other issue I have been having is still there and finally got me to just pull the plug on that DL monitor.

I am apparently losing sync with it constantly. It was occasionally but it just kept happening more and more often to where it is now 3-5 times per minute. Both screens blank, it resets all of the windows onto the monitor attached to the built-in graphics card, then it blanks again as it sees the second monitor and puts things back on the DL monitor. This now reoccurs maybe 3-5 times per minute and is making working infeasible.

I am hooked up with a Macbook into the AV adapter where I have one 4K monitor via HDMI and a USB 3 connection to a USB 3.0 hub. That hub has a hard drive (for backups) attached and the DL adapter for the second monitor.

I can drop the hub and backup drive out of the middle of this, but is there any known issue with doing this over the AV adapter on a Macbook?

[phrogg]

Originally Posted by phrogg

I can drop the hub and backup drive out of the middle of this, but is there any known issue with doing this over the AV adapter on a Macbook?

Well dropping the hub out of the middle sure didn't help .

It happens often enough I can probably catch it on video if you really want to see.

[Carlo]

Originally Posted by phrogg

Well dropping the hub out of the middle sure didn't help .

It happens often enough I can probably catch it on video if you really want to see.

Hi Phrogg,

By the description it looks like the device is falling off the bus. As we have found out investigating another report on the forum, both the 2015 and 2016 MacBooks have problems in keeping the USB3 bus going.

We'll probably have to raise a bug against the hardware for this one. We have to collect USB traces and everything.

If that is the issue (and you are indeed using a USB 3 device), the only workaround I can suggest for the moment is to force the system to use USB2 by using a USB2 cable or a USB2 hub. It should be OK for resolutions up to 2560x1440.

If the explanation does not apply to your case, please raise an issue following the instructions in http://support.displaylink.com/knowl...to-displaylink
Please collect the logs immediately after the screens have come back.

Kind regards,
Carlo

[seastwood]

Yes, I've also moved to the new beta and there are both improvements and new problems.

Our company has just installed 170 workstations with Targus ACP77EUX DisplayLink docks, mixed Windows and Mac OS.

Our mac users are all on MacBook Pros, Sierra, attempting to use the internal display plus one external through the dock. (Currently on a DVI connection, switching to DisplayPort for higher resolution once the cables arrive.)

I've upgraded one machine to these new beta drivers and the 'dropped bus' issue is annoying, as others have reported above - occurring a couple of times a minute.

Is it just the video that's being reset, or ethernet, keyboard, external drives etc connected to the dock?

Thank you,
Simon

[luckman212]

I filed my bug with Apple this morning, #29881919

[Carlo]

Originally Posted by seastwood

Yes, I've also moved to the new beta and there are both improvements and new problems.

Our company has just installed 170 workstations with Targus ACP77EUX DisplayLink docks, mixed Windows and Mac OS.

Our mac users are all on MacBook Pros, Sierra, attempting to use the internal display plus one external through the dock. (Currently on a DVI connection, switching to DisplayPort for higher resolution once the cables arrive.)

I've upgraded one machine to these new beta drivers and the 'dropped bus' issue is annoying, as others have reported above - occurring a couple of times a minute.

Is it just the video that's being reset, or ethernet, keyboard, external drives etc connected to the dock?

Thank you,
Simon

Hi seastwood,

If the issue is only visible with the new drivers it's something else and quite concerning. Can you please open a bug on support.displaylink.com with the logs just after the issue has happened?
Please follow the instructions in http://support.displaylink.com/knowl...to-displaylink

Best regards,
Carlo

[luckman212]

Originally Posted by Carlo

some advantages of the separate spaces:
- Menu bar on all screens
- Full screen video on one screen does not blank all others
- Easier to keep all window contents in one screen

Thanks Carlo. To me having a menu bar on all screens is not really useful, plus it wastes some space. The rest of the features are good but for me, I noticed more crashes in WindowServer (or Finder? not sure which) when I had this option on. Mostly Finder would "freeze" and the menubar would start flickering very rapidly and I would get the spinning beach ball and have to force quit. For me having the option off is more stable, even though there is more artifacting as was seen in my video.

I will try to open a bugreport with Apple in the coming days and reference your bug 29825934

thanks.

[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.