Release [Explorer's Application] Captain's Log

Whether version 2.1.3 is compatible to old versions, for example 1.4.4? It is a pity old to lose expeditions.

No, the 2.x database schemas are not backwards compatible with 1.4.4 - you cannot load 2.x db's into 1.x , neither can you import 1.x databases into 2.x, because there is not enough information in the 1.x database format to properly populate the 2.x databases.

Frontier added a lot of new and useful information to the new and useful Player Journal files, therefore the database format of Captain's Log had to be redesigned. The Player Journal files replaced usage of the old netlog files. The old netlog files had only one thing useful in them - which system you jumped into at which time, which meant you had to manually input star and planet data. Whereas in CL2.x, all data is automatically entered when you scan bodies. The only manual input left, is various notes, bookmarks, and LAT/LON input for the Bearing Calculator.

Personally, I'd stay with using 2.x, as I stopped developing 1.x a long while back.

And version 1.4.4 still working?

Quorthon stated 1.4.4 is still working, a few posts ago.

Regards.
 
I have uninstalled and reinstalled 2.1.4 and the program will not start and gives the python error in the screen grab. Do I need to install anything else? I am running Win10
 
I have uninstalled and reinstalled 2.1.4 and the program will not start and gives the python error in the screen grab. Do I need to install anything else? I am running Win10

*sigh*

Installing and reinstalling will do nothing.

I have told you what you need to do to get it working again.
 
Captain's Log 2.1.4 Released With Some Significant Bugfixes And Attempt At Auto-Repair Of GALAXY.db

I've added a facility in 2.1.4 which examines GALAXY.db and if it sees that the navbeaconscan database column has been added, but the database version isn't the expected number, the it will attempt to stamp the correct version number into the database - an automatic fix for the manual procedure I outlined in an earlier post.

I've also added something which I should have added a long time ago - a Logging facility, which can be found in the Configuration Manager panel, in the new Logging tab. This should prevent any future shenanigans happening whilst upgrading/migrating the GALAXY.db database, or in future the Trip databases, if I'm going to be altering their structure.

There are many other bugfixes in this - and my personal thanks go to a few users who provided valuable feedback in the #beta-testing channel of the Captain's Log Discord server, during the beta stage of 2.1.4. They know who they are.

On that front, if you are willing to try out future Beta versions of CL2, and help stomp out bugs before a full release by reporting your findings, then you are welcome to join the CL2 Discord, address/invite in my signature below.

Download from : https://captainslog.scarygliders.net/download/captains-log-2x/ , there is an alternate download location provided there if you have difficulties downloading from my site.

2.1.4 Changelog

- BUGFIX : check to see if a trip DB has been configured. If not, set to v2default.

- BUGFIX : check to see if configured trip DB exists. If not, set to v2default.

- BUGFIX : treat CMDR's credits as a string when emitting them as a QSignal from the LoadGame parser. Some CMDRs are FAR TOO RICH for their own good!

- pre-emptive BUGFIX : On that note, also send the calculated Total Trip Value as an emitted string from that thread, because some explorers are going to be getting enough scans to have BEEEELIONS! And Qt can't cope with sending anything bigger than 2^31 - 1 as an integer, because obviously maths hurts its poor little GUI head.

- pre-emptive BUGFIX II, The BUGFIX Strikes Back : on that happy note above, receive the value signals data as text and convert it back into Python ints, which can in fact handle the pressure.

- BUGFIX/ENHANCEMENT : Add a logging text widget to ConfigurationManager, in it's own Logging tab. A log for Captain's Log.

- BUGFIX/ENHANCEMENT : Add Python's Logging functionality. Because logs are good.

- BUGFIX/ENHANCEMENT : Divert Python's stdout and stderr to the logging text widget. Because lots of pesky python libraries send pesky messages to stdout and stderr, and a Windows GUI version of a Python program doesn't /have/ stdout and stderr, so there's nowhere for the pesky messages to go, and so you get those even peskier cx_Freeze error dialogues, which peskily enough crash Captain's Log 2, and even peskier things happen. Like, databases not being stamped with the correct version number! Cats and dogs living together! People screaming and on fire! We're talking Armageddon here folks!

- BUGFIX/ENHANCEMENT : Start producing Logging messages at various stages of CL2's initialisation, this helps see where CL2 is crashing if it does. This is an initial implementation so not all stages will be tattle-tales yet.

- BUGFIX FOR A BUGFIX : If starting with a blank trip DB, and the total trip value is Nothing, don't try to convert a text Nothing into an integer Nothing, because Python hates that and prints an Error Message, which gets sent to stderr, which.. well you know the rest. That's fixed now, so all's well with the world. Or should that be galaxy?

- added some logging to ConfigFile class
- added moar logging to configuratiomanager, because why not
- added some logging to V2DBInterface, can never have too much logging

- BUGFIX : altered tooltip of Scan & Import button to reflect what actually happens, rather than troll people by telling them lies, funny though that is :D

- set an application-wide logger for Captain's Log, called "captains_logger". Geddit? captains_logger? Huh? Geddit? I'll fetch me coat.
- added some logging of things to main CL2 loop, because logging is fun.

- BUGFIX : when checking to see if a trip database exists, do remember to suffix the name with ".db" when checking for the actual file, otherwise this sets one up for 45 minutes of frowning at source code and hating life.

- added more informative logging messages, especially around the Player Journal location bits of the code.
- altered some logging messages to be more meaningful/less confusing.
- added a logging message to JournalParser, telling which journal file it has been fed with.
- changed the order in which the journal parser gets started, and the indication that the journal has started.
- added a parserStatus label beside the Elite running label, and the accompanying stylesheets and logic to update it.
- added calling of the afmu and jumponium availability checker after a nav beacon scan, to update those two overlay widgets.
- updated main ui setup.bat to include calling of a couple of widget ui compilations which were missing.

- BUGFIX : Correct the ValueFormula for planets such that it truly reflects the MattG forum formula. Good news guys! Terraformable values get a buff! :D

- BUGFIX : Add an automatic check and fix for GALAXY.db databases which got ruined by those evil 2.1.0 to 2.1.3 versions of Captain's Log. It'll automatically stamp GALAXY.db with the correct version number for the CL 2.1.x series, which enables the loading of them. ONCE AGAIN THE UNIVERSE (Galaxy) HAS BEEN SAVED!

- ENHANCEMENT : Only update the overlay widgets if we are, in fact in Overlay Mode. Why do all that extra work when it's not needed?

- BUGFIX : only display the overlay planet table widget if it has data and has been populated with data. Revert behaviour to selecting the first planet (if any) in the planet table, so that data can be shown on the overlay. This should still fix the old 'subliminal data' bug that the previous fix fixed, but better. Because why not?

- abort CL2 if all else has failed with the GALAXY.db version check.
- flag up for a migration check if the GALAXY.db version check thinks it's a 2.0.0 version.
- ensure overlay Distance To and Odometer are updated, so they can be viewed when going into overlay mode.
- try to make configuration loading more resilient by trapping some errors in loading coordinates and setting those to 0 if such an error occurs. Like trapping rabid animals and turning them into tame pets.
- ENHANCEMENT : When importing Journal logs, attach the Nav Beacon Scan signal to the mark_system_as_navbeacon_data() function in the import journal parser, in order to accurately import nav beacon scan data and mark that as such, so that CL2 doesn't include it in its value estimation for that trip DB.

- Version bumped to 2.1.4
 
Hi Genar-Hofoen,

I'm not sure which app is 'incorrect', but it seems that CL2 and EDD are calculating TC HMC's in quite different ways. In this example, CL2 says it is estimated at 292k whilst EDD says 424k. Given you both use the same maths as far as I understand, I would expect the answers to be same (which they are for other bodies so far...within a credit or so anyway which I assume to be rounding differences)

F6SWpfa.png
 
Hi Genar-Hofoen,

I'm not sure which app is 'incorrect', but it seems that CL2 and EDD are calculating TC HMC's in quite different ways. In this example, CL2 says it is estimated at 292k whilst EDD says 424k. Given you both use the same maths as far as I understand, I would expect the answers to be same (which they are for other bodies so far...within a credit or so anyway which I assume to be rounding differences)

https://i.imgur.com/F6SWpfa.png

There may still be some bug in how I calculate the values. I'll have another go at it for the next release. I did update the formula for 2.1.4, and it did seem to increase the values when I tested it, some by quite a lot.

I'd like you to - if you can/wish - follow this up by telling me what value you got for that world when you get to sell your data to UC, please?

Then I'd be able to try to debug (if needed) my Python version of the calculation :)

Regards, and happy exploring o7
 
There may still be some bug in how I calculate the values. I'll have another go at it for the next release. I did update the formula for 2.1.4, and it did seem to increase the values when I tested it, some by quite a lot.

I'd like you to - if you can/wish - follow this up by telling me what value you got for that world when you get to sell your data to UC, please?

Then I'd be able to try to debug (if needed) my Python version of the calculation :)

Regards, and happy exploring o7

Here you go. Thought I was gonna be months away, but there's an asteroid base in the crab nebula, so...

OCGHIvL.png


TqbK39J.png


{
"timestamp": "2017-10-12T19:10:14Z",
"event": "SellExplorationData",
"Systems": [
"Pyult LQ-O c22-2"
],
"Discovered": [
"Pyult LQ-O c22-2 4"
],
"BaseValue": 426295,
"Bonus": 205747
}
 
Here you go. Thought I was gonna be months away, but there's an asteroid base in the crab nebula, so...

https://i.imgur.com/OCGHIvL.png

https://i.imgur.com/TqbK39J.png

{
"timestamp": "2017-10-12T19:10:14Z",
"event": "SellExplorationData",
"Systems": [
"Pyult LQ-O c22-2"
],
"Discovered": [
"Pyult LQ-O c22-2 4"
],
"BaseValue": 426295,
"Bonus": 205747
}

Thanks for this. I thought for a moment looking at my code I didn't have HMC's, but they're in there with Class II gas giants.

Investigating.
 
Last edited:
Here you go. Thought I was gonna be months away, but there's an asteroid base in the crab nebula, so...

https://i.imgur.com/OCGHIvL.png

https://i.imgur.com/TqbK39J.png

{
"timestamp": "2017-10-12T19:10:14Z",
"event": "SellExplorationData",
"Systems": [
"Pyult LQ-O c22-2"
],
"Discovered": [
"Pyult LQ-O c22-2 4"
],
"BaseValue": 426295,
"Bonus": 205747
}

Okay. I have tracked down the source of the problem and have fixed it. Once I saw it, it was a real facepalm event ;)

Fix is in for next release.

Regards o7
 
Captain's Log 2.1.5 beta 1 Available For Testing

As per title,

A number of bugfixes.

If you wish to try it out, details are on my CL2 Discord server, see my signature for that URL.

Download details in the #beta_testing channel, pinned message.

Beta changelogs available in the #beta_changelogs channel.

Bug reports should be sent to the #beta_bug_reports channel please.

Regards o7
 
Captain's Log 2.1.5 Released with bugfixes, enhancements. Will definitely migrate from 2.0.0

As per title.

Download links on the CL2 site at : https://captainslog.scarygliders.net/download/captains-log-2x/

Please report bugs on the Discord server, #full_release_bug_reports channel, server address : https://discord.gg/F7CJDTM

Changelogs

- BUGFIX : Take into account that 2.0.0 GALAXY databases can be non-empty, as well as empty, when checking to see if they need to be migrated. Sometimes the programmer can be too focused on one thing and forgets other important things. Quit forgetting things, programmer!

- BUGFIX : set the estimated total trip value widgets visible if the value > 0. This should make it visible if you're starting from a blank Trip database and you scan something. Because who doesn't like seeing how much filthy lucre they're making?

- BUGFIX : Corrected the ValueFormula class such that it correctly calculates the estimated value for a terraformable world/ELW/WW, according to the MattG formula. Good news, guys! Values get buffed again! :D

