Brian-
I realize you already sent these same questions to
[email protected], but since they were posed here as well, I want to post our response so others can see.
Used Orbit around Michigan State Stadium. Experienced quite a bit of frame lag. Was still able to orbit 3 times and different altitude and radius. I'll check the video later.
I assume you left the hardware decoding enabled? What type of iOS device are you using? Does it happen all the time and/or do you have a consistent way to reproduce this? All other users have reported that the frame lag in 2.0 has disappeared in the 2.1 update.
Can I check my mod levels on 2.1?
Most settings like this have to be done in the DJI GO app right now. We are open to adding more things like this in to Autopilot (to be honest camera settings are what people want the most), but for the next few releases we are concentrating on features that are not already in GO as that is what differentiates us from the pack, and there is a workaround in the meantime.
Also as far as weak rc signal. The border turns red?
Not right now. What qualifies as a weak signal? Do you want to be able to configure a percent?
Another issue I was experiencing was being able to see my landing gear over 10mph, only for a few seconds. Maybe a setting, or wind and speed combined? Almost like the camera was not keeping up.
Is this issue unique to Autopilot, or does it happen when flying manually / with DJI GO as well? In the end Autopilot is limited by the hardware limitations of the aircraft and environment conditions, such as wind. You can govern Autopilot by choosing higher values for certain settings like
movement responsiveness, or slower closing speeds in Modes that allow speed input, which will result in less tilt of the aircraft, and thus make it less likely to see the struts. If you are using a Phantom 3, you might want to consider upgrading to the Inspire 1 for the retractable gear.
As for the camera not keeping up, you might want to try a lower value for the
gimbal responsiveness.