Common problems with version 0.16/0.17

Created by gzotti on on 2017-06-21
Last updated by:
gzotti on on 2018-01-20


Hardware requirements have not changed since V0.13. Stellarium should work on most computers from 2010 and later, and on older computers equipped with dedicated graphics cards from around 2008 or later, when drivers are up-to-date.

For old computers, we keep a branch of the last series based on Qt4 still alive. Please use version 0.12.9. It included a few backports for important new features, but please note that this old version does not receive much focus.

If you are new to Stellarium and are in doubt that something may not work as expected, please see FAQ on Common Problems with V0.13 and 0.14/0.15 ).

This is a known long-time defect for the default OpenGL mode on Windows when you have Mouse Trails enabled or another reason to use a "software cursor", like f.lux screen color temperature modifier.

Workaround (1) Use ANGLE mode when you need mouse trails or f.lux.
Workaround (2) Make sure to switch off mouse trails to avoid this problem.

On Windows and with some older models of NVidia GeForce (reported for 580M, 770), the color settings dialog in the gridline panel and ArchaeoLines plugin hides when Stellarium is running in Fullscreen and OpenGL mode. The color dialog works in ANGLE mode. On a GeForce GTX 960M we see no problem.

We interpret this as NVidia driver issue. If you are affected, run Stellarium in ANGLE mode.

(2) Mac OS X problems:

We received reports about slowdown of Mac systems compared to 0.15.1. It took three months of repeating the same complaints until one report indicated that only trackpad interaction is slow while mouse works as fast as it has worked previously. This was the first useful hint where to look.
Unfortunately we do not have any developer with a Mac system. It seems to be a problem in the underlying Qt framework. Any help, working patches, hardware donations, etc. welcome.

(3) HiDPI issues: See FAQ


We have finally integrated time zone handling and so got rid of the time zone plugin. Time zones are set in the location panel.
When you configure your own location, make sure to assign a proper time zone name consisting of continent/city notation, else daylight saving time (DST) rules cannot be applied. Assigning UT+/-offsets is possible, but prevents DST.

Times before 1848 are usually shown as local mean time. Time zones were not even discussed before this date, and their use came actually much later. Also when you click on the map to select a site, we must apply Local Mean Time for now because we have no way of looking up the time zone. Please use the dropdown button to select some appropriate timezone for your site.

You can even use local true solar time, i.e. a time where the sun is always highest at 12:00 when it crosses the local meridian. This is the "natural" time shown by sundials.