My personal issues and my PC are in a locked loop with each other, and have been since 1980 or so... 
Release [Explorer's Application] Captain's Log
- Thread starter Genar-Hofoen
- Start date
Windows panicked and hard rebooted while CL 2.1.6 was open and now it complains upon launch:
captainslog2.ini is indeed full of NULLs. Deleting it solves the problem. Of course, I had to redo my config, resupply imgur credentials, etc, which was a bit of a faff.
Not a huge deal but thought you should know. I've now made a backup of the INI file. Not sure how it came to be full of NULLs.
captainslog2.ini is indeed full of NULLs. Deleting it solves the problem. Of course, I had to redo my config, resupply imgur credentials, etc, which was a bit of a faff.
Not a huge deal but thought you should know. I've now made a backup of the INI file. Not sure how it came to be full of NULLs.
Yep it's probably the 5th time someone's had a VERY similar thing happen to the INI file - Imma try to see if I can track down what the Frank the problem is there. Thanks for the feedback - always appreciated!
Well I have this tool working perfectly now. I've discovered what works for me. My log in troubles are solved. Here's what I do:
Launch CL2 1st. My current data-base loads. Next I launch the game. Now before doing anything I re-load my current data-base again.
The program now sees me and I can proceed just fine.
Launch CL2 1st. My current data-base loads. Next I launch the game. Now before doing anything I re-load my current data-base again.
The program now sees me and I can proceed just fine.
I mostly load CL2 first before loading the game in then I always check to make sure it knows the games running but occasionally I have this happen when I make my first jump into a new system;
CL2 didn't move with me to the next system so when I scanned a WW it didn't show up so I re-start CL2 which still listed me as being in the previous system yesterday. So I honked again (pointless really) and then scanned 4 HMC planets which then showed up in CL2 as being part of the last system. You can see the different names/dates in the log on the snapshot I've taken, when I move on to the next system it starts working perfectly again. No idea what causes it but I just have to try and remember to check CL2 after I change location and honk the first time it's loaded in. Love the programme by the way it's in constant use when the games running.
CL2 didn't move with me to the next system so when I scanned a WW it didn't show up so I re-start CL2 which still listed me as being in the previous system yesterday. So I honked again (pointless really) and then scanned 4 HMC planets which then showed up in CL2 as being part of the last system. You can see the different names/dates in the log on the snapshot I've taken, when I move on to the next system it starts working perfectly again. No idea what causes it but I just have to try and remember to check CL2 after I change location and honk the first time it's loaded in. Love the programme by the way it's in constant use when the games running.
Last edited:
So I'm not the only one. Thanks Dave that looks similar to what I was seeing. I'm going to continue using my workaround.
And yes this program is awesome. I absolutely love it. I've since ditched EDD (not because its not good mind you its just I'd rather keep my data private now that I'm out far enough to start finding virgin stuff)
And yes this program is awesome. I absolutely love it. I've since ditched EDD (not because its not good mind you its just I'd rather keep my data private now that I'm out far enough to start finding virgin stuff)
I'll investigate this a bit deeper, guys, thanks for the feedback.
It's difficult if I can't replicate the behaviour though.
I don't think I'll be patching CL2 until after the festival period/New Year. I need a rest
It's difficult if I can't replicate the behaviour though.
I don't think I'll be patching CL2 until after the festival period/New Year. I need a rest
I really like this for exploring, but it still causes headaches. It takes me several load attempts of either or both CL and ED before CL starts recognising that I've jumped to a new system or scanned a planet or star. In the mean time, I lose scan information or it shows up under the wrong system. Very frustrating.
Still, that said, I like the program, and appreciate your work and your efforts to update it.
Still, that said, I like the program, and appreciate your work and your efforts to update it.
Last edited:
Genar now we're seeing more folks with this issue. Thanks for investigating this.
Mike have you tried my work-around?
I think what I did was quit everything, load ED Launcher, load CL, load ED, quit CL, load CL, load CMDR. I may have gotten the first two switched around, but next time I try it, I'll confirm. It did work though, and logged planetary scans in the correct star system as well.
I also use EDengineer and the ED Market Connector to keep Inara and EDSM up-to-date, but I didn't have EDengineer running this time.
[up]
Last edited:
So that makes about 2 CL2 users.
Thing is, if this was an obvious bug, it would be affecting a lot more than 2 people and this thread would be buzzing with reports and I'd have heard about it on the Discord server.
Since it isn't, this means it's more than likely to be an issue with the system CL2 is running on.
So both of you need to find out what the commonality is between your two systems, then perhaps I might be able to do something about it. But if it's something to do with the PC it's running on, I doubt there's going to be much I could do about it.
I cannot replicate the behaviour being reported, and I am not seeing widespread screaming about it - what am I to do?
Thing is, if this was an obvious bug, it would be affecting a lot more than 2 people and this thread would be buzzing with reports and I'd have heard about it on the Discord server.
Since it isn't, this means it's more than likely to be an issue with the system CL2 is running on.
So both of you need to find out what the commonality is between your two systems, then perhaps I might be able to do something about it. But if it's something to do with the PC it's running on, I doubt there's going to be much I could do about it.
I cannot replicate the behaviour being reported, and I am not seeing widespread screaming about it - what am I to do?
This sequence works for me.
Genar, not disagreeing with your point that more users should be affected. I just can't imagine what specific set of circumstances would need to be in place for it to happen, that would only affect 2 of us... :S
So that makes about 2 CL2 users.
Thing is, if this was an obvious bug, it would be affecting a lot more than 2 people and this thread would be buzzing with reports and I'd have heard about it on the Discord server.
Since it isn't, this means it's more than likely to be an issue with the system CL2 is running on.
So both of you need to find out what the commonality is between your two systems, then perhaps I might be able to do something about it. But if it's something to do with the PC it's running on, I doubt there's going to be much I could do about it.
I cannot replicate the behaviour being reported, and I am not seeing widespread screaming about it - what am I to do?
I'm not concerned about it, it's happed maybe 3-4 times in the last 2 months so it's not like it's consistent enough for me to point a finger at a possible cause, I'll just try to remember to check CL on first run of the day. I do have EDSM running and accessing the games journal beside CL2.
Indeed - and all I can do is look at my code and say "welp, things are executing in the correct order upon loading" and then *blank stare*
Indeed... it's a minor irritation compared to others. Oh well... only 99.9952% of the galaxy left to log for EDSM.
FWIW I have symptoms similar to Commander Mike.
I start CL2 and launch ED, jump to a system and scans would not register. This was pretty much reproducible every time. For a while I tried different variations of launch, relaunch, etc.. with no consistent solution. Now, what seems to work best is: launch CL2, launch ED. In CL2 under Configure with the existing DB that is loaded by default highlighted, choose Switch to Highlighted DB, and let that process. Afterwards, scans show up as expected. I don't think I've had the issue at all as long as I perform the "Switch to DB" step before scanning. Whether I launch ED before or after the "Switch DB" step seems to have no effect.
Genar,
Great tool. Many thanks for the efforts you've put into it. It is the perfect companion for my exploration trips.
I start CL2 and launch ED, jump to a system and scans would not register. This was pretty much reproducible every time. For a while I tried different variations of launch, relaunch, etc.. with no consistent solution. Now, what seems to work best is: launch CL2, launch ED. In CL2 under Configure with the existing DB that is loaded by default highlighted, choose Switch to Highlighted DB, and let that process. Afterwards, scans show up as expected. I don't think I've had the issue at all as long as I perform the "Switch to DB" step before scanning. Whether I launch ED before or after the "Switch DB" step seems to have no effect.
Genar,
Great tool. Many thanks for the efforts you've put into it. It is the perfect companion for my exploration trips.
That's my workaround too.
Genar there's something I'd like to see... a jump counter put in the overlay showing your current jump count based on the database your are using.
Is this possible?
I have a weekly goal of systems to explore and it would be nice to have it in the overlay. I know i can alt/c and see it but it's just a suggestion.
Thanks
Hi osser. I'll see about putting that in for the upcoming CL2 release which I'll inevitably need to do to cope with any changes in the Journal which usually occur with a new version of the game.
Regards o7
I have released a Beta version of CL 2 - 2.1.7 Beta 1
NOTE: It will only work with the Beta version of ED. It will NOT work with the current live version of the game. It will only read the JournalBeta files. Do not come back to me with "It ain't workin with the live game no more!!" (I already had that on my Discord channel today )
This beta has realtime LAT/LON update from the 3.0 Beta added into it. You set your target LAT/LON using the Bearing & Distance panel (click on one of the Bearing Buttons either on the Overlay widget or on the main window.)
Once a target LAT/LON is set, make sure you preselect the correct planet you're going to be navigating - this sets the correct planet radius for the Distance calculation.
When you go into Orbital Cruise, and have set a LAT/LON target, a NAV frame will appear on the Overlay, showing the bearing you need to point in to reach your target LAT/LON coordinates, and the ground distance over a sphere (Haversine formula) from your current LAT/LON to your target LAT/LON.
Navigating is now basically matching up the ship's bearing with the CL2 NAV Bearing.
Full details of the Beta are on the Captain's Log Discord server, #beta_testing channel, see pinned message. See my signature for the Discord invite/link.
Here's a video of me testing it out (skip the first 2 minutes - I was pfaffing around Discord at first ) ...
[video=youtube_share;U_gkksC2v9s]https://youtu.be/U_gkksC2v9s[/video]
NOTE: It will only work with the Beta version of ED. It will NOT work with the current live version of the game. It will only read the JournalBeta files. Do not come back to me with "It ain't workin with the live game no more!!" (I already had that on my Discord channel today
)This beta has realtime LAT/LON update from the 3.0 Beta added into it. You set your target LAT/LON using the Bearing & Distance panel (click on one of the Bearing Buttons either on the Overlay widget or on the main window.)
Once a target LAT/LON is set, make sure you preselect the correct planet you're going to be navigating - this sets the correct planet radius for the Distance calculation.
When you go into Orbital Cruise, and have set a LAT/LON target, a NAV frame will appear on the Overlay, showing the bearing you need to point in to reach your target LAT/LON coordinates, and the ground distance over a sphere (Haversine formula) from your current LAT/LON to your target LAT/LON.
Navigating is now basically matching up the ship's bearing with the CL2 NAV Bearing.
Full details of the Beta are on the Captain's Log Discord server, #beta_testing channel, see pinned message. See my signature for the Discord invite/link.
Here's a video of me testing it out (skip the first 2 minutes - I was pfaffing around Discord at first
) ...[video=youtube_share;U_gkksC2v9s]https://youtu.be/U_gkksC2v9s[/video]