Region

Template:Needs Translation/de Template:Needs Translation/es Template:Needs Translation/el Template:Needs Translation/he Template:Needs Translation/ko Template:Needs Translation/nl Template:Needs Translation/hu Template:Needs Translation/no Template:Needs Translation/da Template:Needs Translation/sv Template:Needs Translation/tr Template:Needs Translation/pl Template:Needs Translation/pt Template:Needs Translation/ru Template:Needs Translation/th Template:Needs Translation/uk Template:Needs Translation/zh-Hans Template:Needs Translation/zh-Hant

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<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="SL Knowledge Base: Information about Openspaces (Void Regions)">[1] and four void regions per server host CPU. Void regions support fewer prims and users<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="SL Knowledge Base: Information about Openspaces (Void Regions)">[1].

For more information about server hosts, see the 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

1. ^ SL Knowledge Base: Information about Openspaces (Void Regions)