Download Opengl Drivers
Gianira Jardin
I just bought a PC that has the AMD Radeon RX5700 XT. The PC is running Windows 10 home, I'm a photographer, and when I work on photoshop and select a filter, I use Luminar AI, but when it goes to open, it gives me an error message saying that I need an OpenGL 3.3 graphics driver. I have the latest drivers with the newest AMD software, 24.4.1, and it says my drivers are up to date. Where am I going wrong?
I have mine fixed. I contacted Intel support because I also have an Intel UHD graphics 750 that was also stuck on OpenGL 1.1, so the software guy went into my PC and uninstalled the drivers completely and reinstalled them, but, he some other things that I'm not sure of, but it fixed the OpenGL problem for both the Intel graphics card and the AMD card just by fixing the Intel graphics card.
Thanks I havent tried alternative drivers I will do. I am puzzled as to why this just started happening and whether it was something about upgrading to 82. In the meantime I managed to get a graphics card and corresponding driver and this works fine. (Still need to fix my other PCs though!)
Best
Philip.
ARB usually means the extension or function is under review to be included into the main OpenGL spec. Graphics vendors are free to drop those extensions and functions once they are approved, and are not interested in providing legacy support.
Hi guys,
I am having the same problem. Weirdly, when using the builder, MissingFunctionException says that glActiveTextureARB is missing, when using the coder, it says that glActiveTexture is missing.
I understand that this is not a PsychoPy problem. However, it worked the last time I used it, less then a month ago. However, I was using version 1.94 and now I updated it to version 3.5.
I tried to go back to back to 1.94 but the problem now remains. It might be that my driver updates itself?
I am using Window 10.
Is anyone able to explain to me in plain English (e.g. change your driver would not be useful how I can solve the problem?
Thanks and best wishes
Ale
Thank you, Philip. I understand other things take priority and therefore I cannot expect a step by step guide to solve the problem. However, I cannot use PsychoPy at all at the moment. Could you maybe suggest a guide on how to un-install drivers updates?
It seems that /run/opengl-driver is symlink to opengl-drivers store path which is only referred by nixos-system path and not a single application. Had it been installed as application dependency, the instance which broken application had been built against would still be present and it would run. So why had NixOS crew taken decision to do it another way?
Operating system: Linux (AWS workspaces Power Pro x86_64)
Slicer version: 4.10.2
Expected behavior: Display dicom images
Actual behavior: Error message about not finding latest OpenGL drivers despite those being present on the system.
Just bought a second hand computer for a project I'm doing, needed something with a bit more memory etc. Only problem is when I try to open the program I get an error message saying that the application requires OpenGL 1.3 but my machine only provides OpenGL 1.1.
I downloaded what you sent, an alert came up to say that the driver I had was newer than that I was downloading, tried it anyway but unfortunately having the same issue. Had a look at the website you sent and sure enough, it's saying I should be able to run OpenGL 2.0. Really have no idea how to fix this
However, if you have an available PCIe x16 slot, you MIGHT be able to find a COMPATIBLE add-on card (emphasis on might and compatible), that will give you the graphics you need. Be careful selecting a card. I have nothing against AMD, but their cards seem to have a lot more trouble with backward compatibility than nvidia cards. Note that your old machine is PCIe 2.0, and new graphics cards will be PCIe 3.0 (and claim backward compatibility). And, if successful, you can likely continue to run Windows 10 (until microsoft decides to pull the plug).
The downgrade to Windows 7 allows the OpenGL driver to load because it no longer gets confused. With old Intel hardware on Windows 10 if a program declares Windows 10 compatibility the OpenGL driver exits due Windows version check failing internally. It is possible to workaround. If you want to workaround it open an issue ticket here: -legacy-intel-opengl GitHub - pal1000/save-legacy-intel-opengl
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
Hi
Not being a regular forum user I assume I was correct in adding my query to this posting rather than creating a new subject but correct me if I am wrong, I was wondering if anyone has had any thoughts on my posting yet or whether I should look for alternative software?. Thanks
You seem to be among a small number of people for whom Shotcut does not work with their hardware. Some of those people have found that updating their video drivers helps. But for others it does not. I think your options are to either try different hardware (maybe different video card or different computer) or different software. You can always check back with each new release of Shotcut to see if something has changed that makes it work with your hardware.
Many thanks for your reply Brian, you seem to be doing a lot of the work around there. I had been coming to the conclusion that it must be some deficiency in the graphic card or display adaptor that was the problem but the difficulty is to determine what that is. A reasonable graphics card covers all my work without going to great expense and this was one I was given so I am not aware as yet of its full capabilities but has coped well so far. I could try Shotcut with Linux as I have this as a discrete double boot on that computer but its the same graphics card. I could live without it as the amount of cutting I was to do is small. So I may try another card at some time. Thanks again.
Found a solution to this problem.
Actually my Nvidia PCIe card went phut one fine summer afternoon and i was left with Intel G33/G31 gpu. Got this very error every time i tried to execute Shotcut, so hunted the net and bumped into this solution. It is a very simple one, download the following 7z, it contains 32-bit and 64-bit folder containing a file each for required Win OS.
I removed your link because it leads to code that is suspicious consider its source (somewhere on a file sharing site). The software you linked to is probably a legit copy of Mesa llvmpipe on GitHub (use the mingw build of opengl32.dll). Doing this overrides any selection of Settings > Display Method and makes it use software, which is reliable but not good peformance for video display.
Besides driver changes outside of Shotcut, the biggest factor affecting this in Shotcut is Settings > Display Method. This was added in version 15.09 and defaulted to Automatic, which selects OpenGL, DirectX, or software as determined by Qt - the library we use for the UI. (This library is also responsible for the presentation and wording of the dialog quoted in the original message.) Which setting works best is very system dependent. On many systems, they all work. Therefore, the selection of a default is difficult. Shotcut does not report information to a cloud service and is therefore unable to determine from analytics data.
In version 19.04, I changed it back to Automatic because I added Software (Mesa) option since I upgraded and rebuilt Qt and got it working in both 32- and 64-bit. I wanted to restore the ability for the fresh install experience to be able to fallback to Software (Mesa). Unfortunately, that kind of back-fired. many people again reported problems where changing it to DirectX solved it for them. Also, on one of my systems, Software (Mesa) did not work and gave me the dreaded dialog. This is crazy because the software mode should be foolproof! (But Software should not be default because is slower.)
In version 19.06, I changed it back to DirectX (ANGLE) for the above reasons. Also because I learned that DirectX has a builtin software fallback mode called WARP lending further weight toward making it the default. In this version, I also made a hack to workaround the library limitation and make Software (Mesa) foolproof except if you are running the Microsoft Store app because it is using a technique incompatible with its sandbox mode.
If you are using the Windows installer, you can run the installer again and on a step near the end, there is a set of checkboxes with options:
Click to enable the Remove Shotcut Settings from the Registry and continue.
If you have chosen to use an App Data Directory, there will be a registry value named appdatadir that is set, then you need to look for the file shotcut.ini in the specified folder, open it in a text editor, and remove or change the opengl key to one of:
If you are using the portable or are comfortable to manually edit the registry:
1 - start regedit
2 - navigate to Computer\HKEY_CURRENT_USER\Software\Meltytech\Shotcut
3 - look for the value opengl and change it if found or create it as a DWORD with hex value:
This is almost certainly a problem with the graphics drivers. Intel dropped support for them years ago and as far as I can find - and it's not easy looking, Intel don't make this easy for you, haven't released updated drivers for them in over seven years.
The latest versions of Windows 10 have almost entirely dropped support for "legacy" graphics drivers (now you have to use Microsoft's "DCH" standard), generally older drivers only run well enough to make Windows run.