DJI says support is coming but they haven't given us a date.Any news concerning the I1 Pro with X5?
We have noticed that happen sometimes. If you rotate the phone to portrait and back to landscape it usually wakes it up.In a recent use (beta) I had no camera view at all (blank screen). Any ideas?
What mode are you wanting to operate in? Are you over water? What if the ground isn't level?Can you please allow for lower floor? I'd like to use some of the modes at 5ft. Yes, I realize the risk but should be allowed to acknowledge and take that risk
DJI says support is coming but they haven't given us a date.
We have noticed that happen sometimes. If you rotate the phone to portrait and back to landscape it usually wakes it up.
What mode are you wanting to operate in? Are you over water? What if the ground isn't level?
I find it difficult to move things as well. I can however do it with some patience. Make sure you select it first by tapping on it, then an info bubble will come up, then you can press and hold and drag.Installed Autopilot for dji beta via tesflight version 2.2 build 52.
unable to select objects to move them in place in any mode on the maps
The minimum altitude was originally chosen when using the GPS altitude reference was the only option. Because the GPS sensor has a notoriously bad vertical accuracy (+/- 3m in the best scenarios but often worse), we chose to put the minimum altitude at 4m. I could be convinced to relax the restriction, as long as the GPS altitude reference is not in use - would that be an acceptable compromise?I mean, please give the user some responsibility - not all of us are idiots that need hand holding to avoid crashing our aircraft... make the option available only in advance/expert mode..
We chose to require marker selection before dragging for safety (don't want to accidentally drag) and to handle marker collision. For example, if the Focus Subject is the operator, and the Home location is also the operator, then the markers collide and if you want to move the one on the bottom, you have to tap multiple times to get it selected, at which point it becomes draggable. We are considering making an option to use "large markers" which will make it easier to select them, but waste more screen space and make it harder to tell the exact point the marker is at. Thoughts?I find it difficult to move things as well. I can however do it with some patience. Make sure you select it first by tapping on it, then an info bubble will come up, then you can press and hold and drag.
I find it hard to manipulate the markers esp with cold fingers and bird in the air using up valuable battery. Yes an option for larger would be great for me. Regarding accuracy, why not use a google maps style marker with a large bubble coming to a point at the bottom. Everyone recognizes this method and even more accurate than what we have now.We chose to require marker selection before dragging for safety (don't want to accidentally drag) and to handle marker collision. For example, if the Focus Subject is the operator, and the Home location is also the operator, then the markers collide and if you want to move the one on the bottom, you have to tap multiple times to get it selected, at which point it becomes draggable. We are considering making an option to use "large markers" which will make it easier to select them, but waste more screen space and make it harder to tell the exact point the marker is at. Thoughts?
We chose to require marker selection before dragging for safety (don't want to accidentally drag) and to handle marker collision. For example, if the Focus Subject is the operator, and the Home location is also the operator, then the markers collide and if you want to move the one on the bottom, you have to tap multiple times to get it selected, at which point it becomes draggable. We are considering making an option to use "large markers" which will make it easier to select them, but waste more screen space and make it harder to tell the exact point the marker is at. Thoughts?
The minimum altitude was originally chosen when using the GPS altitude reference was the only option. Because the GPS sensor has a notoriously bad vertical accuracy (+/- 3m in the best scenarios but often worse), we chose to put the minimum altitude at 4m. I could be convinced to relax the restriction, as long as the GPS altitude reference is not in use - would that be an acceptable compromise?
Did build 53 correct this for you?I find it hard to manipulate the markers esp with cold fingers and bird in the air using up valuable battery. Yes an option for larger would be great for me. Regarding accuracy, why not use a google maps style marker with a large bubble coming to a point at the bottom. Everyone recognizes this method and even more accurate than what we have now.
Build 54 has direct coordinate input now.Is it possible(or if not, make it possible) if i get a spesial longitude/lattitude from an architect to be used as an background picture to set this up in app and fly to that spot, take the photos/vids.s
Even though the minimum altitude is 4m, the best it will do is 4 + 1 because it needs some buffer space due to the inaccuracy of the altimeter (otherwise it would just keep bouncing up an down indefinitely). We are strongly considering allowing minimum altitudes down to 1m (very not recommended), as long as you are willing to not use the GPS altimeter reference (i.e. it just won't let you continue if you try).In the settings the minimum altitude is set at 16' and also set it in Cruise, but it simply won't stay there.
Larger markers are perfect. My only difficulty now is that when dragging the marker, the point of the marker is directly under my finger. Is there any way to make the marker snap a little lower while dragging so that the point can be seen (to facilitate precise placement)?Did build 53 correct this for you?
Did build 53 correct this for you?
Build 54 has direct coordinate input now.
Even though the minimum altitude is 4m, the best it will do is 4 + 1 because it needs some buffer space due to the inaccuracy of the altimeter (otherwise it would just keep bouncing up an down indefinitely). We are strongly considering allowing minimum altitudes down to 1m (very not recommended), as long as you are willing to not use the GPS altimeter reference (i.e. it just won't let you continue if you try).
Yes I prefer to be able to go lower as well. I think people need to be aware of their AC and the settings and you cant always babysit everyonethat sounds reasonable - for many of the times when I'm using a lower flight altitude, I'm stationary and will likely use the takeoff fixed altitude.
Did build 53 correct this for you?
We are strongly considering allowing minimum altitudes down to 1m (very not recommended), as long as you are willing to not use the GPS altimeter reference (i.e. it just won't let you continue if you try).
Ok heres another idea to throw out there. For Orbit, how about a "Degrees" setting which would open the orbit circle so then we could only fly a semi circle and maybe as soon as the orbit is anything less than 360 degrees the AC just gets to one end and the goes back to the other end. This would also facilitate people setting the orbit to 359 degrees which would still give you a full circle but the AC would go back and forth instead of in a circle.
We use essential cookies to make this site work, and optional cookies to enhance your experience.