A busy little mouse has updated the online version of the journal guide. Many thanks for that ! 
Journal Manual V37
Journal Manual V37
if a new version will be forthcoming then it would typically drop either with or right before the new release. I don't think there will be a new journal revision this time.
Since U17 the following can happen in the journal files:
As far as I can tell the literal -nan(ind) is not valid JSON (but been a while since I read the JSON specs), and there is meant to be a floating point number there.
I have also reported this bug:
issues.frontierstore.net
As far as I can tell the literal -nan(ind) is not valid JSON (but been a while since I read the JSON specs), and there is meant to be a floating point number there.
I have also reported this bug:
Issue Tracker
issues.frontierstore.net
Last edited:
Is there any chance we could get orbital parameters for stations (including parent body) in one of the events? It seems kinda unfortunate that we get this information for other bodies but not stations / fleet carriers.
Either adding them to the
Either adding them to the
Location event or adding station/FC Scan events seems appropriate.
Hi @hchalkley, will there be an update to status.json flags post the new SC functionality?
Howard don't work hea no mo'
Robert Maynard
Volunteer Moderator
I checked to see whether any Status.json flags or journal events have been added for using the SCO and SCO cooldown. Found none, sadly.
Thanks Robert
Does anyone know if there's a way from journal or status files to know when the external camera is in use?
The value of heading in status.json does not change when in external camera, but lat/long do. It would super useful if there was something in Flags2 or GuiFocus to indicate this.
The value of heading in status.json does not change when in external camera, but lat/long do. It would super useful if there was something in Flags2 or GuiFocus to indicate this.
Hi all,
I check and decode the status.json file as part of my Thrustmaster Target script.
Just recently, whilst on missions to surface the script reports an error when entering glide mode and only during missions.
I will try to grab a copy of status.json next time it's happening but thought I'd ask if anyone knows or has encountered wierdness recently?
EDIT: (Apr30) Never mind...coding error on my part. I didn't allow enough buffer size to read status.json when it exceeds 512 characters.
As you were.
Cheers
I check and decode the status.json file as part of my Thrustmaster Target script.
Just recently, whilst on missions to surface the script reports an error when entering glide mode and only during missions.
I will try to grab a copy of status.json next time it's happening but thought I'd ask if anyone knows or has encountered wierdness recently?
EDIT: (Apr30) Never mind...coding error on my part. I didn't allow enough buffer size to read status.json when it exceeds 512 characters.
As you were.
Cheers
Last edited:
Request to have localised ship name added to the
Also, no vehicle identification is available when embarking onto your SRV, so if you happen to log in while on foot, it is actually impossible to identify your SRV when boarding it. Perhaps add SRVType (+Localised) to
Loadout event. Other events have it, but I think this is the only one that will identify your ship when docking SRV or embarking.Also, no vehicle identification is available when embarking onto your SRV, so if you happen to log in while on foot, it is actually impossible to identify your SRV when boarding it. Perhaps add SRVType (+Localised) to
Disembark, or some new event?
For exploration, it would be awesome if there was something like WasScanned for biologicals, analogous to WasDiscovered and WasMapped for bodies. It could be part of the ScanOrganic event.
And a FirstFootfall event would also be great.
And a FirstFootfall event would also be great.
My guess is
Python_NX because yesterday there where some EDDN messages for 18.04
JSON:
{ "id":129030466, "Name":"python_nx_armour_grade1", "BuyPrice":0 },
{ "id":129030467, "Name":"python_nx_armour_grade2", "BuyPrice":23702103 },
{ "id":129030468, "Name":"python_nx_armour_grade3", "BuyPrice":53329732 },
{ "id":129030469, "Name":"python_nx_armour_mirrored", "BuyPrice":126035933 },
{ "id":129030470, "Name":"python_nx_armour_reactive", "BuyPrice":139664643 },
The problem is that we don't know if this is a placeholder name or the final name and at this rate probably won't until the full release, which puts devs in a tricky spot of either possibly including a wrong ship name map or having to scramble after release. But the name is the least of the issues.
Beyond just the name we don't know of any of the other funky things like modules or naming schemes etc, ship health and integrity details, basically any of the information about the ship that will end up in the journal logs that devs might need to add to their tools. While it can be discovered through trial and error, it's not really an ideal method and doesn't provide us a lot of wiggle room if we choose not to buy or don't have access to the ship. It will cause errors on release if we don't get the information told to us ahead of time.
Last edited: