I was just about to write this

I'm having same issue. Did u find a fix besides going back

@@charlesc7020 Im surprised almost no one is talking about it. But turn on Bi-directional Dshot and it works. if you have a 8Bit BLHeli-S esc flash it with blue jay and then you'll also have bi-directional DSHOT

Model Match: kzfaq.info/get/bejne/ablmmLiIqNfahY0.html

Interesting observation

If you want GPS Rescue failsafe then a future video will cover that. It needs to be configured properly. Otherwise, the default failsafe settings are correct.

@@JoshuaBardwell understood. Yes, was interested in the improvements in gps rescue behavior and any changes in the failsafe tab that we should know about, if any.

It would depend on the FC used and how you have it wired up. In my case I use the same IFlight_Blitz_722 on my Nazgul5 V2. Have the receiver on UART2 and GPS on UART4, so my Ports tab looks like this: USB VCP Configuration/MSP checked 115200 UART1 Configuration/MSP checked 115200, Peripherals VTX(MSP+D)AUTO UART2 Serial Rx Checked UART4 Sensor Input GPS 57600 UART6 Sensor Input ESC AUTO

I would refer to Chris Rosser's pid tuning guide.

@@JoshuaBardwell thx

@@JoshuaBardwellhow many vista can connect with dji intgra?

All of them. I don't now that there is any upper limit.

That is not recommended when going between major versions (e.g. 4.3 to 4.4 to 4.5). It can carry over incorrect settings from previous versions.

10.10 is backwards compatible with recent versions at least as far back as 4.0.

@@JoshuaBardwell I will try 10.10 today then! I bought a BNF with a gps and it came with 4.5 on it and I just haven't been using for fear of having to switch everything else.

Yes it does. Carbon fiber FPV drones, generally speaking, are much more durable than plastic ones. I personally smashed to pieces, no less than 2 DJI FPV Potatoes when I was first learning to fly. In contrast, I've now built 13 "real" FPV drones and have only broken 2 arms, a top plate, and a bottom plate. Not all on the same quad, either. They were easily fixed and are all in flyable condition today.

@@William_NS do u know any cheap builds i can do/get? Ive no idea how to build one but got the dji fpv kit so glasses + controller and dead fpv drone lol

I own the iFlight Chimera7 Pro and a front arm and rear arm broke after the motors unsynced at full throttle. So then I had to buy a front arm pair and a rear arm pair to fix it. It only dropped about 20m into tall grass so I was surprised that it was SO mangled ! The DJI FVP is like flying an Apple Phone lol :D :D

To flash yes.

Yup

I think it's a precaution because I think a lot of people would just restore the backup after update and not realize some items will have failed. The other concern is that the functionality of a setting might have changed and even changing it to the value from the previous version might not be the correct value. For example (and this is only an example and not a real world issue, it only illustrates my point) A few versions back Betaflight changed the way it measures CPU Utilization and the display % changed on average. If you had a setting that would trigger something to happen at 60% utilization (because 60% was more like 90%), but now 60% is no longer considered high and would be wrong. 0-100% is still a valid setting but you would need to set the value to 90% in the new version but the config would have set it to 60. Hope that makes sense and this is only speculative on my part.

This may seem to work fine, and it may work fine sometimes. But for example, some defaults about the PIDs may have changed in the new version, and copying the diff in may overwrite those defaults with new values that are not appropriate. It's a risk, and it's not recommended.

@@CantFly_FPV this complexity to the layman will forever limit the growth on fpv into the normies worlds.

There was one for BF 4.3 but it's no longer up to date.

@@JoshuaBardwell That's a shame, this online tool made it really easy to update. It would be really cool if BF had a built-in tool to update and apply your old config.

(good plan for me to ask You to ask Betaflight... ;))

Some of us devs are here reading the comments for suggestions already 😅 We're aware of the issues some people are having with older saves, JB doesn't need to remind us. There's a lot that can go wrong when automatically converting old values to something that was changed. Not everything may translate directly, some things have been added, some have been removed entirely. Commenting/removing incorrect lines is the safest approach, as that value will now fall back to the default which is good for almost every build. The more involved settings that come with some new features require full setup either way. What I personally do is to keep backups of mostly constant settings - Actual rates, OSD elements and layout, RX config, modes, etc... . Those are then loaded with no issue, and I can set up the few remaining things myself if need be

@@Vitroid First: Great that you read this and thanks for the great work you do. Still: couldn't there be a process that auto-"translates" stuff that is save (you're the ones who know what is) and either put to default new settings what is not safe or ask the user about unsafe stuff "do you really" with for example check boxes? What JB does here is of course a great help but I'd love to keep my settings say on a BNF. My Nazgul for example is still on 4.3 because "the boss doesn't like 4.4" (as they told me in a mail) and they don't publish a CLI dump. As I have no idea what iFlight did in their build I hesitate to just put the defaults on. I'll update my own build once the final release of 4.5 drops as I didn't tune anything...

@@seb-depp iFlight is one of the biggest BNF manufacturers, they get a ton of support requests, and those support requests mostly consist of people messing up their configuration from flashing. They are very insistent on keeping users on whatever the factory default is as is visible from some of the support articles 🤣 Some of what you described already happens: 4.3 tunes can be more or less kept for 4.5, some settings have changed, but since they fall back to defaults, it's more or less fine. If you don't transfer over the tune, you can apply one of many available presets. I am a big fan of that new system, you'll find a tune for basically anything. 5" quads will fly pretty well even on defaults, with presets you can probably get within 10 or 5% of the iflight tune, if not basically the same. Renamed commands fail by principle, and invalid properties are ignored in favor of defaults. When errors are found, it will prevent saving, highlight everything that's incorrect, and prompt the user either to remove them, or continue the save regardless. Conversion tools have been discussed many times, but have been deemed unnecessary given the resources available to touch up anything that was missed. Maybe iFlight will make up to date presets for 4.5, the GPS upgrades will probably pull enough people over for them to consider it worth their time

​​@@Vitroidthank you for reply!!! Yeah, this sounds reasonably... And follows with a question - does it mean that just 'force save' after pick up old config with errors - would\should usually just work?..