Release [Explorer's Application] Captain's Log

disorganise

disorganise
is there an entry in your journal?

Not having a DSS results in a level 2 scan that does NOT make a journal entry for example (seems dumb to me but hey)

Look for files named something like; Journal.170114062118.01
usually in C:\Users\<windows user name>\Saved Games\Frontier Developments\Elite Dangerous
 

CMDR Smior

CMDR Smior
{ "timestamp":"2017-01-14T01:48:29Z", "event":"Scan", "BodyName":"57 Cygni B", "DistanceFromArrivalLS":1222.902954, "StarType":"AeBe", "StellarMass":5.187500, etc...
yes. it showed up in EDDiscovery.
 

Genar-Hofoen

Genar-Hofoen
Regarding the AeBe stars, there's currently a bug in Captain's Log 2.x whereby I managed to create 3 entries of AeBe star types in the database format.

This was due to copying one line of code multiple times when I was designing the DB formats initially, then working down each line editing it to match each star type. I've obviously been distracted at home at some point, left the PC, and subsequently left three AeBe-types in, moving on to some other part of the codebase.

This means that with all versions of CL2 up to beta 6, if you scan an AeBe star, CL2 will search for the AeBe type in its database, and will balk when it finds >1 query results, which breaks the rest of the program flow.

I have, in the as-yet unreleased beta 7, added a fix for this in the form of a button called "Reset star/planet to default values" in the Databases section of the Configuration Manager, which when pressed will both reset the low/high values of stars and planets in the CL2 DB, and also remove the extra AeBe entries, which will get AeBe stars properly being entered when scanned.

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

Speaking about CL2, in the last few weeks I have been working on the new EDSM module, with the intention of having CL2 submit your jumps and/or trips to EDSM. One of the first things I worked on was to be able to download and import the EDSM Nightly Dump of all its star systems and their galactic coordinates.

yxkxVfr.png
pqOES7X.png

I spent a LOT of time and effort on getting it right, and it works superbly, is threaded (does it in the background) and is buttery smooth.

I even added an option to include the imported EDSM database when searching for a star system for setting your Target Destination (a replacement for the current "Distance to Sol" indicator) - that works fantastic too.

jiNxTzJ.png
uz9kuqR.png
o6U6qQK.png

However, I recently had a conversation with Anthor (the EDSM author), about how big the Nightly Dump is getting, noting that EDSM's database is going to become extremely unwieldy - it's already a 757MB download with 5,927,126 star systems and coordinates!

Imagine what it's going to be like when there's 20 million, or 50 million systems in that nightly dump - and you're getting into the multiple-gigabyte download size of JSON files :)

Anthor tends to agree with this assessment.

As such, I am going to remove all that work I did for the download/importer. Instead, I am going to pass the search query on to EDSM itself via the EDSM API, and deal with the results from there.

It's sort of crushing to have to decide to remove a big block of new code I spent time on to run smooth as butter in the background, allowing CL2 to operate normally at the same time - but this is definitely necessary in order to prevent a lot of drama for everyone in the near future :)

Anyway, I shall keep plugging away at CL2 beta 7. "No ETA's, no guarantees"[tm] on a release date as yet. This is just to let you all know I'm still working away on it :)

Regards o7
 

Xeno The Morph

X
Genar-Hofoen said:
<snip>

As such, I am going to remove all that work I did for the download/importer. Instead, I am going to pass the search query on to EDSM itself via the EDSM API, and deal with the results from there.

It's sort of crushing to have to decide to remove a big block of new code I spent time on to run smooth as butter in the background, allowing CL2 to operate normally at the same time - but this is definitely necessary in order to prevent a lot of drama for everyone in the near future :)

Anyway, I shall keep plugging away at CL2 beta 7. "No ETA's, no guarantees"[tm] on a release date as yet. This is just to let you all know I'm still working away on it :)

Regards o7
Click to expand...

I understand your pain :(
When you have to remove a feature or large amount of code, especially when you feel proud of how it is wroking!, due to scope/requirement changes it definitely feels like a big blow... but keep working at it CL is definitely worth it! (well at least for us end users :D)
 

Genar-Hofoen

Genar-Hofoen
New Beta Version available for download : 2.0.0 Beta 7

As title says - new beta 7 available for download and testing/swearing at :)

This is a feature and bugfix release.

Main changes are :

Beginning of an EDSM module - currently you can download and import the EDSM Nightly Dump - currently over 6 million star systems which you can search.

NOTE: Read the documentation about using this Nightly Dump! It's a big file with LOTS of data and it's only going to get bigger :)

JyrhFBv.png

"Destination to Sol" placeholder has been replaced by Set Target Destination

QHbByEI.png


Hn9R3KE.png

Being able to manually set the DB directory and the Player Journal directory

Some restyling.

Lots and lots of bugfixes.

Update checker now altered to be CL2-specific, safe to re-enable

Download and full changelogs from the new web site at : https://captainslog.scarygliders.net/download/captains-log-2x/

There is now full documentation - fully up to date to Beta 7 (need to document the Overlay so that'll happen later), available on the new web site.

Regards o7
 

daver4470

D
Psyched to finally get to try out beta 7! Beta 6 was pretty great... I'd been out of ED for quite a long time (basically since shortly after planetary landings went active), and am surprised how the quality of life for explorers has improved, especially with the journal system. I thank you, as always, for all your work on this app. You and Finwen/everyone else behind EDD are basically the architects of the entire game for me. (I use both, as each offers something I want that the other does not, and they work together very harmoniously.)

Quick question: although B7 fixes the bad value data in the galaxy.db file, those values are still not displayed in Captain's Log proper, correct? Or am I missing something?

Wistful observation: I wish there was a way that CL and EDD could share a common EDSM database, as in the long run it's going to get awfully inefficient to have two of them floating around. Not sure if this is even practical.... I'll live, in any case.

Minor wishlist item: I love the configurable "distance to" odometer. I just wish there was something like a toggle to switch between two targets on the fly, or two customized odometers. (Or a fully customizable odometer panel, but now I'm talking silly talk...) I'm in transit to Colonia right now, and it would be cool to have a live distance to Colonia/distance to Sol on my HUD.

Great job, many thanks as always! o7
 
Last edited:

AntidotE

AntidotE
Hello,

Thank you for new release! :)
Now it comes with some bug:
After install and run I got an error
wxa51Tx.png
Investigation showed that GALAXY.db was stored in folder with trips. Now it is created and used from CaptainsLog2 folder as I can suppose.
And new structure conflicts with existing trip databases.
If I
* replace newly created GALAXY.db with older version then trips are working
or
* delete trip databases then old GALAXY.db does not have sense but CL2 starts :)
 
Last edited:

Genar-Hofoen

Genar-Hofoen
AntidotE said:
Hello,

Thank you for new release! :)
Now it comes with some bug:
After install and run I got an error
http://i.imgur.com/wxa51Tx.png
Investigation showed that GALAXY.db was stored in folder with trips. Now it is created and used from CaptainsLog2 folder as I can suppose.
And new structure conflicts with existing trip databases.
If I
* replace newly created GALAXY.db with older version then trips are working
or
* delete trip databases then old GALAXY.db does not have sense but CL2 starts :)
Click to expand...

