12-02-2016, 02:58 PM | #31 | |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,681
|
Quote:
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
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
|
12-02-2016, 03:41 PM | #32 |
Junior Member
Join Date: Oct 2016
Posts: 5
|
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 ... Last edited by cml; 12-05-2016 at 10:13 AM. Reason: some more details |
12-05-2016, 01:43 PM | #33 | |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,681
|
Quote:
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
|
12-06-2016, 06:52 PM | #34 |
Junior Member
Join Date: Oct 2016
Posts: 5
|
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 Last edited by cml; 12-06-2016 at 06:56 PM. |
12-07-2016, 01:05 PM | #35 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,681
|
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
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
12-07-2016, 10:33 PM | #36 |
Junior Member
Join Date: Nov 2016
Posts: 3
|
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. |
12-16-2016, 03:45 PM | #37 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,681
|
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
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
01-17-2017, 01:11 PM | #38 |
Junior Member
Join Date: Jan 2017
Posts: 1
|
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. |
12-13-2017, 11:31 AM | #39 |
Junior Member
Join Date: Dec 2017
Posts: 3
|
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? |
12-14-2017, 02:25 PM | #40 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,681
|
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
__________________
Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution |
Tags |
intel, nvidia, opengl |
|
|