Difference between revisions of "Region"
(link provides no further explanation since it goes to itself! =D) |
(LSL scripts are generally sim specific, and can't easily roam across the grid) |
||
| Line 4: | Line 4: | ||
See: [[Viewer coordinate frames]] | See: [[Viewer coordinate frames]] | ||
== Effects on LSL Scripting == | |||
Scripts generally only deal with one coordinate system and one sim at a time. Commands that move objects are generally confined to one simulator, covering an area of: | |||
*X: 0 to 255.990 | |||
*Y: 0 to 255.990 | |||
*Z: 0 to 767.990 typical (up to 1023.990 with precision, beyond 4 billion without precision) | |||
Scripts can detect their current region, and can detect region changes, but these factors are normally separate from region coordinates. Non-vehicle scripted objects cannot easily traverse the grid, to move across the world from one particular sim to another. | |||
Revision as of 19:50, 28 May 2008
"Region" is a simulated environment as itself (or simulated parameters). The land in SL is hosted on a Linux server , each CPU handle 65,536 m² (256x256m) region. Current class5 host server has 4 CPU cores, so each server handle 4 regions. (except for void type region which are 4 per CPU).
To learn more about the servers hosting SL, you can read the series of articles [1] that have been posted to the SL blog.
Effects on LSL Scripting
Scripts generally only deal with one coordinate system and one sim at a time. Commands that move objects are generally confined to one simulator, covering an area of:
- X: 0 to 255.990
- Y: 0 to 255.990
- Z: 0 to 767.990 typical (up to 1023.990 with precision, beyond 4 billion without precision)
Scripts can detect their current region, and can detect region changes, but these factors are normally separate from region coordinates. Non-vehicle scripted objects cannot easily traverse the grid, to move across the world from one particular sim to another.