if the beta outputs logs in the same folder as the live install, then no
I don't have beta access so I can't tell you unfortunately
if the beta outputs in the same directory, maybe there's some custom headers in each log file but it's not specified in the documentation afaik
2.2 Heading entry
The Heading record has a Json object with the following values:
• timestamp: the time in GMT, ISO 8601
• part: the file part number
• language: the language code
• gameversion: which version of the game produced the log (will indicate if beta)
• build: game build number
Example:
{ "timestamp":"2016-07-22T10:20:01Z", "event":"fileheader", "part":1, "language":"French/FR", "gameversion":"2.2 Beta 1", "build":"r114123 " }
(If the play session goes on a long time, and the journal gets very large, the file will be closed and a new file started with an increased part number: the heading entry is added at the beginning of every file. See also the "Continued" event)
This tool is great. I am gonna use the hell of italthough I will wait after the QoL engineer updates kick in in a month.
Two questions:
1. How can I configure the tool (e.g. change the ctrl+F10 shortcut)
2. I want to backup the data for EDEngineer so I dont have to retype all data if something happens. Where is it located? (I am sure I saw that it was mentioned somewhere but I cannot find it)
C:\Users\%USERNAME%\AppData\Local\EDEngineer\manualChanges.{cmdr name}.json
the manual changes are located in:
Code:C:\Users\%USERNAME%\AppData\Local\EDEngineer\manualChanges.{cmdr name}.json
the convoluted directory is where the binaries are. I know I shouldn't have used clickonce, that was the lazy solution. Squirrel is a good replacement candidate (even though it's not perfect either)maybe one day I'll find the time to migrate the deployment
Ah well I stand correctedThanks!
I published a patch that makes the app ignore logs from beta (easy fix, most of the hard work was already done in the patch that let the app handle multiple commanders), let me know if it's fine
Released to support Elite dangerous Beta 2.2.3 (Journal fileheader is missing beta tag)
You can use the local API and the /operations route (bottom of this page) to see what the application managed to extract from your logs (with timestamp in UTC) ; by default it outpus json which you can format online (just google "format json") to get something bit more readable.
Could you upload a zip of your log folder on a new github issue? Maybe there's something unexpected in them that I can verify. (If .zip file isn't accepted, just rename the archive to .jpg and upload it like that)
@Exigeous: EDEngineer listens to your filesystem updates to detect if a file changed, so there is no need to restart it ; it just listens to file changes (I basically reimplemented a unix "tail -f"). If you're absolutely sure you're pointing to the correct folder, and you're absolutely sure that EDEngineer doesn't update when you discard a random material, then you might want to check your windows application logs (windows+R "eventvwr"). Not much I can help ; just check your antivirus, or if you have software cleaner utilities running, etc...
No don't worry! I replied to your GitHub issue. (For other people who might encounter the similar issue: ) You were not pointing to the log directory (Elite Dangerous), but the one that contains it (Frontier Developments)
Bad:
C:\Users\%USERNAME%\Saved Games\Frontier Developments
Good:
C:\Users\%USERNAME%\Saved Games\Frontier Developments\Elite Dangerous
I'm 100% sure it wasn't pointing to the correct folder, but in your reply's screenshot it isThe application now shows your commander in the commander's list.
What happened:
- You launched the app, but wrong log directory
- You made some manual changes to sync but the game did not detect any commander, so it created a "default" commander so your manual changes are saved (in the manualChanges.Default.json file)
- Whenever you start the app, EDEngineer tries to detect available commanders :
- by looking in the log directory if available
- and in the manual changes directory when changes are stored in files such as manualChanges.{commander's name}.json
- If only one commander is detected, then it doesn't show the commander name in the UI (would be noise imo). If it finds more than one, it shows a list of commander's name on top of the window so you can switch easily
- In your first screenshot, I don't see that commander's list ; you said you did manual changes though, so a manualChanges file must have been created
- In your second screenshot which shows the correct path to the log directory, we see two commander's on top : Default and Exigeous ; so two commanders were found ! Exigeous comes from your log directory, and Default comes from the manualChanges.Default.json which was generated when you did your manual changes
Hopes that clears it up![]()