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
Some percentage of the time (about %10 of connections), the flight controller isVirtualStickControlModeAvailable result will always be False regardless of whether it is possible to engage virtual stick mode. Under these circumstances, calling enableVirtualStickControlModeWithCompletion will successfully return and virtual stick mode will be enabled. This is frustrating because we attempt to avoid sending lots of useless enableVirtualStickControlModeWithCompletion calls unless there's a chance it will work to minimize system load. Currently we must always try to enable virtual stick mode because otherwise we cannot reliably cause it to engage.
I don't have a specific procedure to reproduce this other than simply connect to the vehicle repeatedly and wait for one of the runs in which it will always return false. The vehicle can stay powered on between instances of this behavior. It appears to happen or not happen every time we open a connection to the vehicle, rather than a one-time occurrence before the first successful time we engage virtual stick mode. We are not doing anything with missions before this behavior it seen.
SDK 3.4.1 and 3.5
Phantom 4 Pro (and Phantom 4)
iOS 9.3.5
iPad Mini 4
Xcode 8.2
The text was updated successfully, but these errors were encountered:
Hi @pquimby, Sorry for the confusion. This interface is used to indicate if the virtualStickControlMode is already enabled or not. We will rename it in the future SDK version.
Some percentage of the time (about %10 of connections), the flight controller
isVirtualStickControlModeAvailable
result will always be False regardless of whether it is possible to engage virtual stick mode. Under these circumstances, callingenableVirtualStickControlModeWithCompletion
will successfully return and virtual stick mode will be enabled. This is frustrating because we attempt to avoid sending lots of uselessenableVirtualStickControlModeWithCompletion
calls unless there's a chance it will work to minimize system load. Currently we must always try to enable virtual stick mode because otherwise we cannot reliably cause it to engage.I don't have a specific procedure to reproduce this other than simply connect to the vehicle repeatedly and wait for one of the runs in which it will always return false. The vehicle can stay powered on between instances of this behavior. It appears to happen or not happen every time we open a connection to the vehicle, rather than a one-time occurrence before the first successful time we engage virtual stick mode. We are not doing anything with missions before this behavior it seen.
SDK 3.4.1 and 3.5
Phantom 4 Pro (and Phantom 4)
iOS 9.3.5
iPad Mini 4
Xcode 8.2
The text was updated successfully, but these errors were encountered: