DShot1200 is officially removed from Betaflight 4.1:
1. Dshot1200 is only needed for 32khz looptime, and 32khz looptime isn't supported any more in Betaflight. The highest looptime in Betaflight (in BF4.1) is 8KHz, and Dshot600 is enough for 8khz looptime
2. Dshot1200 was not stable when used with bidirectional DShot which is required for RPM filter, which has a higher priority than DShot1200

Just thought I should point that out in case someone is looking for the missing DShot1200 in the configurator.

For other changes in Betaflight 4.1, here are the change logs: https://github.com/betaflight/betaflight/releases

I don't use RC versions of firmware but when the final 4.1 version drops I guess I'll have to shift down to DSHOT600.

I'm only using DSHOT1200 with my ESCs because I can. Hopefully I won't notice any difference if I have to switch to DSHOT600.

(28-Sep-2019, 04:24 PM)SnowLeopardFPV Wrote: I don't use RC versions of firmware but when the final 4.1 version drops I guess I'll have to shift down to DSHOT600.

I'm only using DSHOT1200 with my ESCs because I can. Hopefully I won't notice any difference if I have to switch to DSHOT600.

This is an interesting evolution. I was about to re-tune 2 of my quads, was just waiting for 4.1 to come out. Thing is, when I tune I normally turn off most of the filters, run 32/32 and d-shot 1200, I'm now wondering if i'd be better off just going back to 3.5.7 and dialling it in.. There isn't really a reason for me to run the new versions feature wise, hmmmmmm.

(28-Sep-2019, 04:24 PM)SnowLeopardFPV Wrote: I don't use RC versions of firmware but when the final 4.1 version drops I guess I'll have to shift down to DSHOT600.

I'm only using DSHOT1200 with my ESCs because I can. Hopefully I won't notice any difference if I have to switch to DSHOT600.

Same. I figured that higher number == better, but I have no idea if I could tell the difference.

The other knock-on effect is that I now don't really care about BLHeli32. As far as I can tell, the only feature I was using was DSHOT1200, soooo ...

(30-Sep-2019, 08:25 AM)Banelle Wrote: The other knock-on effect is that I now don't really care about BLHeli32. As far as I can tell, the only feature I was using was DSHOT1200, soooo ...

You'll also miss the custom startup tunz as well 

My startup tone is different and I'm running DSHOT600 with JESC firmware
I believe there was a UAVTech video regarding that subject and why it made no sense in continuing the development of 32/32 clock speeds.

BF 3.5.7 for the win!

Yeah I second that, especially on small (3" or less) quads....

how does the faster looptime can cause to much noise? the last information about softmounting let me beleive it could probably be less important than in the past. with all the new filter options... is it still possible to get to much noise with a softmounted copter to make it „allmost impossible to tune“?
i like to play with the looptime at builds where i beleive are possible flyperformence increasments, but i like to hear general impressions about bf4.1 and „fast looptime vibrations“
https://oscarliang.com/best-looptime-flight-controller/
„Faster Looptime In Practice – Noise

Most experienced pilots would agree that higher looptime and a faster ESC protocol can make a significant difference to flight performance. Just think about the days back when we were running 1KHz looptime with Oneshot125, compared to the 8KHz and even 32KHz that is now possible with DShot.

By making looptime faster, you are now also open to a broader spectrum of noise frequency. This broader noise spectrum can manifest as, what is known as “D-Term” oscillation in blackbox data. D-Term oscillation can make your quad harder to tune as well as causing excessive heat in your motors.

Some quadcopters actually run better at slower looptime because a faster looptime generates so much vibration, it is almost impossible to tune out. Therefore, running faster looptime can require additional filtering, that will eat up any latency advantage. Even then there can be some noise issues that the increased filtering can’t handle.

Gyro running a 32KHz sampling rate can be susceptible to noise, a good example would be flight controllers like the Raceflight Revolt which requires soft-mounting.“