Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stellarium-1.1.1-qt6-win64.exe show only blank / black screen #2803

Closed
tflyer-rgb opened this issue Nov 1, 2022 · 29 comments · Fixed by #3414
Closed

stellarium-1.1.1-qt6-win64.exe show only blank / black screen #2803

tflyer-rgb opened this issue Nov 1, 2022 · 29 comments · Fixed by #3414
Assignees
Labels
bug Something likely wrong in the code
Projects
Milestone

Comments

@tflyer-rgb
Copy link

Expected behavior

Show normal sky view after starting the program and not only a blank / black screen

Actual behavior

The application show only a blank / black screen after startup.

Steps to reproduce

Upgrade from version stellarium-1.22.3-win64.exe to stellarium-1.1.1-qt6-win64.exe

I try to start the application in normal, MESA and ANGLE mode always with the same result. The same result was with version 1.1, 1.0 works fine.

Stellarium version: stellarium-1.1.1-qt6-win64.exe
Operating system: Windows 10 21H2 (Build 19044.2130)
Graphics card: AMD Radeon HD 6700M
Screen type: Notebook LCD resolution 1366 x 768
log.txt

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

Thanks for adding your first issue to Stellarium. If you have questions, please do not hesitate to contact us.

@10110111
Copy link
Contributor

10110111 commented Nov 1, 2022

Does pressing F11 twice make it work?

@tflyer-rgb
Copy link
Author

Pressing F11 twice works, with and without startup option --opengl-compat

@gzotti
Copy link
Member

gzotti commented Nov 2, 2022

It seems the Radeon HD is blacklisted from OpenGL use by Qt6, and falls back to Mesa. Use a Qt5-based build (version 0.22.4) for better performance.

@10110111
Copy link
Contributor

10110111 commented Nov 2, 2022

It seems the Radeon HD is blacklisted from OpenGL use by Qt6

This would be strange: it isn't present in the blacklist.

@gzotti
Copy link
Member

gzotti commented Nov 2, 2022

There must be a reason why the logfile says Mesa/OpenGL3.0. And I agree, we should build a more recent Mesa now that could offer 3.3CoreProfile.

@10110111
Copy link
Contributor

10110111 commented Nov 2, 2022

There must be a reason why the logfile says Mesa/OpenGL3.0

Of course there must be, but I don't think the hypothesis of blacklist is plausible due to what's actually present in the blacklist. Is there any way to enable more logging to find out what's going on?

BTW, I have reproduced this problem on... Wine! Here I get OpenGL 4.6 on Intel UHD Graphics 620, not software rendering.

@alex-w alex-w added this to Needs triage in OpenGL/GLSL via automation Nov 2, 2022
@alex-w alex-w added the bug Something likely wrong in the code label Nov 2, 2022
@zeklh
Copy link

zeklh commented Nov 2, 2022

I have the same problem. F11 works. But there is another problem. When I zoom into the moon, planets or deep sky objects which are extended like galaxies they disappear at a certain zoom level. There is only the background to be seen. This is independent whether I activate atmosphere or not.

@10110111
Copy link
Contributor

10110111 commented Nov 2, 2022

When I zoom into the moon, planets or deep sky objects which are extended like galaxies they disappear at a certain zoom level.

This is a separate problem, to be treated in another issue.

@zeklh
Copy link

zeklh commented Nov 3, 2022

Created a new issue

@alex-w
Copy link
Member

alex-w commented Nov 20, 2022

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

@zeklh
Copy link

zeklh commented Nov 22, 2022 via email

@alex-w alex-w moved this from Needs triage to In progress in OpenGL/GLSL Nov 24, 2022
@alex-w
Copy link
Member

alex-w commented Nov 24, 2022

According this report the issue is fixed now

@alex-w
Copy link
Member

alex-w commented Nov 24, 2022

Press F11 twice. It's a bug.

Please more details

@zeklh
Copy link

zeklh commented Nov 24, 2022 via email

@zeklh
Copy link

zeklh commented Nov 24, 2022 via email

@alex-w
Copy link
Member

alex-w commented Dec 14, 2022

@zeklh

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

@gzotti
Copy link
Member

gzotti commented Dec 20, 2022

Update on modernizing Mesa:

  • Download from https://github.com/pal1000/mesa-dist-win/releases
  • copy x64/{libglapi.dll,libgallium_wgl.dll,opengl32.dll} to where the executable stellarium.exe is.
  • set environment variables: QT_OPENGL_DLL=opengl32.dll, QT_OPENGL=software, GALLIUM_DRIVER=llvmpipe
  • run Stellarium with Mesa 22: OpenGL3.3 core.

@alex-w alex-w modified the milestones: 1.2, 23.1 Dec 24, 2022
@alex-w
Copy link
Member

alex-w commented Mar 13, 2023

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

@gzotti
Copy link
Member

gzotti commented Mar 19, 2023

Shall I write these instructions into the wiki, and we close this? Or does sb want to build Mesa with the usual filenames to avoid setting environment variables? (These could be set on the fly when --mesa-mode is called)

@10110111
Copy link
Contributor

Why not simply include whatever is needed into the distribution? These instructions are just a kludge that the users shouldn't need.

@gzotti
Copy link
Member

gzotti commented Mar 19, 2023

Agreed. There are still 2 options. These existing files as outlined (instead of Qt's outdated opengl32sw.dll), with changes in the --mesa-mode call to set envvars, or build new Mesa libs from sources with the names like opengl32sw.dll. The first is easier IMO and could go into 23.1. We may need to add whatever license/acknowledgment is required to include modern Mesa. @alex-w ?

@alex-w
Copy link
Member

alex-w commented Mar 20, 2023

Probably including modern Mesa into installation package will be best solution

@gzotti
Copy link
Member

gzotti commented Mar 20, 2023

Argh, and just now this method above does not work any longer... (tried Mesa 22.3.1 and 23.0.0)

@alex-w alex-w modified the milestones: 23.1, 23.2 Mar 21, 2023
@alex-w alex-w modified the milestones: 23.2, 23.3 Jun 16, 2023
@gzotti
Copy link
Member

gzotti commented Sep 12, 2023

Tested with 23.1.17, and it works. Mesa23 delivers OpenGL 4.5 CoreProfile. We can set the envvars in the CLI wrapper. But the 3 relevant DLLs should be placed into the repo somewhere, and the installer creator should pack then those instead of the outdated Mesa which Qt provides.

@alex-w where to put the DLLs?

@alex-w
Copy link
Member

alex-w commented Sep 12, 2023

@gzotti please see rules in appveyor.yml file

@gzotti
Copy link
Member

gzotti commented Sep 12, 2023

I am afraid I have no idea what to do :-( Please get involved in #3409.

@gzotti gzotti modified the milestones: 23.3, 23.4 Sep 15, 2023
@gzotti gzotti mentioned this issue Sep 16, 2023
14 tasks
OpenGL/GLSL automation moved this from In progress to Done Oct 14, 2023
@alex-w alex-w added the state: published The fix has been published for testing in weekly binary package label Oct 23, 2023
@github-actions
Copy link

Hello @tflyer-rgb!

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

@alex-w alex-w removed the state: published The fix has been published for testing in weekly binary package label Dec 23, 2023
Copy link

Hello @tflyer-rgb!

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something likely wrong in the code
Projects
OpenGL/GLSL
  
Done
5 participants