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

Yesterday we published first release candidate to version 0.19.0. Please help us test it and report us about finded problems (in this topic or in our bug tracker).

Full list of changes between version 0.18.3 and version 0.19.0RC1 (v0.18.3.16781):
- Added new type of computation for AstroCalc/Phenomena tool
- Added GUI options to change constellations and asterisms font size (GH: #576)
- Added new source to star names and added new additional name to kappa Scorpii
- Added tool to detect Intel C/C++ compiler in our Logger
- Added new method into ConstellationMgr class - getConstellationsEnglishNames() to get English names of all constellations in the selected sky culture [Scripting Engine]
- Added new one script 'Constellations Tour' to organize the tour around constellations of the loaded sky culture [Scripting Engine]
- Added constellation boundaries for Chinese Skyculture (GH: #584)
- Added more values to correctly detect MSVC version
- Added few scriptable methods into HighlightMgr class to manage highlight points
- Added translation support for strings within scripts
- Added Chinese medieval sky culture (GH: #604)
- Added Alipurduar town (West Bengal; India) to the default locations list (GH: #606)
- Added extra check-point for data directory in the StelFileMgr class
- Added DSO textures
- Added sensor crop overlay to Ocular plugin (GH: #612)
- Added tool for allow filetype selection for Screenshots (GH: #623)
- Added core.getPlatformName() and core.isMediaPlaybackSupported() methods into scripting engine
- Added scripting function isModuleLoaded()
- Added graph "Transit altitude vs Time" into AstroCalc/Graphs tool
- Added small simplification to scripting through adding master switch by types for grids, lines and points on the sky [Scripting Engine]
- Added showing labels for named highlights (GH: #638)
- Added allow setting location of User Data Dir via environment variable.
- Added scripting graphics tool [Scripting Engine] (GH: #640)
- Added LMC and SMC as addition names for Magellanic Clouds
- Added classifications support for sky cultures
- Added support 2 southern deep sky catalogues (NGC subset; esp. for southern observers)
- Added armintxe, paleolithic sky culture and landscape (GH: #628)
- Added demo script for martian analemma [Scripting Engine]
- Added support sols for setDate() method [Scripting Engine]
- Added code, who indicate to hybrid graphics systems to prefer the discrete part by default (GH: #649)
- Added support for constellation boundaries thickness (GH: #653)
- Added Maya constellations (GH: #635)
- Added normal maps for planets, moons and minor planets
- Fixed Ependes Observatory location (GH: #581)
- Fixed scaling the distance in AstroCalc
- Fixed naming the stars in AstroCalc tool when non-western skyculture is enabled (GH: #577)
- Fixed sorting of column Distance in Astronomical Calculations' Ephemeris tab (GH: #579)
- Fixed wrong calculation the FOV of CCD in Oculars plugin
- Fixed compile Stellarium without media features
- Fixed behaviour of script (The old script 'Constellations Tour' was renamed to the 'Western Constellations Tour' and updated) [Scripting Engine]
- Fixed documents for core.clear() method [Scripting Engine]
- Fixed unit tests failure on Windows and some linuxes (GH: #586, #587, #588)
- Fixed the user interface problems for lenses in Oculars plug-in (GH: #580)
- Fixed copyright years in CREDITS.md file
- Fixed checker in the StelFileMgr class (GH: #589)
- Fixed macOS User Data Directory in documentation (GH: #593)
- Fixed bug report address for .desktop translations
- Fixed a typo in Scenery3D plugin (GH: #600)
- Fixed selecting LMST, LTST and system_default timezone names
- Fixed math error in StelHips (GH: #599)
- Fixed a potential memory leak in libtess (GH: #598)
- Fixed error for ephemeris calculations time window (GH: #605)
- Fixed description data for textures.json
- Fixed missed translatable strings in StelSkyCultureMgr class
- Fixed CWE-404 issues
- Fixed crash when script tried delete already deleted labels (GH: #625)
- Fixed zooming behaviour
- Fixed time zone issue in AstroCalc/WUT tool
- Changed default constellations font size
- Changed HiPS behaviour: don't show tile if it is hidden by children
- Changed behaviour of version checker: introduced the additional check for latest version
- Changed behaviour of the BottomStelBar::updateText() method (GH: #596)
- Updated Reingold and Dershowitz algorithm of DeltaT (New algorithm was taken from the Calendrical Calculations: The Ultimate Edition book)
- Updated cmake rules for ICC/ICPC support (Intel C/C++ compilers)
- Updated GUI in Oculars plugin
- Updated Stellarium User Guide
- Updated technical documentation
- Updated Amalthea texture
- Updated scripts (added i18n support)
- Updated scripting API: added format specification for screenshots. (GH: #623)
- Updated the code (thanks for PVS-Studio to the finding an issues)
- Updated DSO textures
- Updated textures of LMC (GH: #632)
- Updated nomenclature
- Updated jquery and jquery-ui in Remote Control plugin (GH: #620, #621)
- Updated scripting engine: MilkyWay saturation scriptable now
- Updated scripting engine: expanding the core.clear() method
- Updated Satellites plugin: harmonized function name, added a property [Scripting Engine].
- Updated KoreanCM.isl file - typofixes (GH: #639)
- Updated RemoteSync plugin: suppress unsuitable properties (GH: #642)
- Updated AstroCalc/WUT tool: optimizations
- Updated AstroCalc/Positions tool: optimizations
- Updated AstroCalc/Phenomena tool: optimizations
- Updated contact info for plugins
- Removed a long time abandoned incomplete LogBook plugin
- Remove old deprecated methods in scripting engine
- Remove languages without translators and with translations lesser than 1%

Binary packages: https://github.com/Stellarium/stellarium-data/releases/tag/beta

Let's try make Stellarium better by together.

  • Like 2
  • Thanks 6

Share this post


Link to post
Share on other sites

Excellent Alex, will download and try it, thanks for your hard work.

Edited by Pete Presland

Share this post


Link to post
Share on other sites

Do you have a link, please?

I only seem to be able to get the 0.18.* packages.

Share this post


Link to post
Share on other sites

I know, I tried the link.

On the computers I have tried, it's still taking me to the 0.18.* page. :)

Share this post


Link to post
Share on other sites
4 minutes ago, bingevader said:

I know, I tried the link.

On the computers I have tried, it's still taking me to the 0.18.* page. :)

Stellarium 0.18.3.16781 = 0.19.0RC1

Share this post


Link to post
Share on other sites

Downloaded and installed.

Share this post


Link to post
Share on other sites

The third release candidate has been published today (I hop this is final RC).

Share this post


Link to post
Share on other sites

Hi Alexander

Just downloaded and installed 0.19.0 64 bit onto W10 Pro 64 bit machine

Didnt uninstall v18.3 first.

0.19 starts up the 0.19 splash screen then it vanished and nothing happens.

18.3 still works fine

I have downloaded the 0.19 again and reinstalled - same - splash screen then splash screen vanished and then nothing

Any ideas ?

I really dont want to delete previous version - it took me ages to get the custom landscape just right!

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 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'
      TLDR:
      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.