Release [Explorer's Application] Captain's Log

After using Captain's Log 2 for a good while, I had to reload my system, games and Captain's Log. I'm running Elite in Winowed:Borderless and always start CL2 before the game launcher (which was a Steam install). I'm using the

default directories for each of the two log locations, and I can see the log files adding up in the ...\Saved Games\Frontier Developments\Elite Dangerous folder, and CL2 reports that it is parsing the log files and it is aware of when

Elite is running.

A good start...

I just spotted this post right before getting ready for sleep, but here goes ;)

When Elite starts, the app does not snap to the to of the Elite screen in a condensed version as I remember.

Is the Overlay checkbox lit up green (i.e. checked)? If it's not, then you need to check it in order to get the overlay.

But more importantly, it's not getting any information processed into the database. I can't think of anything else to try

and any help you could provide would really be appreciated. Nice program, by the way!

Well that is a puzzle indeed.

You say you had to reinstall Windows?

Did you save your old databases?

What I'd recommend is this...

1) Browse to %localappdata%

2) rename the captainslog2 folder to something else.

3) Run CL2 and configure with defaults.

4) Restart CL2 after configuration

5) Run the game.

If that doesn't work, then I don't know what else would. I have tested starting CL2 completely from scratch many, many times and made sure that it configures with sensible defaults.

Regards
 
I just started exploring with this. Awesome tool! Under planet data when it says Water Geysers does that mean I should be able to find water geysers on the planet somewhere? I have been searching this planet for awhile now and cant find them.
 
I just started exploring with this. Awesome tool! Under planet data when it says Water Geysers does that mean I should be able to find water geysers on the planet somewhere? I have been searching this planet for awhile now and cant find them.

In theory there should be volcanism on the planet which you can find.

Truth be told, I've not managed to find volcanism on a planet either - I don't have the time nor patience to go flying around a planet for hours on end - especially since the only instrument we can use is the Mk.I eyeball :/
 
In theory there should be volcanism on the planet which you can find.

Truth be told, I've not managed to find volcanism on a planet either - I don't have the time nor patience to go flying around a planet for hours on end - especially since the only instrument we can use is the Mk.I eyeball :/

Great! Im not nuts then. I spent an hour looking for one but gave up :eek:
 
I've just bought a new computer that I have installed Captain's Log 1.4.3 and Captain's Log 2.0.0 Beta 9 on. I currently use both because when I started my latest exploration journey 2.0 did not exist yet so I would like to still use 1.4.3 too until my current journey is over. Captain's Log 2 is working correctly but I get an error message when I try to start Captain's Log 1.4.3. It worked on my old computer so I am not sure why it doesn't work on my new one. I think I have copied the databases over to the new computer but maybe I missed a file somewhere.

This is the error message:
CaptainsLogError.png
Can you find out from this error message what settings or files I may be missing on my new computer that Captain's Log 1 needs?
 
I've just bought a new computer that I have installed Captain's Log 1.4.3 and Captain's Log 2.0.0 Beta 9 on. I currently use both because when I started my latest exploration journey 2.0 did not exist yet so I would like to still use 1.4.3 too until my current journey is over. Captain's Log 2 is working correctly but I get an error message when I try to start Captain's Log 1.4.3. It worked on my old computer so I am not sure why it doesn't work on my new one. I think I have copied the databases over to the new computer but maybe I missed a file somewhere.

This is the error message:
View attachment 117127
Can you find out from this error message what settings or files I may be missing on my new computer that Captain's Log 1 needs?

Browse to %localappdata%\captainslog and edit the file captainslog.ini

In the [Misc] section at the bottom there is the option check_for_cl_updates - change the True to False.

CL1.x will then start without trying to check for updates, which is where the failure is occurring.
 
Browse to %localappdata%\captainslog and edit the file captainslog.ini

In the [Misc] section at the bottom there is the option check_for_cl_updates - change the True to False.

CL1.x will then start without trying to check for updates, which is where the failure is occurring.

Thanks, that fixed it!
 
Captain's Log 2.0.0 Beta 10 Released

This is a bugfix and enhancement release.

A lot of internal changes, added the Bearing Calculator to the Overlay Widget, database migration added (alters/adds tables if and when required).

Changelog:

- New signal journalLiftoff added to Journal Parser class
- New signal journalStartJump added to Journal Parser class
- GALAXY database schema versioning and migration system added. I can now alter the GALAXY database format and CL2 will alter existing GALAXY.db databases automatically. This allows for new features which require new Things in the database to be added more easily.
- Added AtmosphereComposition table to GALAXY schema
- Added axialtilt column to GALAXY db schema, in future preparation if FDEV ever decide to add axial tilt of a body into the Player Journal
- All functions that require a database session now obtain their sessions from only one point in the program
- Added parsing of the AtmosphereComposition journal event to the JournalParser
- Check if the SystemName received (due to an FSDJump event) is the same as the last systemname on the jump table. This is because a journalFSD signal is now generated by the journalLocation parser and we don't want to keep adding Jump table entries if we're starting in the same location.
- CL2 will now update your Jump table if you start the game at a different star system from where it thought you were. This should keep scans in synch with the star systems in your Jump table.
- Splash screen now shows up much earlier
- Splash screen has additional "Initialising" message
- Splash screen now stays up right until the program is just about fully initialised and the main window is ready to appear.
- Removed the time delay for the splash screen as it's no longer required - CL2 initialisation is delay enough. This actually saves half a second for app loading ;)
- Elite Running indicator widget now styled early with a "Loading Trip" message, until the elite-running-checker thread is initialised after trip load, then back to normal indication.
- Major overhaul of the JournalScanner class
-- Got rid of 4 specific planet type scan signals and replaced with 1 all-encompassing planet scan parser/signal. Less code to maintain and follows DRY principle.
- Major overhaul of the database interface
-- Got rid of the 4 specific planet type add-to-database functions and replaced with one function which can handle all cases. Less code to maintain and follows DRY principle.
- Changed the journal log importer to suit the parser and dbinterface changes.
- Try to not have the Imgur uploader explode if Imgur reports it's overloaded
- Fixed a bug in the new 'check for same system name in jump table' function such that it does nothing and returns if there are no jumps in the table
- Added Atmospheric Composition data storage for planets to the database
- Added Atmospheric Composition automatic DB migration, which will happen when the new version of CL2 has been loaded
- Make sure the DB migrate module has all the correct application paths
- Adapted the Bearing Calculator class for overlay usage
- Added signals to the Bearing Calculator for overlay usage
- Added a moved() signal to the overlay widget
- Overlay version of the Bearing Calculator added to below the overlay widget
- Overlay version of the Bearing Calculator follows the position of the Overlay Widget when it is moved
- Added Bearing button to the overlay widget, which toggles the Overlay Bearing Calculator on and off
- When LAt/LON and planet radius figures are updated in either of the Bearing Calculators, the other calculator is updated
- Moved loading of the Configuration Manager (and hence the app configuration) to right to the start of the application initialisation.
- Moved the display of the splash screen to just after configuration has been loaded
- BUGFIX: if CL2 is started in Overlay mode, and first goes into overlay mode, it always took 2 presses of ALT-C to bring the main window up. This has now been fixed and the main window now appears on first ALT-C press.
- Materials Donut Chart: Tweaked width of chart, and made gap between material name and precentage value larger
- Materials Donut Chart: Ensure percentage values are rounded off to 2 decimal points and padded with decimal point zeros to maintain a neater looking percentage column
- Remove a scrollToBottom() call for the add_entry_to_jumptable()
function for the jumptablewidget. This should speed up initial loading
of the jump table (no need to scroll to bottom of the table thousands
of times)
- remove a print() statement from edsm nightly build start_download()
as this could potentially cause GUI app problems.
- version bumped to Beta 10
 
Has anyone gotten Captain's Log 1 to work after patch 2.3? It seems that the old style netlogs has changed enough in this patch to make the old version of Captain's Log 1.4.3 to stop working. I have tried adding the verbose logging to the config file but that did not help. I guess it is time for me to retire the old 1.4.3 version.
 
Has anyone gotten Captain's Log 1 to work after patch 2.3? It seems that the old style netlogs has changed enough in this patch to make the old version of Captain's Log 1.4.3 to stop working. I have tried adding the verbose logging to the config file but that did not help. I guess it is time for me to retire the old 1.4.3 version.

Oh have they disabled the System: line in the old netlogs? I'll have to take a look...
 
Has anyone gotten Captain's Log 1 to work after patch 2.3? It seems that the old style netlogs has changed enough in this patch to make the old version of Captain's Log 1.4.3 to stop working. I have tried adding the verbose logging to the config file but that did not help. I guess it is time for me to retire the old 1.4.3 version.

I've just checked.

They've changed the string - yet again! - for the 2.3 old-style netlogs. :(

Old format:

{20:46:30} System:"Plio Eurl PX-W b43-2" StarPos:(2275.000,155.406,-110.406)ly Supercruise

New format:

{16:47:26GMT 265.264s} System:"Synuefe HY-P d6-31" StarPos:(215.969,-306.125,-468.406)ly Supercruise

This means that CL1.x doesn't match the new 2.3 netlogs (NOTE: 1.x, 2.x works fine as it only works with the new Player Journal logs!)

Maybe it's time to retire CL 1.x? It's old and busted. CL2.x is the new hotness, and it'd mean I no longer need to keep maintaining CL1.x. I'm pretty sure FDEV will one day remove that from the old-style netlogs eventually anyway.
 
Last edited:
Captain's Log 2.0.0 Now Out Of Beta!

After a rather lengthy period of being in Beta, many bug reports and fixes, new features, more bug reports and more fixes, Captain's Log 2.0.0 has now come out of Beta into full release.

New releases from now on will follow the usual X.Y.Z format, with Y == Feature release, and Z == bugfix release.

There were some final bugfixes for 2.0.0...

2.0.0 Changelog

- BUGFIX : Prevent the JournalParser (and hence the application) from
crashing due to invalid values detected by the JSON loader during an
edge-case scan of a Ring Belt
- BUGFIX : Make the Scan Event decision-maker function more robust and
less naive by specifically making sure we're either scanning a star
or a planet/moon. Also ignore Ring Belt scans as they provide very
little interesting information. Rings orbiting a star or planet still
get recorded, but at this time CL2 doesn't show their information.
- BUGFIX : Prevent the Player Journal Importer from crashing due to the
same invalid value 'inf' for the JSON.
- Version bumped to 2.0.0, making this the official stable release!

------------

See my signature for links to the web site and the Captain's Log Discord server, there is a bug reports channel on Discord, so report them there. There are also announcements and changelogs channels, and from time to time I'll be there chatting in #general.

Enjoy ;)
 
Back
Top Bottom