Failed to probe OpenGL

[malderli 0]

Hello. I've got a problem. When i try to launch Cura 4.8/4.7 the message "Could not probe OpenGL. This program requires OpenGL 2.0 or higher. Please check your video card drivers" appears. I have modern GPU AMD Radeon RX 550 in my ThinkPad E580. The system is up to date (Windows 10 Pro 20H2/19042.746). Latest AMD Pro drivers installed (version 20.10.27.05-201027a-360165C-RadeonProEnterprise). What is the problem?

Edited January 24, 2021 by malderli

[ahoeben 1,695]

The problem is that when Cura asks your system if it supports at least OpenGL 2.0 (after first asking if OpenGL 4.1 is supported), your system says "no".

 

Are you perhaps trying to start Cura over an RDP ("Remote Desktop") connection? If so, that is known to interfere with your system reporting about its OpenGL capabilities.

[malderli 0]

No, I dont use RDP. I use Cura locally. One more thing: everething worked before I reinstalled my system

[ahoeben 1,695]

15 hours ago, malderli said:

everething worked before I reinstalled my system

This is indicative - to me - that your gpu driver is the problem. Either you don't have a properly installed driver for your gpu, or the driver specifically excludes support for OpenGL. I would not think the latter is likely.

[onedumbtrucker 0]

As this is the first google search result I would like to add the solution I found. I have used this fix a number of times and confirm it works for 4.13.0 and 4.13.1.

 

The issue seems to be the open gl library file "opengl32sw.dll" that installs on my machine. My laptop is 64bit Win10 Pro and this library maybe does not work with something.

 

Replacing this dll with the version "opengl32.dll" works every time. I don't remember where I got it from, maybe a web search or maybe an older version but whenever I install a new version it will be the only file left in the folder for the old versions as it is not in the install log so I just copy it into the new installation directory and bingo, works fine.

 

No idea if this affects performance but it works and I have not found any functionality not work yet.

Edited January 28 by onedumbtrucker

[ahoeben 1,695]

If you have to manually put dll files in places, then something in your system is broken. You risk putting your system in a state where manually putting dll files in specific places is the only way to solve issues. It should only be a last recourse.