Avatar Rendering Cost
From Second Life Wiki
This article is out of date!
- ARC is now called Draw Weight, and calculated differently. See Mesh/Rendering weight for more current information.
What is "ARC"?
"ARC" stands for "Avatar Rendering Cost", an educational tool to help you understand more about sources of Viewer-side lag. Using a point score, Avatar Rendering Cost shows how each avatar affects the rendering performance of the Viewer. The point score is shown over an avatar's head in green, yellow or red, depending on how costly an avatar is for a graphics card to render.
Learn more in this video:
How is the Avatar Rendering Cost determined?
Each face/polygon on an avatar's attachment is assigned a point (times a multiple). Characteristics of that face which might slow down rendering determines the multiple. All the points get added together and presented as "the final cost" estimate of rendering the avatar.
The scores are color coded. The center of the yellow band is a score of about 1,000. The numbers turn fully red at around 2,000 (2,048, to be precise). It's generally best to be considerate of others when putting together your avatar, and to do what you can to stay under a score of 2,000, especially in crowded areas. Under 1,000 is even better. These are only guidelines, but be aware that the higher your score is, the more lag you generate for other Residents, particularly those with older machines.
|Important: ARC isn't the end-all for pinpointing Viewer lag. It's a useful estimate which should be used in conjunction with other tools.|
What types of characteristics affect each face/polygon?
- An avatar with no attachments has a score of 100.
- You can have the fanciest possible Linden (aka mesh) clothing, hair, and shoes, and still have a score of 1.
- 10 points for each prim.
- This is a base cost for the prim, other points add to this cost.
- 5 points for each unique texture (on prims).
- Colored but untextured prims don't add ARC for textures.
- Textures used to make clothing, hair, shoes, etc don't add ARC.
- Each texture counts once, so hair that has fifty prims but only one texture across all the hair adds only 5 points for textures. (Note that most hair has at least two textures, one with transparency to make the 'ends', and one without for the main bulk of the hair. So hair like that adds 10 points for textures.)
- 1 point for each invisiprim.
- This isn't transparency, but the invisiprim texture used for blocking avatar skin. Its most frequent use is prim heels, it's also often used for furry or tiny avatars.
- 1 point for each prim with glow. (If Glow value is set higher than 0.0 in Texture tab of the build tools)
- 1 point for each prim with shininess. (If Shininess is other than "None" in Texture tab of the build tools)
- 1 point for each face of every prim that's planar-mapped. (If Mapping is "Planar" in Texture tab of the build tools)
- 1 point per meter, per axis, for each prim.
- This most often affects skirts, capes, long hair, large wings and long tails.
- 4 points for each prim with bump mapping. (If Bumpiness is other than "None" in Texture tab of the build tools)
- 4 points for each prim face with transparency.
- Note that this is per face, not per prim.
- This includes partial transparency, like 'endy' hair.
- It also includes prims which don't seem to have invisibility, but do - if it shows up as red when you turn 'highlight transparent' on (under the view menu), it counts.
- 4 points for each prim face with an animated texture.
- Note that this is per face, not per prim.
- 8 points for each prim that's flexible.
- 16 points for each prim that emits particles.
- The most common use of particle emitters is bling.
How do I enable ARC?
- Turn on your Advanced menu.
- Enable Advanced > Rendering > Info Displays > Avatar Rendering Cost. Or in SLV 2.8/3.0 Advanced > Performance Tools > Show Avatar Rendering Cost
ORC - Object Rendering Cost
ORC (Object Rendering Cost) is a tool similar to ARC, that measures how selected objects affect the rendering performance of the Viewer. When you select any object, its ORC value is displayed in the main tab of the Edit window, as shown in the picture above.
Lowering your rendering cost
Most people can make an avatar which looks similar to their normal avatar, but has a lower ARC. It can be a good idea to keep a low-ARC avatar to take to high-lag or popular events, or to wear to classes that are likely to generate lag (such as building or scripting classes).
- Start by bringing the ARC up: Advanced Menu > Rendering > Info Displays > Avatar Rendering Cost
- Make a note of all the attachments you wear on your regular avatar.
- Detach everything. (Right click on yourself, select Detach, then select Detach All.)
- Gradually attach each item, making a note of which items increase your ARC most.
- If you're a competent builder yourself, look at "How ARC is calculated" and remove unnecessary particles, flexi, bumpmapping, texture animation and prims from copy/modify high-ARC objects.
Some hairstyles, for instance, have more than one style within the same object, with the second style being invisible. You can reduce the ARC of that hair just by making a version without the second style - and look exactly the same.
- Otherwise, you can look for low ARC objects that have a similar look to the high ARC version. Use demos to figure out the ARC of an object before purchase. *IMPORTANT NOTE* If you mute someone then you will not hear or see messages sent to you from them, and vice versa.
What to do if someone with high rendering cost is causing you lag
If you have avatar impostors enabled, mute them. They will be replaced by an impostor, with the effective rendering cost of 1. Their original rendering cost will still be displayed. This is particularly useful on machines that get poor framerates, you can mute high cost avatars to help increase your framerate in crowded areas.
- IMPORTANT NOTE* If you mute someone then you will not see or hear any of their conversation, or messages, and vice versa.