Did you do a straight upgrade and run or did you attempt to change the DB location?

And yes - it is extremely important to keep the original GALAXY.db - the trip db's get their system ID's from that DB.

Regards
 

AntidotE

AntidotE
Just downloaded, installed, run.
It did not ask for anything - thrown error immediately.

I managed with just replacing data in planettype and startype table with correct valuehi and valuelo fields values.

I have more atmospheretype records (79) comparing to your initial 21.
id,type
1,No atmosphere
2,Suitable for water-based life
3,Ammonia and oxygen
4,Ammonia
5,Water
6,Carbon dioxide
7,Sulphur dioxide
8,Nitrogen
9,Water-rich
10,Methane-rich
11,Ammonia-rich
12,Carbon dioxide-rich
13,Methane
14,Helium
15,Silicate vapour
16,Metallic vapour
17,Neon-rich
18,Argon-rich
19,Neon
20,Argon
21,Oxygen
22,hot thick silicate vapour atmosphere
23,hot thick methane rich atmosphere
24,carbon dioxide atmosphere
25,thin ammonia atmosphere
26,thick argon rich atmosphere
27,argon rich atmosphere
28,nitrogen atmosphere
29,carbon dioxide rich atmosphere
30,thin sulphur dioxide atmosphere
31,helium atmosphere
32,hot thick carbon dioxide atmosphere
33,hot thick water atmosphere
34,thick methane rich atmosphere
35,thick carbon dioxide rich atmosphere
36,hot thick ammonia atmosphere
37,hot carbon dioxide atmosphere
38,thick ammonia atmosphere
39,hot water atmosphere
40,thick atmosphere
41,thick helium atmosphere
42,thick carbon dioxide atmosphere
43,thin methane atmosphere
44,methane atmosphere
45,thin neon atmosphere
46,thick nitrogen atmosphere
47,argon atmosphere
48,thick ammonia rich atmosphere
49,thin oxygen atmosphere
50,thick methane atmosphere
51,neon rich atmosphere
52,hot thick ammonia rich atmosphere
53,thick water rich atmosphere
54,thin carbon dioxide atmosphere
55,sulphur dioxide atmosphere
56,thin argon atmosphere
57,thin neon rich atmosphere
58,thin nitrogen atmosphere
59,hot thick water rich atmosphere
60,hot thick sulphur dioxide atmosphere
61,hot sulphur dioxide atmosphere
62,hot silicate vapour atmosphere
63,hot thick carbon dioxide rich atmosphere
64,hot thick argon rich atmosphere
65,thin carbon dioxide rich atmosphere
66,thin helium atmosphere
67,water atmosphere
68,thin argon rich atmosphere
69,methane rich atmosphere
70,oxygen atmosphere
71,ammonia atmosphere
72,hot thin sulphur dioxide atmosphere
73,thick argon atmosphere
74,thin water rich atmosphere
75,hot thin silicate vapour atmosphere
76,water rich atmosphere
77,ammonia rich atmosphere
78,hot thick metallic vapour atmosphere
79,hot thick methane atmosphere
 
