[ANSWERED] OpenGL 2.0 or higher
-
OpenGL 4.6 not detected on ASUS ROG Zephyrus 2022 with Radeon 6700S
Hello,
I am experiencing an issue with Isadora where it fails to detect the correct OpenGL version on my system. Even though my laptop fully supports OpenGL 4.6, Isadora reports OpenGL 1.0 and refuses to start.
System Details:
-
Laptop: ASUS ROG Zephyrus 2022
-
GPU: AMD Radeon 6700S (dedicated)
-
Windows 11 64-bit
-
AMD Adrenalin Drivers: latest version installed
-
Isadora Version: latest available (4.3.1)
-
The issue occurs with both Isadora 3 and Isadora 4
Steps I have already tried:
-
Verified GPU and OpenGL support
-
In the AMD Radeon Software, OpenGL 4.6 is reported correctly.
-
OpenGL Extensions Viewer confirms OpenGL 4.6 is available.
-
-
GPU settings
-
Set Isadora to “High Performance” in Windows Graphics Settings. (I also tried to assign the other gpu which didn't help either.)
-
Set GPU mode to “Ultimate / dGPU-only” in Armoury Crate.
-
-
Administrator mode
-
Attempted to start Isadora as administrator.
-
-
Overlays and background software
-
Closed Discord, Steam, Radeon Overlay, MSI Afterburner, Nahimic, and all other background apps that might hook OpenGL.
-
-
DLL workaround (tried to force OpenGL DLL)
-
Unable to locate standalone AMD OpenGL DLL (
amdvlk64.dll
oratio6axx.dll
) in the system or driver folders. Modern Adrenalin drivers appear to integrate OpenGL differently, so the classic DLL copy method does not apply.
-
-
Display testing
-
I also tried connecting an external display, as in the past this resolved this issue, but it did not solve the problem this time.
-
-
Compatibility checks
-
Verified Isadora is not running in compatibility mode.
-
Tried on the internal laptop display only, with no external monitors.
-
I've been reading several posts on here but nothing has solved this problem for me. Does anyone have any ideas, what else I can try?
Best regards
Rio -
-
There is a known issue where recent AMD graphics drivers are causing this error/message.
Users have had success installing older driver versions. This seems to be an issue on a select range of machines, we are looking for a solution we can implement for the next Isadora release.