|
|
| (6 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{Help | | #REDIRECT [[Land#Region]] |
| |BugFixes=
| | {{Help|Glossary=*}} |
| |Avatar=
| |
| |Object=
| |
| |Land=
| |
| |Community=
| |
| |Viewer=
| |
| |Communication=
| |
| |Multimedia=
| |
| |Navigation=
| |
| |Misc=
| |
| |Description=
| |
| |Wiki=
| |
| |Glossary=* | |
| }}
| |
| | |
| A named 256m x 256m (65,536 m²) area hosted by a single simulator process. In common usage, the term "simulator" or "sim" may also refer to a region, but in fact a single sim process can host mulitple regions.
| |
| | |
| There are two types of regions: Normal and Void. There are two normal regions per server host CPU{{Footnote|1={{slkb|4235|Information about Openspaces (Void Regions)}}|2={{Slkb|4235|Information about Openspaces (Void Regions)|no-link=*}}|handle=cpu}} and four void regions per server host CPU. Void regions support fewer prims and users{{Footnote|handle=cpu}}.
| |
| | |
| For more information about server hosts, see the [http://blog.secondlife.com/?s=%22class+5%22 Second Life blog].
| |
| | |
| == Effects on Scripting ==
| |
| | |
| Scripts can detect the current region, and detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, because the object and its script's states are serialized, sent to the new region, and then deserialized.
| |
| | |
| == Footnotes ==
| |
| {{Footnotes}}
| |