-
-
Notifications
You must be signed in to change notification settings - Fork 854
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
Graphics issue in 24.1, qt6 and qt5, Latest drivers reinstalled, Intel UHD #3692
Comments
Please try run Stellarium with |
Thanks for the quick reply. With
|
I can try building Stellarium from source in the next few days and throw some breakpoints here and there, but my C/C++ skills are quite basic. Thanks for looking into the issue and for the quick response. |
The garbled screen can't be explained by anything except poor drivers. At least the kind of screen I saw in your video hasn't occurred in my experience except with the reverse-engineered Linux drivers ( The name "Intel(R) HD Graphics Gen11" along with the CPU "Intel(R) Pentium(R) Silver N6000 @ 1.10GHz" also hints in this direction, because normally Pentium N6000 has a UHD Graphics GPU, not HD. Try looking on Intel's website for the drivers for your specific GPU. Failing that, try ANGLE mode in the Qt5 version of Stellarium. |
TL/DR; Angle & Direct3D11 works.
The namings UHD/HD are different depending where I look: dxdiag, GPU-Z, GPU Caps Viewer and so on. I have tried with the latest drivers from both Intel and from Asus which is the manufacturer of the laptop. For intel I have used their utility Intel Driver & Support Assistant so the driver's can't be wrong I guess. https://www.intel.com/content/www/us/en/support/detect.html For Asus I went to their support website and downloaded the latest drivers: https://www.asus.com/laptops/for-home/vivobook/vivobook-13-slate-oled-t3300/helpdesk_download?model2Name=Vivobook-13-Slate-OLED-T3300 I've tried Angle Direct3D11 and it works as it should, around 25fps in both windowed and full screen modes. Same for the other Angle mode, Thanks for the tip about angle. I'll report back after I let it run for a few hours. |
Update on Angle with Direct3D 11 |
Hello @dariusmihai! Please see FAQ in the wiki: |
Sorry, but this issue seems out of our hands. |
Hello.
![main-image](https://private-user-images.githubusercontent.com/34218062/317105338-28e63673-c876-4ae0-85ce-4fca6c5e78a2.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNjYyMDMsIm5iZiI6MTczOTE2NTkwMywicGF0aCI6Ii8zNDIxODA2Mi8zMTcxMDUzMzgtMjhlNjM2NzMtYzg3Ni00YWUwLTg1Y2UtNGZjYTZjNWU3OGEyLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA1MzgyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiY2QxMWU3MjlhNGY4ODE2NjhjZjg1OGIyNzMzNGQ5OGE4NTJlMGUxYmJlZDVkZmFmZGRkMWJmYmEyYmI2MDEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.JLfeljBs_xHF99UXdQECEIDXp0Fiul7bZ7C5g6ujZyk)
I've been experiencing a graphics issue with Stellarium.
Video showcasing this: https://youtu.be/fLxLRETd12g
Image:
I've already looked in the wiki, on this issue tracker and on the forum. Only found some low-fps related issues in the forum but not really the same as this one.
Expected Behaviour
Stellarium can be used in full screen.
Actual Behaviour
Upon doing the first move in full screen, the screen becomes garbled. It stays like that until I get out of full screen.
Also the frame rate is about 2-3 fps even before the garbling, in both windowed and full screen.
Steps to reproduce
Open Stellarium v24.1.0 - can be Qt6 or Qt5.
Issue 1: At this step Stellarium is very slow, 2-3 fps.
Go to full screen.
Move/Rotate the view.
Issue 2: The screen becomes garbled (please have a look at the video).
Depending on how garbled the screen is, I'm usually able to find the button to exit full screen.
At this point the graphics go back to un-garbled, but still at 2-3 fps.
System
Logfile
The text was updated successfully, but these errors were encountered: