Release [Explorer's Application] Captain's Log

[Skyflyer]

I scanned a Herbig Ae/Be star that somehow didn't get picked up by Captain's Log 2. Just before the Herbig star I scanned an O type star and that worked just fine and just after the Herbig star I scanned a type III gas giant without problems. I have no idea why Captain's Log 2 didn't register the star when I scanned it. The section with the scanned star is as following:

{ "timestamp":"2017-04-29T08:49:02Z", "event":"StartJump", "JumpType":"Hyperspace", "StarSystem":"Plimbeau BA-A g1", "StarClass":"O" }
{ "timestamp":"2017-04-29T08:49:20Z", "event":"FSDJump", "StarSystem":"Plimbeau BA-A g1", "StarPos":[-3221.031,1412.344,27382.344], "SystemAllegiance":"", "SystemEconomy":"$economy_None;", "SystemEconomy_Localised":"None", "SystemGovernment":"$government_None;", "SystemGovernment_Localised":"None", "SystemSecurity":"$SYSTEM_SECURITY_low;", "SystemSecurity_Localised":"Low Security", "JumpDist":25.321, "FuelUsed":2.479277, "FuelLevel":21.947332 }
{ "timestamp":"2017-04-29T08:49:41Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 A", "DistanceFromArrivalLS":0.000000, "StarType":"O", "StellarMass":28.980469, "Radius":6139642368.000000, "AbsoluteMagnitude":-8.665710, "Age_MY":0, "SurfaceTemperature":43461.000000, "SemiMajorAxis":7536957718528.000000, "Eccentricity":0.037610, "OrbitalInclination":39.101734, "Periapsis":244.664093, "OrbitalPeriod":20717912064.000000, "RotationPeriod":278434.593750 }
{ "timestamp":"2017-04-29T08:49:47Z", "event":"FuelScoop", "Scooped":5.001029, "Total":26.948341 }
{ "timestamp":"2017-04-29T08:50:00Z", "event":"FuelScoop", "Scooped":5.004536, "Total":31.952847 }
{ "timestamp":"2017-04-29T08:50:01Z", "event":"FuelScoop", "Scooped":0.047153, "Total":32.000000 }
{ "timestamp":"2017-04-29T08:59:31Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 B", "DistanceFromArrivalLS":129464.460938, "StarType":"AeBe", "StellarMass":7.308594, "Radius":120748880.000000, "AbsoluteMagnitude":10.578644, "Age_MY":2, "SurfaceTemperature":3692.000000, "SemiMajorAxis":29877948383232.000000, "Eccentricity":0.037610, "OrbitalInclination":39.101734, "Periapsis":64.664093, "OrbitalPeriod":20717912064.000000, "RotationPeriod":6619.479980 }
{ "timestamp":"2017-04-29T09:01:37Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 B 1", "DistanceFromArrivalLS":129667.257813, "TidalLock":false, "TerraformState":"", "PlanetClass":"Sudarsky class III gas giant", "Atmosphere":"", "AtmosphereComposition":[ { "Name":"Hydrogen", "Percent":73.432655 }, { "Name":"Helium", "Percent":26.567341 } ], "Volcanism":"", "MassEM":655.843994, "Radius":70841344.000000, "SurfaceGravity":52.087841, "SurfaceTemperature":357.551483, "SurfacePressure":0.000000, "Landable":false, "SemiMajorAxis":1260845268992.000000, "Eccentricity":0.433934, "OrbitalInclination":-78.166061, "Periapsis":255.462097, "OrbitalPeriod":285559136.000000, "RotationPeriod":75899.625000 }

I include all the journal entries I got in that system.
The scan got registered in EDDiscovery.

 

[Genar-Hofoen]

I scanned a Herbig Ae/Be star that somehow didn't get picked up by Captain's Log 2. Just before the Herbig star I scanned an O type star and that worked just fine and just after the Herbig star I scanned a type III gas giant without problems. I have no idea why Captain's Log 2 didn't register the star when I scanned it. The section with the scanned star is as following:

{ "timestamp":"2017-04-29T08:49:02Z", "event":"StartJump", "JumpType":"Hyperspace", "StarSystem":"Plimbeau BA-A g1", "StarClass":"O" }
{ "timestamp":"2017-04-29T08:49:20Z", "event":"FSDJump", "StarSystem":"Plimbeau BA-A g1", "StarPos":[-3221.031,1412.344,27382.344], "SystemAllegiance":"", "SystemEconomy":"$economy_None;", "SystemEconomy_Localised":"None", "SystemGovernment":"$government_None;", "SystemGovernment_Localised":"None", "SystemSecurity":"$SYSTEM_SECURITY_low;", "SystemSecurity_Localised":"Low Security", "JumpDist":25.321, "FuelUsed":2.479277, "FuelLevel":21.947332 }
{ "timestamp":"2017-04-29T08:49:41Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 A", "DistanceFromArrivalLS":0.000000, "StarType":"O", "StellarMass":28.980469, "Radius":6139642368.000000, "AbsoluteMagnitude":-8.665710, "Age_MY":0, "SurfaceTemperature":43461.000000, "SemiMajorAxis":7536957718528.000000, "Eccentricity":0.037610, "OrbitalInclination":39.101734, "Periapsis":244.664093, "OrbitalPeriod":20717912064.000000, "RotationPeriod":278434.593750 }
{ "timestamp":"2017-04-29T08:49:47Z", "event":"FuelScoop", "Scooped":5.001029, "Total":26.948341 }
{ "timestamp":"2017-04-29T08:50:00Z", "event":"FuelScoop", "Scooped":5.004536, "Total":31.952847 }
{ "timestamp":"2017-04-29T08:50:01Z", "event":"FuelScoop", "Scooped":0.047153, "Total":32.000000 }
{ "timestamp":"2017-04-29T08:59:31Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 B", "DistanceFromArrivalLS":129464.460938, "StarType":"AeBe", "StellarMass":7.308594, "Radius":120748880.000000, "AbsoluteMagnitude":10.578644, "Age_MY":2, "SurfaceTemperature":3692.000000, "SemiMajorAxis":29877948383232.000000, "Eccentricity":0.037610, "OrbitalInclination":39.101734, "Periapsis":64.664093, "OrbitalPeriod":20717912064.000000, "RotationPeriod":6619.479980 }
{ "timestamp":"2017-04-29T09:01:37Z", "event":"Scan", "BodyName":"Plimbeau BA-A g1 B 1", "DistanceFromArrivalLS":129667.257813, "TidalLock":false, "TerraformState":"", "PlanetClass":"Sudarsky class III gas giant", "Atmosphere":"", "AtmosphereComposition":[ { "Name":"Hydrogen", "Percent":73.432655 }, { "Name":"Helium", "Percent":26.567341 } ], "Volcanism":"", "MassEM":655.843994, "Radius":70841344.000000, "SurfaceGravity":52.087841, "SurfaceTemperature":357.551483, "SurfacePressure":0.000000, "Landable":false, "SemiMajorAxis":1260845268992.000000, "Eccentricity":0.433934, "OrbitalInclination":-78.166061, "Periapsis":255.462097, "OrbitalPeriod":285559136.000000, "RotationPeriod":75899.625000 }

I include all the journal entries I got in that system.
The scan got registered in EDDiscovery.

Try going to Configuration, select your database, and click on the button marked "Reset star/planets to default values" - this does a little bit more than what the button states - it also fixes an error in the GALAXY database introduced from early on in CL 2.x's life in which there were 3 entries for Herbig Ae/Be star types which confuse CL 2.x when looking that type up.

I did have a rather large announcement/warning about that particular error and fix a while back, you might have missed it, sounds like you have.

Once that's done, try scanning another Herbig Ae/Be star - it should now register.

Or if there's not a new one handily close by, try creating a new trip DB and 'scan & import' the journal logs to it - see if it appears for that star system.

 

[Cometborne]

First of all, good job on 2.0.0 "gold". I have three wishes for the bearing calculator:
a) Can you implement a hot-key that opens just the bearing calculator while in overlay mode, please?
b) Can you make the window a little less tall or moveable? At the moment, the combination of the normal overlay plus the bearing calculator covers the heading display.
c) There looks to be a bug in the calculation. If I ask for the course from 10/20 to to 10/-40, it gives me a course of 276 degree. If I reduce the target longitude even further, the calculated course diverts even more northwards. 10/20 to 10/-120 is 296 degree. This should all be 270 degrees

 

