0.20.4: Windows MESA mode broken

[gzotti]

Expected Behaviour

Calling MESA option on startup runs OpenGL processed on the CPU

Actual Behaviour

The program is running with high CPU load without a visible window.

Steps to reproduce

run with MESA option from start menu

Version 0.20.3 works fine.

System

• Stellarium version: 0.20.4-win64.exe
• Operating system: Windows 10 20H2
• Graphics Card: (Geforce,) but the point is circumventing missing GPU by emulated graphics.

Logfile

If possible, attach the logfile log.txt from your user data directory. Look into the Guide for its location.
log.txt

I consider this less critical than the ANGLE issue #1549, as more users likely run ANGLE. Still pretty annoying.

[alex-w]

@gzotti please check the current master

[gzotti]

No, the shader fix #1549 was independent from this issue. It must have crept in between 0.20.3 and 0.20.4.

[alex-w]

Hmmm... what about use library from https://github.com/Stellarium/stellarium-data/releases/tag/qt-5.6 ?

[gzotti]

No, these are for ANGLE. I'm talking about opengl32sw.dll, the CPU-only solution for ~pre-20009 multicore methusalems without proper GPU. Not sure how many are running this, at 5fps or so... (still better than nothing, in some applications, though).

I try to identify the time of incidence. (now "after October 21, 2020".)

[gzotti]

Ah, here. The multisampling ff4a38b.
This broke Spout and Mesa. That means, calling with Mesa must disable multisampling just like spout does.

[github-actions]

Please check the fresh version (development snapshot) of Stellarium:
https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

[github-actions]

Please check the latest stable version of Stellarium:
https://github.com/Stellarium/stellarium/releases/latest