I suggest we don't mix everything and make the same mess as the other thread. It is unhelpful and confusing to anyone trying to get an answer to her/his particular problem.
No, it is not exactly the same and we have third party evidence it is not.
Yes, it is not perfect, and I stated that from the beginning.
1. CPU usage
Having 20% CPU usage does NOT prevent anything from working. I agree this is not ideal, but you have a minimum of 100% (depends on how you count: core or CPU and number of CPUs). So there are still at least 80% left.
Please stop confusing performance and CPU usage. You miss metrics like memory bandwidth usage which are much more important.
I have difficulties understanding how one can claim that it's not possible to work on a machine where CPU is being used.
2. Refresh Issues
There is NO known DisplayLink driver issue with refresh. If you came up with one, document it so we can look at it.
There was one redraw issue in the OS that Microsoft fixed in build 15049 (Creators Update).
Unless you update your OS, things won't magically change by increasing our driver number. We get static/corrupted content, our driver will not invent data it doesn't receive!
We have asked to get the fix backported to 14393 (Anniversary Update) however we need to know the number of machines affected to build the business case to justify Microsoft working on this. How many machines do you have affected by their problem?
I can understand how this would affect working on such machines, and that's why we've relentlessly been pushing for this to be fixed week after week until it was fixed.
3. Game Lagging
Your particular "game is lagging" is because the OS sends the work to the graphics card used for POST (when you boot). In a dual graphics card system, it's usually the Intel integrated graphics.
Here as well, that's a known OS limitation. I've already explained on several posts the possible workaround, depending on what machine you have decided to buy and its limitations. All this happens at the kernel graphics driver level, NOT user mode. DisplayLink driver doesn't have the privilege necessary to access any of that anymore.
Have you asked Microsoft? If not, please use the Windows Feedback Hub to complain. That's what exactly it was designed for. Until enough people report the issue, they can't realise how important to users it is. The message sent to Dell wrongly accusing DisplayLink driver might help as Dell know very well the product they designed and how Windows graphics subsystem work, but I suggest you also express your disappointment to people who are responsible for the issue and can do something about it. That would help us getting it addressed. Microsoft is NOT unwilling to address it, like everything, this is a matter of how high a priority it gets.
4. 8.2 Beta 1 to 8.2 Beta 2
At no point did I ever recommend to try 8.2 Beta 2 compared to 8.2 Beta 1 for the CPU usage. 8.2 Beta 2 was for people wanted to try gamma correction, and was only presented as such.
Domdus does bring an interesting point though: he removed and installed again and the CPU usage has changed. We obviously couldn't change 8.2 Beta 2 in between, so his own tests demonstrates there are external factors to the driver or dock.
Should you have any specific technical question, like how to best report the issue to the people responsible to get assistance, I will be delighted to assist.
Regards,
Alban
|