Inara updates, bug reports, requests

Commanders having Elite from Epic games store with http 400 error
When you try to link your accounts, you may receive the http error 400 about expired tokens. It's an issue on Frontier's end that I cannot solve on Inara. Fortunately, the solution is simple - please give it a few days and it will start to work later (probably when the access token on their cAPI server expires). If the error 400 appeared later and it worked before, try to reauthenticate as said in the error message (may be just a regular reauth forced by Frontier). Alternatively, you can try to use the workaround below. If even that won't work, it's the problem described above.
Please vote for the issue on the official bug tracker: https://issues.frontierstore.net/issue-detail/21258

Possible workaround: Try to connect the account while you are in the game. It may work.

Game data and imports not available for console commanders and PC players with Legacy game version
Inara supports only the Live game version (so PC Horizons 4.0 and Odyssey) since game update 14, thus all the game data on the site and the commander data imports work only for those game versions.
J. J. Thomson
yesterday, 12:41pm
Aunty Sledge
J. J. ThomsonHello to everyone,

I was looking at the ship details in my hanger, and noticed my starting sidewinder shows '-' for the jump range and cargo capacity. My cobra shows the proper values. I only have these two ships since I cleared my save after returning to the game years later.

I use EDDiscovery for API syncs, but I could not find any journal entries that contain these values. My assumption is that Inara calculates them to populate the ship details page. Is there anything I need to do to get those values to update for the sidewinder? It's on OCD thing of mine.

I've used EDDiscovery to sync data since the very first journal entry on this character, so everything should be synced. Ship modules, etc. are all current and accurate.

Thanks Artie!



I can help you with that one as I've had to do the same myself. Jump into each ship, log out to menu and back into the game. That will generate the journal entry with all your stats on the ship you are in.

Do that for each ship with missing stats and they will eventually make their way into Inara. The important bit is to be in the ship with imcomplete data when you log in.



Thanks! That did it.
Sampi Ogonek
yesterday, 4:56pm
AHIs there a way to "ping" Fleet Carrier to see if it's still where it was last reported?

Not really. If the owner is registered on Inara and Inara has a valid Frontier API access token, then the carrier’s location ought to be updated periodically; but even then, the owner might have already moved the FC since the last update. (The owner, or anyone present in the system where the FC is, can also update Inara via a tool like EDMC, but many people don’t, and various bugs and deficiencies in the process may result in the update being delayed.)

AHThis is my 3.. maybe 4th time, when I am way out there, take a detour to get on a FC with services I need, only to find out there is nobody in the system. Time and resources wasted.

As far as I know, the only FCs one can reliably find way out there are listed in the Deep Space Support Array spreadsheet. I suggest to use those only, unless you know the owner of the FC in question and can contact them.

AHI am surprised that ED servers do not push that data out to some type of service we can get notices from.

I am not surprised at all. Having been around since early pre-release versions (being a Kickstarter backer), I am grateful that we do have stuff like cAPI and the journal files. It took years for FDev to start taking this kind of stuff seriously.
AH
yesterday, 7:50pm
Sampi Ogonek

As far as I know, the only FCs one can reliably find way out there are listed in the Deep Space Support Array spreadsheet. I suggest to use those only, unless you know the owner of the FC in question and can contact them.



Thanks. Big help.
BTW, what if they gave you the data and you made it into a searchable like the "nearest"? That would be really awesome.
Thanks.
Artie
today, 12:45pm
AH
Thanks. Big help.
BTW, what if they gave you the data and you made it into a searchable like the "nearest"? That would be really awesome.
Thanks.

Basically as Sampi mentioned. There is no "push" of information from Frontier, some kind of pushed information is only from players via EDDN network (by using EMDC, EDDiscovery, etc.) and that information only tells "the FC is here" for the given star system, but not "the FC is not here" (or at least not very reliably). The rest must be requested and there are various limits (a scope on information provided, etc.). With the fact that FCs can jump very often, there is always a risk the position of FCs outside of very frequent star systems may be outdated.

A large portion of DSSA fleet carriers is in the database already and they should be fairly up to date (assuming most of them are static). There probably were more of them in the database at some point, but as I am pruning carriers nobody saw for a while they are gone now (until next re-visit).
Emily Valefor
today, 4:14pm
Artie
AH
Thanks. Big help.
BTW, what if they gave you the data and you made it into a searchable like the "nearest"? That would be really awesome.
Thanks.


Basically as Sampi mentioned. There is no "push" of information from Frontier, some kind of pushed information is only from players via EDDN network (by using EMDC, EDDiscovery, etc.) and that information only tells "the FC is here" for the given star system, but not "the FC is not here" (or at least not very reliably). The rest must be requested and there are various limits (a scope on information provided, etc.). With the fact that FCs can jump very often, there is always a risk the position of FCs outside of very frequent star systems may be outdated.

A large portion of DSSA fleet carriers is in the database already and they should be fairly up to date (assuming most of them are static). There probably were more of them in the database at some point, but as I am pruning carriers nobody saw for a while they are gone now (until next re-visit).

That completely blows my mind. I had believed until this post that there was some sort of API that exported game activity and that was what powered INARA. The fact you even HAVE this level of data from basically a mass filter option, is incredible. This site is practically essential to the game, I'm amazed Frontier does not do more to support it.
Artie
today, 5:36pm
To be more precise, there is an API on Frontier's end, but it typically provides just player journals (same as a copy on the local PC), player's fleet carrier info and a few other things. But, there are no endpoints like "tell me what stations are in the star system AB" or "tell me details about minor faction XY" or such things. This is stuff that needs to be collected by parsing the journals mentioned (which contains only information related to travels/actions of such player, like the properties of the star systems visited) and then put together. So although journals are a GREAT source of information and Frontier deserves all kudos for them, they need a lot of processing/transforming to make the data usable for everybody and due to the nature of the source it has its limits (like age of the information or a lack of information for star systems/stations nobody visits).
AH
today, 5:56pm
Artie
AH
Thanks. Big help.
BTW, what if they gave you the data and you made it into a searchable like the "nearest"? That would be really awesome.
Thanks.


Basically as Sampi mentioned. There is no "push" of information from Frontier, some kind of pushed information is only from players via EDDN network (by using EMDC, EDDiscovery, etc.) and that information only tells "the FC is here" for the given star system, but not "the FC is not here" (or at least not very reliably). The rest must be requested and there are various limits (a scope on information provided, etc.). With the fact that FCs can jump very often, there is always a risk the position of FCs outside of very frequent star systems may be outdated.

A large portion of DSSA fleet carriers is in the database already and they should be fairly up to date (assuming most of them are static). There probably were more of them in the database at some point, but as I am pruning carriers nobody saw for a while they are gone now (until next re-visit).



I was talking about "Deep Space Support Array spreadsheet" data.
No worries, I found this: https://edastro.com/galmap/?layer=regions&pins=DSSAcarriers
Artie
today, 5:59pm
AH
I was talking about "Deep Space Support Array spreadsheet" data.
No worries, I found this: https://edastro.com/galmap/?layer=regions&pins=DSSAcarriers

Yes, me too. DSSA carriers = Deep Space Support Array carriers and most of them are updated a regular way as any other carrier already, so there is not much a point to import any spreadsheet (that may also get obsolete).

Post a reply

You must be signed in to post here.
Discussion about Inara - any comments, suggestions, feature requests, bug reports are warmly welcomed.

Link to Inara Discord: https://discord.gg/qfkFWTr