AstroPlanner Beta Testing
Introduction
Anyone is free to download and test the latest beta version of the application. Please note that beta versions of the application have a built-in expiration date that is 120 days after the release date. After that date, you can still use it, but you'll be "nagged" to download a more recent release. This is to prevent bugs being reported on older beta versions that have already been fixed in later releases.
Please discuss beta issues only on the Beta Testers mailing list. Click here to join/leave the list.
Click here for more information on how to report a bug.
V2.4 Notes:
- This version requires a larger minimum screen size: 1280 x 720 pixels (2560 x 1440 pixels for Retina/HiDPI).
- This version might not be fully backwards-compatible with V2.3, so backup before trying it, especially the Image and Observation databases.
- As of V2.4a11, the Mac version will run natively on M1-based Macs.
- As of V2.4b6, the Mac and Windows-64 versions are compiled with "aggressive" optimisation switched on. This should make the application perform a bit faster. However it makes the code file a lot bigger, and it takes forever to compile (not your problem).
- As of V2.4b14, the minimum OS requirements for running the application are: MacOS 10.14 or later, Windows 8.1 or later. For the present, betas that run with MacOS 10.11 - 10.13, and Windows 7 SP1 - 8.0 are included below.
- Note that only the 64-bit, non-special versions of the application have been optimised for speed. However, you won't notice much of a difference in real life.
This page last modified: 2024/04/18 19:23 (Pacific time)
Download
Version | Release Date | Expiry Date |
2.4b27 | 2024/02/04 | 120 days from Release Date |
Macintosh
64-bit Application (.dmg) | Download | 160.3MB | 64-bit version. Intel-based Mac with MacOS 10.14 or later. Apple Silicon-based Mac with MacOS 11 or later. |
64-bit Application (.dmg) | Download | 106.5MB | Special version for MacOS 10.11 through 10.13. Intel-only. |
Windows
32-bit Application (.exe) | Download | 91.9MiB | 32-bit version. Installer. Windows 8.1 or later |
32-bit Application (.exe.zip) | Download | 91.4MiB | 32-bit version. Zipped installer |
64-bit Application (.exe) | Download | 87.7MiB | 64-bit version. Installer. Windows 8.1 or later |
64-bit Application (.exe.zip) | Download | 87.2MiB | 64-bit version. Zipped installer |
64-bit Application (.exe.zip) | Download | 143.6MiB | Special 64-bit version for Windows 7 SP1 through 8.0. |
32-bit Application (.exe.zip) | Download | 153MiB | Special 32-bit version for Windows 7 SP1 through 8.0. |
Both platforms
User Manual (.pdf.zip) | Download | 82.8MiB | V2.4 beta user manual |
Note: Beta versions of the application typically do not include the user manual or scripting manual in order to reduce download size.
Release Notes
A list of unresolved bugs can be found here, and feature requests here.
Version: 2.4b28 | Release Date: Soon | Fixes: 11, Enhancements: 2 |
ID: Status: Date: |
Event Scripts The Event Scripts... setting Enabled->Global does not appear to work correctly. An event that is marked Global is not available and executed by all plan documents, but rather the same as Local and is only available in the current plan. Creating a Global, When plan document is opened, myscript only works in the current document. Restarting AP and opening a different document does not run the global script and the opened document does not have a reference to the event in Event Scripts... Resolution: |
ID: Status: Date: |
FindCityDialog.FindCity: Out Of Bounds Exception Exception Type: Out Of Bounds Exception 1: Sub FindCityDialog.FindCity( FindCityDialog )
searching for a place in Spain Resolution: |
ID: Status: Date: |
DateExtensions.AsDateTime: InvalidArgumentException Exception Type: InvalidArgumentException 1: Sub DateTime.Constructor( int64, int64, int64, int64, int64, int64, int64, TimeZone )
Opened Plan creation wizard in an unregistered copy of Astroplanner. The system produce the application exception message.. If I select continue, Astroplanner close Resolution: |
ID: Status: Date: |
Sorting by Magnitude won't Allow Secondary Sorting There are many objects with the same magnitude so this should allow you to continue sorting after going by Magnitude. Steps to Dupe: All the other fields now go gray. Attachment: Companion Objects.apd Resolution: |
ID: Status: Date: |
Fix for menu item enable bug There's a bug in the latest compiler framework that enables all menu items, whether or not it's applicable. Analysis: Resolution: |
ID: Status: Date: |
The Fix for Report ID 7745 Causes Sorting Problems, especially When Using Column Formats Trying to prevent null sorts stops effective sorting techniques, especially when using certain column formats. My bread and butter sort was for Best Time | Transit Time| Altitude [Ascending or Descending would be situational] with Best Time at every 15 minutes and Transit Time at every 5 minutes. To see if these changes would affect my sorting I set both Best Time and Transit Time to Actual Time and looked at the results. I determined that this will really take away from my ability to order things like I used to. I attached a print screen to help illustrate. Steps to Illustrate: Attachment: Tagged Columns.PNGAttachment: AstroPlannerV2-W321.prefsAttachment: Main Objects1.apd Analysis: Resolution: |
ID: Status: Date: |
After upgrading to 2.4b27, User-Defined Fields are Causing Crashes It is giving me a RunTime Error, with no bug report available, and crashing when going to edit a User-Defined Field. Many times it crashes right when I click on it. Sometimes, it does so after trying to append info to it. Steps to Duplicate: 5. Click OK and the program will kick you out. Attachment: AstroPlannerV2-W32.prefsAttachment: 2024-01-30 Current List.apdAttachment: RunTime Err wih UDFs.PNG Resolution: |
ID: Status: Date: |
RA/Dec JNow coordinates Add (optional) RA/Dec coordinates for Epoch JNow to the object list Resolution: |
ID: Status: Date: |
Issues with Syncing I have two computers an M3 MacBook Pro laptop and an M1 Mac mini. In astroplanner I have enable syncing and sync via iCloud. I have also made sure preferences was selected in "items to sync" as well as both computers are pointed to the same path directories. My issue is that I have set up my devises/scopes and location on my laptop and I don't see that data syncing to my Mac mini. Analysis: Resolution: |
ID: Status: Date: |
GraphicsExtensions.PolygonToGraphicsPath: Out Of Bounds Exception Exception Type: Out Of Bounds Exception 1: Function GraphicsExtensions.PolygonToGraphicsPath( Pair() ) as GraphicsPath
a. Was displaying SkyView with several dozen objects and incrementing time one hour. b. I have now tried several different plans. When I select an item and then click on SkyView, I get this error. Thiw was workoing. Not sure what option (of several) that I changed over the last couple of days that made this stop working, but now Sky view is impossible to use. Each time I utilize it, the app crashes. c. In the Sky View tab, set the time to 22 hours in the Date/Time widget, and this exception popped up.
I switched from objects to sky view. That's it...
I select any plan file, select Sky view, and the exception pops up. I have tried with several plans; it seems to be a global problem. Analysis: Resolution: |
ID: Status: Date: |
Selected objects displayed even when set to not display In the Sky Chart, with the option Objects under Plan Objects selected (tickmarked) and set to Highlighted, both highlighter objects (in the list of objects in the Objects tab) and objects selected in the list of objects are displayed, instead of only highlighted objects. Analysis: Resolution: |
ID: Status: Date: |
Update the SDSS image download to use DR18 The current version of the application accesses an older release of SDSS image data (DR7). Update this to use the latest release (currently DR18). Resolution: |
ID: Status: Date: |
Unable to download catalogues When attempting to download a large catalogue the download aborts with the message "Error: Timeout trying to download inventory!". Analysis: Resolution: |
Version: 2.4b27 | Release Date: 2024/02/04 | Fixes: 27, Enhancements: 1 |
ID: Status: Date: |
Observation database window issue The observations list does not remember its column width settings. Resolution: |
ID: Status: Date: |
Hilighting does not update properly with time change Highlight selection is set to "Visible." In the Objects window, when changing the Time in the Date/Time widget, the highlighting immediately changes only in the Azimuth and Altitude columns. This is shown in the attached screenshot which was taken immediately after changing the Time from PM to AM. The highlighting is updated appropriately (i.e. across the whole row) once the window is scrolled. macOS Ventura 13.6.4 on an M2 MacBook Air. AP version 2.4b26 (ARM). Resolution: |
ID: Status: Date: |
Observation missing I am trying to enter old observations. When I enter the first observation, all looks well, when I enter the second observation on a second object, its OK, but when I enter the third observation on a third object, the first will no longer display in the log, although the log indicates that there are three observations. If I then delete the second and third observations that do appear, the first appears. The observation count always stays accurate. Any idea of what may be happening? Analysis: Resolution: |
ID: Status: Date: |
AstroPlanner Hangs Editing User-Defined Fields I have AP hanging in multiple documents when trying to edit a variety of text fields. Steps to Duplicate: NM | NO | NT | PH | Alt>32 Resolution: |
ID: Status: Date: |
CatalogueConstants.GetShortTypeName: Nil Object Exception Exception Type: Nil Object Exception 1: Function CatalogueConstants.GetShortTypeName( int64, color, gueConstants.CatalogueObjectType()() ) as string
I had started AP but was using other applications such email. My mouse moved across AP's window and a Nil object dialog popped up. I don't think I clicked, just moved the mouse over. Resolution: |
ID: Status: Date: |
Issues with scripting Several issues with using the TCPSocket framework class. Also, it is possible to start the script running again before the previous instance has completed, causing hard crashes. Resolution: |
ID: Status: Date: |
ShortTermVisibilityCanvas.DrawShortTermVisibility: Nil Object Exception Exception Type: Nil Object Exception 1: Sub ShortTermVisibilityCanvas.DrawShortTermVisibility( Graphics )
Just installed this version(beta 2.4b26) after removing the previous non-beta version and installing this beta version. Resolution: |
ID: Status: Date: |
Entering new observations - values of user fields When entering subsequent observations, values for user fields (in my case: limiting magnitude, seeing, SQM and temperature) for a new observation are copied from an observation logged at a later time and already present in the observation database. The desired functionality would be to have the values copies from the preceding observation. This is probably a bug, but it would only manifest itself if a sessions already contained (an) observation(s) logged at a later time. Resolution: |
ID: Status: Date: |
ShortTermVisibilityCanvas.DrawShortTermVisibility: Nil Object Exception Exception Type: Nil Object Exception 1: Sub ShortTermVisibilityCanvas.DrawShortTermVisibility( Graphics )
Reference bug report 7721. The first opening of any plan file now gives this error.
Reference bug report 7721. I have just reported an error that occurs when any plan is opened. This error then occurs when the location is changed. Astroplanner then give a message requiring that it close. Resolution: |
ID: Status: Date: |
Solar System Object Motion The Solar System Object Motion shows a mark of the asteroids position but does not show the magnitude or time information. I tried checking them on and off individually but still the information does not appear in the FOV. Analysis: Resolution: |
ID: Status: Date: |
Highlighting rule file loading issue If you import a custom highlighting definition file containing rules on user-defined fields, and the plan does not have such a user-defined field then weird stuff happens. Analysis: Resolution: |
ID: Status: Date: |
Eagle Nebula [1] incorrect in Guides Steps to Duplicate: Not certain if this is fixed so sorry I am still on the older version. My highlight rules didn't convert right somewhere earlier on and I want to fix them before upgrading. 1. Go to New Object and pop down Guides. In Common deep-sky objects..., there are two Eagle Nebula choices. I like the idea of two choices with the first one being M16 instead of Seagull, since the second choice is a cluster type and M16 includes the Nebula. Analysis: Resolution: |
ID: Status: Date: |
Lobster Nebula Confusion NGC 6357 has only 2 nicknames, the main one probably being Lobster Nebula. NGC 6618 has many names, the most popular seeming to be Omega Nebula or Swan Nebula, but also including Lobster Nebula. Both of them are named Lobster Nebula in the Guides drop-down, causing some confusion as to which one goes where. Steps to Duplicate: I think it would be good to somehow clarify any objects, which are actually different, but that can share the same nickname. Maybe a Constellation indicator in perins or something. Resolution: |
ID: Status: Date: |
Custom Colors Overwrite Each Other in Highlight Rules When trying to add a second custom color to the pallette, it overwrites the first one. Steps to Duplicate: I am not sure if I am doing something wrong but I was expecting it to take the next spot for a custom color, not to overwrite the previous one. Attachment: Main Objects.apd Resolution: |
ID: Status: Date: |
Adding Minor object corrupts another object If I add a Minor Planet... using the Add Special button then another object in the plan will have its type changed to Minor and its coordinates set to an object below the horizon. I added M33 to the plan that was currently above the horizon (34 degrees). I then clicked Add Special->Minor Planet... and selected (4) Vesta from the MPC list. Vesta is added but M33's type is changed to minor and the coordinates of M33 are now well below the horizon (-61 degrees). Please find attached a screenshot of the M33 entry and then what happens when (4) Vesta is added. Attachment: Screenshot 2024-01-21 222434.pngAttachment: Screenshot 2024-01-21 222604.png Resolution: |
ID: Status: Date: |
Highlighting rules do not work. I updated from the pre 26 beta to the new b26 and the highlighting rules behaviour has changed. Even though rules are not being satisfied they are being highlighted with the rules colour. The problem appears to happen when more than one rule has been specified. I added a rule to highlight in green when Observability is greater than 50 and another rule to highlight in orange when observability is between 30 and 50. The observability column for the two objects in the plan was 45.2 and 42.2 but they are still highlighted green. Removing the second rule removes the green highlighting. I even managed at one point to get striped green/orange highlighting when the observability of both objects was in the 40s. Resolution: |
ID: Status: Date: |
Supernova with SN type I imported a supernova from ASRAS, 2024gy. Its Type was SN. On the Field of View tab the supernova was not shown. If I changed the type in the Object editor to Supernova then it appeared. In fact changing the type to random names (Fred, BigBaddaBoom) made it appear in the FOV tab. I also tried adding SN as a User-defined type on the Field of View Preferences but it still did not appear. Not sure why the default SN type does not appear on the FOV tab. Resolution: |
ID: Status: Date: |
BackupItem.FilePath: Out Of Bounds Exception Exception Type: Out Of Bounds Exception 1: Function BackupItem.FilePath( int64 ) as FolderItem Resolution: |
ID: Status: Date: |
PlanObsAttachment.Path.Set: Nil Object Exception Exception Type: Nil Object Exception 1: Sub PlanObsAttachment.Path.Set( int32, FolderItem )
Working with observations Resolution: |
ID: Status: Date: |
Utility.ReadBOM: I/O Exception Exception Type: I/O Exception 1: Sub TextInputStream.CheckForError()
Resolution: |
ID: Status: Date: |
NexStarMount.GetItem: Out Of Bounds Exception Exception Type: Out Of Bounds Exception 1: Sub NexStarMount.GetItem( o Resolution: |
ID: Status: Date: |
Always Save Changes issue If I close the plan or exit AstroPlanner, I get the Save Changes dialog again even though I selected Always Save Changes previously. Resolution: |
ID: Status: Date: |
Rise/Transit/Set not recomputed when Site changes I just noticed that the Rise/Transit/Set values in a plan document do not change if the Site is changed. Resolution: |
ID: Status: Date: |
Sort List issue Using the Sort List popup allows you to sort the list by up to three fields. This can provide bogus or null sorts if you sort any field after sorting a "continuous" value field, since there is a very small chance that the first field will be equal for two objects. e.g. if you sort by RA, and then Dec, it's unlikely that two objects will have exactly the same RA value, so the second (Dec) value is never used. However, if you sort by a field with "discrete" values, e.g. constellation, type, etc., then it is valid to add a second field (e.g. magnitude). The Sort List dialog should not allow "bogus" sorts. Resolution: |
ID: Status: Date: |
TypeDisplaySelector.!GetSymbol( string ) as int64: Out Of Bounds Exception Version: 2.4b26 Resolution: |
ID: Status: Date: |
Improvements to Comet/Minor Planet import a. Fixed an issue that greatly improves initial import time for objects, especially for large databases such as MPCORB. b. Added a Settings... button for each data source that lets you choose a convenient subset of the imported data (e.g. first 1000 objects, last 10000 objects, etc.) to improve loading time for data. c. Some minor cosmetic improvements. Resolution: |
ID: Status: Date: |
Import comet data Importing comets for the first time is working fine. Analysis: Resolution: |
ID: Status: Date: |
SolarSystemObjectCollection.DeleteCacheFile: I/O Exception Exception Type: I/O Exception 1: Sub FolderItem._RaiseIOErrorAsNeeded()
Wanted to erase Comet cache by right clicking using the IAU Minor Planet Center Resolution: |