Lucia Nightfire commented at 2020-04-09T12:56:49Z, updated at 2020-04-09T14:58:42Z

I am seeing this behavior on regions with server version 2020-03-30T23:37:53.539435, but not on the latest server version 2020-04-03T19:49:49.539684.

[EDIT] NVM, also seeing it on 2020-04-03T19:49:49.539684 too.

Also seeing this on 2020-03-20T18:40:52.538914 but only when I tp into the region with an altitude close to that of the landing point.

[EDIT] NVM, that behavior is not 100% either.

I think this depends on one of more conditions that I'm not fully aware of ATM.

It "seems" landing points near the ground are ignored while those at high altitude are honored. This could also change with more investigation.

Maestro Linden commented at 2020-04-09T16:38:54Z

Hi Logan, thanks for the report. To be clear, for those example locations, are you trying to TP to http://maps.secondlife.com/secondlife/Lori/48/102/1796 actually arriving at those exact coordinates, rather than the parcel's landing point (which is a few meters away, at <53, 104, 1796>)?

I see that other example, http://maps.secondlife.com/secondlife/The%20Amaretto%20Community/59/227/35 , is definitely more dramatic - a regular (no special estate or parcel privileges) user ends up at the SLURL position, when the landing point is set to <6, 209, 21>.

Both parcels are configured to route visitors to the landing point, so something definitely appears to be wrong.

loganpryor commented at 2020-04-09T16:54:41Z, updated at 2020-04-09T17:06:17Z

Maestro, yes. those are the locations i've landmarked. That's why I noticed the different landing point (so used to the routed landing point, bit disorientating at first landing somewhere else)

[EDIT] I also saw this behaviour on 538907 (rolled out to RC March 25th), but didn't realise it was a problem until the rollback which re-enabled the fixed landing point. - I had assumed owner was allowing landing anywhere.

Maestro Linden commented at 2020-04-09T17:10:08Z

Thanks for the follow-up!