Forgot to mention the other obvious choice: fly the aircraft to the desired altitude before tapping Set Point B.If you really want to you Zip Line, your choices are
Forgot to mention the other obvious choice: fly the aircraft to the desired altitude before tapping Set Point B.If you really want to you Zip Line, your choices are
This might be exactly what I'm looking for. I'll give it a try.If you are trying to place two points right on top of each other to execute a vertical boom, you might consider using Waypoint Mode with a Vertical Waypoint action instead.
If you really want to you Zip Line, your choices are to just move the Point B marker by dragging it on the map (so as to not alter the altitude), or use the Set Point B button, realizing that you will then have to adjust the altitude after it records the aircraft position.
Shouldn't setting a point also set altitude?
Sent from my iPhone using Tapatalk
Not sure I understand this. When you tap Set Point A|B, yes, it registers both location and the altitude of the aircraft for that point. If the altitude of the aircraft is below the min altitude setting, it will bound it.You would think so but I guess if you don't actually fly to the point it doesn't register.
Not sure I understand this. When you tap Set Point A|B, yes, it registers both location and the altitude of the aircraft for that point. If the altitude of the aircraft is below the min altitude setting, it will bound it.
It reverts back to 20 ft because tapping Set Point B records both the location and the altitude. This was explained in the first response. Adjusting the slider by itself won't work because you need to record the location, otherwise point B will stay wherever it currently is. You either need to drag point B on the Map on top of A, or fly the aircraft to the desired altitude before tapping set point B.Problem was; Point B altitude would not register the 120ft, it would revert back to 20ft. The "location" of Point A didn't change, I only wanted to change the altitude and label it as Point B (to create my vertical zip line) but I wasn't able to do that. Now of course I could (in theory) raise the AC to the desired altitude and then hit Set Point B however that would be no different than just adjusting the altitude slider in the app; you would think.
This is behaving exactly as designed. Per the discussion in flight school on the intro to Zip Line:Bird starts at point A on 20m height and launches to point B. The bird reaches very quickly point B but hasn't the correct height so it climbes ~20m while on position. Same behaviour on the way back, it starts at Point B ~150m and flies back to A, was to quick on the spot and descents the last ~10-15m
As you talk about the zip line, i made some tests with it and noticed something strange.
Point A: 20m
Point B: 400m away, 150m
Bird starts at point A on 20m height and launches to point B. The bird reaches very quickly point B but hasn't the correct height so it climbes ~20m while on position. Same behaviour on the way back, it starts at Point B ~150m and flies back to A, was to quick on the spot and descents the last ~10-15m.
You can see the whole thing at (from 0:00 to ~1:23)
PS: as i saw it after i almost wrote the post, this thread is about the BETA but i'm using the lastest official IOS version. If you think this post should not be posted here, please delete, it was not my intention to highjack the discussion..
Chris
This is behaving exactly as designed. Per the discussion in flight school on the intro to Zip Line:
If Point A and Point B are at different altitudes, Autopilot will attempt to follow a straight line in three dimensions within the limitation of the max vertical speed of the aircraft. If the horizontal and vertical distance between the points does not allow a completely straight line, Autopilot will finish the vertical movement when it reaches the target Point.
It reverts back to 20 ft because tapping Set Point B records both the location and the altitude. This was explained in the first response. Adjusting the slider by itself won't work because you need to record the location, otherwise point B will stay wherever it currently is. You either need to drag point B on the Map on top of A, or fly the aircraft to the desired altitude before tapping set point B.
This is behaving exactly as designed. Per the discussion in flight school on the intro to Zip Line:
If Point A and Point B are at different altitudes, Autopilot will attempt to follow a straight line in three dimensions within the limitation of the max vertical speed of the aircraft. If the horizontal and vertical distance between the points does not allow a completely straight line, Autopilot will finish the vertical movement when it reaches the target Point.
I would add to this question: Instead of making a final altitude adjustment at the end, why doesn't zip line slow the speed between the two points so that it does not need to make this final altitude adjustment?May I ask if there is an indication (for planning sake) of how much distance is covered between raises in altitude are applied? For instance if I wanted to travel 150m (zipline A to B) and increase my altitude along the zipline from 10m to 60m. How can I know if 150m is enough time complete the altitude adjustment smoothly at say 8.1mph or it is kind of the luck of the draw?
There is no indication right now, but you could manually compute it by checking the performance specs of your aircraft (max ascent / descent rate) if it was very critical. Granted, it would be nice if it had a warning, but this doesn't exist right now.May I ask if there is an indication (for planning sake) of how much distance is covered between raises in altitude are applied? For instance if I wanted to travel 150m (zipline A to B) and increase my altitude along the zipline from 10m to 60m. How can I know if 150m is enough distance to complete the altitude adjustment smoothly at say 8.1mph or it is kind of the luck of the draw?
No reason, other than it requires more code and it isn't a top priority relative to the rest of the features on the roadmap given the way most people use Zip Line (i.e. it never gets close to the max vertical speed limit).Instead of making a final altitude adjustment at the end, why doesn't zip line slow the speed between the two points so that it does not need to make this final altitude adjustment?
At this point it is probably better to continue the support discussion over email: [email protected]. Briefly: when using Waypoint Mode you should consider using a Vertical Waypoint Action.Can you tell me what I'm doing incorrectly?
Hello,
Today I just need a little help from pro users.
I planned a Waypoint flight at home to save time on the location.
Once there I knew that I need to adjust the heights to be used properly. Now my question:
How do you fix the correct heights for the waypoints and focus triggers whilst flying the first time your path?
Thanks
Patou
Thanks DodgeP, but no...that's not exactly what I want to know.Hit the folder button and save flight, it will ask If you want to update current flight mission.
(at least I think that's what you're asking)
Or tap the first waypoint, a small box will say tap again to edit, edit the altitude, hit next and do it for all the waypoints that need adjustment and then save/update mission.
Thanks DodgeP, but no...that's not exactly what I want to know.
Imagine you fly uphill for about 2 miles and you want to follow the relief at maybe 30 feets AGL with the pre planned waypoints. You need to adjust and record the heights instantly all the time.
Or say it like that:
I like to launch the waypoint flight and adjust the height with the left joystick and hit the C1button to record every single waypoint.
Sorry for my lack of English but I hope you will understand...
We use essential cookies to make this site work, and optional cookies to enhance your experience.