There's a summary of the hotkeys in the manual at https://captainslog.scarygliders.net/user-manuals/captains-log-2x/
Regards o7
Regards o7
Release [Explorer's Application] Captain's Log
- Thread starter Genar-Hofoen
- Start date
Hi. Hope someone can help because I seem to have COMPLETELY buggered up my exploration tracking.
Since the last ED upgrade, Captains Log hasn't been working, but needless to say, I only noticed when I wanted to do another long trip, having made sure I was 'home' for the upgrade. So it was working perfectly until then.
The issue is that it isn't recognising where the log files are going and/or can't find the appconfig.xml file.
Relevant points (I think) are:
1. I've moved the entire ED install off my C drive and onto my F drive (ran out of space) and it's been working successfully there for over a year. However this does mean that I have random files left all over the place and I can't say I'm 100% sure of where everything is going...
2. My log files are definitely going to a directory called F:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs I've seen them going in there and eyeballed them to see if the system names correspond with the location I'm in. This is the directory named in the Captains Log config for 'Player Journal Files Location'.
3. This morning I had the bright idea of going through ALL the appconfig and appconfiglocal files I could find on my system and turning VerboseLogging off in them (deleted the line) on the grounds that Captains Log would then turn it on again (nice feature BTW). Unfortunately CL didn't do this, no files were modified.
4. I've tried creating a new DB and importing log files, but nothing happens.
So - any ideas? Is it not logging because it can't find the appconfig file? The most likely file it SHOULD use is definitely in the F:\Frontier\EDLaunch\Products\elite-dangerous-64 directory which is one above the Logs directory.
Any suggestions gratefully received! I find this app incredibly useful and would really like to get it working again.
Thanks!
Since the last ED upgrade, Captains Log hasn't been working, but needless to say, I only noticed when I wanted to do another long trip, having made sure I was 'home' for the upgrade. So it was working perfectly until then.
The issue is that it isn't recognising where the log files are going and/or can't find the appconfig.xml file.
Relevant points (I think) are:
1. I've moved the entire ED install off my C drive and onto my F drive (ran out of space) and it's been working successfully there for over a year. However this does mean that I have random files left all over the place and I can't say I'm 100% sure of where everything is going...
2. My log files are definitely going to a directory called F:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs I've seen them going in there and eyeballed them to see if the system names correspond with the location I'm in. This is the directory named in the Captains Log config for 'Player Journal Files Location'.
3. This morning I had the bright idea of going through ALL the appconfig and appconfiglocal files I could find on my system and turning VerboseLogging off in them (deleted the line) on the grounds that Captains Log would then turn it on again (nice feature BTW). Unfortunately CL didn't do this, no files were modified.
4. I've tried creating a new DB and importing log files, but nothing happens.
So - any ideas? Is it not logging because it can't find the appconfig file? The most likely file it SHOULD use is definitely in the F:\Frontier\EDLaunch\Products\elite-dangerous-64 directory which is one above the Logs directory.
Any suggestions gratefully received! I find this app incredibly useful and would really like to get it working again.
Thanks!
CL 2 works with journal files, not log files. Your journal files are usually in c:\users\<username>\Saved Games\Frontier Developments\EliteDangerous and the verbosity of the logging is irrelevant. Hope this helps.
Thank you.
Thanks Rhea!
I have added a "How CL2 Works" near the top of the CL2 manual at https://captainslog.scarygliders.net/user-manuals/captains-log-2x/ with this information.
Regards o7
Note: CL2 will not work with the 2.4 beta - the Player Journal is under a different name so CL2 2.0.0 won't see it.
My dev copy of CL2 2.1.0 beta, does, and I'm busy updating CL2 for before 2.4 drops.
Regards
My dev copy of CL2 2.1.0 beta, does, and I'm busy updating CL2 for before 2.4 drops.
Regards
Honk if you want journal files. One curve ball from the 2.4 beta is that scanning a nav beacon will now generate scan events for every body in the system, but only with the basic data set (no material percentages, for example).
According to the changelog, that's a feature, not a bug...
https://forums.frontier.co.uk/showt...ed-Beta-available-to-download-now-(changelog)
Did they have second thoughts about that?
Okay there is some confusion here
1) I already know about the nav beacon scan, thanks!
CL2 beta is already working with it 2) As Jantah kindly pointed out, the nav beacon scan providing system data is intentional - and is a great addition!
3) Currently, this data is only the equivalent of a level 2 scan.
4) I/We in EDCD have suggested it is desirable for this data to be the equivalent of a level 3 scan (because for 'known' systems that is the level of detail available in the system map)
5) Frontier have already mentioned that they are working on providing level 3 scan data for the next beta - which is what Anthor meant.
Hope that clarifies everything.
Regards o7
IMPORTANT: EDSM server is down at the moment and CL2 2.0.0 can't cope - sorry!
The EDSM server has gone down. Captain's Log read a JSON file from there for the Nightly Dump size. This has uncovered a silly bit of coding on my part which crashes CL2 2.0.0
A fix is in for CL2 2.1.0 but I can't release 2.1.0 right now because I'm waiting on some stuff being added to the Player Journal which is incoming in a beta to be released this week.
Once that is done, I may release CL2 2.1.0 Beta 1, which will be more robust against a couple of internet sites (EDSM, imgur) going down.
The EDSM server has gone down. Captain's Log read a JSON file from there for the Nightly Dump size. This has uncovered a silly bit of coding on my part which crashes CL2 2.0.0
A fix is in for CL2 2.1.0 but I can't release 2.1.0 right now because I'm waiting on some stuff being added to the Player Journal which is incoming in a beta to be released this week.
Once that is done, I may release CL2 2.1.0 Beta 1, which will be more robust against a couple of internet sites (EDSM, imgur) going down.
I'm sorry but I'm confused. Can I still continue using 2.0.0 without requesting an EDSM dump? I haven't done that in a long time anyway as I couldn't figure out what that dump would be used for. I'm currently using CL 2.0.0 on my current trip and relying heavily on it to keep tracking my jumps and scan. Thanks in advance.
Therein lies the silliness - CL2 will try to read the nightly dump size from the EDSM server regardless of whether you use it or not - and this means the bit of code which causes the crash (trying to convert a download size in bytes into something more human readable) gets fed a timeout message instead - which crashes CL2.
Yes, it's a whole load of derp on my part.
It's okay, it's just a bug. You'll fix it. Really, it's not an issue.
So, if I understand you correctly, as long as EDSM is down, I can't use CL because it tries to communicate with EDSM and fails, causing a crash. That regardless of the fact that I haven't downloaded a nightly dump from EDSM in ages. If that's the case I guess I'll wait for EDSM to get restored.
EDSM should be back up quite soon.
I'll put in a crapload of failsafes in the next version of CL2. Lesson learned
EDSM is back up and running. So CL2 will also work.
As per title - EDSM back up - CL2 2.0 will also now work.
CL2 2.1 will be released before or on the date that 2.4 goes live. In the meantime I will be adding more stuff to CL2 2.1
Regards o7
As per title - EDSM back up - CL2 2.0 will also now work.
CL2 2.1 will be released before or on the date that 2.4 goes live. In the meantime I will be adding more stuff to CL2 2.1
Regards o7
Hopefully the next version will fail gracefully even if the entire internet connection is down? Not that I can think of much of a use case for Captain's Log in that scenario but at least it will uncover any other tacit server dependencies.
I'll try to make it as bulletproof as possible.
I have a question. I forgot to open CL 2 on my current trip and missed a few jumps. So what I did was isolate only the logs relevant to my trip, create a new database, and run the scan all logs and import to the database, action. Now, EDD tells me that my trip has 584 jumps so far but after importing the logs, CL 2 says I have 645 jumps. It turns out that there are duplicate events imported, I think from logs that had a system jump in one and after I logged off the game and started again, CL 2 read the next log as a jump event and added it again. Everything else seems fine.
Is there a way to remove the duplicate systems? If not, is there any chance you may fix this problem in the new version?
Thanks in advance.
Is there a way to remove the duplicate systems? If not, is there any chance you may fix this problem in the new version?
Thanks in advance.