You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'd like to recommend a feature request that would significantly simplify locating a drone after a crash.
Currently, when disarming, the DVR recording on the goggles/O3 air unit stops almost immediately, assuming automatic recording is enabled when arming.
In critical situations, as we are all accustomed, we almost immediately press disarm, although this is not always due to a loss of video signal - it is often caused by a collision with some object. As a result of such collisions, unpleasant incidents sometimes occur with the detachment of various (unnecessary :-) ) parts from the copter. If the recording stops at the moment of disarming, it is then quite difficult to track the drone's final trajectory and search for these unnecessary elements at the location.
Suggestion - do not send the disarm status to the MSP OSD immediately, but instead implement a timeout of 3 to 5 seconds, or configurable through CLI/Configurator - to save useful recording. This functionality is already implemented in Kiss Ultra and often helps a lot. But Kiss is Kiss, and I would also like to use Betaflight since I love it very much.
What do you think, is this possible?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I'd like to recommend a feature request that would significantly simplify locating a drone after a crash.
Currently, when disarming, the DVR recording on the goggles/O3 air unit stops almost immediately, assuming automatic recording is enabled when arming.
In critical situations, as we are all accustomed, we almost immediately press disarm, although this is not always due to a loss of video signal - it is often caused by a collision with some object. As a result of such collisions, unpleasant incidents sometimes occur with the detachment of various (unnecessary :-) ) parts from the copter. If the recording stops at the moment of disarming, it is then quite difficult to track the drone's final trajectory and search for these unnecessary elements at the location.
Suggestion - do not send the disarm status to the MSP OSD immediately, but instead implement a timeout of 3 to 5 seconds, or configurable through CLI/Configurator - to save useful recording. This functionality is already implemented in Kiss Ultra and often helps a lot. But Kiss is Kiss, and I would also like to use Betaflight since I love it very much.
What do you think, is this possible?
Beta Was this translation helpful? Give feedback.
All reactions