Hi there,

when starting a sphere pano with APAS activated, the panorama wil stop at about 10% (third or fourth picture) and hang. Clicking on stop is the only way to go out of the pano mode.

I thing that should not be the case :-)

Same problem with me also.
No pano photos possible

@dji > Any news on this bug ?

rd73 Posted at 2018-2-13 01:01
@dji > Any news on this bug ?

I don't think this is a bug, APAS is basically a sophisticated obstacle avoidance mode, when shooting pano's you should be in a stationary hover to collect the photos, no need for APAS during the sequence.
Simply turn off the APAS to complete the pano then turn it back on and continue flying.

QuadKid Posted at 2018-2-13 01:10
I don't think this is a bug, APAS is basically a sophisticated obstacle avoidance mode, when shooting pano's you should be in a stationary hover to collect the photos, no need for APAS during the sequence.
Simply turn off the APAS to complete the pano then turn it back on and continue flying.

It is a bug since it stops doing anything forever after having started 3 images.
The bug is easily avoided, thats true.

I have only had this issue during extreme wind with the Mavic Air. Now i do have to import the picture into another app to create the actual sphere though.  I assume that is the same for everyone.  

Just turn APAS off. Do not think this is a bug! Ya dont need APAS for pano's!

yep, but if u fly with APAS (to ge to pano POI), then stop to take shots - as long as drone not moving APAS should not affect doing panoramas...
I think that need of turn it off, and after pano to turn on  just create risk of someone got distracted - forgot to turn it back ON and crash drone... not needet risk IMO really

KREMi Posted at 2018-2-13 07:39
yep, but if u fly with APAS (to ge to pano POI), then stop to take shots - as long as drone not moving APAS should not affect doing panoramas...
I think that need of turn it off, and after pano to turn on  just create risk of someone got distracted - forgot to turn it back ON and crash drone... not needet risk IMO really

Could not have say it better :-) This is no deal breaker for sure, but the fix is easily implemented by DJI.
So, let's do it :-)

it is a bug as before reading this forum thraid i had no idea what was caussing it.. now i know and altough it is easily avoidable...if you know the cause... IT IS A BUG!

It didn't do it before FW update either, so I would say it is a bug and definitely can be corrected by DJI in a future FW update.