Second Life Wiki - User contributions [en]

User:Zephyr Nayl

2010-11-15T15:52:59Z

Zephyr Nayl: Undo revision 1105443 by Zephyr Nayl (Talk)

==Zephyr Nayl==
===About Me===
I've been around for a long time now. Just a fuzzy bunny trying to dominate the metaverse.
====Second Life Profile====
[http://world.secondlife.com/resident/268bf343-463e-42d4-916f-d6546e5ff060 Zephyr Nayl]
====Email Address====
[mailto://zephyr.nayl@gmail.com zephyr.nayl@gmail.com]
----
===My Work===
====Furry Fashion====
[http://maps.secondlife.com/secondlife/Furry%20Fashion/133/115/23/?title=Furry%20Fashion&msg=A%20welcoming,%20friendly%20community%20where%20you%20can%20meet%20new%20furry%20friends.%20Here%20you%20can%20find%20your%20furry%20side%20in%20Second%20Life.%20A%20true%20community%20hub%20with%20a%20club,%20hangout,%20store,%20and%20welcome%20center. Teleport]
====Scripting====
Inquire by IM for details
====[[Snowstorm]]====
[http://hg.secondlife.com/viewer-development Public Repo]
====Second Life Wiki====
[https://wiki.secondlife.com/wiki/Special:Contributions/Zephyr_Nayl Contributions]
====Second Life JIRA====
[https://jira.secondlife.com/secure/ViewProfile.jspa?name=zephyr.nayl Activity Stream]

User:Zephyr Nayl

2010-11-15T05:39:32Z

Zephyr Nayl:

User:Zephyr Nayl

2010-11-06T07:09:37Z

Zephyr Nayl: /* My Work */

User:Zephyr Nayl

2010-11-05T21:44:20Z

Zephyr Nayl:

==Zephyr Nayl==
===About Me===
I've been around for a long time now. Just a fuzzy bunny trying to dominate the metaverse.
====Second Life Profile====
[http://world.secondlife.com/resident/268bf343-463e-42d4-916f-d6546e5ff060 Zephyr Nayl]
====Email Address====
[mailto://zephyr.nayl@gmail.com zephyr.nayl@gmail.com]
----
===My Work===
====Furry Fashion====
[http://maps.secondlife.com/secondlife/Furry%20Fashion/133/115/23/?title=Furry%20Fashion&msg=A%20welcoming,%20friendly%20community%20where%20you%20can%20meet%20new%20furry%20friends.%20Here%20you%20can%20find%20your%20furry%20side%20in%20Second%20Life.%20A%20true%20community%20hub%20with%20a%20club,%20hangout,%20store,%20and%20welcome%20center. Teleport]
====Second Life Wiki====
[https://wiki.secondlife.com/wiki/Special:Contributions/Zephyr_Nayl Contributions]
====Second Life JIRA====
[https://jira.secondlife.com/secure/ViewProfile.jspa?name=zephyr.nayl Activity Stream]

User:Zephyr Nayl

2010-11-04T20:11:40Z

Zephyr Nayl: Created page with 'I've been around for a long time now. Just a fuzzy bunny trying to dominate the metaverse.'

I've been around for a long time now. Just a fuzzy bunny trying to dominate the metaverse.

Improving Region Performance

2010-11-02T21:18:43Z

Zephyr Nayl: Removing texture related reasons to improve performance, Textures are handled via capability and not the simhost.

<noinclude>{{KBmaster}}</noinclude>
<noinclude>
This article explains how to check your Second Life region's performance and some steps you can take to improve it. This article has been written with owners of Estates (sometimes referred to as islands) in mind, but mainland owners may find parts of it helpful.
</noinclude>
===Checking Your Region's Performance===

To see the performance of your region you'll want to check the region's Frames Per Second (FPS). To do this you can use the [[Statistics Bar Guide|Statistics Bar]]. While standing on your land, select '''View > Statistics Bar'''. This can be a bit overwhelming, so we'll guide you through the relevant parts here.

[[Image:kb_region_fps.png]]

''Statistics Bar with '''Sim FPS''' (a measure of your region's Frames Per Second) highlighted.''

{{KBnote| '''Sim''' stands for "simulator" and, for the purposes of this article, is another name for "region."}}

To interpret the '''Sim FPS''' performance of your region:

* 45 FPS: The highest possible value. No action necessary.
* 35 - 44 FPS: This is good performance; you don't need to tune if it never goes below 35 FPS.
* 10 - 35 FPS: This is very slow, and should be noticeable. Adjustment is needed to improve your region's performance.
* 0 - 10 FPS: This is terrible. You may have trouble moving or performing simple tasks. See above.

If your performance of your region is consistently over 35 FPS at its busiest time, you can stop reading here. Fortunately, most regions are above 35 FPS most of the time. For example, during the month of October 2007, all the Second Life regions were below 35 FPS an average of less than 2% of the time.

In the screenshot above, you'll notice the '''Sim FPS''' is '''21''', which means the region is very slow. The '''Main Agents''' line shows '''96''', which is the number of agents (avatars) currently in your region. This is exceptionally high, and is likely the prime cause of this region's slow FPS. The '''Child Agents''' line displays the number of avatars outside your region that can see into it, which can also slow your region down if it's a significant number.

To see more detail on what's slowing down your region, expand the [[Statistics Bar Guide|Statistics Bar]] by clicking on the '''Time (ms)''' line; additional region statistics will appear:

[[Image:kb_stats_time.png]]

The '''Total Frame Time''' displays the number of milliseconds needed (ms) to display a single frame. '''Total Frame Time''' greater than '''22.2 ms''' means your '''Sim FPS''' will be below '''45 FPS'''. For a detailed explanation of the values beneath '''Total Frame Time''', see the [[Statistics Bar Guide|Statistics Bar article]]'s Time section. However, we'll explain some of these measurements below as we walk through the ways to improve your region's performance.

===Improving Your Region's Performance===

There are a number of steps that you can take to improve your region's performance. We've listed the steps in approximate order of the biggest impact and least effort. It's worth noting, however, that each region is unique.

====Reduce the Maximum Number of Avatars in Your Estate====

The number of avatars in a region is the most common cause and usually the biggest contributor to low region FPS. This number has often been increased above the default setting of 40, resulting in lower region performance. Lowering the number of avatars in your region can usually increase your region's FPS. This can be done in the '''Region''' tab of the Region/Estate window ('''World > Region/Estate'''); adjust the '''Agent Limit''' field to specify the number of avatars allowed in your region at any one time.

[[Image:kb_agent_limit.png]]

The default '''Agent Limit''' setting is '''40'''. As an estate owner, you can adjust this setting. We recommend looking at the '''Agent Time''' in the [[Statistics Bar Guide|Statistics Bar]] to see how well your region is performing during your busiest time. Keeping your '''Agent Time''' below '''9ms''' during its busiest time is a good idea.

====Remove Top Scripts====

Inefficient or very busy scripts in your region can slow it down. In the [[Statistics Bar Guide|Statistics Bar]], the '''Script Time''' line shows how many milliseconds each of the scripts in your region is taking to run. If this value is over 5 milliseconds, then it may be worth checking to see if it can be reduced. To see which scripts are the busiest in your region, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Scripts''', which will open the Top Scripts window.

[[Image:kb_top_scripts.png]]

* Clicking twice on the '''Time''' column heading sorts the busiest scripts at the top.
* Since this list is based on a small slice of time, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
* Selecting a line and clicking '''Show Beacon''' activates a beacon inworld highlighting the object running the selected script.

Once you know which scripts are consuming your region's resources, you can remove, replace or optimize them. Also, note that reducing the total number of scripts in your region can improve performance.

Examples of problematic scripts include:

* Scripts that are constantly active without sleeping; for example: Sensor scripts with less than a few-second sleep interval.
* Temp-rezzer scripts that allow a slightly larger number of prims at the expense of region performance.

====Remove Top Colliders====

Physical objects can potentially slow your region down. Specifically, physical objects that are often moving and collide with each other can contribute significantly to the time your region takes to perform the physics calculations. In the [[Statistics Bar Guide|Statistics Bar]], the '''Sim Time (Physics)''' line shows how many milliseconds your physics calculations are taking. If this value is over '''4''' milliseconds, then it may be worth check to see if this can be reduced. To see which colliders are the most active, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Colliders''', which will open the Top Colliders window.

* Clicking twice on the '''Time''' column heading sorts the most active colliders at the top.
* Since the top colliders list is based on a small time slice, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
* Selecting a line and clicking '''Show Beacon''' will activate a beacon inworld highlighting the selected object.

Once you know which objects are your top colliders, you can remove, replace or optimize them. Also note that lowering the total number of moving objects in your region can improve performance.

====Reduce the Number of Prims Used====

Reducing the number of prims your region uses will increase your region's performance. Regions are currently limited to 15,000 prims, but if you stay significantly below this number, your region performs noticeably better.

====Reduce Number of Objects====

Large numbers of objects will slow your region down, especially if they're of any of the following types:

* Moving
* Rotating
* Scripted
* Shape-changing sculpties

====Reduce Visitor Attachments====

While this is harder to do, some regions have seen improvement by having visitors remove attachments, especially high-prim or heavily scripted ones.

====Region Optimizations for Improved Viewer Performance====

The following region items can slow down viewer performance:

* Large or numerous textures, when an avatar first comes within sight of them
* Overuse of [[Sculpted Prims|sculpted prims]], twisted tori, and other geometrically complex objects.
* Particle effects (which includes bling and poofers).

Keep in mind some of your visitors may have slow graphics cards or PCs. [[Typical Frame Rate Performance by Graphics Card/GPU|This article]] discusses frame rate performance per graphics processing unit (GPU).

====More Info on the Region/Estate Window ====

You can perform numerous other estate management tasks using the [[The Region/Estate window|Region/Estate Window]].

===A Frequently-Asked Question About Frames Per Second===

"You know, I have a videogame that runs at a framerate much, much higher than Second Life's. Why is that?"

The quick answer: ''User-generated content.''

The reason why your videogame has such a luxurious, silken-smooth framerate is because its content is pre-rendered, and either installs to your hard drive before you've even begun playing, or streams to your computer from your CD or DVD-ROM drive faster than a contemporary internet connection could hope to be.

Content in Second Life isn't pre-rendered. It's created on the fly and updated constantly by countless individual users every second of every day while being fed to your computer through the internet. All of these factors make Second Life a much more dynamic, complicated world to render, which results in a framerate that's nominally lower than a top-of-the-line first-person shooter. This isn't to say Second Life's maximum framerate might not improve later -- the future is ever unknowable -- but those of you wondering why your region doesn't compare to your favorite next-generation shooter now have your answer.

===Conclusion===

Despite the fact that on average, regions are only below 35 FPS a small percentage of the time, we understand that slow region performance can be aggravating (to say the least). For those region and estate owners, we've described how to achieve good performance by monitoring the [[Statistics Bar Guide|Statistics Bar]] during your busiest times and using the Region/Estate window's tools to adjust the number of avatars, scripts, textures, objects and moving physical objects in your region. We hope this article helps you find the right balance between making your region impressive and fast.
[[Category:Performance and Stability]]
[[Category:Performance]]
[[Category:Inworld Issue]]
[[Category:Improving Performance]]
[[Category:Estates and Private Regions]]
[[Category:Landowners]]
[[Category:Information for Landowners]]
[[Category:Tips and Tricks]]
[[Category:Inworld]]

[[Category:Knowledge Base]]

UpdateScriptTask CAP

2010-10-28T16:35:36Z

Zephyr Nayl: moved UpdateScriptTask CAP to UpdateScriptTask: Removing unneeded CAP

#REDIRECT [[UpdateScriptTask]]

UpdateScriptTask

2010-10-28T16:35:36Z

Zephyr Nayl: moved UpdateScriptTask CAP to UpdateScriptTask: Removing unneeded CAP

POST:
<pre>
<llsd>
<map>
<key>is_script_running</key>
<integer>1</integer>
<key>item_id</key>
<uuid>84609c46-02c9-72a7-2fc5-f6a8ceddb41d</uuid>
<key>target</key>
<string>mono</string>
<key>task_id</key>
<uuid>df9e7ca7-daa9-836b-73e4-3fc1d560d2b9</uuid>
</map>
</llsd>
</pre>

Response:
<pre>
<llsd>
<map>
<key>state</key>
<string>upload</string>
<key>uploader</key>
<string>https://sim2777.agni.lindenlab.com:12043/cap/0573c509-0000-910b-79b2-736a2c98a7c8</string>
</map>
</llsd>
</pre>

Compiling for mono so I just POSTed the the script text to the uploader, and it worked!

Response to upload:
<pre>
<?xml version="1.0" ?>
<llsd>
<map>
<key>compiled</key>
<boolean>true</boolean>

<key>state</key>
<string>complete</string>

<key>new_asset</key>
<uuid>ff2b1049-a949-7ce6-046f-344bb5265ed7</uuid>
</map>
</llsd>
</pre>

UpdateScriptAgent CAP

2010-10-28T16:35:27Z

Zephyr Nayl: moved UpdateScriptAgent CAP to UpdateScriptAgent: Removing unneeded CAP

#REDIRECT [[UpdateScriptAgent]]

UpdateScriptAgent

2010-10-28T16:35:27Z

Zephyr Nayl: moved UpdateScriptAgent CAP to UpdateScriptAgent: Removing unneeded CAP

POST:
<pre>
<llsd>
<map>
<key>item_id</key>
<uuid>49b48bf9-2b40-d3fa-aea7-c856bf8b3dfb</uuid>
<key>target</key>
<string>mono</string>
</map>
</llsd>
</pre>

Response:
<pre>
<llsd>
<map>
<key>state</key>
<string>upload</string>
<key>uploader</key>
<string>https://sim2777.agni.lindenlab.com:12043/cap/c184fe54-9094-353a-4b3c-44f902c61fca</string>
</map>
</llsd>
</pre>

POSTed script text to uploader and it worked

Response to upload:
<pre>
<?xml version="1.0" ?>
<llsd>
<map>
<key>compiled</key>
<boolean>true</boolean>

<key>state</key>
<string>complete</string>

<key>new_asset</key>
<uuid>8cec7e2f-a151-e055-61d2-2d5c5146549b</uuid>
</map>
</llsd>
</pre>

UpdateNotecardAgentInventory CAP

2010-10-28T16:35:15Z

Zephyr Nayl: moved UpdateNotecardAgentInventory CAP to UpdateNotecardAgentInventory: Removing unneeded CAP

#REDIRECT [[UpdateNotecardAgentInventory]]

UpdateNotecardAgentInventory

2010-10-28T16:35:15Z

Zephyr Nayl: moved UpdateNotecardAgentInventory CAP to UpdateNotecardAgentInventory: Removing unneeded CAP

POST:
<pre>
<llsd>
<map>
<key>item_id</key>
<uuid>aae770ec-56d6-a94d-59d4-cd0ab05cad80</uuid>
</map>
</llsd>
</pre>

Response:
<pre>
<llsd>
<map>
<key>state</key>
<string>upload</string>

<key>uploader</key>
<string>https://sim2777.agni.lindenlab.com:12043/cap/0137dbb3-ba98-78ba-19b2-a3bdc1ce524c</string>
</map>
</llsd>
</pre>

UpdateGestureTaskInventory CAP

2010-10-28T16:35:04Z

Zephyr Nayl: moved UpdateGestureTaskInventory CAP to UpdateGestureTaskInventory: Removing unneeded CAP

#REDIRECT [[UpdateGestureTaskInventory]]

UpdateGestureTaskInventory

2010-10-28T16:35:04Z

Zephyr Nayl: moved UpdateGestureTaskInventory CAP to UpdateGestureTaskInventory: Removing unneeded CAP

POST:
<pre>
<llsd>
<map>
<key>item_id</key>
<uuid>4f81bfdc-5e20-00cb-e1d9-42d4d6d12abe</uuid>

<key>task_id</key>
<uuid>b0983d30-98a9-4ad3-769b-b4a27419114c</uuid>
</map>
</llsd>
</pre>

Response:
<pre>
<llsd>
<map>
<key>state</key>
<string>upload</string>

<key>uploader</key>
<string>https://sim2777.agni.lindenlab.com:12043/cap/3b3c0c38-5ef7-599d-4350-081589cc1333</string>
</map>
</llsd>
</pre>

UpdateGestureAgentInventory CAP

2010-10-28T16:34:55Z

Zephyr Nayl: moved UpdateGestureAgentInventory CAP to UpdateGestureAgentInventory: Removing unneeded CAP

#REDIRECT [[UpdateGestureAgentInventory]]

UpdateGestureAgentInventory

2010-10-28T16:34:55Z

Zephyr Nayl: moved UpdateGestureAgentInventory CAP to UpdateGestureAgentInventory: Removing unneeded CAP

POST:
<pre>
<llsd><map><key>item_id</key><uuid>bdb399af-887e-a1de-b730-dc59e56de417</uuid></map></llsd>
</pre>

Response:
<pre>
<llsd><map><key>state</key><string>upload</string><key>uploader</key><string>https://sim5333.agni.lindenlab.com:12043/cap/56305d5f-f98a-7ed5-755c-c4af0fca1abd</string></map></llsd>
</pre>

ServerReleaseNotes CAP

2010-10-28T16:34:33Z

Zephyr Nayl: moved ServerReleaseNotes CAP to ServerReleaseNotes: Removing unneeded CAP

#REDIRECT [[ServerReleaseNotes]]

ServerReleaseNotes

2010-10-28T16:34:33Z

Zephyr Nayl: moved ServerReleaseNotes CAP to ServerReleaseNotes: Removing unneeded CAP

Obtained from a simulator's seed capability, the URI for ServerReleaseNotes points to an html page such as is opened in the official viewer when entering a region running in a different simulator version than the previously occupied region.

===Posted to seed_capability===
<llsd><array><string>ServerReleaseNotes</string></array></llsd>

===Response===
<llsd>
:<map>
::<key>ServerReleaseNotes</key>
::<string>http://s3.amazonaws.com/release-messages/Second%20Life%20Server/1.18.5.73200/releasemessage.htm</string>
:</map>
</llsd>

===HTTP GET http://s3.amazonaws.com/release-messages/Second%20Life%20Server/1.18.5.73200/releasemessage.htm===
<nowiki><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="cache-control" content="no-cache">
<link href="http://www.secondlife.com/_styles/MAIN.css" rel="stylesheet" type="text/css">

<title>Release Message</title>

</head>

<body style="margin:10px;">

<span class="topheader">Region Message</span>
<div id="DEFAULT_content_divider"><img src="http://www.secondlife.com/_img/spacer.gif" width="1" height="1"></div>

<div style="margin-left:10px; margin-right:10px;margin-top:10px; margin-bottom:10px;">

<p><span class="header">Basic Info</span></p>
<p>
You are entering a region which is a running a different simulator version than your previous region.
</p>

<p>
You can obtain more information in the <a href="https://www.secondlife.com/community/support.php">knowledge base</a>.
</p>

</div>

<div class="copyright">
©
Linden Research, Inc.
</div>

</body>
</html></nowiki>

[[Category: AW_Groupies]]

SendUserReportWithScreenshot CAP

2010-10-28T16:34:15Z

Zephyr Nayl: moved SendUserReportWithScreenshot CAP to SendUserReportWithScreenshot: Removing unneeded CAP

#REDIRECT [[SendUserReportWithScreenshot]]

SendUserReportWithScreenshot

2010-10-28T16:34:15Z

Zephyr Nayl: moved SendUserReportWithScreenshot CAP to SendUserReportWithScreenshot: Removing unneeded CAP

POST:
<pre>
<llsd>
<map>
<key>abuse-region-id</key>
<uuid />

<key>abuse-region-name</key>
<string />

<key>abuser-id</key>
<uuid>ffffffff-eeee-dddd-cccc-23e7775c9dce</uuid>

<key>category</key>
<string>45</string>

<key>check-flags</key>
<integer>0</integer>

<key>details</key>
<string>V1.21.5.98701

Abuser name: Test User
Abuser location: secondlife:///Crash%20Me/51/115/23
Enter my text here</string>

<key>object-id</key>
<uuid />

<key>position</key>
<array>
<real>110.21762084960937</real>
<real>78.232200622558594</real>
<real>341.15731811523438</real>
</array>

<key>report-type</key>
<integer>3</integer>

<key>screenshot-id</key>
<uuid>62329894-92db-5769-21a2-e1e7631e8dbd</uuid>

<key>summary</key>
<string> |Halfway| (secondlife:///Crash%20Me/51/115/23) [Disturbing the peace > Repetitive spam] {Test User} "Subject line here"</string>

<key>version-string</key>
<string>1.21.5 Win Intel Pentium Pro/2/3, Core GEFORCE 9600 GT/PCI/SSE2 </string>
</map>
</llsd>
</pre>

Response:
<pre>
<llsd>
<map>
<key>state</key>
<string>upload</string>

<key>uploader</key>
<string>https://sim2332.agni.lindenlab.com:12043/cap/64a50b41-d788-b14c-26cd-16f8bc50acc4</string>
</map>
</llsd>
</pre>

ProvisionVoiceAccountRequest CAP

2010-10-28T16:34:00Z

Zephyr Nayl: moved ProvisionVoiceAccountRequest CAP to ProvisionVoiceAccountRequest: Removing unneeded CAP

#REDIRECT [[ProvisionVoiceAccountRequest]]

ProvisionVoiceAccountRequest

2010-10-28T16:34:00Z

Zephyr Nayl: moved ProvisionVoiceAccountRequest CAP to ProvisionVoiceAccountRequest: Removing unneeded CAP

POST (body doesn't matter)

Response:
<pre>
<llsd>
<map>
<key>password</key>
<string>(password omitted)</string>

<key>username</key>
<string>xl7gX3F3TSYq90lZE0KqPtA==</string>
</map>
</llsd>
</pre>

ParcelVoiceInfoRequest CAP

2010-10-28T16:33:52Z

Zephyr Nayl: moved ParcelVoiceInfoRequest CAP to ParcelVoiceInfoRequest: Removing unneeded CAP

#REDIRECT [[ParcelVoiceInfoRequest]]

ParcelVoiceInfoRequest

2010-10-28T16:33:52Z

Zephyr Nayl: moved ParcelVoiceInfoRequest CAP to ParcelVoiceInfoRequest: Removing unneeded CAP

POST:
<pre>
<llsd><undef /></llsd>
</pre>

Response:
<pre>
<llsd><map><key>parcel_local_id</key><integer>1473</integer><key>region_name</key><string>Dubbs</string><key>voice_credentials</key><map><key>channel_uri</key><string>sip:confctl-2646239@bhr.vivox.com</string></map></map></llsd>
</pre>

MapLayer CAP

2010-10-28T16:33:18Z

Zephyr Nayl: moved MapLayer CAP to MapLayer: Removing unneeded CAP

#REDIRECT [[MapLayer]]

MapLayer

2010-10-28T16:33:18Z

Zephyr Nayl: moved MapLayer CAP to MapLayer: Removing unneeded CAP

POST:
<pre>
<llsd><map><key>Flags</key><integer>0</integer></map></llsd>
</pre>

Response:
<pre>
<llsd><map><key>AgentData</key><map><key>Flags</key><integer>0</integer></map><key>LayerData</key><array><map><key>Bottom</key><integer>990</integer><key>ImageID</key><uuid>77f630e9-d3e9-6c60-a71c-1cb8ca74e8cf</uuid><key>Left</key><integer>968</integer><key>Right</key><integer>999</integer><key>Top</key><integer>1021</integer></map><map><key>Bottom</key><integer>1022</integer><key>ImageID</key><uuid>8853d485-ed4f-a804-81d1-cdadb3d3220e</uuid><key>Left</key><integer>968</integer><key>Right</key><integer>999</integer><key>Top</key><integer>1053</integer></map><map><key>Bottom</key><integer>894</integer><key>ImageID</key><uuid>745cd4e3-ca10-37bf-de91-857d5110dd85</uuid><key>Left</key><integer>1000</integer><key>Right</key><integer>1031</integer><key>Top</key><integer>925</integer></map><map><key>Bottom</key><integer>926</integer><key>ImageID</key><uuid>35537e91-f5ac-5ef0-da01-37899e2347a4</uuid><key>Left</key><integer>1000</integer><key>Right</key><integer>1031</integer><key>Top</key><integer>957</integer></map><map><key>Bottom</key><integer>958</integer><key>ImageID</key><uuid>7e0f3899-e045-a146-d23b-eb9a92b747bf</uuid><key>Left</key><integer>1000</integer><key>Right</key><integer>1031</integer><key>Top</key><integer>989</integer></map><map><key>Bottom</key><integer>990</integer><key>ImageID</key><uuid>6973af92-1b4f-a06c-7d47-0113d96f15e6</uuid><key>Left</key><integer>1000</integer><key>Right</key><integer>1031</integer><key>Top</key><integer>1021</integer></map><map><key>Bottom</key><integer>1022</integer><key>ImageID</key><uuid>e324aa97-45a0-ef2b-2ef2-2f8698a1b097</uuid><key>Left</key><integer>1000</integer><key>Right</key><integer>1031</integer><key>Top</key><integer>1053</integer></map><map><key>Bottom</key><integer>894</integer><key>ImageID</key><uuid>6e7f7421-a21c-51a6-e01e-39f6e3c61608</uuid><key>Left</key><integer>1032</integer><key>Right</key><integer>1063</integer><key>Top</key><integer>925</integer></map><map><key>Bottom</key><integer>926</integer><key>ImageID</key><uuid>2f0ff436-dd4b-f44c-f067-4da2e4faa77a</uuid><key>Left</key><integer>1032</integer><key>Right</key><integer>1063</integer><key>Top</key><integer>957</integer></map><map><key>Bottom</key><integer>958</integer><key>ImageID</key><uuid>70c9e3aa-531c-16c1-c97a-f7463938e1c5</uuid><key>Left</key><integer>1032</integer><key>Right</key><integer>1063</integer><key>Top</key><integer>989</integer></map><map><key>Bottom</key><integer>990</integer><key>ImageID</key><uuid>af5f1fe2-a570-8ef1-26f0-315d157b79c4</uuid><key>Left</key><integer>1032</integer><key>Right</key><integer>1063</integer><key>Top</key><integer>1021</integer></map><map><key>Bottom</key><integer>990</integer><key>ImageID</key><uuid>731bcfa8-dcd4-9f8d-104b-eaa1349780ea</uuid><key>Left</key><integer>1096</integer><key>Right</key><integer>1127</integer><key>Top</key><integer>1021</integer></map><map><key>Bottom</key><integer>1022</integer><key>ImageID</key><uuid>35de51a5-3ea6-803b-095f-4f03c2abc617</uuid><key>Left</key><integer>1096</integer><key>Right</key><integer>1127</integer><key>Top</key><integer>1053</integer></map><map><key>Bottom</key><integer>1054</integer><key>ImageID</key><uuid>8172ec65-ebd2-c252-ab8c-135fb76b0c08</uuid><key>Left</key><integer>1096</integer><key>Right</key><integer>1127</integer><key>Top</key><integer>1085</integer></map><map><key>Bottom</key><integer>1086</integer><key>ImageID</key><uuid>3b6cf80f-a588-6888-5de8-1b5c38927211</uuid><key>Left</key><integer>1096</integer><key>Right</key><integer>1127</integer><key>Top</key><integer>1117</integer></map><map><key>Bottom</key><integer>1022</integer><key>ImageID</key><uuid>5352f9ed-6e22-0e0c-875d-713c99d7bfe8</uuid><key>Left</key><integer>1128</integer><key>Right</key><integer>1159</integer><key>Top</key><integer>1053</integer></map><map><key>Bottom</key><integer>1054</integer><key>ImageID</key><uuid>4f2c57c6-cdf3-64e5-2bc4-da99d61b0f55</uuid><key>Left</key><integer>1128</integer><key>Right</key><integer>1159</integer><key>Top</key><integer>1085</integer></map><map><key>Bottom</key><integer>1086</integer><key>ImageID</key><uuid>bd0eeada-9211-86a0-69a4-8c11d1d8c013</uuid><key>Left</key><integer>1128</integer><key>Right</key><integer>1159</integer><key>Top</key><integer>1117</integer></map><map><key>Bottom</key><integer>1118</integer><key>ImageID</key><uuid>427336e7-9016-0128-785a-5d26180338db</uuid><key>Left</key><integer>1128</integer><key>Right</key><integer>1159</integer><key>Top</key><integer>1149</integer></map><map><key>Bottom</key><integer>1054</integer><key>ImageID</key><uuid>fcb40c89-e324-9170-9174-3c7fe24996c1</uuid><key>Left</key><integer>1160</integer><key>Right</key><integer>1191</integer><key>Top</key><integer>1085</integer></map><map><key>Bottom</key><integer>1086</integer><key>ImageID</key><uuid>e203c454-9b42-dad2-4f43-63dbbb6c8323</uuid><key>Left</key><integer>1160</integer><key>Right</key><integer>1191</integer><key>Top</key><integer>1117</integer></map></array></map></llsd>
</pre>

EventQueueGet CAP

2010-10-28T16:33:02Z

Zephyr Nayl: moved EventQueueGet CAP to EventQueueGet: Removing unneeded CAP

#REDIRECT [[EventQueueGet]]

EventQueueGet

2010-10-28T16:33:02Z

Zephyr Nayl: moved EventQueueGet CAP to EventQueueGet: Removing unneeded CAP

The EventQueueGet cap is actually a service. The CAP provides access to the service.
Currently if the client cannot get an EventQueueGet cap, it will refuse to show neighbor regions and you will not be able to teleport to another region. You're essentially trapped where you are.

It's also very easy for the client to stop polling the EventQueueGet CAP

The Client essentially sends an application/xml Map with two keys. ack and done. Ack is an integer of the last Event ID and done is.. well, we don't know what done is yet besides it's a boolean. At this moment, it's always false.

The simulator will hold on to this request until it has some events to send to the client or the simulator times out the connection with a very specific response. The simulator will usually do this in around 20 to 30 seconds from the request start. To understand this, think in terms of requesting a web page that does a lot of background processing before sending you back a response. If you were to be able to post to the EventQueueGet Cap in a browser, it would look like a white page loading for about 20 or 30 seconds, and then it would give you back a 502 error. Don't fret! the 502 error is normal! When the EventQueueGet service doesn't have any events to send to the client, it typically sends a 'HTTP/1.0 502 Upstream error:' response with 'Upstream error: ' as the body. It's really important to note that the client will *only* accept a response like stated above. If you send it as a HTTP/1.1 response, the client will stop polling!

After the client closes the connection to the simulator (with a DisableSimulator packet), further attempts to poll the EventQueueGet cap will result in a 404 response. This tells the client to stop polling the cap. On the Debug Console, you'll see a nice message paraphrased: EventPollResponder: {1} https://CAPADDRESS/ stop 404

The client will keep polling the EventQueueGet cap until you give it a 404 even after you've left the region!

The client posts to the EventQueueGet cap provided in the region seed cap with an application/xml content type. (this will eventually be application/llsd+xml)

Client Request ->
{
ack : integer,
done : boolean
}

; Successful response (no events) <-
HTTP/1.0 502 Upstream error:
Content-Type: text/plain
Connection: close

Upstream error:

; Successful Response (event) <-
{
events : [ event ],
id : integer
}

There are a few events that OpenSimulator has implemented over the EventQueueGet cap.
So far they're;
* EnableSimulator
* CrossedRegion
* TeleportFinish

===EnableSimulator===
EnableSimulator is the event that tells the client to connect to a new simulator. We use it to inform clients that there is a neighbor region to the one that the avatar is currently in. This causes the client to attempt to connect to the region described in the EnableSimulator event.

{
body : {
SimulatorInfo : [
{
Handle : binary
IP : binary
Port : integer
}
]
},
message : 'EnableSimulator'
}

Remember, Handle is the regionhandle of the new simulator in BIG Endian format, base64 encoded.
IP is the IP Address of the new simulator as a byte array, base64 encoded.
Port is the UDP port of the new simulator UDP service.

Note:
The IP address (24.151.1.250) contains 4 bytes:
24
151
1
250

The regionhandle is a 64 bit representation of the X and Y cordinate of the 0,0 point of the new simulator
Where x is the uint X coordinate, and y is the uint Y coordinate, the formula for creating a regionhandle is:
ulong regionhandle = ((ulong)x << 32) | (ulong)y;

===CrossedRegion===
The simulator uses CrossedRegion to inform your client that it has crossed into a new region. Typically this is sent out when an avatar crosses a border between two simulators.

{
body : {
CrossedRegion : [
{
AgentData : [
{
AgentID : UUID,
SessionID : UUID
}
],
RegionData : [
{
RegionHandle : binary,
SeedCapability : string,
SimIP : binary,
SimPort : integer
}
],
Info : [
{
LookAt : [ real, real, real ],
Position : [ real, real, real ]
}
]
}
]
},
message : 'EnableSimulator'
}

===TeleportFinish===
This tells the client that the serverside processing for teleport is complete and that the client should begin the client side portion of the teleport.
{
body : {
Info : [
{
AgentID : UUID,
LocationID : integer,
RegionHandle : binary,
SeedCapability : string,
SimAccess : integer,
SimIP : binary,
SimPort : integer,
TeleportFlags : binary
}
]
},
message : 'TeleportFinish'
}

You can find additional information on : [http://www.libsecondlife.org/wiki/EventQueueGet a page from libsecondlife.org].

[[Category:Architecture Working Group]]
[[Category:Grid_Interoperability]]
[[Category:AW Groupies]]

ChatSessionRequest CAP

2010-10-28T16:32:41Z

Zephyr Nayl: moved ChatSessionRequest CAP to ChatSessionRequest: Removing unneeded CAP

#REDIRECT [[ChatSessionRequest]]

ChatSessionRequest

2010-10-28T16:32:41Z

Zephyr Nayl: moved ChatSessionRequest CAP to ChatSessionRequest: Removing unneeded CAP

Used to create (and manage?) a conference IM

POST:
<pre>
<llsd><map><key>method</key><string>start conference</string><key>params</key><array><uuid>01234567-0123-0123-0123-0123456789ab</uuid><uuid>fedcba98-fdec-fdec-fdec-fdecba987654</uuid></array><key>session-id</key><uuid>ddd7302b-642b-7114-16ff-6228a61e9b93</uuid></map></llsd>
</pre>

Response:
<pre>
Accepted
</pre>

Response is not xml llsd

POST:
<pre>
<llsd><map><key>method</key><string>call</string><key>session-id</key><uuid>c0da7611-9405-e3a4-0172-c36a1120c77a</uuid></map></llsd>
</pre>

Response:
<pre>
<llsd><map><key>session-id</key><string>c0da7611-9405-e3a4-0172-c36a1120c77a</string><key>voice_credentials</key><map><key>channel_credentials</key><string>rh1iIIiT2v+ebJjRI+klpFHjFmo</string><key>channel_uri</key><string>sip:confctl-12574742@bhr.vivox.com</string></map></map></llsd>
</pre>

Here the response is xml llsd

Current Sim Capabilities

2010-10-28T16:32:07Z

Zephyr Nayl: Updated Caps to include all from 2.3 and Mesh

=Introduction=

In the current protocols, there appear to be at least 2 kinds of [[Capabilities|capabilities]]: [[Current_Sim_Capabilities#Sim capabilities|Sim capabilities]] and [[Current_Sim_Capabilities#Sub-Capabilities|Sub-Capabilities]] obtained from the Sim Capability. The [[Current_login_protocols|current login protocols]] return a "seed-capability" which is actually the Sim-Capability of the sim the avatar enters upon performing a full login. This will change with the new [[Login_Protocol|login protocols]].

The following slides are from an October, 2007 presentation by Tess Linden. Though it was an internal Linden Lab presentation, the slides may be useful for those residents trying to learn Second Life's messaging and capability systems. [[Message_System_and_Capabilities]]

=Accessing Capabilities=

A typical capability is of the form: https://sim1234.agni.lindenlab.com:12345/cap/UUID

In the current client, sim capabilities are accessed via an https request of the form:

https request {POST, URL:port, path, body, header}

where

:• URL:port is of the form: sim1234.agni.lindenlab.com:12345;
:• path is of the form: /cap/UUID;
:• body is an xml-encoded LLSD array of the form: <llsd><array><string>request1</string><string>request2</string></array></llsd>
:• Header is of the form: "content-type": "application/xml";

The response from a sim capability transaction is an xml-encoded LLSD dictionary with key, value pairs in the form:

:• <llsd><map><key>request1</key><string>Capability1</string><key>request2</key><string>Capability2</string</map></llsd>

sub-capabilities apparently use the same protocol, but the body of the https request is dependent on which capability is used, as is the result.

=Sub Capabilities=
The following are among the sub-capabilities returned by the sim cap. Each has its own protocols which will be discussed in separate pages:

* [[AttachmentResources]]
* [[AvatarPickerSearch]]
* [[ChatSessionRequest]]
* [[CopyInventoryFromNotecard]]
* [[DispatchRegionInfo]]
* [[EstateChangeInfo]]
* [[EventQueueGet]]
* [[FetchInventory]]
* [[ObjectMedia]]
* [[ObjectMediaNavigate]]
* [[FetchLib]]
* [[FetchLibDescendents]]
* [[GetDisplayNames]]
* [[GetTexture]]
* [[GetMesh]]
* [[GetObjectCost]]
* [[GetObjectPhysicsData]]
* [[GroupProposalBallot]]
* [[HomeLocation]]
* [[LandResources]]
* [[MapLayer]]
* [[MapLayerGod]]
* [[NewFileAgentInventory]]
* [[NewFileAgentInventoryVariablePrice]]
* [[ObjectAdd]]
* [[ParcelPropertiesUpdate]]
* [[ParcelMediaURLFilterList]]
* [[ParcelNavigateMedia]]
* [[ParcelVoiceInfoRequest]]
* [[ProductInfoRequest]]
* [[ProvisionVoiceAccountRequest]]
* [[RemoteParcelRequest]]
* [[RequestTextureDownload]]
* [[SearchStatRequest]]
* [[SearchStatTracking]]
* [[SendPostcard]]
* [[SendUserReport]]
* [[SendUserReportWithScreenshot]]
* [[ServerReleaseNotes]]
* [[SimConsole]]
* [[SimulatorFeatures]]
* [[SetDisplayName]]
* [[StartGroupProposal]]
* [[TextureStats]]
* [[UntrustedSimulatorMessage]]
* [[UpdateAgentInformation]]
* [[UpdateAgentLanguage]]
* [[UpdateGestureAgentInventory]]
* [[UpdateNotecardAgentInventory]]
* [[UpdateScriptAgent]]
* [[UpdateGestureTaskInventory]]
* [[UpdateNotecardTaskInventory]]
* [[UpdateScriptTask]]
* [[UploadBakedTexture]]
* [[UploadObjectAsset]]
* [[ViewerStartAuction]]
* [[ViewerStats]]
* [[WebFetchInventoryDescendents]]

=External Links=
[http://www.libsecondlife.org/wiki/EventQueueGet] -- EventQueueGet - libsecondlife

[http://www.libsecondlife.org/wiki/MapLayer] -- MapLayer - libsecondlife

[http://www.libsecondlife.org/wiki/NewAgentInventory] -- NewAgentInventory - libsecondlife

[http://www.libsecondlife.org/wiki/UpdateNotecardAgentInventory] -- UpdateNotecardAgentInventory - libsecondlife

[[Category: AW Groupies]]

SetDisplayName

2010-10-28T16:22:05Z

Zephyr Nayl: Created page with '==SetDisplayName Capability== ===Request=== <llsd> <map> <key>display_name</key> <array> <string>The Old Display Name</string> <str...'

==SetDisplayName Capability==

===Request===
<llsd>
<map>
<key>display_name</key>
<array>
<string>The Old Display Name</string>
<string>The New Display Name</string>
</array>
</map>
</llsd>

===Response===
<llsd>
<string>undef</string>
<llsd>

Region Debug Console

2010-10-23T04:56:10Z

Zephyr Nayl:

==Capability Documentation==
Post to Capability: "SimConsole"

Post:
<llsd><string>help</string></llsd>

Response:
<llsd><string>Response</string></llsd>

==Commands==

* Help (Command)
Help is available for the following commands and topics. Type "help <topic>" for more information.
Note that all commands are case insensitive.

Get Retrieve the value of a variable.
Set Set the value of a variable.
Variables List variables you are authorized to view or modify.
Restart Restart the region after a specified amount of time (default 5mins).

* Get (Command)
Syntax: get <parameter>

Retrieve the current value of a simulator or region variable. Note that if the variable was set since the region was restarted, the new value will be returned rather than the value used when the region started. This can be significant for some variables. For more information, see "help <variable>". To retrieve the value of a variable used at startup, use "get -s <variable>".

* Set (Command)
Syntax: set <variable> <value>

Sets the value of a simulator or region variable. Note that some variable will not take effect until the region is restarted. This behavior will typically be specified in the parameter's description (see: "help variables")."

Value Format Examples:
Integer: 1234 or -435 0xffeb6194
Float: -3.4 or 14
Bool: [ON/OFF] or [TRUE/FALSE] or [ENABLED/DISABLED]
Vector: <1.34, -4.2, 8> in <x, y, z> order.

* Help Variables (Command)
Syntax: help variables
You are authorized to access the following parameters in this region:

accurate_terrain
Description: Enable more accurate terrain simulation at the cost of performance. Defaults to disabled.
Access: Read/Write

* Restart (Command)
Syntax: restart <minutes>
Restart the region after a specified amount of time (default 5mins).

Notes:
Can only accept positive integers.
If used during a active countdown will set the countdown to the specified time.
Appears to have no throttling or wait timers.
Giving the time "0" will cause the sim to shutdown immediately with no warning except for Second Life closing with a (Region is going down)
Restarts are warned to all clients with a message like this ([AlertMessage] /RESTART_X_MINUTES 5) (The dialog thing that normally appears.)

==Notable Responses==
If you stumble upon a variable or command not in help these two can show.

* You are not authorized to set that parameter. This event has been logged.
* You are not authorized to perform that command. This event has been logged.

==LSL possibilities==
If you have a bot with estate manager rights hand a LSL script the SimConsole Capability URL you can send commands to it. Note, you can't read the responses.

llHTTPRequest("https://<YOUR REGION HOST>.agni.lindenlab.com:12043/cap/<YOUR CAP HERE>",[HTTP_METHOD,"POST"],"<llsd><string>set accurate_terrain FALSE</string></llsd>");

[[Beta_Server_Office_Hours/Minutes/2010-10-07]]

Region Debug Console

2010-10-23T04:42:00Z

Zephyr Nayl:

Region Debug Console

2010-10-23T04:34:22Z

Zephyr Nayl:

Region Debug Console

2010-10-23T04:19:02Z

Zephyr Nayl: /* Capability Documentation */

==Capability Documentation==
Post to Capability: "SimConsole"

Post:
<llsd><string>help</string></llsd>

Response:
<llsd><string>Response</string></llsd>

==Commands==

* Help (Command)
Help is available for the following commands and topics. Type "help <topic>" for more information.
Note that all commands are case insensitive.

Get Retrieve the value of a variable.
Set Set the value of a variable.
Variables List variables you are authorized to view or modify.
Restart Restart the region after a specified amount of time (default 5mins).

* Get (Command)
Syntax: get <parameter>

Retrieve the current value of a simulator or region variable. Note that if the variable was set since the region was restarted, the new value will be returned rather than the value used when the region started. This can be significant for some variables. For more information, see "help <variable>". To retrieve the value of a variable used at startup, use "get -s <variable>".

* Set (Command)
Syntax: set <variable> <value>

Sets the value of a simulator or region variable. Note that some variable will not take effect until the region is restarted. This behavior will typically be specified in the parameter's description (see: "help variables")."

Value Format Examples:
Integer: 1234 or -4350xffeb6194Float: -3.4 or 14
Bool: [ON/OFF] or [TRUE/FALSE] or [ENABLED/DISABLED]
Vector: <1.34, -4.2, 8> in <x, y, z> order.

* Help Variables (Command)
Syntax: help variables
You are authorized to access the following parameters in this region:

accurate_terrain
Description: Enable more accurate terrain simulation at the cost of performance. Defaults to disabled.
Access: Read/Write

* Restart (Command)
Syntax: restart <minutes>
Restart the region after a specified amount of time (default 5mins).

Notes:
Can only accept positive integers.
If used during a active countdown will set the countdown to the specified time.
Appears to have no throttling or wait timers.
Giving the time "0" will cause the sim to shutdown immediately with no warning except for Second Life closing with a (Region is going down)
Restarts are warned to all clients with a message like this ([AlertMessage] /RESTART_X_MINUTES 5) (The dialog thing that normally appears.)

[[Beta_Server_Office_Hours/Minutes/2010-10-07]]

Region Debug Console

2010-10-23T04:13:46Z

Zephyr Nayl: /* Commands */

==Capability Documentation==
CAP: "SimConsole"

==Commands==

* Help (Command)
Help is available for the following commands and topics. Type "help <topic>" for more information.
Note that all commands are case insensitive.

Get Retrieve the value of a variable.
Set Set the value of a variable.
Variables List variables you are authorized to view or modify.
Restart Restart the region after a specified amount of time (default 5mins).

* Get (Command)
Syntax: get <parameter>

Retrieve the current value of a simulator or region variable. Note that if the variable was set since the region was restarted, the new value will be returned rather than the value used when the region started. This can be significant for some variables. For more information, see "help <variable>". To retrieve the value of a variable used at startup, use "get -s <variable>".

* Set (Command)
Syntax: set <variable> <value>

Sets the value of a simulator or region variable. Note that some variable will not take effect until the region is restarted. This behavior will typically be specified in the parameter's description (see: "help variables")."

Value Format Examples:
Integer: 1234 or -4350xffeb6194Float: -3.4 or 14
Bool: [ON/OFF] or [TRUE/FALSE] or [ENABLED/DISABLED]
Vector: <1.34, -4.2, 8> in <x, y, z> order.

* Help Variables (Command)
Syntax: help variables
You are authorized to access the following parameters in this region:

accurate_terrain
Description: Enable more accurate terrain simulation at the cost of performance. Defaults to disabled.
Access: Read/Write

* Restart (Command)
Syntax: restart <minutes>
Restart the region after a specified amount of time (default 5mins).

Notes:
Can only accept positive integers.
If used during a active countdown will set the countdown to the specified time.
Appears to have no throttling or wait timers.
Giving the time "0" will cause the sim to shutdown immediately with no warning except for Second Life closing with a (Region is going down)
Restarts are warned to all clients with a message like this ([AlertMessage] /RESTART_X_MINUTES 5) (The dialog thing that normally appears.)

[[Beta_Server_Office_Hours/Minutes/2010-10-07]]

Region Debug Console

2010-10-23T03:20:50Z

Zephyr Nayl:

==Capability Documentation==
CAP: "SimConsole"

==Commands==

* help
Help is available for the following commands and topics. Type "help <topic>" for more information.
Note that all commands are case insensitive.
Get Retrieve the value of a variable.
Set Set the value of a variable.
Variables List variables you are authorized to view or modify.
Restart Restart the region after a specified amount of time (default 5mins).

* help Get
Get (Command)
Syntax: get <parameter>

Retrieve the current value of a simulator or region variable. Note that if the variable was set since the region was restarted, the new value will be returned rather than the value used when the region started. This can be significant for some variables. For more information, see "help <variable>". To retrieve the value of a variable used at startup, use "get -s <variable>".

* help Set
Set (Command)
Syntax: set <variable> <value>

Sets the value of a simulator or region variable. Note that some variable will not take effect until the region is restarted. This behavior will typically be specified in the parameter's description (see: "help variables")."

Value Format Examples:
Integer: 1234 or -4350xffeb6194Float: -3.4 or 14
Bool: [ON/OFF] or [TRUE/FALSE] or [ENABLED/DISABLED]
Vector: <1.34, -4.2, 8> in <x, y, z> order.

* help Variables
You are authorized to access the following parameters in this region:
accurate_terrain
Enable more accurate terrain simulation at the cost of performance. Defaults to disabled.
Read/Write

[[Beta_Server_Office_Hours/Minutes/2010-10-07]]

Region Debug Console

2010-10-23T03:18:12Z

Zephyr Nayl:

Region Debug Console

2010-10-19T18:50:21Z

Zephyr Nayl: Confirmed the cap is SimConsole!

==Capability Documentation==
CAP: "SimConsole"

==Commands==

* shutdown
* tri-sampled heightfield

[[Beta_Server_Office_Hours/Minutes/2010-10-07]]

Release Notes/Second Life Server/10

2010-10-19T03:43:46Z

Zephyr Nayl: /* 10.10.11.211793 */

===10.10.11.211793===
* To be deployed: 2010-10-19

'''Features:'''
* [[llSetPrimitiveParams]](<nowiki>[</nowiki>[[PRIM_ROT_LOCAL]], rotation])
** Correct child prim rotations are now easier to achieve.
** This is an implementation of the feature request {{jira|SVC-129}} and an alternative fix for {{jira|SVC-93}}
* Server-side support for experimental "[[SimConsole]]"
** Requires viewer-side updates as well, which are not yet widely available.
** See [[Beta_Server_Office_Hours/Minutes/2010-10-07]] for details.
** [20:41:11] Oskar Linden: sim console is a new level of trickery to allow people shell like access to the simulator through their vwr

'''Bug Fixes:'''
* {{jira|SVC-6063}}: Object doesn't appear in Inventory when taken while frozen by grey goo fence
* Simulator does not preserve static objects' CRC values upon restart
*: This makes objects have to re-download after a sim restart, instead of pulling from cache.
* Faster [[land collision|terrain collisions]]
* Simulator crash fix

===10.09.21.210146===
* Deployed 2010-09-28

* '''Bug Fixes''':
** Simulator crash modes
** Improvements to the [[Region Conductor]]
**: This helps down regions come back up more quickly.
** Modifications to deploy tools to support Release Candidates

=== 10.9.10.210079 ===
* Deployed 2010-09-21

'''Bug fixes''':
* Several simulator crash modes

[[Category:Release Notes]]

Furry

2010-09-16T08:21:03Z

Zephyr Nayl: /* Related Links */

{{Help |Glossary=*}}[[Resident]] using [http://en.wikipedia.org/wiki/Anthropomorphism anthropomorphic] animal [[avatar]]s.

== Related Links ==

* [http://en.wikifur.com/wiki/Furry Wikifur: Furry]

* [http://secondlife.wikia.com/wiki/Furry SL Wikia: Furries]

* [http://en.wikipedia.org/wiki/Furry_fandom Furry Fandom]

* [http://maps.secondlife.com/secondlife/Furry%20Fashion/133/115/23/?title=Furry%20Fashion&msg=A%20welcoming,%20friendly%20community%20where%20you%20can%20meet%20new%20furry%20friends.%20Here%20you%20can%20find%20your%20furry%20side%20in%20Second%20Life.%20A%20true%20community%20hub%20with%20a%20club,%20hangout,%20store,%20and%20welcome%20center. Furry Fashion Community Hub]