Win 10 AU, DisplayLink 8.0M3, and Chrome Issue

[AlbanRampon]

Hello,

Thank you for your patience whilst I was on holidays.

We don't have a reproduction at this stage and you are the unique person who reported this Netflix issue until last week when Roy chipped in so I have not been able to have this prioritised before I left... And you have a straight forward way of making it work. This has nothing to do with not caring!

You indicated everything is peachy with Microsoft Edge and I've already stated our driver is not application aware...
I don't understand why you prefer getting angry with having it stutter on Google Chrome rather than having it smooth on Microsoft Edge.
Would you care to explain why you don't use Edge for now to watch films?

Regards,
Alban

[Trekari]

Because Chrome is the browser I prefer to use. Why should I have to use software I do not care for in order to avoid a problem which should instead be addressed and corrected?

Someone is responsible for this malfunction - either you guys, Google, or Microsoft, and thus far nobody has accepted responsibility or issued a fix. I can't even get someone on the Google product forums to pay attention at all, so the only way I see this getting resolved is if you guys get in touch with Google (or Microsoft) and tell them there's a problem which needs correcting.

I'm upset because this isn't the first time there's been a major issue with my Displaylink device, and it only happened after a forced upgrade from Microsoft to Windows 10 AU, and I'm sick of having hardware/software issues forced upon me and having to sit around and hope that enough people have the issue to where someone cares enough to be bothered to fix it.

[AlbanRampon]

Originally Posted by Trekari

Because Chrome is the browser I prefer to use. Why should I have to use software I do not care for in order to avoid a problem which should instead be addressed and corrected?

Someone is responsible for this malfunction - either you guys, Google, or Microsoft, and thus far nobody has accepted responsibility or issued a fix. I can't even get someone on the Google product forums to pay attention at all, so the only way I see this getting resolved is if you guys get in touch with Google (or Microsoft) and tell them there's a problem which needs correcting.

I'm upset because this isn't the first time there's been a major issue with my Displaylink device, and it only happened after a forced upgrade from Microsoft to Windows 10 AU, and I'm sick of having hardware/software issues forced upon me and having to sit around and hope that enough people have the issue to where someone cares enough to be bothered to fix it.

What I can understand from that is that you are venting on DisplayLink forums because we are the only ones who listen to you and reply. I am obviously not responsible for addressing Google product forums and Microsoft "forced updates".

You are totally welcome to keep using Google Chrome for now if you wish. I personally would prefer having something that works smoothly, whichever free tool provides it to me.
It could also be an issue with the video streaming technology being used, if that's only Netflix... But yeah, Netflix will tell you to remove DisplayLink, it's far easier.

[Trekari]

Originally Posted by AlbanRampon

What I can understand from that is that you are venting on DisplayLink forums because we are the only ones who listen to you and reply. I am obviously not responsible for addressing Google product forums and Microsoft "forced updates".

You are totally welcome to keep using Google Chrome for now if you wish. I personally would prefer having something that works smoothly, whichever free tool provides it to me.
It could also be an issue with the video streaming technology being used, if that's only Netflix... But yeah, Netflix will tell you to remove DisplayLink, it's far easier.

You understand incorrectly. I am not here to vent. I am here to get support and have this issue corrected. You asked for logs; I provided them. I have offered to provide any other information you need to track this down. Thus far, that offer has been met with silence.

You're correct that you are not responsible for what happens on Google product forums, or Microsoft's updates. But let's not pretend that you don't have an avenue of communication with other major hardware and software providers that you could utilize to help resolve this.

I use Chrome because it is a browser I have confidence in, and it automatically syncs with my cellphone. It has features which Edge does not - features which matter to me. What you prefer to use is your decision, and what I prefer to use is mine. Complaining about my browser of choice is not the job of technical support.

If you consider this to be venting, then it is only because I'm NOT getting support and this issue is NOT being resolved. Once again - if you need more information or logs, tell me how to provide them and I will do so. Criticizing my choice of browser will not benefit anyone.

[AlbanRampon]

Trekari,

I have not pretended anything in this thread.

We do have contact with Microsoft graphics, obviously as we have press release about that. But I do not expect any traction whatsoever explaining that there is an issue on Netflix when not using Microsoft Edge but only using Google Chrome browser.
We do have contacts with Google in different team, but not in the team doing the browser.
We do not have contacts at Netflix at all.

When this has reached the top of the backlog and if the team needs more information, then we will ask. Unfortunately today I have only 2 reports out of millions of displays currently in use with a straight forward workaround.

Of course, if you get feedback from the other suppliers, this will be helpful.

Regards,
Alban

[Trekari]

I would not expect you to discuss anything with the Edge browser team. My remarks regarding Microsoft are in reference to the WDDM change implemented in the Anniversary Update. That may have nothing to do with it, but it's the only graphics-related change that I'm aware of, and I know it came with the AU. Prior to AU, everything was fine, thus my suspicion that the 2.1 version of WDDM might have something to do with it.


Trust me: if I get any updates from anyone else about this, I will let you know.

[AlbanRampon]

Hello,

You could check about the WDDM version impact by downgrading your primary graphics card driver.
If you take one from about March 2016, it would be WDDM 2.0 and therefore work as such.

Kind regards,
Alban