Difference between revisions of "Parcel encroachment"

From Second Life Wiki
Jump to navigation Jump to search
Line 1: Line 1:
;Encroachment
;Encroachment
:When an object's position is on one parcel, but part of it extends into another neighboring parcel, often against the wishes of the owner of that other parcel.
:When an object's position is on one parcel of land but part of it extends into a neighboring parcel, often against the wishes of the neighbor.


The problem is that residents can place objects such that they are on their own parcels but invade the space of their neighbor's.
The problem is that residents can place objects such that they are on their own parcels but invade the space of their neighbor's.
The neighbor has no capability of moving or returning the object and must appeal to a higher power such as an Estate Manager or Linden Support.
In January 2011 a partial solution was deployed.  Estate owners can now enable a feature that allows people to manually return objects that encroach upon their parcels.


The solution is to allow parcel owners to select and return any objects that encroach upon their parcel.
==How it works==
First of all the returnability of encroaching objects must be enabled on a per-region basis.
See the '''How To Enable''' section for information on how do do this.


Testing whether an object overlaps a parcel is done by building a collision body for each parcel and using the physics engine to make a collision query between the object and the parcels.
When someone tries to return an object the server will first check the normal object and parcel permissions and if those fail it will then build a collision body in the physics engine for nearby parcels and then perform a collision query between the object and the parcels.
This is only done when a viewer requests that an object be returned.
If the object overlaps one of their parcels then it will be returned.
The normal object and parcel permissions are checked first, then the object is checked for overlap.


Unfortunately some regions use encroachment as a feature.
Some regions use encroachment as a feature, where large "public works" structures overlap privately owned parcels.
An example is '''Luna''' which is a Linden-owned shopping mall with 3rd party vendors.
To protect such content the encroachment returnability feature has been split between regular privately owned content and '''estate-content''' that is owned by the Estate Managers.
Each vendor owns a small parcel of land inside the mall and can build their shop within their land, however they cannot return the walls or roof of the mall which nevertheless may encroach.
The returnability of regular overlapping content can be enabled while blocking return of overlapping estate-content.
While returning encroaching objects will be a manual process (only done on request) it would be a problem if people could accidentally or maliciously return existing content that has relies on encroachment.
 
Therefore, the ability to return encroaching objects will be disabled by default everywhere first, and must be enabled on a per region basis by Estate Managers.
Also the encroachment returnability logic introduces the concept of '''estate content''' and allows an exception for it.
 
'''estate content''' -- Objects owned by the Estate Owner or an Estate Manager.
 
A region can be configured such most objects are returnable upon encroachment but estate content is immune.


==How to Enable==
==How to Enable==
Here is how to enable the encroachment returnability feature:
Here is how to enable the encroachment returnability feature:


# Install a recent viewer that supports the '''Sim Console''' feature (latest Viewer 2 beta viewer, to be safe)
# Install a recent viewer that supports the '''Sim Console''' feature.
# Login as an Estate Manager
# Login as an Estate Manager
# Open the Sim Console with {{K|Ctrl|shift|`}} ''( '''`''' is the grave accent, commonly below {{K|Esc}} on QUERTY keyboards)''
# Open the Sim Console with {{K|Ctrl|shift|`}} ''( '''`''' is the grave accent, commonly below {{K|Esc}} on QUERTY keyboards)''

Revision as of 17:28, 25 January 2011

Encroachment
When an object's position is on one parcel of land but part of it extends into a neighboring parcel, often against the wishes of the neighbor.

The problem is that residents can place objects such that they are on their own parcels but invade the space of their neighbor's. In January 2011 a partial solution was deployed. Estate owners can now enable a feature that allows people to manually return objects that encroach upon their parcels.

How it works

First of all the returnability of encroaching objects must be enabled on a per-region basis. See the How To Enable section for information on how do do this.

When someone tries to return an object the server will first check the normal object and parcel permissions and if those fail it will then build a collision body in the physics engine for nearby parcels and then perform a collision query between the object and the parcels. If the object overlaps one of their parcels then it will be returned.

Some regions use encroachment as a feature, where large "public works" structures overlap privately owned parcels. To protect such content the encroachment returnability feature has been split between regular privately owned content and estate-content that is owned by the Estate Managers. The returnability of regular overlapping content can be enabled while blocking return of overlapping estate-content.

How to Enable

Here is how to enable the encroachment returnability feature:

  1. Install a recent viewer that supports the Sim Console feature.
  2. Login as an Estate Manager
  3. Open the Sim Console with Ctrl+Shift ⇧+` ( ` is the grave accent, commonly below Esc on QUERTY keyboards)
  4. Type the following command: set allow_return_encroaching_object true
  5. To allow return of estate content type: set allow_return_encroaching_estate_object true
  6. To check whether the feature is enabled or not type: get allow_return_encroaching_object

Misc Details and Known Bugs

  • The returnability logic relies on the object's physical shape which can differ from its visible shape. There may be cases where an object appears to overlap but is not returnable, or visa versa.
  • Visible and physical shape mismatch will be worst for the following objects:
    • trees and grass
    • sculpty prims
    • flexi prims
    • static objects using the llTargetOmega() feature -- they appear to be spinning but are not spinning in the physics engine
  • Phantom and Volume Detect objects will still collide for encroachment.
  • Encroachment across region boundaries is not yet supported but is under development.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Parcel_encroachment&oldid=1132585"