Windows 10 Anniversary OpenGL Drivers Ancient
 

The recent Windows 10 Anniversary update has removed the DisplayLink driver and replaced it with the new driver. Everything works okay except for apps that require at least OpenGL version 2.1 because the new Windows driver only supports OpenGL 1.0.

Is there a way to update OpenGL for the DisplayLink hardware to OpenGL 2.1 or higher? 4.3 would be nice!

Hello,

We have noticed an issue with graphics card capability enumeration. DisplayLink does not compute so we don't do the OpenGL, the primary graphics card does the work.

Do you have a multi graphics card machine? Something like Intel + nVidia for instance.
If so, can you try and disable the Intel card?

Having your logs (described in my forum signature) along with the name of the application you are using would be helpful. I'd like to see if this will be addressed with the next Windows release.

Kind regards,
Alban

Hi,
The app that has an issue is a 3D Printer app called XYZWare from this company http://www.xyzprinting.com/

The second app that has an issue is a Web App from Onshape.com.

The XYZ app works fine on the primary display but will not work correctly (image quality is degraded) on the DisplayLink monitors. XYZWare shows an error message that OpenGL2.1 is required.

The Onshape.com web app crashes with a WebGL error. Both of these apps worked fine on the DisplayLink monitors before the latest update. Onshape is now crashing on the primary monitor which runs opengl 4.3

Thank you, I wrote to XYZ. I haven't seen the logs or answer to the questions so we'll see what we can do without...
Before the Windows 10 v1607, the operating system and graphics were different. However in all cases, the pixels are always computed by the primary graphics card regardless of where the monitor was and is now connected.

Kind regards,
Alban

Hi Alban, WebGL crashes with the latest update. Here's the GPU status reported by the Chrome browser if that helps. I don't know if this is directly attributable to DisplayLink or not - it's very hard to say but since the Windows 10 update, things have really impacted me negatively. I rely heavily on my dual monitor setup with DisplayLink.


Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_discard_framebuffer
disable_framebuffer_cmaa
exit_on_context_lost
scalarize_vec_and_mat_constructor_args
Problems Detected
Drivers older than 2009-01 on Windows are possibly unreliable: 72979, 89802, 315205
Disabled Features: all
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Accelerated rasterization has been disabled, either via blacklist, about:flags or the command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers

Log Messages
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[632:14872:1006/140957:ERROR:gpu_video_decode_accelerator.cc(365)] : HW video decode not available for profile 1
[632:14872:1006/140957:ERROR:gpu_video_decode_accelerator.cc(365)] : HW video decode not available for profile 1
[632:14872:1006/140958:ERROR:gpu_video_decode_accelerator.cc(365)] : HW video decode not available for profile 1
GpuProcessHostUIShim: The GPU process crashed!

Hello Deon,

I'm delighted to report I received a reply from XYZ Printing very quickly.

Would you please be able to run our customer support tool and post the resulting ZIP file?
My signature explains how to provide this, and the file posted here can only be downloaded by employees.
Having this will give the machine details to find ideas and identify the closest machine we have.

Could you also save the output of the Chrome GPU diag as a PDF and attach? You can do this by pasting chrome://gpu in the omnibox.

Kind regards,
Alban

Hi Alban, files are attached
Attachment 2926

Attachment 2927

Thanks
Deon

Hi Alban, any thoughts? There is a definite problem with all OpenGL apps. Onshape.com for example is virtually unusable on the Displaylink monitors. On the primary laptop screen, things work in real-time when the display link hub is disconnected.

Deon

Hi Deon,

I was trying to get the software from them to get a repro for debugging. After providing me with a link which doesn't work as it's a login wall, a "technical manager" told me to get lost: I'm so not only supposed to magically have the software but I'm also expected to already know how to use it to create a 3D model.
I'm highly unimpressed.

Regards,
Alban

Hi Alban, customer support has never been very good over there! However, I ran into another app that is freely downloadable that has a very similar problem. Designspark PCB. Whenever you try to display a 3D image of the circuit board on a DisplayLink monitor, the system bogs down completely. You can download the software from here: https://www.rs-online.com/designspar...rical-software

Registration is free as is use of the software. When you open the software, a default circuit board is loaded. Click on the .PCB tab and then choose 3D from the menu. The 3D view will eventually display but interaction with it is painfully slow. Rotate or pan the model to see what I mean. This software definitely used to work in realtime before this latest driver update.
Software works fine on a non-displaylink monitor. Since all my work is 3D related, and it all used to work just fine on my displaylink monitors, it is definitely related to the driver update. I now have to do everything on my laptop screen. This is the only way to work in realtime!

Regards
Deon

same problem here!
 

I could work with my Lenovo carbon x1 + Lenovo ThinkPad USB3.0 Dock (0A33971)
and DisplayLink until the Windows 10 Anniversary came along. Everything is fine, if I only use my build-in-display. If I try to use my external monitors, I get this log:
[INFO ] Kivy: v1.9.0
[INFO ] Python: v2.7.9 (default, Dec 10 2014, 12:28:03) [MSC v.1500 64 bit (AMD64)]
[INFO ] Factory: 173 symbols loaded
[INFO ] Image: Providers: img_tex, img_dds, img_gif, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO ] OSC: using <thread> for socket
[INFO ] Window: Provider: sdl2
[INFO ] GL: GLEW initialization succeeded
[INFO ] GL: OpenGL version <1.1.0>
[INFO ] GL: OpenGL vendor <Microsoft Corporation>
[INFO ] GL: OpenGL renderer <GDI Generic>
[INFO ] GL: OpenGL parsed version: 1, 1
[CRITICAL ] GL: Minimum required OpenGL version (2.0) NOT found!
OpenGL version detected: 1.1
Version: 1.1.0
Vendor: Microsoft Corporation
Renderer: GDI Generic
Try upgrading your graphics drivers and/or your graphics hardware in case of problems.
The application will leave now.

Now I downgraded to the previous Windows 10 build and everything works again. I'm only afraid looking in the near future (<4 month), when Windows 10 Anniversary is unavoidable!
I'm hoping, there will be a solution soon.

kind regards
Carsten

Hello Carsten, and all,

I have a question.
When you boot, what display is the primary?
If going through the Indirect Display engine, could you please try to make the laptop monitor primary, then reboot and see if it changes the behaviour?
We have a suspicion that the graphics adapter may be enumerated in a different order and therefore you won't have the "Microsoft Corporation 1.1.0" first.

I'd welcome your feedback on this as it would help get this fixed... We don't really have control over what the OS lists as cards, and you've stated that what the capability returned does not look to be from DisplayLink driver.

Kind regards,
Alban

mhm - I would like to, but I don't know, if I can be of any help anymore, since I downgraded win10 and got therefore OpenGL V.4 support back - see actual log:

[INFO ] [Window ] Provider: sdl2
[INFO ] [GL ] GLEW initialization succeeded
[INFO ] [GL ] OpenGL version <4.0.0 - Build 10.18.10.4358>
[INFO ] [GL ] OpenGL vendor <Intel>
[INFO ] [GL ] OpenGL renderer <Intel(R) HD Graphics 4000>
[INFO ] [GL ] OpenGL parsed version: 4, 0
[INFO ] [GL ] Shading version <4.00 - Build 10.18.10.4358>
[INFO ] [GL ] Texture max size <16384>
[INFO ] [GL ] Texture max units <16>
[INFO ] [Window ] auto add sdl2 input provider

