-
-
Notifications
You must be signed in to change notification settings - Fork 792
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
Laggy Performance on Windows 11 Pro #3675
Comments
This is quite an odd ratio, which resulted in a strange FBO size. What is the exact physical resolution of your screen? What if you set the scaling factor to something nicer, like 150%? |
Drivers seem latest, nothing suspicious apart from a sub-2GHz CPU. The main loop runs on 1 core, so single-core speed counts. Stellarium reduces fps when idling. Is it also 5fps when moving the scene by mouse dragging? Configure in the settings dialog. Maybe it's just too many pixels for the Intel GPU? Try reducing resolution (https://github.com/Stellarium/stellarium/wiki/Common-Problems-for-the-current-version#windows-gui-scaling) |
I set the scale to 100%, restarted, and the frame rate raised to around 8.6 fps with the Atmosphere and the Artificial SAtellites disabled. When zoom in, the frame rate increases to 10 fps.
Dragging the mouse doesn't affect the frame rate. The odd thing is that the GPU doesn't pass the 40% of use. |
What about the CPU load caused by Stellarium? Is it much higher than 12,5% (indicating main thread occupying one core)? I mean, my really terrible 1GHz dual-core netbook from 2013 has 8fps (on a 1366 screen). If you don't need them, disable satellites. Use only few text labels (you mentioned DSO labels), these are surprisingly costly. |
The CPU is under 4%. Disabling DSO Labels doesn't change the frame rate. |
Switching between 5000 DSO labels and none has a high impact. 2-5 DSOs of course is not perceivable. |
Does this happen on a clean install with the default settings? Intel UHD Graphics 620 is what I have on my laptop, and it doesn't seem too slow (though I'm using it on a FullHD screen). But, what if you try Also, please tell the exact physical resolution (or model) of your monitor. |
Yes, but the difference is barely visible.
How do I install the weekly build in Windows?
|
Get an installer here and install it as usual. |
OK, some interesting news. Firstly, I installed the weekly build qt5 version. On this one, I got spikes of around 28 fps when dragging the mouse, and after, a steady 17,9 fps. Secondly, I installed the qt6 version, and the performance was pretty much the same I got with the stable version. So, I reinstalled the qt5 version and launched. And I got, more or less, the not so good performance of the qt6 version... I closed and opened again, and the performance recovered, with 17,9 fps and spikes of around 28fps when dragging the mouse. On both versions, the CPU is around 3-4%, and the GPU around 40% of use. So, this looks a bit weird... |
That indicates you have native 28fps when interacting, which is adequate for the Intel GPU, and idle rate of 18fps which is probably default. You can set the latter in the Configuration/Tools dialog. |
I searched over the config.ini file, but couldn't find the idle rate or any frame rate related parameter. What am I missing? |
You did not read instructions properly.
|
OK, sorry, I got it know. But the settings are 18 fps minimum and 1000 maximum. |
Yes, intents. Low to conserve energy, high for fluid display. 18 can usually be met, 1000 usually won't (just means as fast as system can go). |
@psmelo1975 does it work OK for you now, can we close this? |
Hello @psmelo1975! We really need your feedback. |
Hi.
I installed the Stellarium 23.4 version on a Dell Latitude 7390. 8GB Ram, GPU UHD620, CPU I8350, outputting to an external monitor 2.5k resolution. Running Windows 11 Pro updated.
My problem is the very low frame rate. The best I can get is around 4 to 5 fps. With the CPU barely touched, and the GPU running at around 30%.
I tested the other modes, like Single Buffer, Angle mode and so on. The results were the same or much worse, adding some issues with the DSO labels.
Here is the log:
The text was updated successfully, but these errors were encountered: