Release [Explorer's Application] Captain's Log

[Genar-Hofoen]

To be honest it seems huge to me!
EDSM database is not as big as that and we handle more than 10K commanders.

I know CL will update to work on demand and I also tried to explain that for EDD.
It would be far more efficient to ask for system on EDSM on demand. It doesn't take much time or resources or even hard drive space fir the users.

Effectively our dumps will always grows, I'm not even sure that they will stay in place more than a year, because they took a lot of time to generate, and occupy a lot of our hard drive. They also tend to make software download too much things that will almost never be used !

Everything he said.

Also, as Anthor and I discussed on Discord recently, the reason I kept the EDSM nightly dump stuff in for this beta 7 update was because I had spent an awfully large amount of time getting this feature right, fast, and to have a small memory footprint. There's not much I can do about the space it takes up on the hard drive due to the download size, and that's always going to be an issue, but as I mentioned in my previous post, the actual EDSM nightly dump is currently manageable with the caveat that sooner or later, it is going to become a behemoth just down to the nature of the game and the data it generates

The other reason, and this is one which may or may not be considered important, is that if for some reason the EDSM site goes down, well at least one has a snapshot of the data from some point in time. Now hopefully, EDSM will be with us forever! But stuff happens.

As I've stated in large red letters in the CL2 documentation - just be aware of the file size and storage space requirements of the nightly dump, before you hit that button. The decision is entirely up to you, dear users

 

[iain666]

To be honest it seems huge to me!
EDSM database is not as big as that and we handle more than 10K commanders.

6GB seems very large to me too - and that's speaking as an EDD developer...

I've got 1.5GB for my EDDSystem database (the one that's got all the downloaded data in it). For EDSM we only keep the system names/coordinates locally for drawing the 3D map - we have some EDDB data locally as well and could probably normalise those two datasets and shrink it a bit.

6GB sounds like the old one - it'll be called EDDiscovery.sqlite - which blew up massively when the number of known positions ballooned with 2.1 and caused a re-organisation into EDDSystem and EDDUser. If anyone still has a huge EDDiscovery.sqlite then they can safely delete that. It shouldn't be growing any more though.

 

[Genar-Hofoen]

6GB seems very large to me too - and that's speaking as an EDD developer...

I've got 1.5GB for my EDDSystem database (the one that's got all the downloaded data in it). For EDSM we only keep the system names/coordinates locally for drawing the 3D map - we have some EDDB data locally as well and could probably normalise those two datasets and shrink it a bit.

6GB sounds like the old one - it'll be called EDDiscovery.sqlite - which blew up massively when the number of known positions ballooned with 2.1 and caused a re-organisation into EDDSystem and EDDUser. If anyone still has a huge EDDiscovery.sqlite then they can safely delete that. It shouldn't be growing any more though.

+rep

"Captain's Log - so good, it even brings up bug reports about EDDiscovery!"

 

[VerticalBlank]

LOL yes - I know about that one, I just haven't fixed it yet.

I use a Python function to capitalize a sentence but unfortunately it changes things like "III" to "Iii" which is kind of 'eww', so I'm going to have to re-think how to do this

It's been a while since I last looked at the Python libs: maybe there is a general Roman numeral parser nowadays that isn't too compute-heavy?

 

[daver4470]

Not sure what you meant as EDSM is already a universal database with all the requises API.
CL is integrating them, hopefully it will come soon.

Anthor -- the others are correct. I meant having one local copy of the DB that both CL and EDD pull from (and update). Right now, each program pulls its own data file from EDSM, so I've got two full databases. Which right now is fine, but I see it becoming an issue in the long run. I don't view it as an EDSM issue -- I think having an API that allows clients to interact with the master database is almost certainly the best possible implementation. I'd just like it if I could point one of the two to the other's file, such that only one file was necessary. Hope that clears it up!

- - - Updated - - -

+rep

"Captain's Log - so good, it even brings up bug reports about EDDiscovery!"

