Releases: betaflight/betaflight
Releases · betaflight/betaflight
Betaflight 4.1.0 Release Candidate 4
Important
This is a release candidate. It is intended for testing, and some things still need fixing and fine tuning. Please use it with caution and report back any issues at https://github.com/betaflight/betaflight/issues. Thank you.
Important information when upgrading
- A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.6.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.6.0 (or newer) as soon as it is available, or use the CLI for now;
- if you are using the Blackbox Log Viewer, there will be an updated version 3.4.0 to go with Betaflight 4.1 (installation instructions here). Please update as soon as it becomes available;
- bidirectional Dshot, which is the basis for RPM based filtering, has been improved and is now available with BLHeli_32 (from version 32.7 on) and on BLHeli_S hardware (by using the JESC firmware). Use these instructions to get it set up (#8554, #8779);
- as you have come to expect, there is a detailed Tuning Notes for Betaflight 4.1. Use them, or use the new tuning sliders in the Betaflight configurator 10.6.0 to get your craft tuned. Please do not paste tuning configurations from previous versions of the firmware. Some defaults have been changed, and some parameters are used in different ways, so previous tuning settings will not work well with Betaflight 4.1 (#8623, #8736);
- with the introduction of fully configurable VTX control (VTX tables), after flashing the firmware you now have to load a VTX tables appropriate for your VTX and for the country you are flying in before you can control your VTX through Betaflight. Support for loading VTX tables from files will be integrated in the upcoming Betaflight configurator 10.6.0, for now you have to use CLI to set up the VTX tables, see here for details (#7251);
- some optimisations were made to the OSD fonts, and some characters were improved. In order to get a properly working OSD with Betaflight 4.1, the font loaded onto the OSD needs to be updated to the latest version (available in configurator 10.6.0 or newer) (#8390);
- as announced before the release of Betaflight 4.0, support for F3 based flight controllers has been removed from Betaflight 4.1.
Major features:
- new and improved feed forward 2.0 (#8623, #8736);
- reworked bidirectional Dshot (#8554, #8779);
- dynamic idle management using RPM telemetry (#8604);
- fully configurable VTX control with VTX tables (#7251).
Minor features:
- support for the Spektrum SRXL2 serial protocol (#8606);
- support for board-specific custom defaults (#8707);
- support for arbitrary gyro and mag alignment (#8474).
Changes from the previous Release Candidate:
Fixes:
- fixed potential resource conflict with bitbanged Dshot (#8893);
- fixed bug in Dshot code (#8897);
- fixed problem causing lockups of VTX control with some VTX (#8903);
- fixed problems with setting power on IRC Tramp VTX (#8907);
- fixed bug causing lockups in the STM32F745 target (#8914);
- added missing definition for SPI5 on STM32H7 (#8920);
- fixed UART DMA for F4 (#8924).
Target Updates:
Betaflight 4.1.0 Release Candidate 3
Important
This is a release candidate. It is intended for testing, and some things still need fixing and fine tuning. Please use it with caution and report back any issues at https://github.com/betaflight/betaflight/issues. Thank you.
Important information when upgrading
- A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.6.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.6.0 (or newer) as soon as it is available, or use the CLI for now;
- if you are using the Blackbox Log Viewer, there will be an updated version 3.4.0 to go with Betaflight 4.1 (installation instructions here). Please update as soon as it becomes available;
- bidirectional Dshot, which is the basis for RPM based filtering, has been improved and is now available with BLHeli_32 (from version 32.7 on) and on BLHeli_S hardware (by using the JESC firmware). Use these instructions to get it set up (#8554, #8779);
- as you have come to expect, there is a detailed Tuning Notes for Betaflight 4.1. Use them, or use the new tuning sliders in the Betaflight configurator 10.6.0 to get your craft tuned. Please do not paste tuning configurations from previous versions of the firmware. Some defaults have been changed, and some parameters are used in different ways, so previous tuning settings will not work well with Betaflight 4.1 (#8623, #8736);
- with the introduction of fully configurable VTX control (VTX tables), after flashing the firmware you now have to load a VTX tables appropriate for your VTX and for the country you are flying in before you can control your VTX through Betaflight. Support for loading VTX tables from files will be integrated in the upcoming Betaflight configurator 10.6.0, for now you have to use CLI to set up the VTX tables, see here for details (#7251);
- some optimisations were made to the OSD fonts, and some characters were improved. In order to get a properly working OSD with Betaflight 4.1, the font loaded onto the OSD needs to be updated to the latest version (available in configurator 10.6.0 or newer) (#8390);
- as announced before the release of Betaflight 4.0, support for F3 based flight controllers has been removed from Betaflight 4.1.
Major features:
- new and improved feed forward 2.0 (#8623, #8736);
- reworked bidirectional Dshot (#8554, #8779);
- dynamic idle management using RPM telemetry (#8604);
- fully configurable VTX control with VTX tables (#7251).
Minor features:
- support for the Spektrum SRXL2 serial protocol (#8606);
- support for board-specific custom defaults (#8707);
- support for arbitrary gyro and mag alignment (#8474).
Changes from the previous Release Candidate:
Fixes:
Betaflight 4.1.0 Release Candidate 2
Important
This is a release candidate. It is intended for testing, and some things still need fixing and fine tuning. Please use it with caution and report back any issues at https://github.com/betaflight/betaflight/issues. Thank you.
Important information when upgrading
- A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.6.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.6.0 (or newer) as soon as it is available, or use the CLI for now;
- if you are using the Blackbox Log Viewer, there will be an updated version 3.4.0 to go with Betaflight 4.1 (installation instructions here). Please update as soon as it becomes available;
- bidirectional Dshot, which is the basis for RPM based filtering, has been improved and is now available with BLHeli_32 (from version 32.7 on) and on BLHeli_S hardware (by using the JESC firmware). Use these instructions to get it set up (#8554, #8779);
- as you have come to expect, there is a detailed Tuning Notes for Betaflight 4.1. Use them, or use the new tuning sliders in the Betaflight configurator 10.6.0 to get your craft tuned. Please do not paste tuning configurations from previous versions of the firmware. Some defaults have been changed, and some parameters are used in different ways, so previous tuning settings will not work well with Betaflight 4.1 (#8623, #8736);
- with the introduction of fully configurable VTX control (VTX tables), after flashing the firmware you now have to load a VTX tables appropriate for your VTX and for the country you are flying in before you can control your VTX through Betaflight. Support for loading VTX tables from files will be integrated in the upcoming Betaflight configurator 10.6.0, for now you have to use CLI to set up the VTX tables, see here for details (#7251);
- some optimisations were made to the OSD fonts, and some characters were improved. In order to get a properly working OSD with Betaflight 4.1, the font loaded onto the OSD needs to be updated to the latest version (available in configurator 10.6.0 or newer) (#8390);
- as announced before the release of Betaflight 4.0, support for F3 based flight controllers has been removed from Betaflight 4.1.
Major features:
- new and improved feed forward 2.0 (#8623, #8736);
- reworked bidirectional Dshot (#8554, #8779);
- dynamic idle management using RPM telemetry (#8604);
- fully configurable VTX control with VTX tables (#7251).
Minor features:
- support for the Spektrum SRXL2 serial protocol (#8606);
- support for board-specific custom defaults (#8707);
- support for aribtrary gyro and mag alignment (#8474).
Changes from the previous Release Candidate:
Fixes:
- fixed bug allowing dynamic notch to go into 'high' mode (#8796);
- fixed serial ESC feedback when bitbanged Dshot is enabled (#8828);
- fixed bug causing unused LEDs in an LED_STRIP to become 'stuck' after a configuration change (#8830);
- fixed bug in SPI bus driver code (#8835);
- fixed bug breaking Dshot commands when using bitbanged Dshot (#8839);
- fixed spike suppression in feedforward boost (#8842);
- fixed bitbanged Dshot for Dshot600 (#8843);
- fixed problem with "" as pre-existing manufacturer id (#8848);
- fixed 'sd_info' in CLI showing incorrect information when SD card support is not configured (#8849);
- fixed bug allowing multiple timer allocations with bitbanged Dshot (#8852);
- fixed problems with bitbanged Dshot on F411 targets (#8853);
- added missing labels for dynamic notch to the blackbox header (#8856);
- fixed timer selection on STM32F411 (#8860);
- fixed potential resource conflicts with bitbanged Dshot (#8861);
- fixed problems with feedforward boost on yaw (#8864);
- fixed incorrect timer allocation with bitbanged Dshot (#8865);
- fixed lockups when configuring VTX control port without a VTX table loaded (#8866);
- fixed random activation of VTX pit mode when configuring VTX in configurator (#8869);
- fixed problems with runaway takeoff prevention activating when GPS rescue is active (#8870).
Target Updates:
- added missing MAG support for FURYF4 and FURYF4OSD targets (#8834).
Betaflight 4.1.0 Release Candidate 1
Important
This is a release candidate. It is intended for testing, and some things still need fixing and fine tuning. Please use it with caution and report back any issues at https://github.com/betaflight/betaflight/issues. Thank you.
Important information when upgrading
- A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.6.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.6.0 (or newer) as soon as it is available, or use the CLI for now;
- if you are using the Blackbox Log Viewer, there will be an updated version 3.4.0 to go with Betaflight 4.1 (installation instructions here). Please update as soon as it becomes available;
- with the introduction of fully configurable VTX control (VTX tables), after flashing the firmware you now have to load a VTX tables appropriate for your VTX and for the country you are flying in before you can control your VTX through Betaflight. Support for loading VTX tables from files will be integrated in the upcoming Betaflight configurator 10.6.0, for now you have to use CLI to set up the VTX tables: https://github.com/betaflight/betaflight/wiki/VTX-Tables (#7251);
- some optimisations were made to the OSD fonts, and some characters were improved. In order to get a properly working OSD with Betaflight 4.1, the font loaded onto the OSD needs to be updated to the latest version (available in configurator 10.6.0 or newer) (#8390);
- as announced before the release of Betaflight 4.0, support for F3 based flight controllers has been removed from Betaflight 4.1.
Major features:
- new and improved feed forward 2.0 (#8623, #8736);
- reworked bidirectional Dshot (#8554, #8779);
- dynamic idle management using RPM telemetry (#8604);
- fully configurable VTX control with VTX tables (#7251).
Minor features:
Betaflight 4.0.6
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading from an earlier version of 4.0
- a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
- Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148);
- the format of the CLI
timercommand that is used to configure a timer has been changed. It now uses the alternate function index that is also used in the hardware manufacturer's reference documentation:timer <pin> af<alternate function>. The format that was introduced with Betaflight 4.0.0 that used an arbitrary option number (timer <pin> <option>) is deprecated and will be dropped in Betaflight 4.1 (#8305, #8306, #8320); - unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).
Fixes:
- fixed formatting and help text of
vtxtablein CLI (#8646, #8663); - made SD card report as 'not supported' on targets with no configured SD card slot (#8656);
- fixed the UART pin definitions for STM32F411 (#8659);
- fixed compilation errors if
USE_ABSOLUTE_CONTROLif defined butUSE_ITERM_RELAXis not (#8683); - fixed incorrect reporting of SD card capacity (#8703);
- fixed lockups in FrSky SPI RX when using SmartPort telemetry (#8702);
- fixed lockup when trying to use Dshot with missing DMA assignments (#8705);
- fixed display of date / time when no valid time is set (#8731);
- fixed compilation warning when
USE_TASK_STATISTICSis not defined (#8765, #8782).
Target Updates:
Betaflight 4.0.5
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading from an earlier version of 4.0
- a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
- Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148);
- the format of the CLI
timercommand that is used to configure a timer has been changed. It now uses the alternate function index that is also used in the hardware manufacturer's reference documentation:timer <pin> af<alternate function>. The format that was introduced with Betaflight 4.0.0 that used an arbitrary option number (timer <pin> <option>) is deprecated and will be dropped in Betaflight 4.1 (#8305, #8306, #8320); - unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).
Fixes:
- fixed calibration of the ADC and made (#8427, #8594);
- added enforcement of upper limits for filter frequencies (#8512);
- fixed bind button support for SPI RX (#8543);
- fixed default setting for gyro 2 (#8544);
- fixed potential problem with the detection of SD cards (#8557);
- fixed multiple reset after the reset button was used (#8619).
Target Updates:
Betaflight 4.0.4
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading from an earlier version of 4.0
- a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
- Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148);
- the format of the CLI
timercommand that is used to configure a timer has been changed. It now uses the alternate function index that is also used in the hardware manufacturer's reference documentation:timer <pin> af<alternate function>. The format that was introduced with Betaflight 4.0.0 that used an arbitrary option number (timer <pin> <option>) is deprecated and will be dropped in Betaflight 4.1 (#8305, #8306, #8320); - unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).
Fixes:
- fixed a typo in CLI help (#8365);
- fixed OSD display of negative GPS coordinates (#8374);
- fixed bug in adjustment ranges when failsafe is active (#8386);
- fixed resource display of UARTs in CLI (#8392);
- fixed build error on targets without ESC sensor support (#8403);
- added missing
osd_esc_rpm_freq_posparameter in CLI (#8404); - fixed bug affecting SmartAudio 2.1 (#8438);
- fixed bug affecting the detection of FrSky SPI RX (#8441);
- fixed invalid upper limit for filters (#8475);
- fixed MAX7456 OSD support for Unified Targets (#8504);
- fixed return of MAX7456 detection result over MSP (#8505);
- fixed build for targets without support for Dshot, LED_STRIP, and transponder (#8506).
Target Updates:
- removed unneeded configuration for barometer and compass from target SPRACINGF3NEO (#8332);
- added support for MPU6000 gyroscope to target KAKUTEF7 (#8375);
- added support for RacePIT mini to target FF_RACEPIT (#8387);
- fixed bug in gyroscope configuration and added PINIOBOX defaults to target EXF722DUAL (#8449);
- updated defaults and added PINIOBOX defaults to target CLRACINGF4 (#8463);
- updated the hardware configuration for target CLRACINGF7 (#8479).
Betaflight 4.0.3
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading from an earlier version of 4.0
- a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
- Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148);
- the format of the CLI
timercommand that is used to configure a timer has been changed. It now uses the alternate function index that is also used in the hardware manufacturer's reference documentation:timer <pin> af<alternate function>. The format that was introduced with Betaflight 4.0.0 that used an arbitrary option number (timer <pin> <option>) is deprecated and will be dropped in Betaflight 4.1 (#8305, #8306, #8320); - unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).
Fixes:
- fixed inconsistency in the D_min configuration (#8167);
- fixed USB ID pin support (#8170);
- fixed crash in CMS (#8222);
- fixed flash initialisation (#8238);
- fixed bug causing blackbox header corruption (#8284);
- fixed setting / printing of 32 bit values in CLI (#8302);
- fixed printing of DMA options in CLI 'diff' (#8303);
- changed CLI 'timer' command to use alternate functions (#8305, #8306, #8320);
- removed RTC6705 VTX clock hack (#8322);
- fixed bug affecting copying of profiles (#8331);
- fixed bug corrupting the configuration when setting VTX frequency directly (#8338);
- fixed bug in flash erasing (#8342);
- fixed bug allowing distance for descent to go negative in GPS rescue (#8356).
Target Updates:
- added gyro support for the Viva F4 AIO board to the DALRCF405 target (#8097, #8349);
- added new target MAMBAF722 (#8182);
- removed the FURYF7 target (#8205);
- added new target AIRBOTF7 (#8208, #8328);
- added new target XILOF4 (#8209);
- added new target OMNIBUSF7NANOV7 (#8210);
- removed unneeded pin definition on NUCLEOF722 target (#8220);
- added new target TRANSTECF7 (#8243);
- added new target VGOODRCF4 (#8249);
- added camera control pin to FURYF4 target (#8264);
- added support for multi gyro on OMNIBUSF4NANOV7 target (#8267);
- removed deprecated use of USE_MULTI_GYRO (#8281);
- removed deprecated ACC_x_ALIGN defines (#8287);
- added barometer support to SPRACINGF3NEO target (#8321);
- added barometer, flash, softserial to EXF722DUAL target (#8333);
- fixed barometer support for SPARKY2 target (#8346).
Betaflight 4.0.2
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading from an earlier version of 4.0
- a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
- Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148).
- unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).
Fixes:
- fixed problems when using AND conditions to configure modes (#8130);
- fixed build problem if no barometer is configured (#8133);
- fixed problems with output pins on F3 (#8148);
- fixed freeze when enabling LED_STRIP without a pin defined (#8157);
- fixed incorrect confirmation when changing timer from 'NONE' in CLI (#8165).
Target Updates:
Betaflight 4.0.1
Important
Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug will be included in 4.0.2 (#8148). Until the release of 4.0.2, 4.0.0 should be used on F3 based flight controllers.
Maintenance Release
Please read the Betaflight 4.0 Release Notes.
This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Safety Improvements:
- changed the default filter settings to reduce the risk of flyaways (#8043).
Fixes:
- fixed gyro initialisation for setups with multiple MPU6000 / MPU9250 (#7950);
- lowered the minimum frequency for dynamic notch filters to 60hz (#7984);
- fixed OSD crash when enabling vario display on targets without barometer (#7993);
- fixed excessive return speed with GPS rescue in edge cases (#8007);
- fixed display of failsafe flight mode in OSD (#8010);
- added overflow checking for OSD timers (#8016);
- fixed gyro detection code code for multi gyro setups (#8033);
- added detection for screen overflow in OSD (#8063);
- fixed problem with power level display for SmartAudio in OSD (#8064);
- fixed writing of debug mode into the blackbox log header (#8089);
- fixed problem with timers when using pins with no defined timers (#8093);
- fixed inconsistency in the active gyro configuration (#8102);
- fixed incorrect application of motor output limits when changing profiles (#8108);
- fixed resource configuration for CC2500 based SPI RX (#8120);
- fixed build problems on targets without barometer / magnetometer support (#8121);
- fixed problem with incorrectly reporting barometer / magnetometer as present for targets built without support for them (#8135);
- fixed GPS rescue problem for builds without barometer support (#8136).