Product version: [3.2.0]
SDK version: [3.9.2]
Use of libARController: [YES/] (Only for ARSDK)
SDK platform: [/Android//…]
Reproductible with the official app: [YES//]
So ARMavlinkMissionItem.CreateMavlinkCreatePanoramaMissionItem appears to be broken and it is next to impossible to reverse engineer what Flight Plan is doing because Flight Plan is currently doing it wrong.
Negative values for tilt point the nose down and positive values point it up but in FP (and the resulting mavlink files) the input and results are the exact opposite… and when you try to execute the plan (assuming you provided decent downward angle) the camera gets stuck looking up.
In my own implementations it is very hit or miss. I’m setting the camera angles - for down and + for up and staying within the limits (17 and -83 for the Bebop 2) but the results are very unpredictable.