I think you've got the pullquote for the box!

 

[Genar-Hofoen]

Anthor -- the others are correct. I meant having one local copy of the DB that both CL and EDD pull from (and update). Right now, each program pulls its own data file from EDSM, so I've got two full databases. Which right now is fine, but I see it becoming an issue in the long run. I don't view it as an EDSM issue -- I think having an API that allows clients to interact with the master database is almost certainly the best possible implementation. I'd just like it if I could point one of the two to the other's file, such that only one file was necessary. Hope that clears it up!

- - - Updated - - -



I think you've got the pullquote for the box!

Again, CL2 isn't pulling anything from anything - not unless you choose to - it's an entirely optional thing at your discretion

 

[Finwen]

I presume they mean local copies - my EDD is at 6.5GB and growing; if CL2 has another copy of a 6GB DB of the same data, it does seem a bit inefficient

EDDiscoverys database should not be so big. My EDDSystems.sqlite is around 1.5 GB.
But you space is probably used up by older obsolete copies from Pre Elite dangerous 2.2 era.

 

[disorganise]

6GB seems very large to me too - and that's speaking as an EDD developer...

I've got 1.5GB for my EDDSystem database (the one that's got all the downloaded data in it). For EDSM we only keep the system names/coordinates locally for drawing the 3D map - we have some EDDB data locally as well and could probably normalise those two datasets and shrink it a bit.

6GB sounds like the old one - it'll be called EDDiscovery.sqlite - which blew up massively when the number of known positions ballooned with 2.1 and caused a re-organisation into EDDSystem and EDDUser. If anyone still has a huge EDDiscovery.sqlite then they can safely delete that. It shouldn't be growing any more though.

yip, something like 4.2GB of EDDiscovery.sqlite...and now I look more closely the last mod date is October. I'll move em to another folder in preparation to delete. thanks

 

[Straha Yeagar]

Noticed in the beta 7 notes the bit about scan values...so is there a high and low value payout estimator anywhere? I can't seem to find it...

 

[daver4470]

Again, CL2 isn't pulling anything from anything - not unless you choose to - it's an entirely optional thing at your discretion

Oh yeah, I get that. I'm not complaining, just observing. And the odometer is... not exceptionally easy to use if you don't have the database (unless you love looking up coordinates on your own!), so I think it's kind of a mandatory optional feature...

With the database... man, that's a slick feature, and almost idiot-proof. (Note: Tested by at least one idiot.) Although thanks to the letter diarrhea in ED's naming system, half the time the odometer text string runs outside the box. I can live with that. (It keeps the destination name in the box, and that's what matters.)

 

[daver4470]

One more thing -- apologies if this has been discussed elsewhere, too.

I've had a recurring problem with beta 6 and now beta 7 where ALT-C would not bring up the console for me. (I did check for conflicting keybindings - not the issue.) You could tell it was doing something.... but no console. And alt-tabbing out didn't do anything either; there's no icon on the taskbar to click, and the systray icon doesn't have functionality.

It took me a while, but I did finally figure out the issue. I think. Apparently, if you minimize the CL2 window to the taskbar prior to starting ED, the window gets "stuck" in a minimized state. ALT-C does "bring up" the window -- a minimized window. And since the taskbar icon goes away while the game is running if you're in overlay mode, you can't un-minimize it without closing the ED client.

As the fix is trivially easy, I don't really see this as a bug. Just posting here as a general FYI so that others know to keep the window up.

Again, apologies if this is all old news. As noted before, I've been gone for a while....

 

[EUS]

Every once in a while I have to come back and express thanks for this program again.
I've recently set out again, and am still using this program.
So, thank you, and o7 Genar-Hofoen.

 

[Genar-Hofoen]

Captain's Log has a Discord channel...

Last year I created a Discord channel but never advertised it.

The CL Discord channel is here : https://discord.gg/F7CJDTM

Regards o7

p.s. Thanks EUS

- - - Updated - - -

One more thing -- apologies if this has been discussed elsewhere, too.

I've had a recurring problem with beta 6 and now beta 7 where ALT-C would not bring up the console for me. (I did check for conflicting keybindings - not the issue.) You could tell it was doing something.... but no console. And alt-tabbing out didn't do anything either; there's no icon on the taskbar to click, and the systray icon doesn't have functionality.

It took me a while, but I did finally figure out the issue. I think. Apparently, if you minimize the CL2 window to the taskbar prior to starting ED, the window gets "stuck" in a minimized state. ALT-C does "bring up" the window -- a minimized window. And since the taskbar icon goes away while the game is running if you're in overlay mode, you can't un-minimize it without closing the ED client.

As the fix is trivially easy, I don't really see this as a bug. Just posting here as a general FYI so that others know to keep the window up.

Again, apologies if this is all old news. As noted before, I've been gone for a while....

Thanks for that - adding to my Issue tracker now to sort out!

 

[Skyflyer]

I have a feature request. I am running 2.0.0 Beta 6 so I am not sure if it has already been fixed in the latest beta.

When I double click on the column Sys Notes to edit the system notes for a specific system it would be great if the text editor can be focused so I can just start typing the text. Now it is not focused for me and I have to click in the editor before I type.

 

[Genar-Hofoen]

I have a feature request. I am running 2.0.0 Beta 6 so I am not sure if it has already been fixed in the latest beta.

When I double click on the column Sys Notes to edit the system notes for a specific system it would be great if the text editor can be focused so I can just start typing the text. Now it is not focused for me and I have to click in the editor before I type.

Thanks - entered into my Issue Tracker as a bug to remind me to fix it.

 

[AleNinja]

Are you planning to put back the Statistics panel?

 

[Genar-Hofoen]

Are you planning to put back the Statistics panel?

Yep. Will probably be in beta 9 or so - I'm putting priority into working on bugfixes and stuff for beta 8, and with the upcoming 2.3, beta 8 already includes changes necessary to read the upcoming changes in the Player Journal.

 

[Genar-Hofoen]

Captain's Log 2.0.0 Beta 8 Released

Changelog

IMPORTANT NOTE:

One of the bugs fixed was to have CL2 look for the GALAXY.db and EDSMStarSystems.db in your configured database directory.

After upgrading to Beta 8, and before running beta 8, and IF in beta 7 you reconfigured where your DB files are, you will need to manually move or copy GALAXY.db and EDSMStarData.db (if you have one) from your
%localappdata%\captainslog2 folder to wherever you configured your DB location during usage of beta 7.

- Changed the Go To Jump button in the mainwindow search results panel from a QpushButton to a QToolButton, so now it gets its proper styling
- BUGFIX : clear contents of the mainwindow Search Results table upon a new search
- BUGFIX : do not try to Go To Jump in the trip jumps table is there are no results in the mainwindow Search Results table. This fixes Issue #6 in the CL2 issues tracker.
- BUGFIX : Make sure when we display the body type by capitalising it that strings like "Ii", "Iii", "Iv" are changed to "II", "III", and "IV". Closes Issue #7
- EDSM panel : display size of EDSM.db file. Closes Issue #3
- EDSM panel : remove EDSM Nightly Dump file after import or if there was a download error as partial downloads are not useful.
- Added a compatibility function in to cope with ED 2.2 and prior Player-Journal Scan/Materials JSON format, and the new format in 2.3
- BUGFIX : Make sure if CL2 has been set to overlay mode and is minimised when the game starts, that the mainwindow can be seen when recalled. Closes Issue #14
- BUGFIX : Make sure planets are sorted naturally by designation rather than using an ordinary computer sort. Closes Issue #16
- BUGFIX : Make sure system and jump notes get input focus when called. Closes Issue #15
- ENHANCEMENT : Redesigned Player Journal Scan & Import
- Scan & Import now has feedback
- Scan & Import will only import to a blank database
- Scan & Import will not import to the currently active database
- BUGFIX : All databases - including the GALAXY, EDSMStarData, and trip databases, will be stored wherever the Database Directory has been configured. Closes Issue #1
- Updated and made more use of the AreYouSure widget, for messaging and asking questions
- ENHANCEMENT : CL2 will now relocate DB files for you if you select a different location
- Added option in DB Location setting to NOT move the files, as a checkbox. Click to toggle option.
- DB Relocation made more resilient
- DB Reloaction has user feedback during operation
- Removed python print statements from Imgur Access Checker, as this could potentially freeze or crash the program.
- Made DB table functions more generic, able to specify a table widget, for future enhancement of DB management
- Split the creation of GALAXY and Trip database sessions to make them a single-point-of-access function for all other functions requireing a database session
- Changed other functions such that they get their DB sessions from a single point,/one function.
- Retrieved CL1's old manual planet and star adding widgets in preparation for future addition of a manual system editing function, not in live CL2 yet.
- BUGFIX : Made some threads deletion even safer - this was necessary for being able to close all threads, unlock DB files, and relocate them.
- added an OK button to the AreYouSure widget and buttons can be set visible or invisible according to the desired usage context
- ENHANCEMENT : During iinitial loading of Trip DB, progress bar now shows X of Y jumps loaded
- BUGFIX : Squished some really horrible bugs to do with threading/threading stop and deletion which was causing CL2 to crash.
- NEW FEATURE : Added The Bearing Calculator!
- Bearing Calculator will indicate which bearing you need to head towards a given Latitude and Longitude, from a given start Latitude and Longitude. (Note: bearing is experimental and may need tweaking - feedback gladly accepted!)
- Bearing Calculator will also indicate the distance between those two points, if the planet radius is known.
- Bearing Calculator will obtain the planet's radius from a seleceted planet in the Planet Table, if that radius is known (i.e. a scanned planet).
- Bearing Calculator can also obtain a planet's radius via manual input if necessary.
- Version bumped to 2.0.0 Beta 8

The user manual updated to suit the changes.

 

[Genar-Hofoen]

Captain's Log 2.0.0 Beta 9 Released

- BUGFIX : Make sure db sessions are committed/closed where appropriate. Closes Issue #24 whereby bookmarks couldn't be made on new jumps.
- BUGFIX : Bearing calculator : the Distance calculation function was being fed latitude and longitude in reverse - that's bad. Fixed.
- NEW FEATURE : Automatically feed your ship's Latitude and Longitude coordinates to the Bearing Calculator's starting position input fields upon landing on a planet (Touchdown). If you have a destination set it'll recalculate the Bearing. If the planet's radius in km is known (should be for scanned landable planets and automatically filled in upon a detailed scan), then the distance to target coords is also recalculated.
- Touchdown parsing and signal added to the Journal Parser class
- BUGFIX : Overlay mode : Actually going into overlay mode is now done at a more sensible time. Previously it was being initialised upon CL2 startup, right after the splash screen. Now, it will only go into overlay mode if the elite running thread has detected if the game is running. Also check to see if we're actually in overlay mode or not, as we don't need to set for non-overlay mode if we're already not in overlay mode. Closes Issue #23
- Overlay Mode : The above also stops that annoying mainwindow disappearance/reappearance flicker when switching off the overlay mode, if we're not already actually in overlay mode.
- ENHANCEMENT : Window Position : CL2 will now save its current non-overlay mainwindow position when exiting and will restart in that position when loaded.
- ENHANCEMENT : Window Position : Added a menu item to the systray icon to reset (recover) the mainwindow position if required (e.g. was using 2 monitors and now only using one but window position was saved to be off the screen of the 1 monitor). This will make the Mainwindow appear in the center of the active monitor. Closes Issue #18

 

[jimspahr]

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.
When Elite starts, the app does not snap to the to of the Elite screen in a condensed version as I remember. 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!