Second Life Wiki - User contributions [en]

Limits

2009-07-25T07:36:10Z

Bayru Jiagu: /* Performance */

{{Help
|BugFixes=
|Avatar=
|Object=
|Land=
|Community=
|Viewer=
|Communication=
|Multimedia=
|Navigation=
|Misc=*
|Description=
|Wiki=
|Glossary=*
}}
{{RightToc}}
This page is an easy reference to common queries about '''Second Life limits'''. Some of these will almost definitely change over time, so if you spot something incorrect/outdated, please take a moment to update it. You can also see the [http://support.secondlife.com/ics/support/default.asp?deptID=4417&task=knowledge&questionID=5480 Knowledge Base counterpart of this article], which isn't as updated.

== [[Avatar]] ==
* '''Max. # of attachment points''' - 30 for avatar, 8 for [[HUD]].
** They can be viewed in Edit menu > Detach Object.
* '''Max. unassisted fly height''' - Stable hover almost 150m above the ground (terrain mesh).
** You can easily acquire a flight attachment to fly up to seemingly infinite heights. See [[flight limit]].
* '''Common shoe sizes''' - Most women's shoes are designed for a size 0 (zero) foot. Men's generally scale up to 14.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.
* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).
* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed''' - 3 teleports per 15 seconds (server 1.27.0) and 10 teleports per 15 seconds (server 1.27.1)

== Building ==
* '''Max. [[prim]] dimensions (non-[[megaprim]])''' - 10x10x10m
* '''Min. prim dimensions''' - 0.01x0.01x0.01m
* '''Max. # of prims in a linkset''' - 256
** It was 255 before SL Server 1.26.
* '''Max. link distance''' - See [[Linkability Rules]].
* '''Max. # of prims in a physical object''' - 32
** If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
** This limit includes the driver and passengers of physics-enabled vehicles, e.g., if you're making a car to seat 4 people, 28 prims are available for the car itself.
* '''Max. build height''' - 4,096m
** This is 768m for viewers prior to SL 1.20
** Building above 768m can cause prim drift, distortion, misalignment, shifting and general weirdness. For small/precise builds, it's best to work at a lower level.
*** ''I'm familiar with some of this, but please provide a reference — like a reproducible bug on the [[Issue Tracker]]. Otherwise, it's unsubstantiated. '''- [[Image:Torley-favicon.png]] [[User:Torley Linden|Torley]] on 2009-05-06 @ 6:01 AM PST'''''
**** This could be related to http://jira.secondlife.com/browse/SVC-1170, but this describes "prim drift" not based on height.
* '''Max. prim name length''' - 63 bytes UTF8 [[string]]
** Note: This is the same total character limit as avatar names.
* '''Max. prim description length''' - 127 bytes UTF8 [[string]]
* '''Temporary prim lifetime''' - around 60 seconds
* '''Max. number of temporary prims''' - regular_prim_limit - current_regular_prims + minimum(0.5 * regular_prim_limit + 400, 1000) ''(see Andrew Linden's [http://forums.secondlife.com/showthread.php?t=305651 February 2009 discussion])''

== Chat (text) ==
* '''Whisper distance''' - 10 m
* '''Chat distance''' - 20 m
* '''Shout distance''' - 100 m
** Rule of thumb: when you're at default zoom (View menu > Reset View), if you can see another person's nametag, they can see your chat. If they're far enough away that you don't see a nametag, they won't "hear" you unless you shout.
* '''Max. length of a chat message''' - 1023 bytes/single-byte characters
** The same holds true for an IM <-> email replies.
* '''Capped''' - Maximum number of offline messages (involving [[IM]]s, inventory offers, group notices and group invitations) received before messages get capped is 25.
** Senders can't know whether their messages were capped or not.
* '''Email -> IM''' replies can be sent up to 5 days after receiving the offline IM the email is meant to answer.[[https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing blog]]
* '''IMs''' are retained on Linden Lab's servers for up to 31 days before being discarded. For example, if someone sends you an Instant Message and the next time you login is 33 days later, you won't get it.
** Torley confirmed this with Kelly Linden.

== [[Group]]s ==
* '''Max. # of groups you can belong to''' - 25
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Min. # of members in a group''' - 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Max. # of roles allowed in a group''' - 10 (including "Owners" and "Everyone", which can't be deleted)

== [[Inventory]] ==
* '''Max. # of inventory items that can be sent in a folder''' - 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references. ;)
* '''Max. notecard line''' - None, but scripts can only read the first 255 bytes
* '''Max. notecard size''' - 65,536 bytes

