Context OSD layouts - have the OSD clear or most things unless you need to know about them..

[Painless360]

The current behaviour is that all OSD elements are static in the frame (with the exception of items like the text warnings).

This allows us to layout a number OSD screens with elements to let us know when we are flying close to limits. These OSD elements are always shown taking up space in the image irrespective if they are for information, awareness or warning levels.

My suggestion is to allow an option for elements to only appear when the pilots needs to know about them. i.e. When approaching certain heights, when approaching certain distances from home, battery voltages, current drawn from pack, remaining flight time and approaching stall speeds. Adding an ICON that is similar to a MASTER ALARM in a full size could be interesting to add too for then any item passes a key threshold.

This would allow for a very uncluttered layout for those pilots who like to only want to see key OSD pieces when they are needed. The trigger values could be setup for the 'warning' (appear in OSD briefly), critical (appear solid in OSD) and WARNING (appear in OSD and flash)

This could also tie into mode selection too. i.e. in NAV WP, waypoints dynamically appear with remaining flight time shown..

This would impact pilots like me who like to fly with the minimum of OSD pieces to have other OSD elements only appear when I need to know about them. I.e. for pilots who only care about making sure they don't fly above a local 400ft ceiling, have the ALT. displayed when they pass 300, become critical when they pass 350 and become a warning when they pass 380. I could identify the area of the screen I want my alerts in and then as they happen they appear in that area.

Thanks for looking at this idea. It is one of my more wacky ones. Happy flying and thanks for all of the hard work providing us with such a fantastic project!

[b14ckyy]

As both requests are very similar I allow myself to copy my request here (as yours is older) and close mine.

Current Behavior

Right now, all alarms only make OSD Items blink. This means we cannot have Alarms for Items that are not on Screen. Also Blinking on MSP-DP based systems (Basically all digital FPV systems now) has issues with very slow blink rates or disappearing elements.

Desired Behavior

Show Alarms as System Messages and/or blinking as Options.

Suggested Solution

I suggest that any Alarm can be shown as a System message.
There should be 3 Settings to select from for Alarms: Blinking / System Message / Both
If multiple alarms appear, they should rotate as usual
If possible, general Info messages like Waypoint info or Radar Info should be disabled when an alarm happens to make sure it is not missed.

Alternative:
Instead of using system messages, another option could be to have a dedicated OSD element for warnings. This element could be placed individually on the screen or any layout and show something like this: WARN:XXXXX
So this dedicated OSD element would just be 10 chars wide and show the actual warning element with its value. Leaving 5 chars for the OSD element should be sufficient for all the warning elements. maybe 6 if needed. I guess the used mAh needs 6 fields as the unit consists of 2 fields + 4 digits

Who does this impact? Who is this for?

Any Pilot in General but mostly Digital Pilots where the OSD Elements have usually a very slow update rate to preserve bandwidth.
This also allows a cleaner OSD with less elements while still preserve critical warnings like ESC Temp, IMU temp or RSSI/SNR Alarms while only having LQ on screen.

Additional context