- ENHANCEMENT : comma-formatted the Distance To, and the Odometer values, on the Overlay. Because commas are awesome.

- BUGFIX : The text for Odometer was in a different font on the Overlay. It's now been changed to the same font as Distance To. Frankly I'm surprised no one reported this one. Gotcha! :D

- ENHANCEMENT : added a BETA flag which disables checking for updates if this is a beta version of CL2. No more annoying Update window for the testers!

- BUGFIX : ValueFormula : Earthlike Worlds automatically get a bonus added to them. Like a participation medal just for being the beautiful thing they are!

- Version bumped to 2.1.5
 
Really disliking that this thread got moved as I didn't see the updates. ( whinge at FD and their thread re org)

Anyways.... have downloaded and will try it out in the morning.
Fwiw, the installer spits an error and Bitdefender pops a block at the end of the install....I * think* it's for shortcut creation as the program did load OK and I recall a similar error on previous version ( but without the BD pop up.... but weird stuff was happening anyway so I reset windows so now everything is new and its clear BD is blocking something but it just won't say what)
 
Really disliking that this thread got moved as I didn't see the updates. ( whinge at FD and their thread re org)

Anyways.... have downloaded and will try it out in the morning.
Fwiw, the installer spits an error and Bitdefender pops a block at the end of the install....I * think* it's for shortcut creation as the program did load OK and I recall a similar error on previous version ( but without the BD pop up.... but weird stuff was happening anyway so I reset windows so now everything is new and its clear BD is blocking something but it just won't say what)

I requested the thread be moved to the more relevant area :p

I've had a rant recently as to why you only need Windows Defender and why most other anti-virus packages are in my opinion no longer relevant today and are merely produced by self-serving companies it's in their own self-interest to produce drama and big red DANGER boxes at the merest whiff of something banal :)

Anyway - it was probably good that you missed the trauma of 2.1.0 to 2.1.3 ;) ... you dodged a real bullet there :p
 
Captain's Log 2.1.6 beta 1 available for download and testing...

This is a beta test of some improvements to the Overlay, and by side-effect making the GUI more snappy.

From 2.1.5 downwards, turns out the Overlay was displaying details for the first planet in the scanned planets table, then switching to the details for the latest scanned planet. Reports were that this became increasingly noticeable, the more scans one had in the trip database.

So I've made a few changes in how stars and planets details get updated after a scan, resulting in much snappier GUI response and curing the Overlay woes.

So far I've had good feedback from testers.

Details available on the CL Discord, invite URL in my signature. See pinned message in the #beta-testing channel for a download link, and feedback appreciated in that channel and if a bug is found in the beta, #beta_bug_reports.

Regards o7
 
Back
Top Bottom