== [[Land]] ==
* '''Max. [[Land#Parcel|parcel]] size''' - 65,536 m²
** Covering a whole region, or square on the World Map.
* '''Min. parcel size''' - 16 m²
* '''Max. parcel name length''' - 63 characters
* '''Region name length''' - Min. 3 characters, max. 25 characters (including spaces){{KB|5215|Guidelines for Private Region Naming}}
* '''Max. "NO ENTRY" ban line height''' - 768 m above the terrain mesh.
** This is if you're explicitly banned from a parcel. If the parcel is simply not public access or restricted to certain Residents or a group, then the access lines go up to 50 m above the terrain mesh.
* '''Max. prims in a [[Land#Region|region]]:'''
** Full region - 15,000
** [[Land#Homestead|Homestead]] - 3,750
** [[Land#Openspace|Openspace]] - 750
* '''Max. Autoreturn value''' - Besides "0" (which means ''never''), 999,999 minutes is the highest autoreturn value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by +/-4 m.
** Some mainland can't be terraformed, including: Bay City Regions, Blumfield, Boardman, Brown, De Haro, Nautilus City Regions, Nova Albion Regions, Shermerville Regions, and West Haven.
** A few, very old mainland Regions like Da Boom have a terraform range of +/-40 m.
** Estate (private island) terraformability is settable to a max of +/-100 m by the estate owner or managers.
*** ''However, baking the land will allow it to be raised to at least 300 m. haven't tested any higher.--[[User:Liny Odell|Liny Odell]] 03:11, 6 May 2009 (UTC)''
* '''Max. water height''' - 100 m using in-world controls (mainland limit), 255 m by using a .raw file upload.
** Region water height is usually 20 m, and adjacent regions should have the same water height, or else they'll look discontinuous.
* '''Max. terrain height''' - 255 m using in-world controls (mainland limit), 510 m by using a .raw file upload.
* '''Misc. estate limits''' - You can have a max. of 10 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Mainland max. # of agents''' - 40 avatars/region
* '''Island max. # of agents:'''
** Full region - 100
** [[Land#Homestead|Homestead]] - 20
** [[Land#Openspace|Openspace]] - 10
* '''Freeze Time''' - Land owners can [[freeze]] other Residents for up to 30 seconds.
* '''Min. parcel that can be listed in Places or All search:''' 144 m² 
* '''Min. parcel that can be listed in Events:''' 512 m²

== Misc. ==
*'''[http://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [http://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.
*'''Contacts in Communication > Friends tab ''' - A maximum of 20 simultaneous contacts can be selected to change permissions, remove, or invite for a conference chat.

== Profile ==
*'''2nd Life tab's About field''' - 500 characters
*'''Picks tab''' - 10 picks with 1023 characters each
*'''1st Life tab's Info field''' - 250 characters
*'''My Notes''' - 1022 characters

== Performance ==
* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via Help menu > Lag Meter, or for more advanced usage, see View menu > Statistics Bar. (FPS as high as 120 and more have been observed, but FPS above 70 mostly seem to occur at times of network instability. --[[User:Bayru Jiagu|Bayru Jiagu]] )
* '''Avatar Rendering Cost scores''' - [http://blog.secondlife.com/2008/05/01/who-me-yes-you-couldnt-be-then-who-introducing-avatar-rendering-cost/ Learn all about it!]

== Scripting ==
* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls continue to remain active when you fly down.
* For specific scripting limits, lookup calls in the '''[[LSL Portal]]'''.

== Textures ==
* '''Aspect ratios''' of profile, place, etc. pictures — all of these were measured at UI size = 1.000:
** '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256x192 pixels)
** '''Search > Places and Classified tabs''' - ~7:5 (398x282 pixels)
** '''Search > Land tab''' - ~7:5 (358x252 pixels)
** '''Profile > 2nd Life tab''' - ~4:3 (178x133 pixels)
** '''Profile > Picks tab''' - ~16:9 (288x162 pixels)
** '''Profile > 1st Life tab''' - 1:1 (133x133 pixels)
** '''Profile > Classifieds tab''' - ~3:2 (206x137 pixels)
** '''Profile > Web tab''' - 1:1 (400x400 pixels)
*** A scrollbar uses 15 pixels on the right-hand side.
** '''About Land > Options tab''' - ~3:2 (178x117 pixels)
** '''Group Information > General tab's "Group Insignia"''' - 1:1 (126x126 pixels)
*** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.

* '''Maximum texture size''' - 1024x1024 pixels
** Some textures inworld have a resolution as high as 2048x2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load. See [[Avatar Rendering Cost]].

[[Category:Creation]] [[Category:Tutorials]]

Message linked

2008-10-06T10:49:44Z

Bayru Jiagu: Redirecting to Link message

#redirect [[link_message]]

Linked message

2008-10-06T10:49:28Z

Bayru Jiagu: Redirecting to Link message

#redirect [[link_message]]

Talk:VEHICLE TYPE SLED

2008-06-27T08:43:33Z

Bayru Jiagu: New page: Shouldn't float values like in "llSetVehicleFloatParam(integer int, float flt);" be given as floats to optimise performance rather than having the system lose time typecasting the variable...

Shouldn't float values like in "llSetVehicleFloatParam(integer int, float flt);" be given as floats to optimise performance rather than having the system lose time typecasting the variables?
All float parameters in the articles examples default values script are given as integers, is that because the Lindens have set them as integers?
--[[User:Bayru Jiagu|Bayru Jiagu]] 01:43, 27 June 2008 (PDT)

User:Bayru Jiagu

2008-02-28T13:11:12Z

Bayru Jiagu:

== About ==
*Born : 1983
*Languages : Dutch(M), English, French, (German).

== Projects ==
*RentalBox bay0.0 (All-in-one rentalbox Rental/Parcel-flags/Security/Media/Audio)
*Vendor bay0.0 (3-prim vendor)
*Bayradar bay0.0 (Costumisable radar-HUD with GPS-waypoint-functionality)
*Dancefloor bay0.1 (On-step dancefloor)

== Tracking the following issues on JIRA ==
*[https://jira.secondlife.com/browse/SVC-1167 Script function to return objects.]
== Voted for on JIRA ==
*[https://jira.secondlife.com/browse/SVC-1167 Script function to return objects.]
*[https://jira.secondlife.com/browse/MISC-64 Allow group IMs to be muted.]
*[https://jira.secondlife.com/browse/SVC-1385 Redefine SL system time as UTC/GMT instead of PST-PDT California time.]

User:Bayru Jiagu

2008-02-28T12:46:12Z

Bayru Jiagu: New page: == About == *Born : 1983 *Languages : Dutch(M), English, French, (German). == Projects == *RentalBox bay0.0 == Tracking the following issues on JIRA == *[https://jira.secondlife.com/brow...

== About ==
*Born : 1983
*Languages : Dutch(M), English, French, (German).

== Projects ==
*RentalBox bay0.0

== Tracking the following issues on JIRA ==
*[https://jira.secondlife.com/browse/SVC-1167 Script function to return objects.]
== Voted for on JIRA ==
*[https://jira.secondlife.com/browse/SVC-1167 Script function to return objects.]
*[https://jira.secondlife.com/browse/MISC-64 Allow group IMs to be muted.]

Talk:Object Oriented LSL

2008-01-25T15:11:32Z

Bayru Jiagu: comment

The perspective of having some kind of OOP support in LSL is really exciting, and such a feature would definitely come as a relief to experienced programmers. However, from what I understand about [[LSO]], I'm afraid it would require more than just "''some tweaking''".

There are just too many intrinsic limitations with the current implementation of LSO; it makes absolutely ''no provision'' for classes support, the closest thing you might get to references are ''heap pointers''; not to mention the fact that LSL scripts are self-contained, which means you can't access members (functions or variables) across scripts, etc...

At the very least should a couple of new opcodes or built-in functions be implemented, that would pop a key (as a ''class reference'') and a function number (as a ''member method reference'') from the stack, and then call the appropriate function (same for variables). I'm talking ''classes'' and not ''objects'' here, because you wouldn't have any instantiation mechanism anyway, so it would be like working only with full ''static'' classes, all the way.

Before you could even start dealing with common OOP features, such as inheritance, access protection issues etc., you would have to get a significant amount of work done on the VM just to get the basics right.

It's such a shame that the original LSO implementation was so poor, a better implementation could have led the way to many interesting and challenging opportunities, like translating Java bytecode to LSO, using design pattern constructs such as interfaces, listeners, etc... right from the start, and thus promoting good OOP practice.

So let's just wait for Mono integration now, and hope for the best.

-- Suleyman Polikarpov 10:28, 10 December 2007 (PST)

:Not to mention that the 16k limit. The overhead of classes would be horrendous. By the time you had everything defined you would have used up most of your memory. -- [[User:Strife Onizuka|Strife Onizuka]] 23:32, 10 December 2007 (PST)

:I believe it is already possible to approach lsl scripting in an object oriented way. Be it in a more literal sense than most scripting/programming languages. If you come to think of it, every prim is an object. And then I mean it in the programming sense of that word. A prim already has 'batteries included' attributes (shape, color, name, description, id, etc.) and methods (llSetPos/llGetPos/llSetLocalRot etc.). You can even regard 'on_rez' as an overridable '.__init__(self)' method. You can communicate to prims by using 'llListen' and 'llSay' in a very easy straightforward way. You are actually creating an instance by rezzing a prim. You define classes by designing new prims and you instantiate them by rezzing a copy of that prim. You add and override methods by dragging scripts to them. I'm actually happy I don't have to spend a lot of time defining a new class before I can make an instance to it. It happends simultaniously in SL. and if you really want to do classdefinitions you can create a script that rezzes your prim with all the desired values for you.
:Only thing I miss using prims as objects (but I have seen another feature request for it) is more elaborate 'root'-'child'-linking functionality ... And an easy/documented way to write/edit notecards ... Just my thoughts ... [[User:Bayru Jiagu|Bayru Jiagu]] 07:11, 25 January 2008 (PST)

Project:Languages/nl

2008-01-23T14:35:26Z

Bayru Jiagu: Translation to dutch

{{Multi-lang}}

= Taalrichtlijnen voor de SL wiki =

Deze pagina bespreekt de richtlijnen over het gebruik van de moedertaal en de vertaling van SL wiki-inhoud (http://wiki.secondlife.com). Vertaling van de SL Viewer UI wordt besproken op een aparte pagina [[How to Localize Your World]]. Informatie over een bewoner-georganiseerde activiteit genaamd I18N Project is verkrijgbaar via [[Project:I18n]].

Op dit moment is de inhoud van deze pagina slechts een verzameling voorstellen. Wees zo vrij commentaar te leveren via 'the [[Project talk:Languages|associated discussion page]]' of deze pagina zelf te wijzigen. Men verwacht echter dat de volledige inhoud van de SL wiki in de toekomst de herziene richtlijnen op deze pagina zal volgen. Wanneer men bestaande gebruiken wijzigt dient iemand de bestaande pagina's te herschrijven zodat ze voldoen aan de nieuwe regels.

Als u dus iets over dit onderwerp te zeggen hebt, wacht er dan alstublieft niet mee!

= Algemeen =

Over 't algemeen volgt SL wiki de ideeën en mechanismes van [http://www.mediawiki.org/wiki/Project:Language_policy MediaWiki site's language policy on Help pages], in tegenstelling tot [http://www.wikipedia.org Wikipedia] zijn taalversies.

= Nieuwe pagina's aanmaken =

== Eerste taal ==

Het Engels is de eerste taal van SL wiki.

Het Engels werd gekozen omdat het vandaag de dag de meest gedeelde taal is in internationale communicatie. Niet om mensen met het Engels als moedertaal voor te trekken. Gelieve dus, zelfs als u zich zeer goed in het Engels kunt uitdrukken, aan te nemen dat de lezers niet vloeiend zijn in het Engels en u te beperken tot het gebruik van simpele bewoordingen.

U mag in Engelstalige zinnen vreemde woorden of uitdrukkingen gebruiken waar u dat nodig acht. Gelieve echter het elitaristische gebruik van uitdrukkingen in het Latijn, het Grieks of het Frans te vermijden.

== Paginatitels ==

De titel van een pagina in SL wiki dient gebaseerd te worden op de Engelstalige titel.

Hoewel MediaWiki de capaciteit heeft om niet Engelstalige titels toe te staan (zoals het gebruik van eender welke Unicode karakters), zal SL Wiki van deze mogelijkheid geen gebruik maken.

== Niet Engelstalige inhoud ==

Als u een nieuwe pagina wil schrijven in een taal bezijds het Engels, gelieve dan te overwegen deze pagina in twee talen aan te maken; één in het Engels en een tweede in uw eigen taal, waarbij u de Engelstalige pagina als hoofdpagina aanmaakt en de niet Engelstalige pagina een [[#Translation|vertaling]]. De Engelstalige pagina hoeft in dit geval geen volledige pagina te zijn. Een korte samenvatting is voldoende.

Zelfs als u niet bereid bent om de pagina in het Engels te schrijven of u daartoe de nodige vaardigheden mist, is het aangeraden een bijna lege ''Engelstalige'' pagina aan te maken waarop u iets vermeldt in de zin van "The content of this page is not available in English for the moment", en uw niet Engelstalige pagina te schrijven als een ''vertaling''.

Op deze manier kunnen andere bewoners uw onderwerp naar het Engels vertalen zonder volledige pagina-structuren te moeten wijzigen.

= Vertaling =

Het vertalen van pagina's op de SL Wiki naar andere talen wordt verwelkomd.

== Pagina titels ==

de vertaling wordt geschreven als een aparte pagina.

De titel van deze vertaling dient de titel van de overeenkomstige Engelstalige pagina te zijn, plus ee ncode voor de taal, van elkaar gescheiden door een schuine streep (/). De Nederlandstalige versie van de '[[Main Page]]' is getiteld; '[[Main Page/nl]]', in tegenstelling tot '''Hoofdpagina''' of '''Hoofdpagina/nl''', waarbij '''nl''' (en dus niet 'ned') de taalcode voor het Nederlands is.
Zie [[#Language codes|Taal code]] hieronder voor mogelijke codes.

De taalcode wordt volledig in kleine letters geschreven.

== Talensjabloon ==

Vertaalde pagina's dienen aangeduid te worden met het [[Template:Multi-lang|<nowiki>{{Multi-lang}}</nowiki> sjabloon]]. Hetzelfde geldt voor Engelstalige pagina's waarvoor één of meer vertalingen beschikbaar zijn. Het <nowiki>{{Multi-lang}}</nowiki> sjabloon dient bovenaan de pagina geplaatst te worden en op dezelfde plaats gehouden te worden als in vertalingen van dezelfde pagina.

Het consequent gebruik van het <nowiki>{{Multi-lang}}</nowiki> sjabloon helpt lezers de pagina in de taal van hun voorkeur terug te vinden.

Let erop dat [[:Template:Multi-lang]] ook beschikbaar is onder de andere naam [[:Template:Languages]] voor historische gegroeide redenen.

== Links ==

Als u naar een andere pagina linkt van een niet Engelstalige pagina, en de doelpagina heeft een vertaling in dezelfde taal, is het beter een link naar de vertaalde pagina te gebruiken. Deze links hebben beter een 'translated' anker.

Als u bijvoorbeeld een Franstalige pagina aan het schrijven bent, en u wilt een link naar de naar het Frans vertaalde versie van de pagina '''Voice''' opzetten, is het beter de link te schrijven als <code><nowiki>[[Voice/fr|voix]]</nowiki></code> dan als <code><nowiki>[[Voice/fr]]</nowiki></code>.

Ja, dit is een ietswat ongemakkelijk neveneffect van de bovenstaande richtlijn, dat wil zeggen; de paginatitel is steeds gebaseerd op het Engels. (Graag uw mening op de [[Project talk:Languages|discussion]] pagina.)

Als de doelpagina geen vertaling heeft naar dezelfde taal, link dan naar de primaire (Engelstalige) pagina.

== Synchronisatie ==

Probeer de inhoud van de vertaalde pagina's te synchroniseren met de overeenkomstige Engelstalige pagina. U als vertaler hebt evenwel niet de plicht de wijzigingen in de originele pagina op te volgen. Elke bewoner die een verandering opmerkt wordt aangemoedigd de vertaling bij te werken.

Enkel op de vertaalde pagina informatie toevoegen is dus gevaarlijk, aangezien andere bewoners de toevoeging kan verwijderen om de inhoud te ''synchroniseren''. Er is een duidelijke aanduiding nodig als u iets toevoegt.

= Taalcodes =

SL wiki gebruikt zowel ISO 639-1 (alpha-2) codes als ISO 639-3 codes voor taalherkenning.

Wanneer beiden toepasbaar zijn, heeft 639-1 alpha-2 code voorrang.

(Zie [[Project talk:Languages|discussion page]] voor dit standpunt.)

== Lijst van taalcodes ==

Met ingang van dit schrijven worden volgende taalcodes gebruikt in SL Wiki (de lijst zal van tijd tot tijd uitgebreid worden);

{| border="1" cellspacing="0"
!Code!!Language
|-
|de||Duits
|-
|en||Engels
|-
|es||Spaans
|-
|fr||Frans
|-
|it||Italiaans
|-
|ja||Japanees
|-
|nl||Nederlands
|-
|pl||Pools
|-
|pt||Portugees
|-
|zh||Chinees
|}

Merk op dat de Engelstalige paginatitels niet van een taalcode voorzien worden. Er zal dus geen pagina zijn met de titel "Something/en". De code '''en''' voor het Engels wordt echter wel op verscheidene plaatsen gebruikt.