Genar, is this indicative of me having moved the DB? If so how can I get it to start and point to the new location?
Otherwise, can only think this is because I upgraded to windows 10
View attachment 53276
Thanks for your world-changing efforts, as always
Yeah this'll happen if you move the DB and CL isn't expecting that
Either move the DB back to where it was, or remove the CL config file (captainslog.cfg) and re-do the initial configuration, pointing to where you keep that DB file now.
Lemme know how you got on.
Regards
Thanks buddy, we have success!
You'll be pleased to know that the legendary piece of coding called Captain's Log works on Windows 10.
That's like telling an engineer the space suit he invented made a successful test run inside the corona of a star




Hi again! I think I may have found another bug, this time with the estimated values.
The first image shows a single M star, here the values are correct (the values are ones I put in myself, hence the difference to the defaults).
The second image shows a single L star, still correct.
The third is 2 M stars, also correct.
But the fourth image where it has 1 M and 1 L star the value isn't just M+L, but rather more than the two individual values added together. This happens with any stars not just the M and L types (just took those for examples), it may also happen with planets but I'm not sure.
Thanks!![]()
Hello there
Yes, there is indeed a bug - someone pointed that out to me on my website a few days ago, and this has already been fixed in the code but not yet released. It was a really silly bug too
Notice though that the bug only affects the estimate in the System Bodies tab - the stats tab shows the correct values
But thanks for bringing this up here as well
Regards
I'm working on changing the planets input method to something similar to stars (i.e. Clickety click)...
Just got the icons created earlier. Added the clickable widgets and configured those with the relevant icon.
Next up will be the epic coding session it's going to take to replace the old input method with awesome clicky goodness.![]()
While you're at it, something that i dislike is the input of a designation, would it be easy for you to scrap this or make like a switch to an auto input like elw1,hmc1 etc., because that's what i'm doing manually atm. and it's cumbersome i'd say.
and one question, i abbreviate terraforming with "tf" so why is it "tc" in your case?
That's the whole idea of what I'm doing - getting rid of the cumbersome manual input of designations
Even I am growing tired of that!
(It was 'placeholder' content anyway)
EDIT: "TC" because "Terraforming Candidate" !
Regards
I always see this abbreviated as "TFC" for clarity.EDIT: "TC" because "Terraforming Candidate" !
I always see this abbreviated as "TFC" for clarity.
When I can feed my Asp a sandvich, I'll consider getting confused by that. XDNo good, that's for Team Fortress.
Question, would I still be able to add new types of planets?
Perhaps future-proofing: add an "Unclassified" type where people can add a note to the effect of what it actually is.Yes, that's where the problem lies - what to do about custom planet types?
To say nothing of what might change about the kinds (and volume!) of notes/data we need to record on existing types.Also - it looks very much like with the upcoming Horizons season, planet types might change in ways we don't yet know about.
Perhaps future-proofing: add an "Unclassified" type where people can add a note to the effect of what it actually is.
Otherwise people will end up having to choose another type arbitrarily to stand in for "unclassified" worlds, and that could result in dirty data.
To say nothing of what might change about the kinds (and volume!) of notes/data we need to record on existing types.

