INARA shows ghost carriers in system
- Thread starter AceMcKool
- Start date
Inara doesn't have access to the in game databases. It is just updated by players. So if you see something like, carrier location 16 hours ago note that the commander could have jumped it away any time in the last 16 hours (it only takes 15 minutes to jump) and if they didn't update the new location to Inara and they jumped somewhere no commander has visited since, inara won't know where they are now. Take Inara with a grain of salt as it's only as good as the inputs coming in.
What about the input I'm sending via EDMC while in-system? That doesn't count?
Apparently not.
I don't think it's instant. Your ED data client sends it to the EDDB, who knows when that's processed. Inara eventually queries EDDB for an update, at God knows when. 
The only way to make Inara update instantly - is to quit to desktop, then manually update on Inara website. Even that on a rare occasion (or with some types of data, thargoids kill counts, etc) could also not work instantly. There is a delay in communication between servers/services in the chain and available/verifiable data. Inara is doing a fantastic job of aggregating all the available data, but because all game data is not immediately saved and transferred by the game servers to Inara in short regular intervals - there will always be discrepancies.
You are sending direct to Inara?
This makes me wonder which info about carrier locations is in the journals... I must have a peek.
My understanding had been that carrier updates relied on people to actually visit them (and send their data to EDDN and/or directly to Inara) . However, that can't be the whole story, I now realise, because I think this wouldn't give Inara the distances from the main star (which are sometimes missing).
EDDB is long dead. You mean EDDN, though EDDN is not a database, so this isn't the reason. Inara listens to EDDN and keeps its own database that it queries, and if commanders are sending to EDDN, it processes within seconds.I don't think it's instant. Your ED data client sends it to the EDDB, who knows when that's processed. Inara eventually queries EDDB for an update, at God knows when.
The issue is that this (FSSSignalDiscovered) isn't falsifiable: players never get a complete list of all signals in a system written to the journal. So third parties cannot tell for sure when a carrier leaves: it might still be there but the player just didn't get it in their signal list (journal) at that time.
The way to update all those carriers is indeed to find them in other systems.
Ahhh, thanks.
I also now see (having explored the journal a wee bit) that the FSSSignalDiscovered journal entry doesn't contain the in-system distance, so I'm now puzzled about where Inara gets this for some carriers and why others don't show it. You don't by any chance understand this bit too?
I just checked the system I'm in right now and it has 61 carriers listed by Inara, only 12 of which have a "station distance" listed. Can't see a definitive pattern in terms of last update time, or the owner being listed on Inara.
I even checked the CAPI to see if that's where it gets the distance info but according to the docs I found, nope.
The only idea I've got left is that somehow Inara combines the info from neighbouring SupercruiseDestinationDrop and SupercruiseExit entries...
From the Docked event which includes distance. Also, a DistFromStarLS of 0 seemds to be shown as "-" in Inara. The below is old, my carrier is now right next to a star and DistFromStarLS is 0 but Inara shows "-".
JSON:
{
"timestamp": "2024-12-23T01:04:20Z",
"event": "Docked",
"StationName": "V4T-T9K",
"StationType": "FleetCarrier",
...
"DistFromStarLS": 2448.898048,
"LandingPads": {
"Small": 4,
"Medium": 4,
"Large": 8
}
}
Last edited:
Oh wow, thanks - I was absolutely convinced I had checked the Docked event in the journal
I must instead have checked it only in EDDiscovery, which has a habit of utterly rewriting the journal entries and omitting some stuff (I must also have failed to use the "Copy journal entry to clipboard/log" button, doh).
Incidentally, mini-rant: it's at times like this when I find that the EDDiscovery search function is rendered massively less useful by its refusal to search for info in the "long" version of each entry (the version you see when you double click on any given text box). I can only persuade it to search the abbreviated version, and of course you need to use entirely different search terms from what appears in the actual journals, due to the text being rewritten, further harming its usefulness. It's also bizarre that the UI doesn't give any hints about which text boxes have more info if you do double click... (I've been searching the raw journals most of the time.)