Closed bid closed 5 years ago
I see a Galnet Monitor exception in the log and the Cargo Monitor is not even starting, let alone handling journal events. This is likely the cause.
Try disabling the Galnet Monitor (or deleting the galnetmonitor.josn file will cause EDDI to default to disabled) and test the Cargo Monitor again. Meanwhile, we'll investigate why a web request timeout (from FDEV) is not playing nicely.
Will do and report if that changes anything. I've just posted a second bug report about the GalNet Reporter, which has its very own problems. ;) There's a longer log with more error messages about GalNet in that report.
EDIT: Hm. Doesn't seem to help. The log is less chaotic, but cargo stays empty...
@bid Where you able to figure out what was going on with this issue? We're not seeing anything that looks off on our side... the cargo monitor appears to register all cargo correctly from the event.
@Tkael Sorry, I missed your message. No news on my side, but I didn't do any more investigation in the meantime. Took a few days of Elite-break. :) Cargomonitor is the only monitor not working for me. The others (ship-monitor, mission-monitor, material-monitor) all seem fine. And the speech output also tells me when I buy/sell cargo, so that event fires too. It's just the monitor itself that doesn't work.
One single thing I thought about in the meantime: I have Elite installed in a "non-standard" location on my second harddisk. Shouldn't really make any difference but who knows? I actually thought about checking the code myself and check for differences between the different monitors. But I've never looked at EDDIs sources and it would take me a while to get up to speed how everything is set up here.
Edit: If the bug stops, I will immediately know, because it will stop to tell me that I have no limpets EVERY TIME I leave a station, although I never forget my limpets... :P
Are your EDDI config files or your Saved games
folder in a non-standard location too?
Is the status monitor working? It reads status.json
in pretty much the same way we read cargo.json
(from the Saved Games folder where your journal entries are stored).
Hi @bid , any updates on this issue?
Closed due to lack of response and inability to replicate the issue (please let us know if you are still encountering this issue!)
Sorry guys, the cargo monitor is still not running or not running yet.
EDDI version 3.4.1-rc1 (stand alone)
EDDI version in which issue is found
3.4.0
VoiceAttack version in which issue is found (as applicable)
No VoiceAttack used
Steps to reproduce
No real steps. Cargomonitor just doesn't reflect ANY changes in cargo and cargomonitor.json stays with an empty list.
Expected
Cargomonitor to reflect my actual cargo.
Observed
cargomonitor.json just stays with an empty list and "cargocarried": 0, no matter what I do.
Investigation
Things I tried:
Other tools, like "E:D Market Connector" and "Trading Computer Extension MKII" reflect my current cargo without problems.
cargomonitor.json: { "cargo": [], "cargocarried": 0, "updatedat": "2019-04-26T20:12:38Z" } eddi.log
Cargo.json: { "timestamp":"2019-04-26T20:12:38Z", "event":"Cargo", "Vessel":"Ship", "Count":8, "Inventory":[ { "Name":"survivalequipment", "Name_Localised":"Survival Equipment", "Count":1, "Stolen":0 }, { "Name":"drones", "Name_Localised":"Limpet", "Count":7, "Stolen":0 } ] }