[VerticalBlank]

I don't think that's a bug. It's computing the shortest path, along a great circle, not along a parallel of latitude.

 

[Genar-Hofoen]

First of all, good job on 2.0.0 "gold". I have three wishes for the bearing calculator:
a) Can you implement a hot-key that opens just the bearing calculator while in overlay mode, please?
b) Can you make the window a little less tall or moveable? At the moment, the combination of the normal overlay plus the bearing calculator covers the heading display.
c) There looks to be a bug in the calculation. If I ask for the course from 10/20 to to 10/-40, it gives me a course of 276 degree. If I reduce the target longitude even further, the calculated course diverts even more northwards. 10/20 to 10/-120 is 296 degree. This should all be 270 degrees

Hi Udo,

(a) Can do - I was thinking about it at the time I implemented the Bearing Calc for the overlay, but obviously didn't do it for 2.0.0

(b) I could make the window independently movable - it's actually an independent window, but at this time it's programmed to follow the overlay window position like an obedient puppy.

That's a bit easier to do than adjust the size, because the Bearing Calc is actually an almost standalone Class in programming parlance and as such meant I could re-use the module for the overlay. If I adjusted the size for the overlay, it would adjust the size for the one running in the main window.

(c) I'm not sure if there is a problem. I have tested the Bearing calculation itself quite extensively, by flying a ship from a known point on a planet to another point, and taking a note of the different LAT/LON coordinates, then flying to other positions, and seeing if I can get back to the original point by using the bearing calculation, and it's always seemed to work for me, so I'm pretty much convinced it does work as intended. There are two different bits of maths used in the Calculator as well - one for the bearing, and the other uses the Haversine Formula for calculating distance around a sphere between two coordinates, based on sphere diameter. That seems to be spot on as well, and automatically adjusts to suit according to the varying diameter of the body being landed on.

 

[Taranis Dekker]

Firslty, thanks to the author for putting this together - and maintaining it as well. I've only just started exploring (properly anyway), and I do like it.

I do have one problem with it, though, and I can't for the life of me work out why it's occurring, or how to stop it.

I load up the log, fire up ED launcher, and then ED, and start playing. However, the Log doesn't update with new systems I jump to, or planets I scan. I have to quit out of everything, back to bare desktop, and then reload everything, same order, and then it will start logging scans and jumps. I don't have any other ED apps running - I use ED Engineer, but the issue occurs without that running.

Any thoughts?

 

[Genar-Hofoen]

Firslty, thanks to the author for putting this together - and maintaining it as well. I've only just started exploring (properly anyway), and I do like it.

I do have one problem with it, though, and I can't for the life of me work out why it's occurring, or how to stop it.

I load up the log, fire up ED launcher, and then ED, and start playing. However, the Log doesn't update with new systems I jump to, or planets I scan. I have to quit out of everything, back to bare desktop, and then reload everything, same order, and then it will start logging scans and jumps. I don't have any other ED apps running - I use ED Engineer, but the issue occurs without that running.

Any thoughts?

That's a new one on me - I do the exact same thing and it works first time all the time. Weird!

 

[Aura Lorell]

That's a new one on me - I do the exact same thing and it works first time all the time. Weird!

