Inara updates, bug reports, requests
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.
02 Oct 2017, 1:18pm
02 Oct 2017, 7:49pm
INLINESIX@Artie Did you draft your planned API project somewhere? I am working at something which could add some comfort to the grind, but it needs a cmdr's material stock for that. So instead of typing in materials, it would be handy to get it from a cmdr's personal account on his request?!
In the meantime wouldn't it be more convenient to just parse the logs, rather than typing it in?
Logs can be a bit more work if you want to be accurate and include all material collected during the session, as there is no summary on logout (would be pretty neat if there was).
On inara for example the event SellExplorationData is not tracked. To have the assets correctly reflect the CR gain from this, one needs to relog once after selling the data.
(Dunno if Artie just parses the summary for CR/Material, just noticed this with exploration data)
02 Oct 2017, 7:59pm
INLINESIX@Artie Did you draft your planned API project somewhere? I am working at something which could add some comfort to the grind, but it needs a cmdr's material stock for that. So instead of typing in materials, it would be handy to get it from a cmdr's personal account on his request?!
Actually, I have no plans to provide detailed commander data/inventory/etc on the initial release, but it may (or may be not) added later.
Pazze
In the meantime wouldn't it be more convenient to just parse the logs, rather than typing it in?
Logs can be a bit more work if you want to be accurate and include all material collected during the session, as there is no summary on logout (would be pretty neat if there was).
On inara for example the event SellExplorationData is not tracked. To have the assets correctly reflect the CR gain from this, one needs to relog once after selling the data.
(Dunno if Artie just parses the summary for CR/Material, just noticed this with exploration data)
I am tracking also all credit changes, but I am not storing them on the end of the session, because it is usually off due missing crew wage cuts in the journals.
02 Oct 2017, 10:04pm
Artie[quote=INLINESIX]I am tracking also all credit changes, but I am not storing them on the end of the session, because it is usually off due missing crew wage cuts in the journals.
I'm sure this was mentioned before - but is it possible to manually set crew cuts? If it is off by a few credits, it gets rectified on the next startup.
I for myself haven't got any crew so that cut would be 0.
03 Oct 2017, 10:01am
Artie I am tracking also all credit changes, but I am not storing them on the end of the session, because it is usually off due missing crew wage cuts in the journals.
Good to know, haven't flown with crew yet. Considering that mission rewards can also be off in the journal if they hit the new payout cap, it's probably best to stick with the summary for CR.
03 Oct 2017, 2:28pm
LeifArtieINLINESIXI am tracking also all credit changes, but I am not storing them on the end of the session, because it is usually off due missing crew wage cuts in the journals.
I'm sure this was mentioned before - but is it possible to manually set crew cuts? If it is off by a few credits, it gets rectified on the next startup.
I for myself haven't got any crew so that cut would be 0.
It is complicated, as different crew members may be having different cuts. So my hopes are that Frontier will add those values to the journals (and it was already proposed to them) as it will make things much easier.
03 Oct 2017, 8:15pm
04 Oct 2017, 12:22pm
https://inara.cz/galaxy-starsystem/11383/
04 Oct 2017, 1:29pm
04 Oct 2017, 1:40pm
AthanasiusAny idea what causes the system influence graphs to bounce down to a zero value and then back up, even twice as on this example ?
https://inara.cz/galaxy-starsystem/11383/
I noticed that in other systems yesterday, currently investigating the cause of this issue.
04 Oct 2017, 2:07pm
Jemine CaesarI'd imagine it's because no data was downloaded to Inara from wherever it comes from.
I'd expect it to be re-using the old value(s) then, only plotting between the values it has, not suddenly deciding some must be zero. Good to hear Artie is looking into it. I should have said something sooner, as I've been noticing this for a long, long time (up to a year perhaps).
04 Oct 2017, 2:17pm
05 Oct 2017, 3:39am
Link to Inara Discord: https://discord.gg/qfkFWTr