Last edited:

AnthorNet

AnthorNet
daver4470 said:
Wistful observation: I wish there was a way that CL and EDD could share a common EDSM database, as in the long run it's going to get awfully inefficient to have two of them floating around.
Click to expand...

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.
 

disorganise

disorganise
AnthorNet said:
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.
Click to expand...

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
 

Genar-Hofoen

Genar-Hofoen
disorganise said:
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
Click to expand...

Ah, no. At the moment CL2 only downloads the nightly dump from EDSM. Today that file is 819MB in size. It's a JSON text file.

Then CL2 reads that, and creates a database out of it. The created EDSM.db is smaller at 523MB.

You have to remember something; What's being stored is: <system name> , <edsm id> , <x coord> , <y coord> , <z coord>. Now, times that by 6 million, four hundred and 9 thousand, three hundred and sixteen - because that's how many records were in the Nightly Dump which my CL2 downloaded and imported today.

6,409,316 records of <system name> , <edsm id> , <x coord> , <y coord> , <z coord>

That's a LOT of data. There will be more at EDSM's server.

Frankly it's amazing.

I am trying to keep CL2's disk space usage to a minimum, as well as its memory footprint, and so far I've been managing to do so. CL2's GALAXY db is a compact format, but it too has to store system names, planet designations, planet types, planet scan data, materials and so on. Nevertheless it's still a compact format.

If I started to think about just how much data FDEV has to store, I probably wouldn't be able to sleep at night :)

So as far as CL2 is concerned, it's not going to be generating 6GB databases any time soon - although data IS going to be an issue for everyone, as more people explore the galaxy and send back more data - it's only going to go up.

Lastly, usage of the EDSM nightly dump is entirely optional in CL2. You can choose not to download the Nightly Dump and it won't impact on the operation of CL2. Nothing is downloaded automatically on startup. You choose whether you want to utilise the Nightly Dump data or not, and you also choose whether or not you want to update that data.

I could, for example, update, like I did today, then not update for another month or so. Entirely up to you.

Regards
 

AnthorNet

AnthorNet
disorganise said:
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
Click to expand...

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 !
 
You must log in or register to reply here.
Back
Top Bottom