
| Key: |
SVC-221
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
Solomon Canning
|
| Votes: |
12
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
llSetPos() can move an object around, but one generally has to wrap it with some checks to be sure that this object is welcome at the proposed destination. This mostly works well, except at a sim boundary. llSetPos() lets you move an object a little bit into the next sim by setting the position x or y cooridinate outside of [0,256). But llGetParcelFlags, llScriptDanger, and even llGetLandOwnerAt all simply return information for the parcel nearest the border, but still inside the current sim.
For example, an object at <71, 250, 70> returns the same information for its own position as for <71, 257, 70>. I would expect it to return the correct information for the <71, 1, 70> parcel in the next region to the north.
If this "peeking" into the next sim was limited to 10m from the object, that would be acceptable, since that's all that llSetPos() will move anyway.
|
|
Description
|
llSetPos() can move an object around, but one generally has to wrap it with some checks to be sure that this object is welcome at the proposed destination. This mostly works well, except at a sim boundary. llSetPos() lets you move an object a little bit into the next sim by setting the position x or y cooridinate outside of [0,256). But llGetParcelFlags, llScriptDanger, and even llGetLandOwnerAt all simply return information for the parcel nearest the border, but still inside the current sim.
For example, an object at <71, 250, 70> returns the same information for its own position as for <71, 257, 70>. I would expect it to return the correct information for the <71, 1, 70> parcel in the next region to the north.
If this "peeking" into the next sim was limited to 10m from the object, that would be acceptable, since that's all that llSetPos() will move anyway. |
Show » |
|