Ready to download the daily build 2.3.8f of Voyager:
NEW => Array → Added new action (usable also from the main Array management window) to focus with RoboStar on a single star of all nodes without using the default filters and the Offset but directly the final filters. It is necessary to use homogeneous filters such as all narrow or all broadband otherwise the focus could fail
NEW => Array → Added new action (also usable from the main Array management window) to perform the LocalField focus on the whole field of all the nodes without using the default filters and the Offset but directly the final filters
NEW => Array → Added new sequence action without any use of offsets, sequence configuration has been changed to now have this option and decide which filters to use for focus. Obviously, if the focus on a single star (RoboStar) is used, it is necessary to use homogeneous filters for all nodes in the entire sequence, such as all narrow or all broadband, otherwise the focus could fail
NEW => Safety Monitor → Added new Safety Monitor URL Text control for reading the content of remote web pages in the same way as the Text File
NEW => Sequence → Added possibility to reconnect internally to the Sequence without abort the Camera and FilterWheel if present following a CameraShot type error, you can also set how many times to restart before aborting the sequence. It is absolutely not certain that this procedure can be effective for all setups and for all types of errors. The solution is always to fix the camera or its configuration.
MOD => Array → Last used OnTheFly configurations of all command actions dedicated to Array are now stored in profile and not in volatile memory
MOD => Camera → Added memory optimizations for very large sensors
BUG => Array → The enable/disable command buttons of the Array Management Window were not always consistent with the current state of the Array
BUG => Array → Some array action configuration windows did not correctly disable the settings and commands of unconfigured or disabled nodes
BUG => Array → If the start of the sequence was requested with the mount in No Goto Zone for meridian cross the sequence waited for the exit from the no goto zone even if the requested object was not in this zone
BUG => Array → in case of use of the virtual mount on an instance in a second PC a GeoData Cache absence error was generated which interrupted the Setup connection. IMPORTANT !!! Bug introduced with version 2.3.8b
BUG => RoboData → Voyager instances from the second onwards used the RoboData database of the first instance
Thanks to everyone have contributed to this daily build with their test and report.
Daily Build is declared potentially unstable … download the last official release version to rollback
All the best