please let us have full support for information from the Inav Flight controller and to the Goggles. Very missed is warnings, Direction home and compass and the artifical horizon, which at the moment is not moving. stupid to se that pitch value is changing but the art. horisont is not.

please DJI add the artificial horizon, throttle position, warnings and the stats screen after disarm.

Yes we need inav support! Warnings are key

Hello there Tekniqueman. Thank you for reaching out and for sharing your insights with regards to this matter. I will cascade this thread to the designated DJI department for further attention. All significant suggestions or requests will be implemented after the evaluation of the DJI Engineers. For the latest updates on DJI, please stay tuned to our DJI official website at www.dji.com. Thank you and please stay safe always.

INAV and dji fpv - made for each other ! We are waiting for OSD support in INAV!

PLZ update the FPV Googles, to get ALL INAV OSD things on the goggles. must be a few to implement.

i wont use the goggles anymore, because i have not all important infos on screen...

INAV OSD on my DJI goggles, that would be great. Please DJI people ! We're waiting !

The community would greatly appreciate implementation of the missing OSD elements from iNav in the DJI OSD!  

In INAV 2.6, the developers have spend much time to use the DJI craft_name for showing warnings etc. This works well, but still much information is missing in the OSD.
Examples of important things: virtual horizon, OSD menu

So, I think that the INAV team has done what they can. INAV one of (if not "the") most common firmware for (intelligent) airplanes and flying wings. It would be really great if DJI could support this flight controller firmware in a improved way.
I know several people that do not buy DJI because they would loose so much information on the OSD.

For airplanes / wings, the most important OSD functions would be:
- virtual horizon
- throttle position
- OSD menu
- stats display after disarm
- (warnings implemented w/o workaround from INAV)

Thank you very much in advance for this improvement, DJI!