Open GL error
Samanthie
Posts: 308
Hi, haven't been using Daz for awhile and have version 4.7. I try to launch DS and get a message about only having opengl 1.1 and need version 1.3 to run Daz Studio. My drivers are as updated as they can get. The reason for my post is DS did work prior to this version and before I upgraded to windows 10. I can't upgrade my lowly chipset graphics so does this mean I can't use Daz any longer? Thank you for your reply and any help.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Have you tried the manufacturer for a Win10 compatible driver?
If by 'lowly chipset driver' you mean an Intel onboard video...maybe. Some Intel chipsets do not have Win10 drivers...but check with the machine manufacturer and if it is Intel, Intel itself for a reference driver.
It's common that drivers are incompatible with windows 10 so that could be the problem, OpenGL 1.1 indicates it's falling back on the software driver and not using any HW driver at all, so you may need to find something that works with Windows 10.
yes I did and found a tutorial with driver download but the driver is exactly the same driver and win 10 won't install it. I get the message most current driver already installed.
Yes this is what I have onboard Mobile Intel 4 Chipset family (microsoft corp-WDDM 1.1) I went to the Intel site and downloaded a scanner and it says nothing is available
I am not sure where to look. I will try again today and see if there is something I've missed. I mean Daz worked before so this doesn't make sense but if I could go back to windows 8 I would.
Thanks everyone, will look further.
Edited to fix quotes
The windows 10 forum gave instructions to uninstall and then reinstall the driver in compatability mode which I did but still doesn't work. Then I found out there will be no new drivers from Intel to fix the issue. The chipset 4 family is now a legacy item so they won't be updating the drivers. I can't roll back to windows 8.1 either. Anyway if someone has found a workaround for this issue I would love to know, thanks. I have an HP Notebook 2000. I'll most likely have to start looking for a new laptop.
Unfortunately if Intel doesn't have it, then it's 'unsupported' and will not be supported...(on the Intel forums the iintel_name folks are 'official'...)
https://communities.intel.com/thread/77847?start=0&tstart=0
That's what I've been reading as well. Thank you for looking that up. I have already begun searching for a new laptop.Just an update on this...I decided to do a reformat on my laptop (actually HP Notebook 2000) so I could go back to the original windows 7. Daz Studio works again! I may not be able to upgrade to the latest version but glad to have 4.7 running. I will not be updating this machine to windows 8.1 nor 10. Nice to have my simpler and much less cluttered windows 7 back I must say. :)
well. my 2400 euro gaming pc, now show same [annoying] error with opengl 1.1 when need 1.3
id say this is [nonsense].
PS: it did launch like 2 hour ago when i just installed it back on pc,, but now after install manager did download and install all [stuff] from the list, it gives the open gl [nonsense] error....
Edited for profanity
What GPU do you have? Have you installed the maker's drivers instead of the basic Windows drivers, which often fall short on OpenGL support?
Windows 10 arrogantly over-writes your GPU drivers. Nvidia has an early access driver update that solves this problem. I've applied it to my PCs and it does the trick.
https://forums.geforce.com/default/topic/1051755/geforce-drivers/announcing-geforce-hotfix-driver-397-55/
I've just started to have this problem in the last week. But honestly, when I check the driver it never says that it's been replaced by the windows version. Rebooting always allows DAZ Studio to work again, but it seems odd that I'd have this problem out of the blue.
The latest Nvidia drivers solve the "windows forgets about the driver" problem, but some people have reported dForce issues with that driver. Personally, I had that issue after the April update, then upgraded my Nvidia drivers to the latest (397.64) and that solved the issue (and dForce still works). But YMMV.