You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have set up EDMC to output ship loadouts to .txt files. (In Settings → Output tab, “Ship loadout” and “Automatically update on docking” are checked.) This works for every ship I have… except Python Mk II and Type-8 Transporter. No .txt file is saved if I change the loadout of either ship.
It did work in the past, because I have a couple of EDMC-generated files containing those ships’ loadouts. The last of those files is dated 2024-08-08, so it must have stopped working at some later update.
In case it matters, both those ships have been bought with ARX.
The ships are identified correctly in the EDMC GUI, and exported correctly to EDSY on left-click.
I have checked the Known Issues list to ensure this is not a duplicate
Attaching EDMarketConnector-debug.log, cut down to just today’s log and with personal information redacted. I can see some likely related “Invalid journal entry” errors there. EDMarketConnector-debug.log
The text was updated successfully, but these errors were encountered:
EDMC Version: 5.12.1+fc00839
OS Details:
Environment Details
Bug description
I have set up EDMC to output ship loadouts to .txt files. (In Settings → Output tab, “Ship loadout” and “Automatically update on docking” are checked.) This works for every ship I have… except Python Mk II and Type-8 Transporter. No .txt file is saved if I change the loadout of either ship.
It did work in the past, because I have a couple of EDMC-generated files containing those ships’ loadouts. The last of those files is dated 2024-08-08, so it must have stopped working at some later update.
In case it matters, both those ships have been bought with ARX.
The ships are identified correctly in the EDMC GUI, and exported correctly to EDSY on left-click.
Logs
Attaching
EDMarketConnector-debug.log
, cut down to just today’s log and with personal information redacted. I can see some likely related “Invalid journal entry” errors there.EDMarketConnector-debug.log
The text was updated successfully, but these errors were encountered: