I just watched the first 30-40 mins of the live stream.

Yes, GPS Rescue will require an FC but I can see the potential on crippled FC's and AIOs with only 1.5 UARTS not needing a full UART for GPS. It will not help fly the quad back home but at the least we have coordinates from telemetry which can be useful to find the quad/plane.

The first post of this thread has now been updated with release notes for the new 6.19 firmware version that was officially released to the public a few days ago.

Makes me sad that encryption will not co-exist with multi-bind.

How could it possibly work? They are polar opposites of each other.

Encryption across multiple different quads (that you own) shouldn't be hard if you use certs. I wonder what system they use that doesn't require certs. Probably some Whatsapp level E2E. But technically if you use a PKE system it shouldn't be that hard to create a secure tunnel that would still work across multiple owned quads, since each would use the same public/private keys. If you are talking multiple unique keys, then yes it wouldn't work seamlessly, but being able to handle multiple certs/keys from the radio shouldn't be all that hard (it's just a text file).

It could be greatly improved if the cpu chips (quad, radio, goggles) had some sort of on board crypto, which i believe they don't currently. At least AES 128/256 at the hardware level would make using crypto less of a ball ache.

Why turn on encryption on a hobby drone?

We can do more damage with a simple RF signal jammer.

That's also kind of my point. Encrypted telemetry could be sent over an encrypted tunnel or just encrypted on the fly and sent back to the radio and decrypted using a keyphrase. It doesn't have to be military grade, even something simple like RC5 or DES would suffice. We aren't trying to stop state level hacking here. As long as it's fast and uses very little resources, it would be enough.

Anyway I honestly don't see why anyone would need encryption on a quad, not full blown anyway. if it's about making it hard to hijack a quad, a hashed binding phrase would suffice. But then you could just use a signal jammer as you mentioned, Kafie.

I think its all about adding in new functionality, regardless of whether anyone has any real world use for it or not. Like, lets add encryption so it sounds like our product is cool and modern and we can hype it up (and charge more). But in the real world everyone is like but why, what use do we really have for this?

We finally have new Crossfire / Tracer firmware from TBS nearly 18 months after the V6.19 firmware was released  Firmware V6.26 and V6.27 were released earlier this month. The release notes for those two versions have been added to the first post of this thread.

Firmware release V6.27 appears to have been pulled which I guess was due to some reported issues and it was re-released (I assume with any relevant fixes in) as firmware V6.31. Release notes for V6.31 seem to be exactly the same as for V6.27 with no information about what the issues actually were or what was fixed to correct them. Details for the new V6.31 firmware release have been added to the first post in this thread.

For anyone who is running a full size Crossfire TX or a Sixty9, TBS added some fixes to the latest V6.33 firmware version that was released 3 weeks ago. Details are in the first post of this thread.