Captain's Log 2.1.6 Released

Nov. 10, 2017

Notes :

Should be safe to upgrade from CL 2.0.0. NOTE: your GALAXY.db will be upgraded and will no longer be compatible with CL 2.0.0 so back everything up.
Should be safe to upgrade from 2.1.3 - 2.1.6 beta 4.
Uninstall other versions of CL2 before installing.
Otherwise just uninstall CL2 before installing this version, if you want to err on the safe side.

If you see Luminosity values are missing for previously scanned stars for which the game's Player Journal provided that value, create a new blank trip DB, highlight it and hit the Import Journals button - this will update/refresh the starsystems from the scans in the Journals with any Luminosity values in more recent Journals. Then select your current live Trip database and click the Switch To button to reload it. Luminosity values should now be visible for stars which have them.

If you notice any oddness with AeBe stars (i.e. they don't appear in Captain's Log after a scan), hit the "Reset star/planet to default values" button in the DB Tasks panel of the Trip Databases tab in the Configuration window, then restart CL2. This fixes a legacy problem with AeBe stars which was introduced when CL2 2.0.0 was released. This is only for those that notice they have odd beheviour as desribed with AeBe stars. If you don't have this problem, no need to worry.

DOWNLOAD from from the download page.

Changelogs

Captain's Log 2.1.6

- store total value of planets calculated in PlanetTableWidget
- store total value of stars calculated in StarTableWidget
- BUGFIX : don't send total trip value to the system value visibility checker function. Dolt.
- ENHANCEMENT : A lot of work done to make the Overlay WAY more responsive when scanning stars and planets, which once and for all stops the first planet data showing up in the Overlay widget before the latest-scanned planet data.
- added journalSupercruiseExit signal (& parser) to JournalParser class.

- ENHANCEMENT : When exiting supercruise near a planet, CL2 will auto-select that planet's details. (Thanks Cometborne for the idea!)
- BUGFIX : made the planet data parser more robust to prevent missing body parameters from preventing the Nav Beacon Scan data import from completing. Triton in the Sol system, I'm looking at you -.-
- also changed the Nav Beacon Scan bits of the JournalParser to be more DRY. Less code! Less bugs! Honest!
- a couple of internal variables renamed to make more sense. It helps. A lot.
- tidied up some nav beacon scan update code. Now all neat and tidy.
- BUGFIX : get the GALAXY database AeBe de-duplication function working again. This fixes a legacy bug in the GALAXY database from CL2 2.0.0 where AeBe star types were duplicated about 3 times and which confuses CL2 when looking up the AeBe type for various things like scans of that type etc. If you encounter weirdness in CL2 whereby you get no information about AeBe star types, then you need to go into the Configuration Manager and click on the blue "reset star/planet to default values" button, which will also de-duplicate the AeBe star types in the GALAXY database, and should fix the weirdness. I tried to think of some way of making this bugfix text much, much longer to read but couldn't... Oh, there ya go! :D
- BUGFIX : JournalParser float values are now all converted to text before being emitted as a Signal() to the relevant handlers.
- BUGFIX : v2DBInterface - signal handlers now receive floating point values as text and converts them back into floats. Pennywise eat your heart out. Here, THEY ALL FLOAT!
- BUGFIX : removed incorrect luminosity floating point column from the database and added a starluminosity text column instead
- altered the attempt_repair_of_galaxy_database() functions to take into account further database migrations
- BUGFIX : properly use and take note of a star's Luminosity from a scan.
- added a database migration script to alter the GALAXY database with the new luminosity column.

Captain's Log 2.1.6 Released

Changelogs

Your browser is out-of-date!