It has also happened to me and it's intermittent at best. The best way to describe it is that if I start Captain's Log before I start Elite, there is a good chance it will not pick up any changes in the journal. The only way around it is if I start Elite first, load into the level (although loading into the level is probably irrelevant) and then start Captain's Log. Of course the trouble is that if I forget to start CL and make a jump or scan things it won't pick up the changes (and even worse if I start after I've jumped and scan it will put the scanned bodies in the wrong system). It would be awesome if it did pick up the changes, I understand the structure and functionality of the journal and it's not exactly impossible to pick up any changes from the last entry to the most recent (and no, importing ALL journal logs is not the answer to this issue).

 

[Taranis Dekker]

It has also happened to me and it's intermittent at best. The best way to describe it is that if I start Captain's Log before I start Elite, there is a good chance it will not pick up any changes in the journal. The only way around it is if I start Elite first, load into the level (although loading into the level is probably irrelevant) and then start Captain's Log. Of course the trouble is that if I forget to start CL and make a jump or scan things it won't pick up the changes (and even worse if I start after I've jumped and scan it will put the scanned bodies in the wrong system). It would be awesome if it did pick up the changes, I understand the structure and functionality of the journal and it's not exactly impossible to pick up any changes from the last entry to the most recent (and no, importing ALL journal logs is not the answer to this issue).

I'll try doing it that way this afternoon. I've just docked at the asteroid base in the Soul nebula, on my way to the Rift, so I can scan around in-system before I jump out. I figure losing a single planet-scan is less painful to me than losing an entire jump + star scan - which has happened before I noticed it wasn't logging.

Edited... I can confirm that it worked first time, loading into game + save, then loading Captain's Log afterwards. Thanks for the tip [up]

 

[Genar-Hofoen]

I'll try to investigate what's happening. It sounds like from the description, that CL isn't picking up on a new journal log being created when the game is started - what should happen is that upon starting up the app, CL should get the last journal entry - if you then start the game and a new journal log is created, CL should detect that and start using the new journal log.

If that isn't happening for some reason, then CL will still be looking at the last journal log, which would exhibit the behaviour being reported.

The trouble is, seeing as that has never happened on my PC, that's going to be a tough one for me to investigate.

 

[Ralph Vargr]

Any chance for an export to CSV?

 

[Genar-Hofoen]

Any chance for an export to CSV?

It's on The List[tm]

 

[wilodonny]

Personally edit data

I have just found out about this piece of software and gave it a try and got to say works fantastic (2.0) im using.

My question is though for some reason i can add new data for unexplored planets and stars yet i cannot get the data for any i have found for example i am in LT 133 and can see all planets even which are landable etc yet on this software it is showing 0 stars and 0 planets. So i would like to know how i would go about adding data for any planet/star previously scanned.

To add ... i did do the import DB so it has correctly scanned my journals and is showing all of my previous jumps from before installing this software.

Any help would be greatly appreciated.

 

[Genar-Hofoen]

I have just found out about this piece of software and gave it a try and got to say works fantastic (2.0) im using.

My question is though for some reason i can add new data for unexplored planets and stars yet i cannot get the data for any i have found for example i am in LT 133 and can see all planets even which are landable etc yet on this software it is showing 0 stars and 0 planets. So i would like to know how i would go about adding data for any planet/star previously scanned.

To add ... i did do the import DB so it has correctly scanned my journals and is showing all of my previous jumps from before installing this software.

Any help would be greatly appreciated.

Hi - you won't get any data for exisiting data you already have - these are called the 'known systems' - your ship already magically had this data to begin with when you first started playing the game. There are still a lot of systems in the Bubble for which you don't have data on, but there are a lot of systems in the bubble for which you already had the data on. And seeing as there's no way to re-scan systems you already have data for, there will be no Player Journal entry created for them for this app or any other app to work with.

Regards o7

 

[wilodonny]

Hi - you won't get any data for exisiting data you already have - these are called the 'known systems' - your ship already magically had this data to begin with when you first started playing the game. There are still a lot of systems in the Bubble for which you don't have data on, but there are a lot of systems in the bubble for which you already had the data on. And seeing as there's no way to re-scan systems you already have data for, there will be no Player Journal entry created for them for this app or any other app to work with.

Regards o7

Hey thanks for a speedy reply. So if i undestand this correctly this will only add data from sources entitled "unexplored" and there is no way to add date from planets/star that were previously called "unexplored" that i have persoanlly scanned before using this software?

 

[wilodonny]

Hi - you won't get any data for exisiting data you already have - these are called the 'known systems' - your ship already magically had this data to begin with when you first started playing the game. There are still a lot of systems in the Bubble for which you don't have data on, but there are a lot of systems in the bubble for which you already had the data on. And seeing as there's no way to re-scan systems you already have data for, there will be no Player Journal entry created for them for this app or any other app to work with.

Regards o7

but is there a way i can persoanl enter star/planet information to an area that falls under this rule???

 

[Genar-Hofoen]

but is there a way i can persoanl enter star/planet information to an area that falls under this rule???

Not currently in the program. It's one of the things I have on The List[tm] - but as Sandro says... "No ETA's, no guarantees!" - it'd take a bit of work to get something like that into the application.

Regards o7

 

[disorganise]

Rather than write code in CL2 itself....would it be possible to create fake entries in the journal instead and have CL2 suck them in?
If yes I guess a standalone tool will be possible to make such a thing easier.

 

[Genar-Hofoen]

Rather than write code in CL2 itself....would it be possible to create fake entries in the journal instead and have CL2 suck them in?
If yes I guess a standalone tool will be possible to make such a thing easier.

It'd be entirely possible to write a Fake Player Journal Generator, that's a fantastic idea, in fact. +repped.

I now await someone to write such a beast

EDIT: Actually, the best outcome would be if Frontier made a change to the Detailed Surface Scanner - if they could make it so it could be manually triggered by a Commander, and if that would produce a Player Journal entry for the body being scanned - then 3rd party apps like Captain's Log, and EDDiscovery for example, could read the Journal and add or update the info for that body. That would be awesome if they did even that - and apart from perhaps some additional GUI coding and an adjustment to their DSS code, it probably wouldn't be anything like a radical re-write or somesuch.

 

[VerticalBlank]

Isn't that data already in Ross / EDDB for the most part? Reading it from there sounds like a better idea than messing around with fake journal entries.