Closed bazza14 closed 5 years ago
In what way? It should pick them up, but certain records won't show properly at this point until i do another release. We are waiting on the final journal format before we do that
EDDiscovery should put beta logs under [BETA] CommanderName
I don't know in what way. It's simply not reading them. I had no issues with the last beta in Feb this year. I have a Beta commander showing in EDD settings and I've set the location of the Journal to the location of the journal.
Perhaps this is the problem. Beta log { "timestamp":"2018-11-08T07:42:31Z", "event":"Commander", "FID":"F1321420", "Name":"Zaphod Beeblebrox IV" }
Normal log { "timestamp":"2018-11-08T00:43:47Z", "event":"Commander", "Name":"Zaphod Beeblebrox IV" }
I didn't have that FID field in the Feb beta
What OS are you running on?
Win 10
I'm not sure why JournalBeta.*.log
files would not appear to be getting read.
If you look at the trace log, do you see any messages about "TLU X:\Path\To\Dir updated with commander n`?
If running EDDiscovery while Elite Dangerous beta is running, do you see any Change to scan X:\Path\To\JournalBeta.datetime.01.log
?
Do you see any messages with something of the form of Write Journal to db {date} {time} {event}
?
Weird, tested it today and there were the Beta logs. Closing this.
EDD is not reading the 3.3 beta logs.