Yep! There is a small "A" added in front of the regular symbol. You can see it when I take off using auto-launch.

What do I do with this HEX file now? How do I use it?

​@@DZARO perfect!! Thanks again

@@sandro9389 You just flash your FC with that hex file. In the bottom corner on the firmware flashing page you have an icon called "Load firmware [local]". Just pick the HEX file and press flash. Obviously, you need to be in DFU mode.

@@DZARO Thank you. That's exactly how I did it. The FC is also flashed with the official INAV 7.1.1 but when I select your hex it doesn't do anything. It just says: "USB device successfully closed" 😃 Do you have another tip for me?

Man, I tried everything. I'm not giving up yet, but it didn't lead anywhere because they didn't want to accept it. And I get it, it's not that it's their fault. At the end of the day, it is DJI's fault. But they could just accept the couple of changes that I proposed and just let everyone get on with their business. They blame me for making it "political", but at the end of the day, they added those annoying questionmarks, not me. I'm just the loudest voice at the moment challening their decisions. None of us (DJI O3 and Goggles 2 users) agree with their reasoning, but's ok. In time, everything will get resolved one way or the other.

@@DZARO Sadly, it's not a "new" fight. It has been going on for more than a year. Check Inav's PR numbers 8926, 8928 and 9389, which were made by me. Read the discussion in them. They were met with the same fierce resistance and hostility that you were met with. You are probably the fourth or fifth person to try to improve the O3 OSD and face this non-sensical gatekeeping, and it's always by the same people. It really is sad and lamentable. I run my own custom version with almost all OSD elements fixed, there are no ambiguities and no question marks at all in my OSD. It has all been replaced by a combination of the available icons and letters. This shows it's possible to have a fully working O3 OSD with Inav. It just required some changes to the osd.c file code that, although simple and well organized, would never get past the current gatekeeping standards. Really unfortunate for the whole Inav community.

@@Rmaia3d Today I was wondering why the up and down sidebar scrolling arrows were missing. Surprisingly it was a simple mistake that someone made in the naming of the defines. In once case they used DECORATION, in the other DIRECTION. Ambiguity can be removed, but they do have a point that DJI has done a piss-poor job of implementing any sort of reasonable font. I pointed this out to Mosca, but he completey ignored the fact that the bf_osd_symbols.h, bcause neither of the BF fonts actually match what is used by DJI. DJI just did a mix-and-match of whatever they wanted, which is also stupid. When I shared this with Darren, he made a table comparing the DJI fornt set with the other two font sets that are used by BF. I made some changes to that table so here is the link: docs.google.com/spreadsheets/d/1QnSLL68rN3doS0G9fcQBSaIkM589n1OF/edit I made the image below the DJI heading and it's a combination of BF1 and BF2. This would be a PNG of what DJI is actually using. I don't support their perspective, but DJI has screwed us over with this garbage font from over 5 years ago for sure, so it's not fair to blame the INAV devs for that. What I would say is thay they should rename the whole thing to DJICOMPAT mode and just mention in the release that this is just a workaround and that not everything is perfect. Because all that DJI did was to extend the OSD to a wider 16:9 canvas. The font is still the same one used by the V1 and V2 goggles. I would love to see how you implemented the efficiency symbol! Could you share a link to your fork?

On the first point: I've been trying to argue that same point with the INAV devs. They want to keep the '?' to remove ambiguity, but in fact is has the polar oposite effect because now you are just looking at abunch of '?' and you are even more puzzled. Their idea behind keeping the '?' is to show that the system is actually only partially compatible. FYI, have a look at my latest build of the firmware binaries from the 7.1.1 Google Drive folder. You'll find some interesting things, such as multiple crosshairs available. On the second point: I don't know if that is possible and how someone might go about it. Maybe the WTF.OS team are already working on this, who knows. If they manage to get a crack for the O3 AU, they might even crack the Goggles 2. But is that really necessary? Should we, the users, have to go through that trouble? The point is that DJI should have done a proper implementation of canvas mode and they should have implemented at least three tables of symbols/icons, one for Betaflight, one for INAV and one for Ardupilot! That would be the correct approach in my opinion.

@@DZARO yea I've seen your other comments, it really sounds like they're keeping it like that just to spite DJI. Which is incredibly annoying. I spoke with the wtf developers on discord, they say the V2 goggles are fully unlocked and the air unit doesn't need to be unlocked because it is already sending the msp stream anyways. So it would just need someone to write some code to implement a different font set and enable the recording on the v2. Then you can use the existing wtf modules to load the code onto the goggles. I would do it, they even offered some support for loading it onto the goggles, but unfortunately it's too hard for me with my limited coding knowledge. And they will not do this, most have moved on to other projects. Of course it's on dji to fix this, but they don't care and so it's probably never gonna happen:/ it's just frustrating to know that it's so close and it could be so great but it's just out of reach.

Unfortunately, I have to agree with you. It's not fair towards those who have already bought into the DJI ecosystem, such as myself. I honestly don't know what they are expecting us to do? I have over 10 Vistas, 2 orginal AU's and several O3 AU's. Are they expecting people to just sell all of that for a loss and get Caddx/Walksnail gear for all our planes and quads? I don't see myself getting any other system to be honest. There is a workaround, it's possible to do, they just don't want to take it because it's not according to their expectation of DJI is supposed to offer them.

@@DZARO I am same situation as you to many DJI vtx and O3 units to change to another brand that at least are 3 o 4 years behind the features and quality link o DJI. I don´t like bending the knee to DJI but if there is a work around to salve this problem I take it. Again thanks for you efford and I will ask for some targets to compile. I would like to help but my programings skills are absosulute ZERO but I can buy coffes if you need to support you ;-)

@@moriwaky Don't worry at all, just send me the target name, I'll built it for you and I'll add it to the Google drive folder asap :))

@@DZARO thanks for the HEXs and I am sorry for your PR on github been close

@@DZARO Target for 7.1.1 for a Speedybee F405 WING would be awesome ! Thanks a lot !!!!

This is the Heewing T2 Cruza! It's an excellent model!

I can't understand how developers of an open project have such a closed mind. It's not fair to close your PR. They are unable to see the big picture, too much testosterone and too little intelligence. my two cents.

@@moriwaky And now they restricted my comments on the PD as well hahahahahaha

Ther is no secret at all! Just a few edits in the code to make sure that there is some icon or letter where there used to be a questionmark. Nothing special at all!

Come to Discord and we'll sort it out together. discord.com/channels/1082026163746115645/1082027032390672405

We had problems with a buddy this week, couldn't flash, no idea why. He went home, tried it on his own PC, and it worked straight away.

Have a look at this: kzfaq.info/get/bejne/Y7xzla6Ks8yUhnU.html

@@DZARO Thank you for thinking of me.👌👍👍👍😀