Hey All. With the release of Betaflight 4.4 HD OSD, I want to give you an update on changes necessary to get this working correctly on 4.4. If you follow the exact steps in the video without these changes, your OSD will be shrunk into 1/3 of the screen in the goggles. You can follow all the steps in the video EXCEPT, 1 - There is no need for the FakeHD (do not run the CLI commands below in WTFOS). 2 - You should set the OSD to HD in Betaflight, and 3 - No need for the throttle position OSD element in position 4. Everything else works perfect. package-config set msp-osd fakehd_enable true package-config set msp-osd fakehd_hide_menu_switch true
@@Pozzix65 Yes, this will only take effect when you're using the vista though (DIY mode). The O3 mode will continue to work as originally provided by DJI.
Hey Everyone! Thanks for watching this video! Make sure you check out the video description for links and CLI commands used in this video. Also, if this feature blows your mind, please take a few minutes to support these projects by visiting their Github site and making a donation to the developers.
After root the sd card is no longer required but it is required for the fonts with FakeHD. If you remove it, FakeHD will not find the font files and then will revert to its stock fonts and icons.
Hi There, Great informative video. I saw on another channel the below commands ran. Do you have to run these each time you run updates? If I'm missing something please let me know Thanks Air unit and caddx vista package-config set msp-osd compress_osd true package-config apply msp-osd DJI Goggles package-config set msp-osd rec_enabled true package-config apply msp-osd
I didn't use that command on the air unit side. It seems like it may be specific for INAV so that it sends compressed OSD vs. RAW data. No need to reapply.
Great tutorial. But please let me know. How to make step back from fakeOSD. How come back to default OSD with WTFOS or disable any changes you showed? :)
Thanks! Run these commands to disable the fakeHD. If you made any changes to the native XML of the DJI OSD, use the adb steps to put the original XML file back onto the goggles. package-config set msp-osd fakehd_enable false package-config apply msp-osd
Hi, i followed every step till the point of getting the conthrax -sb font to the goggles and i am lost. Can you elaborate more on it. in Minimal ADB and fastboot termminal after pulling the XML file , i checked in my folder the "system folder" apprears as it should be as per your instructions. I have downloaded the conthrax fonts do i copy the font file into the Minimal ADB and fastboot folder and rename the file ending .ttf? I am stuck at pushing the conthrax sb fonts to the goggles. some help much appreciated.
You copy the font file to the minimal adb folder. The font file should already have an extension of .ttf. If it doesn't, make sure that you are actually seeing the file extensions (windows hides these by default).
Thanks! But the icons are so cool! :) I think with BF 4.4 you may get the ability of pushing the elements to the edge of the screen but that's all I am expecting. I tried the BF 4.4 RC1 and it did not work with the DJI, still limited to 4:3. I saw RC2 is out but I haven't had a chance to try that one yet.
@@Mangorille V2, and all is on 0606, got the font files in the goggles sd card, most of the times I get “waiting for OSD” bottom right, but never loads unless I re flash on the WTF site.
Not with the O3, this only works on the prior system with the V1/V2 goggles. The O3 will work as you mention and even the new version of betaflight doesn't seem to resolve that.
@mangorille Hello! Have some questions. 1 iam using mi v2 for mi caddx vista build and for mi potato dji fpv doing this It affects in something the potato? And also when changing cadx vista firmware, y Will loose bf configuration? Like pids rates and all the others config un bf? Thanks!
No, it wouldn't impact the DJI FPV mode as the Caddx Vista runs in the DJI FPV System mode. Changing the Caddx Vista firmware does not change your Betaflight configuration. They are completely unrelated.
@@Mqzfpv Sounds like the font size you have is too large. Try adjusting the font size smaller. I have my XML file in the video description if you want to give that a try.
@@e2untae If the OSD keeps rebooting it means you have an issue with the XML file (i.e. you made a change that broke the expected format). You can grab my file from the video description and then make changes very slowly until you have the desired layout.
@@SplashOne-ul5wi And you did the root and WTFOS install already? I don't have these goggles anymore to help you troubleshoot step by step, I'd suggest going over to discord.
You're not supposed to see the throttle position on the screen. It is just a flag used by FakeHD to turn itself on or off. Do you want to see it? If so, you need to change one of the command lines I provided.
@@SKocinski Because you're already turned it off, run these two commands: package-config set msp-osd fakehd_hide_menu_switch false package-config apply msp-osd
Do you know how to get the mbps/sec and ch to appear correctly? I tried to copy the .xml file provided in the github page but those three above the battery won't show up
Try using the file I put in the video description (goggle drive). Those will have the items displayed and then you can follow the instructions in the video to fine tune through trial and error to get it exactly where you want.
Hi @Mangorille ! thanks for making a video about my work ;) Tell me why the Python script doesn't work at 13:02 ? Maybe I can help you Also, I've modified the doc since then, the 606 versions of googles are the most used but not obligatory. I did not test other versions but it can work. The important thing is to have the same version on both.
Hey, what a small world, thanks for figuring this out! Please feel free to link to my video on your page if you think it would be helpful for folks. Here is the error I get when I try to run the Python script: File "D:\Drone\WTFOS\show_xml.py", line 71 dji_stuff/show_xml.py at 581dcb42ac6aa2f282d7b5c5085d97d4312492bd · druckgott/dji_stuff · GitHub ^ SyntaxError: invalid decimal literal
Thank you man for your guide, but I've one question: after following all the steps in worked perfectly fine, but... Bitrate and latency are not showing up anymore. Just the icons, with no values. Any help? Thanks again!
Did you try moving them around? Possible that you moved them off the screen. You can try using the XML file I have linked in the video description and then tweaking the X and Y values every so slightly. It's a trial and error process.
@@Mangorille Thank for you reply, I fixed it. Problem awas I didn't push .ttf file also for DJI HUD. I told the goggles to use it while not pushing it in the right folder. Have a nice day🤜🤛
All looks very good. I have a dji air unit that wouldn't show a picture in my goggles. I put another one in the drone and it worked so no issues with setup or wiring of the quad. I put the the first one back in and nothing. I took the antennas off (under a fan) and powered it up and there was a picture again. Plugged the antennas back in and powered up and no picture again. They are original dji antennas. I did this ten times and the result was the same every time. Anyone have any idea what is going on? Thanks.
Try double checking the camera cable or the connection of the cable. I'd suggest trying to swap the camera and cable from the known working unit over to the one that does not seem to work consistently.
@Mangorille cheers mate. Its definitely a strange one that it works every time without the antennas plugged in but doesn't work when they are. I will try what you suggest. Thank you
I cant get custom osd elements to work. I followed all these steps and got wtf os working on goggles. on the goggles on bottom right it says waiting for osd. please help i want to fly lol
@@sjacksonhodum If you unplugged it during updating, I'd suggest you start the process from the beginning again just in case something didn't get updated correctly. You can uninstall WTFOS and then refresh the DJI firmware. No need to re-root the goggles, that's a one time.
@@Mangorille thanks!! I fixed it and am loving the pretty osd and the longer range with 1200mw. I love ur video. It helped lots. I had to hold usb cable at certain angle lol. Thanks once again
@@Mangorille No, no, not this known issue. Recording in the V2 Goggle does not work properly anymore for some people using wtfos. Take a look at Discord.
You mean the throttle stick position doesn't show in the goggles? If so, it's because we ran a command to hide it. If you want to see it I can give you the command to show it.
@@Yukrop Correct, and then make sure to run the apply command afterwards. package-config set msp-osd fakehd_hide_menu_switch false package-config apply msp-osd
Yes, the xml file has an issue. You may have moved it too far off the screen. Unfortunately it is a lot of trial and error unless you can get that overlay preview tool working (which I wasn't able to).
Which air unit are you using and which OSD? There are different methods of OSD right now: 1. On the Vista/original Air Unit, there is a custom OSD built into the goggles. This will not work for all elements. 2. On the Vista/original Air Unit, there is the MSP Display Port when using WTFOS 3. On the O3 Air unit, there is the MSP Display Port by default
@@rahmatrizki2811 Ah okay. I'll let someone else comment, I don't use GPS on my quads. Only thing that comes to mind is whether you had sat lock before you took off?
@@Mangorille one last thing. And Also some elements are not fully shown (cropped) which I think this has something to do with why my “Home direction” does not appear.
@@rahmatrizki2811 Are they cropped or do you see them wrapping around. If they are wrapping around, you need to look at that mapping of how the FakeHD takes the 4:3 and makes it 16:9 (the diagram with the colours) @ 4:13 in the video
After "package-config set msp-osd rec_enabled true" and the "package-config apply msp-osd" I don't get a .osd file on my goggles, and yes I rooted and installed wftos on the goggles and air unit. Do you need to arm the aircraft in order for this to work? I only see the .srt file.
Thanks for this video, but I'm missing something obviously... My DJI fonts have changed but I keep getting the message "OSD waiting..." What am I doing wrong? Thanks for your help!
@@Mangorille Yes I have powerd it and I thought maybe I had set the wrong MSP port, but I'm quite sure it's good now. But still I get the same message... If I choose custom OSD I get my 'old" OSD back in the goggles but in the bottom still the message OSD waiting..
hello :-) I follow your video on every step, I change DJI font for new one - Conthrax TTF but still see just old analog text and battery icons from osd and dont see ani colour elements. Just mix DJI info on left and other font in middle and right side ... not sure whats wrong :-(
Wow! That's a very indepth video! Unfortunately I'm not a nerd so it kinda made my head hurt! 🥴😂. I've been using the WTF OSD hack for a while with a custom font and icons, but haven't managed to push the icons out to 16:9. I tried using the CLI on WTF with the FakeHD command lines, but it wouldn't work - something about packages not found. Do I need to update my V2 goggles firmware first before the FakeHD will work? Thanks again for your awesome content! 🙏
Do you have the msp osd package installed in WTFOS? You want these commands for FakeHD: package-config set msp-osd fakehd_enable true package-config apply msp-osd package-config set msp-osd fakehd_hide_menu_switch true package-config apply msp-osd package-config set msp-osd rec_enabled true package-config apply msp-osd
@@Mangorille Yes, I've had it installed for some time. Been working fine, but the elements were limited to 4:3 without the FakeHD. I tried the CLI on WTF configurator and it wouldn't work. I reloaded the page and power-cycled the goggles, then cut and pasted your CLI lines above and bingo! It's working now! I just powered my quads and goggles and moved OSD elements around in Betaflight. It looks great! Thanks so much for your help mate. It's so much nicer with a HUD like this! 🙏❤
@@Mangorille v2 googles and O3 unit. I have the OSD. It's just that the font never change.. Im pretty sure I followed from step one all the way to the end. Idk why it doesn't work..
@@russgrgda8198 This does not work with the O3. It requires WTFOS which only works with the vista/old style air unit. You probably did the WTFOS on your V2 goggles in the Digital FPV mode. You would have needed to also install WTFOS on the air unit side and it wouldn't have worked with the O3.
I did everything like described in the video. Thanks. It works - but I can‘t select/switch anymore from 1 to the other system. I configurate everything fine on DJI FPV digital system, but after I can‘t switch anymore to DJI O3 system. 😢😢😢
Heloo mangorille. I have done everething as you said, iam also on 01.00.0607 but i have this mensage " 00:04 Attempting Step 1... 00:41 - Found Device: GP150, Version: 01.00.0607 00:41 Step 1 - Success! Rebooting... 01:06 Attempting Step 2... 01:17 Step 2 - Success! 01:20 Attempting Step 3... 01:24 Failed! Your firmware might not be rootable, please try downgrading with Butter." I have used butter as you also but iam getting that message at the end thanks
You should use butter to downgrade your v2 goggles to 606 firmware (you are on 607). Also make sure you’re on the DIY mode in the goggles when rooting.
@@Mangorille i have done that but i can't still see de new fonts :( what i could be doing wrong? Also, when You done the wtfos You upgrades Again the googles with assistant, why is that? It si not supposed to be o. 0606? Thanks
@@gonzafpv2843 Did you make sure to root and install the MSP OSD on the vista as well? Once you root, you can use the DJI software to upgrade the firmware.
why cant all the files needed be put in their correct place then simply make it available in a zip file? a shorter video could be done showing how to customize the scripts.
I have everything linked in the video description plus the command lines so hopefully that helps. Problem here is that it is more than just the files, you need to actually use the DJI software, WTFOS software, etc...
saaalooooowwww dooooowwwnnnn maaannnnnn. I mean, I already got the OSD n stuff, but just couldn't keep up yo. Preeeechiate it, nun the less. Just too fast ma bro
Lots to cover and this is already an 18 minute video. You can slow the video down by clicking the gear icon and going like 1/2 speed playback with subtitles.
Hello, after I did wtfos my video was in 4:3 size. It's like that on goggles too. What could I do? use inav 7.0 Video: ruclips.net/video/kcvC68v8ELc/видео.htmlsi=AODkIjTCvEF5Jff6
Ya, but the O3 supports the MSP Canvas mode natively. Sure it doesn't look as nice with the custom logos and fonts but you get other things with the O3 that the old air unit doesn't support. Still neither system is perfect and I find myself flying both.
Hey So i've installed the WTFos both on Vista and Goggles v2, and tried to add the FakeHD and same custom font as u. Unfortunetly i've ran into an issue where the OSD is freezing and restarting. Also im unable to enter the DJI osd menu. Tried to hold the Backbutton for 5 sec, also doesn't help to show the DJI osd. Anyone had same/similar issue? Uninstalling WTFos from the googles might help fixing it? wanna rollback before installing FakeHD ruclips.net/video/ejuo7FJ0UxQ/видео.html
Hey All. With the release of Betaflight 4.4 HD OSD, I want to give you an update on changes necessary to get this working correctly on 4.4. If you follow the exact steps in the video without these changes, your OSD will be shrunk into 1/3 of the screen in the goggles. You can follow all the steps in the video EXCEPT, 1 - There is no need for the FakeHD (do not run the CLI commands below in WTFOS). 2 - You should set the OSD to HD in Betaflight, and 3 - No need for the throttle position OSD element in position 4. Everything else works perfect.
package-config set msp-osd fakehd_enable true
package-config set msp-osd fakehd_hide_menu_switch true
so if I have some vistas vtx and camera AND O3 also, can this procedure work? (suppose that I have all my quads on BF 4.4.x) TIA
@@Pozzix65 Yes, this will only take effect when you're using the vista though (DIY mode). The O3 mode will continue to work as originally provided by DJI.
Hey Everyone! Thanks for watching this video! Make sure you check out the video description for links and CLI commands used in this video. Also, if this feature blows your mind, please take a few minutes to support these projects by visiting their Github site and making a donation to the developers.
Thanks! This is so cool, I finally turned off the annoying default voltage/timer and moved all the icons around to make it look clean.
Ya, takes a while to get perfect but time well spent. I miss this level of customization now that solely use the goggles 2.
Can we remove the sd card after root and font install?
After root the sd card is no longer required but it is required for the fonts with FakeHD. If you remove it, FakeHD will not find the font files and then will revert to its stock fonts and icons.
Thank you. This is much better than the stock osd
Welcome, I thought it was awesome and a shame it doesn't work on the Goggles 2/O3.
Hey man does work with the v2 when using the 03 air unit?
No, this only works with the WTFOS partition and that only works with the previous generation.
Hi There,
Great informative video. I saw on another channel the below commands ran. Do you have to run these each time you run updates? If I'm missing something please let me know
Thanks
Air unit and caddx vista
package-config set msp-osd compress_osd true
package-config apply msp-osd
DJI Goggles
package-config set msp-osd rec_enabled true
package-config apply msp-osd
I didn't use that command on the air unit side. It seems like it may be specific for INAV so that it sends compressed OSD vs. RAW data. No need to reapply.
Great video mate... It really helps a lot. Thanks.
Great tutorial. But please let me know. How to make step back from fakeOSD. How come back to default OSD with WTFOS or disable any changes you showed? :)
Thanks! Run these commands to disable the fakeHD. If you made any changes to the native XML of the DJI OSD, use the adb steps to put the original XML file back onto the goggles.
package-config set msp-osd fakehd_enable false
package-config apply msp-osd
Excellent instructional video. Can't find a video like this for Ardupilot.
Thanks Buddy! Happy flying!
Thanks for putting together, looks neat and worth the effort
Hi , when I run adb device , The code responds to me :no devices are displayed
You already ran the adb start-server command? Are you goggles rooted already with WTFOS installed?
Hi, i followed every step till the point of getting the conthrax -sb font to the goggles and i am lost. Can you elaborate more on it. in Minimal ADB and fastboot termminal after pulling the XML file , i checked in my folder the "system folder" apprears as it should be as per your instructions. I have downloaded the conthrax fonts do i copy the font file into the Minimal ADB and fastboot folder and rename the file ending .ttf? I am stuck at pushing the conthrax sb fonts to the goggles. some help much appreciated.
You copy the font file to the minimal adb folder. The font file should already have an extension of .ttf. If it doesn't, make sure that you are actually seeing the file extensions (windows hides these by default).
@@Mangorille hi, thanks for the reply. I will give it a try again.
Great job! Too much for some cool icons, hope BF 4.4 will include some of it! Loving WTFOS so far. Doesn’t always boot up but works most of the times.
Thanks! But the icons are so cool! :) I think with BF 4.4 you may get the ability of pushing the elements to the edge of the screen but that's all I am expecting. I tried the BF 4.4 RC1 and it did not work with the DJI, still limited to 4:3. I saw RC2 is out but I haven't had a chance to try that one yet.
@@Mangorille
Sure. Funny thing WTFOS works some of the times for me. Good thing one can switch back to the older DJI OSD and just fly.
@@MindRiderFPV Which goggles and firmware version are you running? So far it has been working consistently for me.
@@Mangorille
V2, and all is on 0606, got the font files in the goggles sd card, most of the times I get “waiting for OSD” bottom right, but never loads unless I re flash on the WTF site.
@@MindRiderFPV Weird, I've updated the V2 to 0607 and been working okay so far.
Can i do with my dji integra?
No, this is only for the V1 and V2. You can do this with your Integra though: ruclips.net/video/U5Icx5UsSUc/видео.html
Hi. Does this work to dji o3. I find the osd in the center and not in the end of each sides.
Not with the O3, this only works on the prior system with the V1/V2 goggles. The O3 will work as you mention and even the new version of betaflight doesn't seem to resolve that.
@mangorille
Hello! Have some questions. 1 iam using mi v2 for mi caddx vista build and for mi potato dji fpv doing this It affects in something the potato? And also when changing cadx vista firmware, y Will loose bf configuration? Like pids rates and all the others config un bf? Thanks!
No, it wouldn't impact the DJI FPV mode as the Caddx Vista runs in the DJI FPV System mode. Changing the Caddx Vista firmware does not change your Betaflight configuration. They are completely unrelated.
my native Hud is squashed so it doesnt get the full text how do i move that around so it gets more space ?
Squashed into 1/3 of the screen with Betaflight 4.4? If so, look at the pinned comment.
@@Mangorille No. the volt. timer and google battery is squashed with conthrax. so it show like 22...... and tiemr 0.0..... and google battery 14......
@@Mqzfpv Sounds like the font size you have is too large. Try adjusting the font size smaller. I have my XML file in the video description if you want to give that a try.
Hello Why does the OSD keep blurring?
What do you mean by blurring
@@Mangorille goggles V1 reboot osd mess
I'm not good at English sorry!
@@e2untae If the OSD keeps rebooting it means you have an issue with the XML file (i.e. you made a change that broke the expected format). You can grab my file from the video description and then make changes very slowly until you have the desired layout.
This doesn’t work with my speedybee F405 I tried for 2 hours the cli isn’t recognized in betaflight
Are you using betaflight 4.4? If so, check the pinned comment.
i cant find the racing_chnl_osd_win.xml in my Minimal ADB and Fastboot folder. What can i do?
Is this the exact command you used in adb?
adb pull /system/gui/xml/racing_chnl_osd_win.xml
Do you see your goggles when you do adb devices?
@@Mangorille yes i followed every step till there and i couldnt find the file. The goggles do show up in my devices
@@SplashOne-ul5wi And you did the root and WTFOS install already? I don't have these goggles anymore to help you troubleshoot step by step, I'd suggest going over to discord.
@@Mangorille sure, do you have a server?
@@SplashOne-ul5wi No, check out the github page of the person who published this. github.com/EVilm1/WIKI-HACK-DJI-OSD
Hi I have issues with throttle position..I moved it to same position like you and I don't know who but I can't see it on goggles screen
You're not supposed to see the throttle position on the screen. It is just a flag used by FakeHD to turn itself on or off. Do you want to see it? If so, you need to change one of the command lines I provided.
@@Mangorille do you know this command to fix it I really need to see throttle position. Thanks
@@SKocinski Because you're already turned it off, run these two commands:
package-config set msp-osd fakehd_hide_menu_switch false
package-config apply msp-osd
@@Mangorille thank you for your help 🙃🙃
Great was of consolidating that convoluted process, thank you
dont know why the adb can not find my font file used same as you downloaded the ttf file installed on my machine but it can not find the fine crazy.
Did you place the font file in the same folder as your adb.exe?
@@Mangorille thank you for responding but i just got it!! thanks for the upload by far the best around
Do you know how to get the mbps/sec and ch to appear correctly? I tried to copy the .xml file provided in the github page but those three above the battery won't show up
Try using the file I put in the video description (goggle drive). Those will have the items displayed and then you can follow the instructions in the video to fine tune through trial and error to get it exactly where you want.
Hi @Mangorille ! thanks for making a video about my work ;)
Tell me why the Python script doesn't work at 13:02 ? Maybe I can help you
Also, I've modified the doc since then, the 606 versions of googles are the most used but not obligatory. I did not test other versions but it can work. The important thing is to have the same version on both.
Hey, what a small world, thanks for figuring this out! Please feel free to link to my video on your page if you think it would be helpful for folks. Here is the error I get when I try to run the Python script:
File "D:\Drone\WTFOS\show_xml.py", line 71
dji_stuff/show_xml.py at 581dcb42ac6aa2f282d7b5c5085d97d4312492bd · druckgott/dji_stuff · GitHub
^
SyntaxError: invalid decimal literal
Does this work for V2 with o3 air unit?
No, this is only for the systems that can support the WTFOS (O3 doesn't... yet...)
Thank you man for your guide, but I've one question: after following all the steps in worked perfectly fine, but... Bitrate and latency are not showing up anymore. Just the icons, with no values. Any help? Thanks again!
Did you try moving them around? Possible that you moved them off the screen. You can try using the XML file I have linked in the video description and then tweaking the X and Y values every so slightly. It's a trial and error process.
@@Mangorille Thank for you reply, I fixed it. Problem awas I didn't push .ttf file also for DJI HUD. I told the goggles to use it while not pushing it in the right folder. Have a nice day🤜🤛
@@gabrielezilliFPV Ya that'd do it, glad you got it figured out. Happy flying!
I did everything like you and it worked 😊 Tanks 👍
Great! Happy flying!
All looks very good. I have a dji air unit that wouldn't show a picture in my goggles. I put another one in the drone and it worked so no issues with setup or wiring of the quad. I put the the first one back in and nothing. I took the antennas off (under a fan) and powered it up and there was a picture again. Plugged the antennas back in and powered up and no picture again. They are original dji antennas. I did this ten times and the result was the same every time. Anyone have any idea what is going on? Thanks.
Try double checking the camera cable or the connection of the cable. I'd suggest trying to swap the camera and cable from the known working unit over to the one that does not seem to work consistently.
@Mangorille cheers mate. Its definitely a strange one that it works every time without the antennas plugged in but doesn't work when they are. I will try what you suggest. Thank you
I cant get custom osd elements to work. I followed all these steps and got wtf os working on goggles. on the goggles on bottom right it says waiting for osd. please help i want to fly lol
Did you make sure to install WTFOS and MSP Displayport on the vista air unit as wlel?
@@Mangorille i accidentally unplugged during updating but it still shows video and pops up for a second on wtfos and then disappeares
I also reflashed with butter
@@sjacksonhodum If you unplugged it during updating, I'd suggest you start the process from the beginning again just in case something didn't get updated correctly. You can uninstall WTFOS and then refresh the DJI firmware. No need to re-root the goggles, that's a one time.
@@Mangorille thanks!! I fixed it and am loving the pretty osd and the longer range with 1200mw. I love ur video. It helped lots. I had to hold usb cable at certain angle lol. Thanks once again
I faced some "SD Slow" warnings and abnormal video recording terminations since using wtfos/msp-osd. I set HD in BF 4.4RC2.
Sounds like you are using the full size air unit. That SD Slow error has been an issue since 2019. :)
@@Mangorille No, no, not this known issue. Recording in the V2 Goggle does not work properly anymore for some people using wtfos. Take a look at Discord.
@@maryjane136 Good to know, thanks for letting me know. I haven't had this issue... yet...
Excellent video. Thanks for sharing
everything works except stick throttle why
You mean the throttle stick position doesn't show in the goggles? If so, it's because we ran a command to hide it. If you want to see it I can give you the command to show it.
@@Mangorille yes i will be grateful
@@Mangorille fakehd_hide_menu_switch false ? i have to do the command false
@@Yukrop Correct, and then make sure to run the apply command afterwards.
package-config set msp-osd fakehd_hide_menu_switch false
package-config apply msp-osd
@@Mangorille tnx
my goggoles and goggle record time dissapper... @@ wrong on xml isnt?
Yes, the xml file has an issue. You may have moved it too far off the screen. Unfortunately it is a lot of trial and error unless you can get that overlay preview tool working (which I wasn't able to).
@@Mangorille i see... I think will root back to first place 😅.
btw i message you on instagram
to send you image from goggles.
Anyway thanks
hey, quick question. why my "home direction" osd does not appear on my goggle ?
Which air unit are you using and which OSD? There are different methods of OSD right now:
1. On the Vista/original Air Unit, there is a custom OSD built into the goggles. This will not work for all elements.
2. On the Vista/original Air Unit, there is the MSP Display Port when using WTFOS
3. On the O3 Air unit, there is the MSP Display Port by default
@@Mangorille im using the wtfos OSD and still cant see it. is there something I missed ?
@@rahmatrizki2811 Ah okay. I'll let someone else comment, I don't use GPS on my quads. Only thing that comes to mind is whether you had sat lock before you took off?
@@Mangorille one last thing. And Also some elements are not fully shown (cropped) which I think this has something to do with why my “Home direction” does not appear.
@@rahmatrizki2811 Are they cropped or do you see them wrapping around. If they are wrapping around, you need to look at that mapping of how the FakeHD takes the 4:3 and makes it 16:9 (the diagram with the colours) @ 4:13 in the video
After "package-config set msp-osd rec_enabled true" and the "package-config apply msp-osd" I don't get a .osd file on my goggles, and yes I rooted and installed wftos on the goggles and air unit. Do you need to arm the aircraft in order for this to work? I only see the .srt file.
You either need to arm or you need to turn off the auto temp control.
Thanks for this video, but I'm missing something obviously... My DJI fonts have changed but I keep getting the message "OSD waiting..." What am I doing wrong? Thanks for your help!
Have you powered on and connected your air unit? OSD waiting means that the wtfos is waiting for an active connection to load the custom osd.
@@Mangorille Yes I have powerd it and I thought maybe I had set the wrong MSP port, but I'm quite sure it's good now. But still I get the same message... If I choose custom OSD I get my 'old" OSD back in the goggles but in the bottom still the message OSD waiting..
@@Flying_yesenaer Did you root the air unit as well and install the msp osd package on the air unit too?
@@Mangorille Ah that part i missed... I'll try that first! Thanks a lot 👍
@@Flying_yesenaer No problem. Email me if you need any further help so we can exchange screenshots etc.
hello :-) I follow your video on every step, I change DJI font for new one - Conthrax TTF but still see just old analog text and battery icons from osd and dont see ani colour elements. Just mix DJI info on left and other font in middle and right side ... not sure whats wrong :-(
Did you put the font files onto the SD card?
@@Mangorille yes
@@SalySalymon All four font files on the root of the SD card? Did you unplug the USB from the goggles and restart the goggles?
@@Mangorille yes I do :-( ita really posaible got color font i googles? its font from DJI side (googles) or from transmiter?
@@SalySalymon The OSD is driven by the goggles.
Hoping we get this for goggles 2
Same, probably will take a while to hack the new software though.
Wow! That's a very indepth video! Unfortunately I'm not a nerd so it kinda made my head hurt! 🥴😂. I've been using the WTF OSD hack for a while with a custom font and icons, but haven't managed to push the icons out to 16:9. I tried using the CLI on WTF with the FakeHD command lines, but it wouldn't work - something about packages not found. Do I need to update my V2 goggles firmware first before the FakeHD will work? Thanks again for your awesome content! 🙏
Do you have the msp osd package installed in WTFOS? You want these commands for FakeHD:
package-config set msp-osd fakehd_enable true
package-config apply msp-osd
package-config set msp-osd fakehd_hide_menu_switch true
package-config apply msp-osd
package-config set msp-osd rec_enabled true
package-config apply msp-osd
@@Mangorille Yes, I've had it installed for some time. Been working fine, but the elements were limited to 4:3 without the FakeHD. I tried the CLI on WTF configurator and it wouldn't work. I reloaded the page and power-cycled the goggles, then cut and pasted your CLI lines above and bingo! It's working now! I just powered my quads and goggles and moved OSD elements around in Betaflight. It looks great! Thanks so much for your help mate. It's so much nicer with a HUD like this! 🙏❤
@@AcruxFPV Awesome, welcome to the world of eye candy ;)
We're all nerds here ;)
Haha, this particular one takes nerdism to a new level ;)
This dint work for me idk what I did wrong. I followed every steps in the video
What happens exactly after you followed these steps? Which goggles and air unit did you try this on?
@@Mangorille v2 googles and O3 unit. I have the OSD. It's just that the font never change..
Im pretty sure I followed from step one all the way to the end. Idk why it doesn't work..
@@russgrgda8198 This does not work with the O3. It requires WTFOS which only works with the vista/old style air unit. You probably did the WTFOS on your V2 goggles in the Digital FPV mode. You would have needed to also install WTFOS on the air unit side and it wouldn't have worked with the O3.
I did everything like described in the video. Thanks. It works - but I can‘t select/switch anymore from 1 to the other system. I configurate everything fine on DJI FPV digital system, but after I can‘t switch anymore to DJI O3 system. 😢😢😢
You no longer see the DJI O3 option in your Goggles V2?
@@Mangorille yes. The Wtfos MSP OSD software is great but after installing i can‘t select anymore Dji O3 system with V2-Goggles
@@elmarirony5580 Check this page about half way down: github.com/fpv-wtf/butter
Loss of O3 mode after re-installing wtfos
@@Mangorille thanks Mangorille, now works very well. 🙏
Is it possible to use WTFOS also for O3-system?
Heloo mangorille. I have done everething as you said, iam also on 01.00.0607 but i have this mensage
" 00:04 Attempting Step 1...
00:41 - Found Device: GP150, Version: 01.00.0607
00:41 Step 1 - Success! Rebooting...
01:06 Attempting Step 2...
01:17 Step 2 - Success!
01:20 Attempting Step 3...
01:24 Failed! Your firmware might not be rootable, please try downgrading with Butter."
I have used butter as you also but iam getting that message at the end
thanks
You should use butter to downgrade your v2 goggles to 606 firmware (you are on 607). Also make sure you’re on the DIY mode in the goggles when rooting.
@@Mangorille i could do it. But know i can't see the new font in googles, what could that be? I see the old letters in fake hd
@@gonzafpv2843 Make sure you unplug the goggles from the computer. I noticed that the fonts will not pull in as well when connected to the computer.
@@Mangorille i have done that but i can't still see de new fonts :( what i could be doing wrong? Also, when You done the wtfos You upgrades Again the googles with assistant, why is that? It si not supposed to be o. 0606? Thanks
@@gonzafpv2843 Did you make sure to root and install the MSP OSD on the vista as well? Once you root, you can use the DJI software to upgrade the firmware.
why cant all the files needed be put in their correct place then simply make it available in a zip file? a shorter video could be done showing how to customize the scripts.
I have everything linked in the video description plus the command lines so hopefully that helps. Problem here is that it is more than just the files, you need to actually use the DJI software, WTFOS software, etc...
saaalooooowwww dooooowwwnnnn maaannnnnn. I mean, I already got the OSD n stuff, but just couldn't keep up yo. Preeeechiate it, nun the less. Just too fast ma bro
Lots to cover and this is already an 18 minute video. You can slow the video down by clicking the gear icon and going like 1/2 speed playback with subtitles.
@@Mangorille you know, it’s really my brain that needs to speed up! Haha thanks you man!
Hear you. Let me know if you have any questions and I’ll try to answer.
Hello, after I did wtfos my video was in 4:3 size. It's like that on goggles too. What could I do? use inav 7.0 Video: ruclips.net/video/kcvC68v8ELc/видео.htmlsi=AODkIjTCvEF5Jff6
And the winner is......the OLD AirUnit - because the NEW SHINY O3 isnt working with that !!!
Ya, but the O3 supports the MSP Canvas mode natively. Sure it doesn't look as nice with the custom logos and fonts but you get other things with the O3 that the old air unit doesn't support. Still neither system is perfect and I find myself flying both.
Hey
So i've installed the WTFos both on Vista and Goggles v2, and tried to add the FakeHD and same custom font as u.
Unfortunetly i've ran into an issue where the OSD is freezing and restarting.
Also im unable to enter the DJI osd menu. Tried to hold the Backbutton for 5 sec, also doesn't help to show the DJI osd.
Anyone had same/similar issue?
Uninstalling WTFos from the googles might help fixing it? wanna rollback before installing FakeHD
ruclips.net/video/ejuo7FJ0UxQ/видео.html
nevermind - found the problem was missing " after the font name in racing_chnl_osd_win file
@@Faronsky Glad you fixed... The restarting OSD is a sign that something got messed up in the XML file.
Hi . my goggles say "OSD WAITING" where did i go wrong? HELP
Was the OSD working fine before you tried this mod? Did you make sure to root and install WTFOS on both the Goggles and Air Unit?