The HasLatLon thingy in the Status.json has been fixed, but I've just decided to stick with my own internally built version of that, coz it works so why notI guess we really won't know if there are any Sneak Changes that will cause issues until 3.0 drops, but I assume that the problem in the Journals that you had to code around has been acknowledged by FD? Really find CL a Huge Help even when I am in the Bubble.
Is there an way to fill in missed jumps?
After 3.0 downloaded this morning (my time) and I eventually got in passed the nginx errors, I noticed CL was not updating.
I quit and restarted...still nope.
Quit and started as admin....nope....scanned a body and it appeared and next jump was noted.
Clearly I have some odd issue to fix (I'll try take ownership of all the relevant folders), but is there a way to get the missing half dozen or so jumps into the trip log?
Darn. OK. I'll live with the gap.. I'm 130kly into the trip..nginx errors?
If jumps have been missed, the only way to get 'em back in would be to start a new blank trip DB and import the logs into that.
I think CL2 needs to know about the planet - I may have coded everything with the assumption that the planet you want to land on or fly around has had a scan performed and hence the data loaded into CL2.I have downloaded updated to CL 2.1.7 as per the instructions and was anxious to try out the Navigation function. I may be doing it wrong and not understand the new function, but it does not appear to be working for me.
I approached a planet (didn't have to scan it, it was already known to me but not in the CL database) and once in Orbital Cruise I opened the main CL window by hotkey and I set the planets Radius and the destination coordinates. No bearing indicator showed on the overlay.
Does it not work on planets that are not scanned by me (therefore not in the CL Database) but already known? Must I have the Detailed Scanner even on known worlds? (I was in a new ship for testing)
Am I doing it wrong? (probably the right answer)
Definitely in the bubble known system, Shinrarta, so I had all the data. I assumed that CL would pick it up from the journals and know I would be on approach when in orbital and would take my coordinates.I think CL2 needs to know about the planet - I may have coded everything with the assumption that the planet you want to land on or fly around has had a scan performed and hence the data loaded into CL2.
It is an app with Exploration in mind after all
If this is a planet in one of the 'known' systems - i.e. the ship already had all the scan data (as with a lot of bubble systems), and if that system has a Nav Beacon, you can go to the Nav Beacon and scan it. Note that having a DSS fitted whilst doing so is recommended. Captain's Log will then receive all the data about all the bodies within that system, exactly as if you have DSS scanned them yourself.
That's the only way Frontier has provided - very kindly too I might add! We didn't have the nav beacon scan like that before! That was introduced in the previous last Horizons update.Definitely in the bubble known system, Shinrarta, so I had all the data. I assumed that CL would pick it up from the journals and know I would be on approach when in orbital and would take my coordinates.
I know its more for exploration, which I am using it for, but the other uses for it on known planets because of the navigation ability would a boon. I am using it on my other account, but was dying to try out the Chieftain and of course, that meant landing on a new looking planet to compare how it looked before.
So scanning the Beacon would be the only option for places that are already know?
You're running a 4K or otherwise Hi-DPI screen, right?
You are correct, I am running 4K and your suggestion fixed the problem, thank you very much.You're running a 4K or otherwise Hi-DPI screen, right?
Try bringing up the Windows Preferences menu for the CL2 exe file and going to the Compatibility tab - Override Hi-DPI Scaling Behaviour like so...
It'll be one of those options of Application, System, or System (Enhanced) which might work to bring those pesky fonts back under control.
Think of CL2 as using 'legacy' toolkits for its production. One of these days I'll be able to switch over to something more modern.
Currently you can only add bookmarks to landable planets already known to CL2.So quick question about the planet bookmarks. Didn't get chance to try yet (have landed and noted the coordinates updating ) but are these addable only for planets you're currently or specifically known to you (well...CL)?
Maybe I'm better pitching an idea...
Being on an expedition at the moment (DECE) the base camp coordinates get published a few days or weeks ahead of time by the scouts. It would be awesome to be able to add these coordinates into CL so when we arrive and scan the planet, the base camp is known so we be directed towards it.
I don't know how bookmarks are handled (yet) but if there were multiple on a body, perhaps a mini list could pop up and something magical like 'Alt & arrow up/down' could be used to choose the one you want without necessarily losing control of the ship.
The prepopulating bookmarks idea also gives rise to extension.....export/import options for easy sharing between Cmdr's, and maybe having them stored and read from EDSM (restricted to expedition organisers perhaps for the storing and obviously EDSM needs to be extended for this).
Ring systems do not have any kind of coordinate system in the game, so there is nothing to work with to accomplish something like that.Loving the new versions of Captains Log, (just returned to the game after a year away, and the improvements to this application are astonishing).
Quite interested in the planet bookmarks, though I have yet to find anything worthy of them to test them on. What I'm more curious about though is if its possible to extend that coordinate system to cover planetary rings?
Reading some of the other threads about mining, it seems that the contents of planetary rings are persistent, so being able to book mark lucrative coordinates would be very very useful.
I think it could only be for bodies scanned and pushed to EDSM. So system and body names can be searchable from EDSM, much like the set destination is done now.You would have to manually add the star system name, then the planet name, then the planet data (e.g. radius and all the rest) before being able to add bookmarks. And that'd be horribly cumbersome and laborious. I'd also need to design a UI for that, plus write the UI glue code and the necessary code to bung that data to the Galaxy database.
Ideas are always appreciatedI think it could only be for bodies scanned and pushed to EDSM. So system and body names can be searchable from EDSM, much like the set destination is done now.
I think you only need to store the co-ords up front. When we arrive in system and scan the body, all radius etc becomes known to CL and it can then calculate headings etc. This calculation only makes sense as we enter orbit, so knowing the radius beforehand ought not be needed. The bookmark is just a pair of arbitrary numbers until we get there.
The programme is awesome already
Just tossing ideas around really