v2.5.0 : Fixes and Faster!

CMDR Genar_Hofoen

July 26, 2022

Version has been upped to 2.5.0 from 2.4.0 because there's been a change in how Trip databases are loaded, making it orders of magnitude faster!

Other fixes and tweak have been made, see the changelogs below.

Download from the downloads section.

Bug reports should be sent to the Discord channel.

Enjoy! o7

v2.5.0 Changelogs:
[FIX] - the direction decider for the navigation arrows wasn't working properly on-foot in Odyssey, because the current Heading in Status.json given out by Odyssey when on-foot has - of course - a completely different number range from when in-Ship or in-SRV. The fix is simple and works on both types of supplied Heading number ranges.
[FIX] - Target Lat/Lon Clear button stylesheet setting was missing.
[FIX] - Include safety check for errant Ring data which found itself somehow inserted into the SystemBody table. Ignore this record and continue to populate the planet table. Remove the exception catcher wrapped around this function because we need to know if and when further crashes happen, which will be written to the error log.
[FIX] - add a tidy_up_errant_rings() function to the DBInterface which removes any errant Ring records either residing in the SystemBody table (where they shouldn't be) and/or in the BodyRing table where they don't have a systembody_id which ties them back to a planet. This function gets called when exiting.
[MISC] - Include planet type in retrieve_system_body_data() in DBInterface.
[MISC] - Small potential speedup in the PlanetData() class, create_planet_table_to_info_row() function; One less DB query required for planet type as that was included in the retrieve planet data function in the DBInterface.
[MISC] - Reduced Nav system arrow direction decision "leeway" to between -2 and +2 degrees when deciding to point straight ahead.
[SPEEDUP] - Quite a large speedup achieved when loading a Trip database! By replacing the old database-query-per-Jump iteration with a single Trip database query, then a single Galaxy DB query for only the list of star systems involved in the Trip being loaded, the initial loading of the Trip has been sped up rather nicely.
[SPEEDUP] - Vastly reduced DB queries for detecting all available raw materials in a given star system by using a similar method as the Trip loading speedup. This has more benefit for records of star systems with a large amount of landable planets with raw materials.
[MISC] - Add a sprinkle of QCoreApplication.processEvents() into the planettablewidget code for a slightly smoother experience
[MISC] - replace the outdated 'backref=' with 'back_populates=' relationships in the database schema definitions.
[MISC] - since we're now using the new and faster Trip/Jump/Starsystem data retrieval method, ensure the count of stars or planets in a given starsystem read "0" instead of "None", on the Trip table.
[MISC] - increase the frequency that the StatusParser reads Status.json
[MISC] - set default value to "0%" in a couple of progress status bar widgets.
[MISC] - tweaked the layout of the Overlay widget so that the Target LAT/LON input widgets are wider, making the display of lat/lon coords match the current lat/lon.

 

blog comments powered by Disqus