Request for a bit of OSD.

[FPVGizmo]

Loving the sim, keep up the great work.

Any chance of a small OSD for altitude?

[CurryKitten]

I've actually had one in the sim before for debugging stuff. What's the reasoning here - do you want to know how high you are from the take-off point (as per a regular IRL OSD) or how high of the current altitude from the ground you are ?

[FPVGizmo]

Either would be nice, just want a visual of dive speeds and fall rates.

Thanks again

On Fri, 6 Mar 2020 at 16:03, CurryKitten [email protected] wrote:

I've actually had one in the sim before for debugging stuff. What's the reasoning here - do you want to know how high you are from the take-off point (as per a regular IRL OSD) or how high of the current altitude from the ground you are ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CurryKitten/CurryKitten-Sim/issues/37?email_source=notifications&email_token=AOYB73ZNYGEESFQB5E77UNDRGENGVA5CNFSM4LC7SX22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOB35AA#issuecomment-595836544, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOYB73ZKSD6RYJGBG67CM5LRGENGVANCNFSM4LC7SX2Q .

[CurryKitten]

There's been a few requests for OSD's, but in the current form I'm not at all convinced about it. It feels like the sim would have to go much more over to the sim side of things that it's current form - which is all about flying very unrestrictedly. So it gets a new status label as I'll keep it around to think about in the future

[danielchan9999]

+1 to some OSD information.

Some points:

• in simulators it is very easy to fly extremely high, which is normally not practical in real drone flights, for fear of loosing the drone. Having the altitude can help users aim to keep under 10-20meters, where most try to keep their flying to. (excepting dives etc).

Other suggestions for OSD:

• battery indicator, flight time indicator, throttle %, RSSI (if its possible to be simulated). OSD Summary when armed / disarmed.

None of these are required for simulations... but in terms of beginners learning, learning to watch your flight time, battery voltage, RSSI etc is key parts of learning quad flying.

[CurryKitten]

I'm still undecided about the extent of what's required in a sim OSD, but lots of people have asked for a central crosshair to help them line up, so I'll spin that off on a separate issue

[pilotnbr1]

I'm still undecided about the extent of what's required in a sim OSD, but lots of people have asked for a central crosshair to help them line up, so I'll spin that off on a separate issue

Does your sim utilize mavlink (or any type of telemetry) ?

if so , you expose the telemetry on port 14550 the qopenhd app and it’s osd can utilize it. Within the qopenhd app the app background can be made transparent and the visuals of the sim can be seen. So you would have to position the qopenhd app window over the sim window. Qopenhd is cross platform as well.

Qopenhd could be made to consume the sim visuals directly as a container within qopenhd as well

[CurryKitten]

I'm still undecided about the extent of what's required in a sim OSD, but lots of people have asked for a central crosshair to help them line up, so I'll spin that off on a separate issue

Does your sim utilize mavlink (or any type of telemetry) ?

if so , you expose the telemetry on port 14550 the qopenhd app and it’s osd can utilize it. Within the qopenhd app the app background can be made transparent and the visuals of the sim can be seen. So you would have to position the qopenhd app window over the sim window. Qopenhd is cross platform as well.

Qopenhd could be made to consume the sim visuals directly as a container within qopenhd as well

It's an interesting idea - especially in potential terms of being able to fly with your normal OSD - but right now there's no telemetry as such. What's there is calculated as part of the sim code and can be displayed - so this is somewhat out of scope at the moment.