Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.


Recommended Posts

Today we released version 0.20.2 of planetarium. Thank you very much to community for bug reports, feature requests and contributions!
This is the anniversary version of Stellarium - the project is 20 years old now.

Full list of changes:

  • Added rectangular sensor crop overlay support [Oculars] (GH: #1069)
  • Added support newly marker in Search Tool (Position and Settings tabs) [Search Tool]
  • Added new features for scripting engine: extend the JavaScript classes corresponding to Vec3f and Vec3d [Scripting]
  • Added options to be able to define and use custom FOV circles for Telrad [Oculars] (GH: #1057)
  • Added VecMath tests for the new functions (GH: #1055)
  • Added VecMath feature: Vector/QColor conversions (GH: #1055)
  • Added feature to set current date and time as initial data when AstroCalc/Ephemeris is open [AstroCalc]
  • Added notification for user when version of DSO catalog is mismatched
  • Added support Trumpler Catalogue (Tr or Trumpler) [DSO Catalog, v3.10] (GH: #965)
  • Added support Stock Catalogue (St or Stock) [DSO Catalog, v3.10] (GH: #965)
  • Added support Ruprecht Catalogue (Ru or Ruprecht) [DSO Catalog, v3.10] (GH: #965)
  • Added support "van den Bergh-Hagen Catalogue" (VdB-Ha) [DSO Catalog, v3.10] (GH: #965)
  • Added support search by long name for Trumpler, Stock, Ruprecht, Collinder and Melotte catalogues [DSO Catalog, v3.10]
  • Added new type of DSO objects: region of the sky [DSO Catalog, v3.10] (GH: #1067)
  • Added special case for improve DSO regions visibility [DSO Catalog, v3.10] (GH: #1067)
  • Added outlines for DSO regions [DSO Catalog, v3.10] (GH: #1067)
  • Added marker of center of FOV on the sky [Special Markers]
  • Added circular marker of FOV on the sky [Special Markers]
  • Added rectangular marker of FOV on the sky [Special Markers]
  • Added tool for adjustable thickness of the planetary trails (GH: #1087)
  • Added tool for adjustable line thickness for ephemeris lines (GH: #1087)
  • Added tool for adjustable thickness of the planetary orbits
  • Added a column, showing the elevation of the object at transit times into AstroCalc/WUT tool [AstroCalc] (GH: #1089)
  • Added new category into AstroCalc/WUT tool: regions of the sky [AstroCalc]
  • Added new category into AstroCalc/WUT tool: pulsars (the category available if Pulsars plugin is loaded and pulsars are enabled to display) [AstroCalc]
  • Added new category into AstroCalc/WUT tool: bright nova stars (the category available if Bright Novae plugin is loaded) [AstroCalc]
  • Added new category into AstroCalc/WUT tool: bright supernova stars (the category available if Historical Supernovae plugin is loaded) [AstroCalc]
  • Added new category into AstroCalc/WUT tool: exoplanetary systems (the category available if Exoplanets plugin is loaded and exoplanets are enabled to display) [AstroCalc]
  • Added new category into AstroCalc/WUT tool: active galaxies (this category may include additional quasars if Quasars plugin is loaded and quasars are enabled to display) [AstroCalc]
  • Added new category into AstroCalc/WUT tool: interacting galaxies [AstroCalc]
  • Added new unit tests for DeltaT
  • Added tool to guess the group of satellites by their names [Satellites]
  • Added new groups of satellites [Satellites]
  • Added method to check state of loading for the plugins
  • Added column Elevation for AstroCalc/Phenomena tool [AstroCalc]
  • Added default groups for some satellites from default JSON catalog [Satellites]
  • Added missing tool for define color of regions of the sky
  • Added regions of the sky into Lists of Search Tool [Search Tool]
  • Added tool to export version of Stellarium through StelProperty and Remote Control plugin
  • Added display of epoch of the TLE for artificial satellites [Satellites] (GH: #1096)
  • Added new flag for InfoString of planets, comets and minor planets
  • Added better arrangement of InfoString entries for planets, comets and minor planets
  • Added highlighting for string literals between apostrophes for Script Console [Scripting] (GH: #1101, #1107)
  • Added highlighting for regular expressions for Script Console [Scripting] (GH: #1101, #1107)
  • Added highlighting for multiline comments for Script Console [Scripting] (GH: #1101, #1107)
  • Added highlighting for exponential numeric format for Script Console [Scripting] (GH: #1101, #1107)
  • Added highlighting for hexadecimal numeric literals for Script Console [Scripting] (GH: #1101, #1107)
  • Added separate highlighting of predefined names from that of keywords for Script Console [Scripting] (GH: #1101, #1107)
  • Added red highlighting for unknown methods of Stellarium modules for Script Console [Scripting] (GH: #1101, #1107)
  • Added highlighting for methods of StelSkyDrawer and core for Script Console [Scripting] (GH: #1101, #1107)
  • Added penumbral and umbral magnitudes during lunar eclipse (GH: #1113)
  • Added comments for scripters [Scripting]
  • Added radar cross-section (RCS) data for satellites [Satellites]
  • Added calculate approximaged visual magnitude for satellites from their RCS value [Satellites]
  • Added special case for set RCS value for Starlink satellites [Satellites]
  • Added option to allow drawing of landscape polygon only, if a polygon is defined [Landscapes]
  • Added option to allow a polygon to be drawn in the foreground (out of regular call sequence) [Landscapes]
  • Added option to allow landscape polygon overdrawn onto the 3D scenery [Scenery3D]
  • Added computation an approximated angular size of satellites (the linear size is obtained from RCS value and we use spherical shape for satellites) [Satellites]
  • Added special case for computation an approximated angular size of ISS (we are defined linear size of ISS by "hands") [Satellites]
  • Added tool to display a focuser overlay in the sensor view [Oculars] (GH: #1110)
  • Added checking conflicts for keyboard shortcuts with informing user if conflicts are exist (GH: #1025)
  • Added tool to rescale oversize textures on-the-fly (GH: #1121)
  • Added show a fuchsia-colored replacement texture for wrong filename (GH: #1121)
  • Added NORAD numbers in addition to name of artificial satellite in Satellites Import Dialog for available for search [Satellites]
  • Added function to compute distance between locations, on a flattened planet, in km
  • Added geographic coordinates of center line for total and annular solar eclipse (GH: #1116)
  • Fixed GUI and minor redesign of remaining icons [GUI] (GH: #752, #951)
  • Fixed security issue for jquery (CVE-2020-11022; GH: #1073)
  • Fixed magnitudes for planetary nebulae [DSO Catalog, v3.10] (GH: #913)
  • Fixed data for "Part of a Galaxy" objects [DSO Catalog, v3.10] (GH: #996)
  • Fixed work for clipboard in Script Console tool: avoid effects caused by QTextEdit after copy-paste from HTML pages. [Scripting] (GH: #1070)
  • Fixed telescope syncing for INDI [Telescope Control] (GH: #1065)
  • Fixed "Uninitialized members" issue in Script Console [Scripting]
  • Fixed VecMath features: moved vector/string conversion previously in StelUtils to the VecMath classes (GH: #1055)
  • Fixed VecMath feature:  moved un-inlineable definitions to separate cpp file (GH: #1055)
  • Fixed proper motion output (GH: #1006, #1041)
  • Fixed time delay with planet movement information (GH: #1006, #1103)
  • Fixed cross-id data for open clusters [DSO Catalog, v3.10] 
  • Fixed designations for van den Bergh catalogues [DSO Catalog, v3.10] (GH: #965)
  • Fixed descriptions for van den Bergh catalogues [DSO Catalog, v3.10] (GH: #965)
  • Fixed crash in scripting method core.setObserverLocation() when planet is not defined or not exist [Scripting]
  • Fixed core.setObserverLocation() behaviour: avoid duplicating a country if script programmer provides one [Scripting] (GH: #1076)
  • Fixed object type info for meteor showers [Meteor Showers]
  • Fixed crash when lens are deleted in Oculars plugin [Oculars] (GH: #1078)
  • Fixed (a temporary fix) crash Stellarium when autoconnect is enabled for ASCOM device, but device is not attached [Telescope Control] (GH: #928)
  • Fixed wrong approximated visual magnitude of satellites [Satellites]
  • Fixed guessing groups of satellites [Satellites]
  • Fixed possible cache problem for magnitudes
  • Fixed casting warnings
  • Fixed topocentric/geocentric corrections for ArchaeoLines plugin [ArchaeoLines]
  • Fixed crash AstroCalc/WUT tool when required plugin is not loaded [AstroCalc]
  • Fixed docs and tooltips
  • Fixed visibility of deep-sky regions of the sky
  • Fixed work of regions of the sky in AstroCalc/Positions tool [AstroCalc]
  • Fixed missing object in Bennett's list of deep-sky objects (switched to synonym of missed object) [Search Tool]
  • Fixed missing object in Dunlop's list of deep-sky objects (switched to synonym of missed object) [Search Tool]
  • Fixed visual style for dialog to define custom equation of DeltaT
  • Fixed crossquarter declinations in ArchaeoLines plugin [ArchaeoLines]
  • Fixed updating timezones when loading landscapes/sceneries
  • Fixed updating location panel when off-screen
  • Fixed a deprecation warning for InfoString of planets, comets and minor planets
  • Fixed broken highlighting for quoted string literals for Script Console [Scripting] (GH: #1101, #1107)
  • Fixed broken highlighting for line comment for Script Console [Scripting] (GH: #1101, #1107)
  • Fixed indentation problems in the code
  • Fixed crash when removing already removed selection of constellations (GH: #1104)
  • Fixed jumping of the Moon
  • Fixed visibility for telescope selector when image sensor frame enabled after binocular [Oculars] (GH: #1108)
  • Fixed saving thickness of the planetary trails and orbits
  • Fixed context data for unit measure in Satellites plugin [Satellites]
  • Fixed a stupid bug in ArchaeoLines [ArchaeoLines]
  • Fixed sign of one element in the matrix sequence for nutation
  • Fixed Scripting Engine bug: a script isn't terminated properly via the stop script button [Scripting] (GH: #1118)
  • Fixed crash when texture isn't found (GH: #1121)
  • Fixed the maximum size of CCD: increased limit of sensor size to 100000 pixels [Oculars] (GH: #1123)
  • Fixed visual artifacts on the sky (GH: #475, #1126)
  • Fixed bug in Vec3d constructor for scripting engine [Scripting]
  • Fixed shader bug visible during Total Solar Eclipses only
  • Updated default settings for InnoSetup Script (.iss) file
  • Updated Stellarium User Guide
  • Updated morphological classification of open clusters [DSO Catalog, v3.10]
  • Updated subsystem to obtain the standard magnitudes of artificial satellites [Satellites]
  • Updated method for load standard magnitudes and RCS data for satellites [Satellites]
  • Updated size of window resize border to reduce difficulties to their resize (GH: #937, #1099)
  • Updated InfoString block for artificial satellites [Satellites]
  • Updated minimum height of artificial satellite to check the valid orbit [Satellites]
  • Updated default source of Starlink TLE's [Satellites]
  • Changed behaviour of GUI in Satellites tab in Satellites plugin [Satellites]
  • Changed AstroCalc/WUT tool behaviour: radiogalaxies, active galaxies, quasars, blazars and BL Lac objects was moved from 'Galaxies' category into 'Active galaxies' category [AstroCalc]
  • Changed behaviour of AstroCalc/WUT tool: let's use visual magnitude for all objects without extinction data [AstroCalc]
  • Changed "Arguments" to "arguments" for highlighter in Script Console [Scripting] (GH: #1101, #1107)
  • Removed obsolete scripting methods from StarMgr class [Scripting]
  • Removed duplicate code for InfoString of planets, comets and minor planets
  • Removed "Global" from highlighter in Script Console [Scripting] (GH: #1101, #1107)
  • Removed unused variables

Binary packages you may download at https://stellarium.org website

  • Like 6
  • Thanks 3

Share this post

Link to post
Share on other sites

Congratulations.  Its a superb app.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gstallichet
      I just bought a Celestron 8se.  Which planetarium/scope control software do you recommend, Stellarium or Celestron's Starry Nights,  and why?
    • By pete_81
      Hi guys,
      With new mount and upgraded scope features, now looking to venture into imaging.
      Before I start, I'm not looking to get feedback on polar alignment, mono guidecam, better imaging cameras, etc; this is more a 'dummies guide' setup discussion! I'm not expecting to get great images at this stage, just more the options available, getting over some issues, so that I can jump outside on a clear night with an ideal, foolproof(!), setup for either imaging or visual as time would permit and what may work best for me. As you may guess from the topic name, I'm a mac user (Macbook Pro) and would rather keep to this if possible (whilst I do have Windows (and Ubuntu) via parallels, I'd rather not use these).
      I've got a setup which has worked well for visual, and obviously want to have a couple of 'staple' setups that I can use depending on expectations of night observing or imaging. So far, the best one for me has been the Skywatcher Wifi Synscan controller, which has worked a treat with my Android phone - I use the Synscan app to complete alignment and GOTO stars/planets/DSO etc, or Stellarium_plus after completing alignment. This removes the need for the Synscan Handset and any USB cables to the mount altogether. But I don't know if this will work for guiding.
      That then brings me to my issue on mac - connecting USB(A) between Macbook and Handset, I've attempted to control the mount through Stellarium. Trying each of the available connections (/dev/tty.usbsetial-1420, /dev/cu.usbsetial-1420, and just for sake of it, the /dev/tty.Bluetooth-Incoming-Port and /dev/cu.Bluetooth-Incoming-Port) in the dropdown menu under DeviceSettings/SerialPort, I cannot get the mount to connect (well, more like selecting the telescope and clicking the "Start" on the TelescopeControl just results in the spinning icon and I have to Force-Quit Stellarium and start again with the same result each time. Annoyingly (for fellow mac users!), Parallels/Windows/Stellarium connects and controls the mount fine! As the mount is the newer "pro" type, I also have a USB connection directly under the hand-controller RJ45 and AutoGuider ST4 sockets, but using this still results in the same issue. Another issue I have seen is that when I unplug the USB from the computer when connected to the handset, the date on the controller jumps significantly - for example, last night at ~23:30, I was transported through the local wormhole galaxy to Jan 2048 according to Synscan! Obviously unplugging isn't going to happen during a genuine session, but just wondering if this is a possible issue somewhere?!
      Any other mac users connecting USB directly to the SW 'Pro' mounts?
      Software wise, would folks generally suggest steering away from Stellarium towards KStars or SkySafari(Plus) for controlling the mount?
      Can the Wifi dongle be used for controlling mount from computer (any OS) or do I need to go USB either to handset or directly to mount?
      Is there an issue in using Mac USB to the telescope compared to 'straight' Windows (i.e. PC/laptop with Windows instead of virtual)?
      Anyway, back to topic... I've a Nikon DSLR to use for primary camera at this stage, which would be triggered independently from guiding software. PHD2 is my hopeful choice of guiding software (is EKOS with KStars similar?), with T7C guide-camera on 240mm f/4 guidescope, and at this stage, I can confirm PHD2 at least connects to the camera on OS-X. There is an ST4 port on the camera, but having read several topics, I think I want to pulse-guide directly - is this correct or is ST4 best for this setup? This sorta comes back to software and connections - my understanding is one of the following cable setups for guiding (as a minimum) :
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => SynscanHandset => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => Wifi => SynscaWifi Adapter on AZEQ6
      [using ST4: ST4_on_AZEQ6 => Guiding-camera => USB(A) => Macbook => PHD2] (no additional connections needed if ST4 is used)
      Additionally, I'd like to use an observatory package, say Stellarium/KStars/SkySafari, to select objects and drive the mount, then use guiding software to keep good 'tracking'.
      Where in this train does EQMac fit in, or when is it used?
      What about the 2019 addition to EQMod (ASCOM Alpaca)? Can this be used or is it already in other packages?!
      For Windows users, how does EQMod fit in (if I go down route of getting Windows laptop for controlling things, is the setup similar to above?
      There may be bits in the above that repeat, and for that, I'm sorry, just want to get across the message that I'm new to the guiding but haven't quite settled down into the software/hardware I'm expecting to use for 'goto' and 'guiding'
      For a mac user, what setup and software are folks using for guiding and observatory softwares for the newer USB-on-mount 'AZEQ6/EQ6-R Pro' mounts from SW?
    • By deflatedfruit
      I'm trying to set up Stellarium with my cameras (Canon EOS 1300D and a Canon EOS 2000D) and my telescope (Celestron NexStar 127SLT). I think I've found the correct values for everything like focal length and sensor size etc... but the FoV in Stellarium it is different to what I actually see. I've attached screenshots of the settings, as well as the predicted image and an image I captured using the EOS 1300D and the Celestron NexStar 127SLT (it's not very good, I know).
      Any help would be much appreciated. (And I apologise if I've posted this in the wrong place - I'm new)

    • By alexwolf
      Today we published a fresh weekly snapshot of Stellarium (v0.20.2.18140): https://github.com/Stellarium/stellarium-data/releases/tag/beta
      And we need some feedback from users. At the moment we need to know your opinion about changes in 2 plugins - Satellites and Oculars. Of course we'll accept your opinion about changes in other parts of the planetarium too, but those 2 plugins in our focus.
      Thanks for your attention and testing.
    • By RobertK
      I've always used the web version, but since I got the telescope I decided to install the full desktop version. I managed to save my setup and eyepieces etc.
      Things that I unable to save and not sure whether I should be able to:
      - start in Windowed mode
      - fixed both settings and viewing bars bottom left corner
      - Object information - I set my 'Customised' options, but after relaunching the app they are lost_
      - basic stuff like date format, start-up time (default to 10pm)
      - I think I can say that NONE of the Configuration [F2] settings save
      - Sky and viewing options window [F4] - NONE of the options changed here save between sessions
      The only thing that saves is .. my location.
      Am I missing a plugin, some sort of trick to save those, should I reinstall or does Stellarium simply not save these F2 and F4 settings between sessions?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.