Status.json going bananas

Bionic Bytes

Bionic Bytes
Anyone else noticing that whilst docked at a station, Status.Json is being updated with new latitude and longitude values (alt and heading remain at zero).
This is new behaviour and whilst docked these values should not be present - according to your own documents.

@FDEV care to comment?
 

Drelthar

Drelthar
Bionic Bytes said:
Anyone else noticing that whilst docked at a station, Status.Json is being updated with new latitude and longitude values (alt and heading remain at zero).
This is new behaviour and whilst docked these values should not be present - according to your own documents.

@FDEV care to comment?
Click to expand...

I know the issue tracker sucks, but it's probably a better place for something like this... much as I hate to say it.
 

Robert Maynard

Volunteer Moderator
Robert Maynard
Bionic Bytes said:
That’s my understanding. Lat long is only when we are navigating a planet surface.
Click to expand...
Indeed, it wasn't published when docked in a station prior to the September update.

As can be seen from this docked example, BodyName and PlanetRadius are absent, so the position could be ignored:
Code: 
{ "timestamp":"2019-10-15T21:22:05Z", "event":"Status", "Flags":153157645, "Pips":[4,8,0], "FireGroup":0, "GuiFocus":0, "Fuel":{ "FuelMain":64.000000, "FuelReservoir":1.160000 }, "Cargo":0.000000, "LegalState":"Clean", "Latitude":-15.911971, "Longitude":-38.204762, "Heading":0, "Altitude":0 }
 
You must log in or register to reply here.
Back
Top Bottom