I updated my Ipad to DD 3.8 and found that the Auto Flight Modes and other Precesion House modes do not work at all. You can click the button but the map will not update and you can not plan. My Iphone X was using DD 3.7 and working fine. I updated it to 3.8 and now it too will not allow for flight planning. Now I am stuck using my PC to plan my flights while this problem is going on. Any solutions? I talked to Adam at support.
He sent me a message before sign off but I tired it today and it still does not work
Bugger, mine too. Seems my iPad auto-updated - was on 3.7.0 a couple of days ago and working fine. Hope this gets sorted very quickly. Supposed to be flying in 2-3 days and no idea how to downgrade or if it’s even possible. Only have iOS for DD and no idea how to use it really.
It seems like GCP’s are not working right now either…
Hi James, It’s too late in this case. But for future reference…
Turn off auto updates (obvious)
Before updating the app, make a backup of your iPad to your pc via the iTunes app.
Then, if you update and the app has issues, you simply restore the backup and you have the old version.
Android is easier with this kind of thing. But as we all know, ios devices seem to function better with dji gear.
Thanks for this. I actually thought the updates were turned off, only that seem to be the case.
Android I know back to front in terms of apks and the ability to install them manually, but iOS I know nothing. I have just about got to grips with the operating system on a day to day basis but in terms of side loading, not a clue.
You’ve just reminded me however. I only received my iPad back from Apple’s repair centre a couple of weeks ago and so do as it happens have a system backup of it dated a month old. I’d rather not backdate it by a month but if I have to in order to fly the mission this week then so be it. Cheers.
Great. At least that will reduce the stress related to that upcoming mission.
I just did two GCP missions Friday and another 3 this morning. I’ll update once I tag them.
Hi guys! If you can please email firstname.lastname@example.org with these issue reports, we’ll investigate them all. It sounds like we may have bug here - we’d like to get it fixed ASAP. Thank you.
Found today that if I select ‘Crosshatch’ on the desktop before I leave the office, it does still appear as a Crosshatch on the iPad. Only if I try to create a crosshatch through the app does it fail. Fingers crossed tomorrow the missionary stored as a crosshatch flys as one. And best hope I don’t need to make any tweaks whilst out in the field.
As it happens after connecting the drone to the app, the planned route changed and so it did require the the configuration to be amended. I was thankfully able to make the adjustments in the app without a problem so it seems the only problem the app has with regards to the Auto Flight Modes is that the buttons themselves don’t work.
The only setting I can see that is not accessible without clicking ‘Crosshatch’ again is the angle the gimbal is set at. Annoyingly, if there the gimbal angle needs to be displayed (for checking) within either the app or on the desktop, you have to select Crosshatch again which then that resets all of the Advanced settings previously set - although in the app right now it just reverts to Ortho.
All 3 of my missions tagged properly and I am in process of doing two more now.
As of 10 minutes ago, I am no longer able to select ‘Crosshatch’ using a PC. It behaves the same as the app now, in that a grid flashes up on the screen when Crosshatch is selected before instantly disappearing, leaving Crosshatch selected but only one direction of flight lines shown.
And now all is well on the PC. Opened it back up having added it in Android and I can turn Crosshatch on and off freely on the PC.
I just used crosshatch on an iPad. Please upgrade to 3.9.0.
I think the Pad’s on 3.9.0. It was the PC that I was having difficulty with today.
Heck, I tried using our Matrice 210 for the first time with DD (it had been away for warranty work) and I had one heck of a time getting it to connect.
Once I did, even though it recognized my location, it kept throwing my default location as the San Francisco Bay Area. I would then have to go and find myself (in Idaho) and try to work around the UI as the keyboard didn’t want to close after entering the name of my project.
Meh, maybe it was a hiccup.
San Francisco Bay Area is the Headquarters for DD, lol.
As for not finding you in Idaho, something was wrong with your GPS on your computer/phone/tablet. By default DD will get your location based off your GPS location that is supplied by what your connect to. I guess if it had a issue it defaulted back to there. Maybe @Adam_Carp can shed some light on the subject.