Wrong JSON File output for /getDrone endpoint about ficsitremotemonitoring

[porisius]

Well, I think I found the problem. I think it might be better just to change it from an integer to a float. (mind the spaghetti)

[Jonathan-Hofmann]

Perfect thanks!

[Jonathan-Hofmann]

Is the FlyingSpeed working in Version 0.8.25? As I still get the same 1,000, value...

[porisius]

I just saw it, not sure why it didn't register as a static value for some reason. Probably because I looked at it before the caffeine kicked in.

[porisius]

I wonder if it is something that CSS hasn't finished, started on and stopped, or a bug. There are three flying modes, None/Docked, Flying, Traveling which are all ENums. These each have their own values (0, 1000, and 7000). Still checking, but I don't think the fault is mine now.

"FlyingSpeed":0,
"CurrentFlyingMode":"DFM_None"

"FlyingSpeed":1000,
"CurrentFlyingMode":"DFM_Flying"

"FlyingSpeed":7000,
"CurrentFlyingMode":"DFM_Travel"

[Jonathan-Hofmann]

So flyingSpeed is not like the ForwardSpeed field from f.ex. the train-json? It is more like a targeted Speed?

If so maybe it would be better leaving FlyingSpeed out of the response JSON as we cannot use the JSON with the formatting error...

[porisius]

Curious why you are still getting that... this is my 0.8.25 test

[porisius]

0.8.26:


I don't think you'll have that problem anymore... plus I am using the FGDrone actor's vector length to calculate a speed in knots, since that is what aircraft use anyways.

[Jonathan-Hofmann]

Nice! Works now like a charm!

[Jonathan-Hofmann]

Thank you again ;)