Hey,
I had win 7 and intel HD Graphics 3000 and i was running program on Blender program normally after i have installed win 10 and the Graphics driver still the same it shows me an erro "OpenGL is not supported by the video card" knowing that my graphics driver is up to date
Thank you.
链接已复制
Inteh HD Graphics 3000 is not supported on Windows 10:
https://www.intel.com/content/www/us/en/support/articles/000005526/graphics-drivers.html Supported Operating Systems for Intel® Graphics Products
This also means your processor is not supported on Windows 10.
Regarding, OpenGl support, it does support OpenGL 3.x.
Look under 2nd generation processors here:
https://www.intel.com/content/www/us/en/support/articles/000005524/graphics-drivers.html?eu-cookie-notice Supported APIs and Features for Intel® Graphics Drivers
It is time for you to upgrade to a new or newer system that is supported on Windows 10 and has opengl support that your program needs.
Doc
There is no driver that will update your "card", or OpenGL, to anything greater or a newer revision.
Yes, you have to change the hardware.
One possible solution is, if your machine is a desktop, is to find a compatible add-on graphics card (nvidia or amd-based) that has support for the opengl level you need. That is more difficult than it sounds.
Doc
@Shefo you may be able to fix your program if you do the following:
- make sure your program doesn't declare Windows 10 compatibility (most commonly this is done via executable manifest, if the executable manifest contains a SupportedOS tag with a property called ID with a value that begins with {8, then you can be sure the program declares Windows 10 compatibility);
- I looked at Blender and while it doesn't declare Windows 10 compatibility, Python 3.5.3 which is bundled with it does. So if your program is a python script that uses Blender https://github.com/pal1000/save-legacy-intel-opengl this can help. Download that repository and apply the fix via python.cmd
If this helps I'd appreciate if you upvote this feedback: https://aka.ms/Sn9jtj https://aka.ms/Sn9jtj
Just followed this video and it worked successfully
https://www.youtube.com/watch?v=Yqe5cgthZH4 https://www.youtube.com/watch?v=Yqe5cgthZH4
Considering you hinted me that you are a software developer I should have expected you being able to clear the compatibility shim creation tutorial yourself. That's the tutorial I originally made to solve this issue on a case by case basis. Since then someone from here took it and posted with permission on Youtube where you found it.
Since you managed to fix your software you may contribute with the .sdb file https://github.com/pal1000/save-legacy-intel-opengl here.
You can zip the SDB file and attach it to a reply on this post. Note that an SDB file is needed for each architecture. If your program is both 32 and 64-bit there has to be 2 SDB files, one for each ABI. If your program is single ABI I need to know which is it. Of course you can build the installation batch script yourself, it's very easy. There are a few examples there and you don't need a Github account to inspect the code.
I didn't know the fix you were looking for was for Java. Sorry but that's the first fix I ever added to https://github.com/pal1000/save-legacy-intel-opengl Save legacy Intel OpenGL repository. You could just download the repository as ZIP using Clone or download button, extract it and run java-runtime-environment.cmd. There is no need of Git or Github account to do that. Speaking of waste of time, when you created the fix I think you followed my original video that was later posted on youtube in a too accurate manner that you managed to replicate a mistake I made there between 10:10 and 12:10. I accidentally left FILE_VERSION matching information checked which means the fix will stop working if you update or downgrade Java.
If you still have that fragile fix you need to uninstall it first (standard software uninstall procedure applies). The record name from Program and Features / Apps & Features matches the name you gave to the database and not the name of the sdb file. After that you should apply the fix from the Github repository.
Well I tried pal1000 fix's first as he told me and nothing was fixed in addition to it gave me some errors while trying to apply the fix sometimes and i didn't inspect the contents well so i couldn't find the sdb file but i appreciate his help and tried to help him back and now the problem was fixed and as he said due to poor communication didn't realize that he had fixed it already any way thank you for your help and your time.
