You can just put the "altitude" symbol on everything and achieve essentially the same result. They won't be labeled with a question mark, they be labeled "altitude" instead.
@@senseisecurityschool9337 Yeah, but I chose icons that make sense to a cetain degree. Ofc it's not perfect, but it's acceptable give what the alternative is.
@@DZARO You chose icons that mean something else. You choose "K" for distance in METERS. THen when we told you that you made the change in the wrong file and you should move your changes to the appropriate place, and that M would better than K, you started slandering us.
Hi. Today I experienced some INAV OSD freezing/flickering during my 2nd flight. I don't know what happend, I flew the same local spot and the link quality is perfect during theses freezing. I noticed it concern only the INAV layer, the DJI parts are solid. Did you experienced this too?
hi, after 2 hours of flight with the OSD I noticed the Wh/Km icon don't appear on my goggles, I see only the value and that's the most important of course. I don't know if it is a normal behavior or an issue. Another thing concern the flight stats: At the end of flight, I can see them in my goggles but they never appear in the OSD recordings, is it possible to let them recorded too? Many thanks to you.
Regarding the flight stats: The goggles stop the recording very quickly after you disarm and the end screen does not show. I have the same issues. The only way is to start the recording before you arm and then it will continue recording after you disarm. It works on the Vista running the O3-compatible firmware, not sure if it will work for an O3, I have to try this. Regarding the icon: I'm not sure what you mean. Form what I understand, you don't see the characters in flight, but then you do see them in the recording? Is that correct? maybe you can try to explain it again or upload a video.
@@DZARO I only see the numbers but not the unit appear, neither in flight nor in the recording, I having this issue only with the Wh/Km icon. It's a shame not to be able to record the stats because it's very useful for comparing different configurations.😃 EDIT: I have a second issue with the power (W) the value not always match the power, I guess when the power exceeds 100W the problem appear. I have published a video here: th-cam.com/video/fpkzQL4G1iM/w-d-xo.html
OK, so I looked into this and here is a detailed explanation: The [mAh/km] is made up of two symbols: *SYM_MAH_KM_0* and *SYM_MAH_KM_1* These have been substituted with the following: *[mAh]* symbol and the letter [E], standing for efficiency. It is up to the user to know that the units symbolise "mAh of Efficiency". In case of the [Wh/km], there is only one part to the symbol: *SYM_WH_KM* This means that it can only be substituted with one character, not two. I have left this one as blank because there is no adequate way to symbolise "Wh of Efficiency" My suggestion to you is to use [mAh/km] as the efficinecy units, so that you don't have blank spaces. I know the solution is not perfect, but there is no alternative at the moment. If you look at the following image below, you'll see that the [mAh/km] is made of two characters and the [Wh/km] is made of only one. The rest of the code is based on how these are being used and combined. github.com/iNavFlight/inav-configurator/blob/master/resources/osd/analogue/default.png?raw=true
I understand it is a software limitation, not a bug. Thank you! Have you seen my video with the W unit which disappear when I guess exceeds 100W? Maybe the same software limitation?
If this is not merge on the official Inav releases I don´t know what deserve to be on the project. Thanks again for your time!
How much do you want to bet that it will not be merged?
You can just put the "altitude" symbol on everything and achieve essentially the same result. They won't be labeled with a question mark, they be labeled "altitude" instead.
@@senseisecurityschool9337 Yeah, but I chose icons that make sense to a cetain degree. Ofc it's not perfect, but it's acceptable give what the alternative is.
@@DZARO You chose icons that mean something else. You choose "K" for distance in METERS. THen when we told you that you made the change in the wrong file and you should move your changes to the appropriate place, and that M would better than K, you started slandering us.
@@senseisecurityschool9337 And what is written in this PR is not slander of DJI for example:
github.com/iNavFlight/inav/pull/10046
🤣
This is great! Thanks for all your work and thanks for sharing it with us!
Let me know how it goes and what you think of it after you give it a try!
@@DZARO Will do!
Awesome job!
Thanks!
Nice work 🤩
Thanks 😁
Wow man... Great job!!! 🔥
Thank you 🙌
@@DZARO Can you please add Matek 765SE ??
Added, check the Google Drive Firmware folder!
@@DZAROthanks!!
this is fantastic, thanks man. Is it possible to make the horizon indicator "- - - - -" a bit less bold, and thinner, maybe ". . . ." instead?
Sadly, this is not possible at the moment.
Perfect job. What font do you use?😁
Only one font availabe, DJI's font. You can't change this sadly.
well done! Please take over INAV dev :D
Would love to but I'm not a coder. It would take me a considerable amount of time to learn this. But maybe, maybe in the future, you never know . . .
@@DZARO I understand, but you have the right mindset. Thank you! Hope this gets merged!
Hi. Today I experienced some INAV OSD freezing/flickering during my 2nd flight. I don't know what happend, I flew the same local spot and the link quality is perfect during theses freezing. I noticed it concern only the INAV layer, the DJI parts are solid. Did you experienced this too?
I didn't have this issue until now.
hi, after 2 hours of flight with the OSD I noticed the Wh/Km icon don't appear on my goggles, I see only the value and that's the most important of course. I don't know if it is a normal behavior or an issue. Another thing concern the flight stats: At the end of flight, I can see them in my goggles but they never appear in the OSD recordings, is it possible to let them recorded too? Many thanks to you.
Regarding the flight stats: The goggles stop the recording very quickly after you disarm and the end screen does not show. I have the same issues. The only way is to start the recording before you arm and then it will continue recording after you disarm. It works on the Vista running the O3-compatible firmware, not sure if it will work for an O3, I have to try this.
Regarding the icon: I'm not sure what you mean. Form what I understand, you don't see the characters in flight, but then you do see them in the recording? Is that correct? maybe you can try to explain it again or upload a video.
@@DZARO I only see the numbers but not the unit appear, neither in flight nor in the recording, I having this issue only with the Wh/Km icon.
It's a shame not to be able to record the stats because it's very useful for comparing different configurations.😃
EDIT: I have a second issue with the power (W) the value not always match the power, I guess when the power exceeds 100W the problem appear. I have published a video here: th-cam.com/video/fpkzQL4G1iM/w-d-xo.html
OK, so I looked into this and here is a detailed explanation:
The [mAh/km] is made up of two symbols:
*SYM_MAH_KM_0* and *SYM_MAH_KM_1*
These have been substituted with the following:
*[mAh]* symbol and the letter [E], standing for efficiency.
It is up to the user to know that the units symbolise "mAh of Efficiency".
In case of the [Wh/km], there is only one part to the symbol:
*SYM_WH_KM*
This means that it can only be substituted with one character, not two.
I have left this one as blank because there is no adequate way to symbolise "Wh of Efficiency"
My suggestion to you is to use [mAh/km] as the efficinecy units, so that you don't have blank spaces.
I know the solution is not perfect, but there is no alternative at the moment.
If you look at the following image below, you'll see that the [mAh/km] is made of two characters and the [Wh/km] is made of only one. The rest of the code is based on how these are being used and combined.
github.com/iNavFlight/inav-configurator/blob/master/resources/osd/analogue/default.png?raw=true
I understand it is a software limitation, not a bug. Thank you! Have you seen my video with the W unit which disappear when I guess exceeds 100W? Maybe the same software limitation?
Thanks a lot! Can you please update ATOMRCF405 ?
It's already there. Check the name of your target in your diff. I think it should be ATOMRCF405NAVI. This FC's HEX is in the firmware folder.
@@DZARO hmm I see it but getting - Could not Download ... HTTP Error. I still can download others
@@techlock5406 What about this link?
drive.google.com/file/d/1E1ZRply8qfYlU6yGjcc7lGDFifvWclPu/view?usp=drive_link
@@DZARO this one works just fine. Thanks!
@@techlock5406 I might be making a few more little changes and updates this weekend, just want to get it perfect.
the standard air unit doesnt need this special firmware right?
No, you can use the WTF.OS hack.
Can this be used without WTF.OS? For example: 03 Air Unit and Googles 2 or later on INAV.
@@johnrobert6378 That is the purpose of the whole thing. It's because there is no WTF.OS for Goggles 2 that this workaround was created.
Oh, great! Would it be possible to post a set of instructions on how to make this change. I’m familiar with INAV but not that familiar. Thank you!
@@johnrobert6378 hi, DZARO also did the tutorial for this purpose, it is very easy to do: th-cam.com/video/-VCbKYNf0VA/w-d-xo.html