Hi all,
I am trying to set up Launch Control in BF 4.4 but getting an error message for "set osd_warn_launch_control = on".
I would like to see the actual angle in the goggle...

Am I missing anything?

Thanks

The Launch Control feature isn't automatically compiled into the firmware for Betaflight 4.4.x unless you explicitly specify the USE_LAUNCH_CONTROL custom define in the Build Configuration section of the Firmware Flasher when flashing new firmware. The Custom Defines box will only appear if you have Expert Mode switched on. You will therefore need to re-flash the firmware with USE_LAUNCH_CONTROL specified. After doing that the Launch Control related CLI commands will then work as expected.

Thanks. Launch control was included when I flashed the firmware. All other commands work except that one. Anyway. I can live with that...
Thanks again for the quick reply

I've been a little busy over the last few days but I just took some time out and did some digging through the Betaflight 4.4.x source code. What I discovered is that all of the individual CLI osd_warn_* settings that were present in previous versions of Betaflight (including osd_warn_launch_control) have now all been consolidated into a single osd_warn_bitmask setting in Betaflight 4.4.x which is just a single number. To enable the warnings you want displayed, just add up the numbers for each of the warning options you want from the list below and then set the osd_warn_bitmask setting to that value.

For example, if you wanted warnings for Battery Warning (4), Battery Critical (8), Failsafe (512) and Link Quality (16384) you would set the osd_warn_bitmask setting value to 16908 (which is 4 + 6 + 512 + 16384).

Warning option bitmask values:

• 0 = No Warnings
  
• 1 = Arming Disabled
  
• 2 = Battery Not Full
  
• 4 = Battery Warning
  
• 8 = Battery Critical
  
• 16 = Visual Beeper
  
• 32 = Crash Flip Mode
  
• 64 = ESC Fail
  
• 128 = Core Temperature
  
• 256 = RC Smoothing Failure
  
• 512 = Failsafe
  
• 1024 = Launch Control
  
• 2048 = GPS Rescue Unavailable
  
• 4096 = GPS Rescue Disabled
  
• 8192 = RSSI
  
• 16384 = Link Quality
  
• 32768 = RSSI dBm
  
• 65536 = Battery Over Capacity
  
• 131072 = RNSR
  

Alternatively just go to the OSD tab in the Betaflight Configurator GUI and manually switch on the warning options you want in the Warnings panel on the right and that will automatically calculate and set the correct osd_warn_bitmask value behind the scenes for the options that you switched on...

Thanks a lot