When executing an auto take off, let the drone ascend to what ever height "IT Wants to go" and it will stop automatically. Let it sit there for about 5 seconds.
My Mavic Air would ascend to 16 feet then stop to capture Precision Landing data. My
Mavic 2 Pro ascends to 4 feet then stops to capture Precision Landing data. There is a message that pops up telling you what height your drone will ascend to and stop. WHERE EVER it stops when using auto take off is the height YOUR drone needs to record Precision Landing data.
I've tested the 5 second rule (My Rule) and when I auto ascend to XX feet and then immediately fly off the drone seldom returns to the (near) exact landing pad location (usually within 10 feet though). BUT when I let auto take off and hover (at what ever height it wants to) and let it hover there for several seconds, the drone will (almost) always land back on my orange/blue landing pad from which it departed when I use the Return To Home button.
If you do the same 5 second hover in low light conditions (like flying to capture a sunset), the sensors have a hard time matching up with the precision landing data upon returning that it recorded at time of take off (because its getting darker quickly) and the drone will have to depend solely on GPS recoded at take off for a landing location. Sometime it will hit the landing pad, sometimes it will not. Your good for about 6 to 10 feet accuracy in that case. So, Yes it does record its Precision Data at auto take off if you give it time to do so.
Upon return to home, GPS gets the drone close to landing sight and then it switches into Precision Landing mode to match the current scenery of the ground with what it recorded on take off.
In the .txt files these messages appear:
-- APP_TIP_tip message issued: Aircraft is returning to the Home Point. Minimum RTH Altitude is196ft. You can reset the RTH Altitude in Remote Controller Settings after cancelling RTH.
-- APP_TIP_tip message issued: Aircraft close to Home Point. "go home" shifts to "landing"
-- APP_TIP_tip message issued: Precision Landing__Locating Landing Point
*** "Your results may vary" LOL, had to toss that in there....