Facade Video Mavic Air 2
I'm on version 3.0.0 (174) | Kernel 3.0.0 and have had troubles with facade flights going too far off range while taking video & photos on my Mavic Air 2. Is anyone else experiencing this? Am I missing a setting adjustment?
Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
7 comments
Are you saying it was working well before and now it is not with 3.0.0?
I am curious what your recreational use case is for Facade scanning.
So previous versions never added this extra height (trying to capture a screenshot of it), at the end of the first horizontal run on a facade-based path, which causes it to error out the mission. I have tried this with both the Mavic Air 2 (48 MP) and Mavic Air 2 cameras, also with photo and video options, with similar inconsistent results. Does this make sense?
I have a hobby love for old craftsmanship and have found flying facades to be some of the best ways to turn photogrammetry into 3D printable models for my display (dork mode activated).
Are the collision sensors activating and not allowing the drone to move?
No collisions in the area (all very open space) in my tests.
I was able to capture the path in the act. Attached (below?) should be 3 screenshots. 2 of them are from when I was flying (you can see the spikes @ the ends of the flight extents). The 3rd is the unmodified preview from the web app showing path.
Here's a quick snag of my settings
The .kmz export to Google Earth also aligns with the preview and expected flight path (for what it's worth).
I tried flying your mission but I was not able to reproduce what was in your screenshots with the spikes. Have you tried using a more modern device (iPhone 8 is old...)?
Please sign in to leave a comment.