... so for now the problem is gone.
(Besides I didn't completely understand, how to make "laptop monitor primary".)

Hi Alban, what I have tried is to boot the laptop without Displaylink connected. Then after I log in, I connect the displaylink hub to the laptop. After a bit of initialization, the display link monitors display content and the laptop display switches off. Now if I run any openGL app, the problem of everything being incredibly slow reoccurs, and XYZWare again reports OpenGL 1.

Regards
Deon

Good afternoon,

The primary monitor is the one with the system tray icons.
To change the primary monitor, simply right-click on the desktop, then select Display settings, then click on the monitor you wish to make primary, then tick the box "Make this my main display", then click Apply.

Deon,
On Windows 10 Anniversary Update, when no DisplayLink chip is connected, there is nothing from DisplayLink running. However, the Windows OS part of the logic doing the indirectly connected display is still there and is always running.
Just now, I'm looking for an OpenGL basic application to do the test on my machine.

Kind regards,
Alban

Deon,
Would you please be able to post a zip with a project for DesignSpark?
Nobody else will be able to download the zip.
When I open the tool, there is nothing. I have tried adding components on the schematics but that doesn't give me a PCB...
Thanks,
Alban

There are a number of samples that you can use. A good reference is located on your harddrive here: C:\Users\Public\Documents\DesignSpark PCB 7.2\Examples\ChipKitMax32

Open the chipKIT Max32.pcb file.

Hi Alban,
If you'd like 2 free applications that have this openGL error on launch then you could look at Nox and Memu android emulators.
Both are FOC to download and run and don't require a signup

Nox:
http://en.bignox.com/
Memu:
http://www.memuplay.com/

Nox will work using your solution of disconnection dock, launching app, re-connecting dock.
Memu won't
shout if you need further info on it.

Hi Alban, any further thoughts on this? WebGL and OpenGL are broken.

Regards
Deon

Hi Deon,
The PCB thing wasn't part of DesignSpark Electrical software linked but another one I downloaded it and ran the PCB 3D rendering. It struggled for about 3s and then was smooth on my Surface Pro 3 through Dell D3100 docks and dual HD monitors and on the Surface Pro native monitor without the dock connected so that won't be a good proof point.
The OpenGL Extension Viewer 4.1 application shows that DisplayLink has both non-accelerated and accelerated (1.1 and 4.x), identical to without DisplayLink... So that's not a good way to report this either...

That's why I have added the task to the engineering backlog. They will need to investigate and create the analysis report to Microsoft.

Kind regards,
Alban

I got an update from Microsoft. The graphics card vendor should have implemented the new support in their drivers for the Anniversary Update.

Could you please post the result of the following command line so they can look into it?
This will tell them if the driver you use is supposed to have it implemented or not. If it's implemented, then the issue would be elsewhere... for instance it might be the graphics card enumeration of the application.
Run the following in a command line and post the dxdiag.txt

dxdiag /t dxdiag.txt

Kind regards,
Alban

Hi Alban,

I have the similar problem, and hope, there will be an easy solution.
If i can help, please let me know. I can send you this dxdiag.txt, but dont know, if it needs the computer to be plugged into the dock, and monitor (i think so). I can not do that at the moment, only a few days later, if it is still ok for you.

Also, i have tried to use hdmi cable, and directly connect the external monitor to the laptop. It worked perfectly, and i could use the secondary graphic driver. I'm not a tech expert, but my bet would be the usb port as the problem source. Maybe the updated win 10 cannot handle the monitor data through the nvidia card, and usb port?

What im using:
Dell Vostro 5470
Dynadock u3.0
Windows 10, version1607

Kind regards,
Kalman

Hello everyone,

I asked Microsoft last night and they haven't yet received the feedback from the graphics card vendors.
The graphics card vendor should have implemented OpenGL for indirect displays in their driver for the Windows 10 Anniversary Update release.

Kalman, I looked and the Dell Vostro 5470 is Intel 4th generation. I don't believe Intel will issue any new driver for that architecture as they just released the 7th generation... As far as I've seen they already did not release any WDDM 2.0 driver for Windows 10 Threshold (the initial version).

Kind regards,
Alban

Thanks a lot for the information, didnt know, my laptop is that behind. :)

Even if there will not be any new driver, shouldn't the old one still work? I mean, the new update should really overwrite an already working driver, with a non-working version?

What drivers shall I downgrade to have it work? Can you help me with this? Even in e-mails, or another thread? Or should i turn to Microsoft?

I have tried previous graphic drivers (even with complete removal of the NVidia driver).

Good afternoon Kalman,

The old driver is not expected to work because this is a new OS feature in Windows 10 Anniversary Update. Therefore the driver would never have supported this.
In previous versions of Windows, instead of using (now) standard OS calls, we used a different methods.

The previous method could cause stability issues as each graphics driver update and months of work with each new version of Windows, especially in mutli/hybrid graphics systems... With Microsoft churning versions of the OS every two weeks through the Windows Insider Program, the few month development each time wouldn't have quite worked. Also, the new standard OS calls mean that having DisplayLink work is important to Microsoft as we helped design/develop it.

At the moment, I am waiting for Microsoft feedback to know what will happen next. And they are waiting for the graphics vendors to inform them about their progress.
If it turns out that the graphics vendors have actually already implemented the changes to pass-through the OpenGL, then the solution will be elsewhere.

Kind regards,
Alban

This thread interests me greatly.

I have an UP-BOARD SBC with HDMI out and also trying to use a USB3.0 display from Asus which uses the DisplayLink driver. OpenGL 3.3 and later work fine on an HDMI connected display, but not on the USB-connected display via DisplayLink driver.

I hope a fix is issued soon. Thanks.

Hello N@UT,
The fix as it stands today is getting graphics drivers supporting the indirect display driver model.
This will come from the graphics card vendor, unless Microsoft discovers something wrong in the OS.
OpenGL is for compute, therefore the OS gives the task to the graphics card to do: even for indirectly connected displays like DisplayLink, the graphics card does the computing. There is no reason for a difference in OpenGL version between a direct and an indirect display.

Kind regards,
Alban

Hello N@UT,
The fix as it stands today is getting graphics drivers supporting the indirect display driver model.
This will come from the graphics card vendor, unless Microsoft discovers something wrong in the OS.
OpenGL is for compute, therefore the OS gives the task to the graphics card to do: even for indirectly connected displays like DisplayLink, the graphics card does the computing. There is no reason for a difference in OpenGL version between a direct and an indirect display.

Kind regards,
Alban

compatibility list
 

Hello Alban,

is it somehow possible for you to ask Microsoft for a kind of compatibility list of graphic-card-drivers which are able to support the new standard calls? Maybe you can provide this list then to us.
In my case it is a "Intel(R) HD Graphics 4000" built in a Lenovo laptop. The driver I'm using is version 10.18.10.4358 dated 21.12.2015 (as far as I know there is no newer available). This version obviously is not able to manage to use the OpenGL 4.x renderer from the graphics card when DisplayLink gets involved.
Any chance that I can continue using DisplayLink anymore, if I would - or better: have to - upgrade soon to win anniversary upgrade?

kind regards
Carsten

Hello CML,

That version predates Windows 10 Anniversary Update by too much to support it.
The hint is the version number starts with 10. A driver made for the initial Windows 10 (WDDM 2.0) would start with 20. 10 should mean WDDM 1.3 so intrduced for Windows 8.1
You have a more recent driver for your graphics card: v4525 from May 2016. However I doubt it will have it: it looks like it's Intel 3rd Gen CPU (Ivy Bridge) which is out of support. To install it, you must take the zip version and assign it through Device Manager if the executable has been blocked by your machine manufacturer.

Kind regards,
Alban

Hello CML,

That version predates Windows 10 Anniversary Update by too much to support it.
The hint is the version number starts with 10. A driver made for the initial Windows 10 (WDDM 2.0) would start with 20. 10 should mean WDDM 1.3 so intrduced for Windows 8.1
You have a more recent driver for your graphics card: v4525 from May 2016. However I doubt it will have it: it looks like it's Intel 3rd Gen CPU (Ivy Bridge) which is out of support. To install it, you must take the zip version and assign it through Device Manager if the executable has been blocked by your machine manufacturer.

Kind regards,
Alban

Thanks for your investigation. I followed your link to Intel, but reading in their release notes that driver version 15.33.43.64.4425 - this is the package version, the included graphics driver version is 10.18.10.4425 - "will include support for Windows Display Driver Model (WDDM) 1.3" which tells me, that it has actually *no* support for WDDM 2.0
If I understand you right, WDDM 2.0-support is absolutely required here!?
This now makes me kinda nervous ...

Hi CML, I don't know if it's in direct relation to WDDM version. However, that gave me an indication of what the the driver was designed for.

Hi Alban,
I find this quite confusing and frustating: I already invested hours and hours after being upgraded to MS Windows Pro 1607 ("Anniversary Update") only to found out, that OpenGL 2.0 and above is not working any longer with DisplayLink.
It is not completely clear why.
From Intel-side there will be probably no support for WDDM 2.0 for my 3 year-old embedded graphic-card. But - as you said - it's not even clear, if that's the crucial point.
I don't need OpenGL 2.0 for gaming, it is my environment for professional software-development.
MS on the other hand is not willing to support OpenGL much for strategic reasons, as they want to make their own DirectX the dominant graphics language.
I just don't have the time to make another attempt of upgrading to win 1607 with incalculable outcome.
Now I have to find a way to prevent any automatic upgrade because this would destroy my working environment. Absurd. That said, I promised myself, that I'll never ever again will use Windows again as my basic OS on any new machine I'll get.
I would like to know, what's the crucial point here and if there is any workaround possible to continue working with my configuration - with which I was pretty satisfied until this mess.
How can I direct DisplayLink to let my graphics card doing the rendering unter win 1607 as it does now unter win 1511?

kind regards
cml

Hello CML,

Windows 10 v1607 is a new operating system. It looks like v1511, it is also called 10 but it is a different OS, with a different graphics subsystem. Whether your GPU vendor and the driver you have supports it or not is not appropriate for me to comment on. Microsoft indicated that is the root cause for your issue. My contacts are the people who designed the API and be certain they also want it to work properly!

DisplayLink driver does not interpret OpenGL and never has done so. There is no way to tell DisplayLink driver to interpret OpenGL and select what to do with it because DisplayLink is not a GPU. Here, DisplayLink drivers will get computed pixels = the driver has NO visibility/access to the OpenGL API calls or applications running. That's up to the kernel mode driver.
DisplayLink is not able to solve these third party shortcomings. We do not have control over that code base and the information I have is from third parties.

You may also wish to switch to the Windows 10 LTSB if you believe your GPU vendor will never address the Windows 10 Anniversary Update operating system requirements and if you don't wish to receive the Windows Updates for Windows 10 v1607 yet. If you want to install 7.9 M7 on it and take the responsibility of the consequences of that attempt, then you are free to do so.
DisplayLink driver 7.9 is incompatible with WDDM 2.1 primary graphics card drivers and not supported on Windows 10 v1607. If you then start using a WDDM 2.1 primary graphics card driver, you *will* have issues, upto not being able to use the computer. That is why DisplayLink driver 8.0+ is the minimum version supported on Windows 10 v1607.

I am as frustrated and almost as powerless as you are.
Please do ask your GPU vendor to provide graphics drivers for Windows 10 v1607 so we can get this progressed.

Regards,
Alban

Hi Alban,

I need some technical insight from you about this issue.

I'm using the laptop with a hdmi connection to the monitor, works perfectly fine (Nvidia GT 740M). Phototeca (needs OpenGL 2.0+) also runs smoothly.
As soon as I switch the monitor to the dock, only the integrated intel HD 4400 works, without OpenGL 2.0 (or whatever is the current version).

I understand WDDM 2.1 has a new method, but it did not disable the drivers in the laptop. I have the latest drivers for the dock and graphic card, according to the computer.
That is why I brought up the possibility about the USB port. If the Dynadock driver works perfectly, only a few explanation remained, I think (only by sheer logic, not with technical knowledge):
1. Windows 10 makes Dynadock unusable. But only part of the graphics.
2. Update (version 1607) has a bug, that prevents Dynadock identify OpenGL and second graphic card through the USB port.
3. Dynadock driver has a blind spot in communication with Windows, because of the update. It should work, but cannot.

Based, on what you wrote to CML, the dock only takes the final picture, and forwards it to the monitor. Still, the laptop can use everything, but the dock can not.

Please help me understand the situation, because I want to turn to Microsoft, and I would not run the same rounds again and again, manufacturers pointing at each other.

Good afternoon,

Microsoft confirmed to me the issue lies with the graphics driver.
They have created a bug report to Intel about this.
The reference of the bug from MS to Intel, should you wish to help push for a fix, is "Sysdev 10134913".

Kind regards,
Alban

OpenGL Incorrect Version Problem
 

I have a Dell XPS laptop with Nvidia 960M which runs OpenGL 4.4 on Windows 10 Home (Build 14393.693). I connect to a larger monitor via the Dell D3100 docking station.

Recently I have noticed some OpenGL applications which I have coded in the past (and worked fine) have started to not work properly when I have try and run them when attached to the larger monitor via the dock. I am certain this wasn't the case until recently and have replicated these issues with demo OpenGL apps from trusted sources.

Upon closer examination I have found that if I have the screen set to "display only on 2nd display" i.e. large monitor on / laptop screen off (which is how I normally run my setup when in the office), the OpenGL version registered as running is as follows:

Running on a GDI Generic from Microsoft Corporation
OpenGL version 1.1.0 is supported

However if I try and run with only my laptop screen or the screen set to "extend" i.e. both large monitor and laptop screen on, I get the following:

Running on a Intel(R) HD Graphics 530 from Intel
OpenGL version 4.4.0 - Build 20.19.15.4474 is supported

Note:- Due to the strange way the Dell XPS display system is built, you can't turn off Intel Graphics / enforce the nVidia driver at all times, the system decides as and when which to use..

Clearly something is wrong here as OpenGL 4.4 is installed on the system, but when I have display on 2nd screen only it seems to pick some weird generic driver.

Hi there, I am having the same issue exactly but with more software:
1. SolidWorks
2. CURA
3. Google Sketchup
4. Altium Designer

Please advise, what should i do?

Hello,

We've updated the FAQ but not this thread.
Intel recognised and fixed their bug.

The first fixed driver is https://downloadcenter.intel.com/dow...-Windows-15-60

Kind regards,
Alban