Second Life Wiki - User contributions [en]

Mesh and LOD

2012-10-30T23:52:19Z

Sylvan Mole: /* Low poly modeling */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.

More than you'll Ever need to know about COLLADA.
[http://en.wikipedia.org/wiki/COLLADA]
[https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema]

Second Life COLLADA format spec.
[http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===

*Uploader Generated LODs*

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle count until satisfied with the transition between the LODs
Done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference. [https://wiki.secondlife.com/wiki/Mesh/Upload_Model_UI_reference]

*User created LOD files*

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok[https://wiki.secondlife.com/wiki/Physics_engine] LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export using a .dae COLLADA file.

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal direction. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]
Two spheres. Left: Normals pointing out, Right: Normals pointing in.

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]
Two 5 sided cylinders. Top: Solid Normals. Bottom: Smooth normals.
Note where both cylinders intersect the walls, they show the profile of the actual geometry.

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload.
*Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-30T23:49:02Z

Sylvan Mole: /* Normals */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.

More than you'll Ever need to know about COLLADA.
[http://en.wikipedia.org/wiki/COLLADA]
[https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema]

Second Life COLLADA format spec.
[http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===

*Uploader Generated LODs*

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle count until satisfied with the transition between the LODs
Done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference. [https://wiki.secondlife.com/wiki/Mesh/Upload_Model_UI_reference]

*User created LOD files*

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok[https://wiki.secondlife.com/wiki/Physics_engine] LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export using a .dae COLLADA file.

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal direction. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]
Two spheres. Left: Normals pointing out, Right: Normals pointing in.

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]
Two 5 sided cylinders. Top: Solid Normals. Bottom: Smooth normals.
Note where both cylinders intersect the walls, they show the profile of the actual geometry.

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

File:Normal and flipped normal sphere.png

2012-10-30T23:41:18Z

Sylvan Mole:

File:Smooth cylinder next to not smooth.png

2012-10-30T23:40:14Z

Sylvan Mole:

File:Candlestick.png

2012-10-30T23:36:58Z

Sylvan Mole: uploaded a new version of "File:Candlestick.png"

File:Candlestick.png

2012-10-30T23:34:09Z

Sylvan Mole: uploaded a new version of "File:Candlestick.png"

File:Candlestick.png

2012-10-30T23:31:42Z

Sylvan Mole:

Mesh and LOD

2012-10-30T22:53:13Z

Sylvan Mole: /* Physics */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.

More than you'll Ever need to know about COLLADA.
[http://en.wikipedia.org/wiki/COLLADA]
[https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema]

Second Life COLLADA format spec.
[http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===

*Uploader Generated LODs*

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle count until satisfied with the transition between the LODs
Done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference. [https://wiki.secondlife.com/wiki/Mesh/Upload_Model_UI_reference]

*User created LOD files*

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok[https://wiki.secondlife.com/wiki/Physics_engine] LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export using a .dae COLLADA file.

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal direction. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-30T22:40:00Z

Sylvan Mole: /* Brief Uploader LOD section walk through, two ways */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.

More than you'll Ever need to know about COLLADA.
[http://en.wikipedia.org/wiki/COLLADA]
[https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema]

Second Life COLLADA format spec.
[http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===

*Uploader Generated LODs*

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle count until satisfied with the transition between the LODs
Done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference. [https://wiki.secondlife.com/wiki/Mesh/Upload_Model_UI_reference]

*User created LOD files*

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal dirrection. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-30T22:18:54Z

Sylvan Mole: /* File Format */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.

More than you'll Ever need to know about COLLADA.
[http://en.wikipedia.org/wiki/COLLADA]
[https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema]

Second Life COLLADA format spec.
[http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal dirrection. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T20:23:55Z

Sylvan Mole: /* Physics shapes and how they relate to mesh uploads and LOD */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided faces with respect to the normal dirrection. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:42:13Z

Sylvan Mole: /* Normals */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles but assumes model is Manifold (enclosed in a way that won't encourage views inline with the normal, or are double sided where needed)

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:40:02Z

Sylvan Mole: /* Normals */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes model is Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:37:17Z

Sylvan Mole: /* Level Of Detail */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by an objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:34:23Z

Sylvan Mole: /* Mesh will make Second Life beautiful! */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. Vertices define points in space, their direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:29:24Z

Sylvan Mole: /* Low Poly Texture baking tricks */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

===Low Poly Texture baking tricks===
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:28:23Z

Sylvan Mole: /* Brief Uploader LOD section walk through, two ways */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

===Brief Uploader LOD section walk through, two ways===
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:28:00Z

Sylvan Mole: /* Physics shapes and how they relate to mesh uploads and LOD */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

===Physics shapes and how they relate to mesh uploads and LOD===

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:27:50Z

Sylvan Mole: /* General Havok Physics thoughts and over simplifications */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

===General Havok Physics thoughts and over simplifications===
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:27:21Z

Sylvan Mole: /* Physics shapes and how they relate to mesh uploads and LOD */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:25:31Z

Sylvan Mole: /* Smooth Normals */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

===Smooth Normals===
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:24:44Z

Sylvan Mole:

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:23:27Z

Sylvan Mole: /* Baking textures */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces== this cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:22:55Z

Sylvan Mole: /* Baking textures */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces== ?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:22:19Z

Sylvan Mole: /* Baking textures */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

====Baking textures====
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:22:04Z

Sylvan Mole: /* Projection UV mapping */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

====Projection UV mapping====
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

==Baking textures==
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:21:52Z

Sylvan Mole: /* Standard UV mapping */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

====Standard UV mapping====
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

==Projection UV mapping==
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

==Baking textures==
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:21:34Z

Sylvan Mole: /* General UV mapping techniques */

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

===General UV mapping techniques===

==Standard UV mapping==
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

==Projection UV mapping==
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

==Baking textures==
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

Mesh and LOD

2012-10-17T18:13:44Z

Sylvan Mole: Created page with "Scope: This is to compliment existing information, and links off to avoid too much redundancy. ==Mesh will make Second Life beautiful!== Mesh is of a collection of Vertices, E…"

Scope: This is to compliment existing information, and links off to avoid too much redundancy.

==Mesh will make Second Life beautiful!==

Mesh is of a collection of Vertices, Edges, and Faces that define a 3D shape within computer software.

*The basic element of mesh is a Vertex. A vertices define a points in space, the direction, texture information, and much more.
*Connecting two vertices creates an Edge.
*Connecting a three or four edges together creates a face.
**There are two kinds of faces.
***Triangle faces.
***Quad faces.

[[File:vertices black640.png]]
Three vertices

[[File:edges 640.png]]
Two Edges connecting three vertices

[[File:triangle6401.png]]
Triangle face connecting 3 edges

[[File:quad640.png]]
Quad face connecting 4 edges.

Together they combine to make This!

[[File:Mesh Image640.png]]

==File Format==
Second Life uses COLLADA's 1.4.1 ? file format for the uploading of mesh items.
COLLADA is a powerful open standard collaborative format. The files are in a humanly readable XML format with an extension of .dae.
http://en.wikipedia.org/wiki/COLLADA
https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema
more than you'll Ever need to know about COLLADA.
Second Life COLLADA format spec. [http://wiki.secondlife.com/wiki/Mesh/Mesh_Asset_Format]

==Software==

The list of applications that can create mesh and export to COLLADA is long and exciting!

Here is the short list:

*Maya [http://usa.autodesk.com/maya/]
*3dsMax [http://usa.autodesk.com/3ds-max/]
**Including many other Autodesk tools.
*Blender [http://www.blender.org/]
**Blender history(interesting read) [http://en.wikipedia.org/wiki/Blender_%28software%29]
**additional Second Life Mesh Blender specific tutorials here: [http://blog.machinimatrix.org/] and [http://cgcookie.com]
*Sketchup [http://www.sketchup.com/]
*Wings 3D [http://www.wings3d.com/]
**no UV mapping tool.
*Daz Studio [http://www.daz3d.com/]

Many other software packages can create mesh, though, some may require minor settings adjustments or even external programs to generate .dae files.

Here is the extensive list. [http://wiki.secondlife.com/wiki/Mesh/Tools]

*File Examples in COLLADA .dae file format. [http://wiki.secondlife.com/wiki/Mesh/Sample_Content]

==Further detail and spec.==

==Level Of Detail==

Level Of Detail or LOD is the art of lowering an objects detail as the viewer gets further away. With Mesh uploads we now have complete control over each level.

*The uploader supports 4 LOD levels.
*The uploader will generate LOD levels for you. Which are sufficient, but one can achieve smoother transitions between levels by creating you own LOD models.
*The uploader allows the same file to be used in multiple LOD level slots. This is handy for smaller objects, but use it carefully and wisely.
*LOD culling is affected by the objects scale. A larger object with show a higher LOD level than a smaller one at the same distance. Remember this when creating your LOD models and when uploading.
*Each LOD model must retain all the materials of the highest detailed model. If your model has 8 materials, so must all your LOD models. Ignoring this will result in unpredictable texture location changes.
TIP:ignoring this requirement wont stop the uploader. If you have a model that is displaying textures oddly, look closely at the materials in your LOD files.
*It is also important that the bounding boxes of all the LOD models are identical in size. This keeps the object from changing its scale as it transitions through the LOD levels. Most modeling applications offer up ways to view the bounding box of multiple objects at the same time.

A good general rule to go by when creating LOD models would be to half the poly count of the level above it. For example: If the hero model is 500 poly, the next level should be close to 250 poly, the next 125, and the lowest near 75 poly. This can't be a hard rule, as object size, and use cases have to be taken into account.

Uploading a mesh model step by step
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185]

==Brief Uploader LOD section walk through, two ways==
this should be removed.?(
=Uploader Generated LODs=

*1 Choose Build > Upload > Model...
*2 In the High file slot open select the .dae file on your computer and click Open.
*3 Clicking on the Medium level slot to highlight that level. Highlighting any level displays that levels model in the window to the right. Use the up and down arrows in each level to raise or lower the triangle triangle until satisfied with the transition between the LODs
done! Hit calculate and see if you like the LI count. But don't upload yet! I have more tricks to show you.
For full details on Triangle Limit and Error Threshold, see Upload Model UI reference.

=User created LOD files=

*1 Choose Build > Upload > Model...
*2 In the High LOD slot load the highest detailed model.
*3 In the Medium slot load the second highest LOD model.
*4 In the Low file slot load the second to lowest LOD model
*5 In the Lowest slot load the lowest LOD model.

Hit calculate and see if you like the LI count, but don't upload yet! A physics shape still needs to be assigned.

==Physics==

Second Life supports custom physics shapes. Both uploaded with a mesh object or uploaded independently. This allows for a visually complex object with an low physics impact/cost.

==General Havok Physics thoughts and over simplifications==
Havok LOVES cubes. More than we love chocolate! It doesn't like triangles nearly as much. Here is why. When Havok sees a cube it is optimized to process that cube nearly instantaneously. Conversely, when Havok encounters an object more complex than a cube(even a hollow or cut cube) it then has to count Every Single triangle on that object and ponder what to do with each one. So keep those physics shapes as simple as possible!

==Physics shapes and how they relate to mesh uploads and LOD==

*Creating your own physics shapes in a modeling application is easy.
**Keep the poly count extremely low.
**Make sure the physics shape model fills the bounding box of your model and LODs, or it will not line up with your visual geometry.
**Export is as a .dae COLLADA file. .

The physics tab of the uploader step by step.
[http://community.secondlife.com/t5/English-Knowledge-Base/Uploading-a-mesh-model/ta-p/974185#Section_.5]

This tab allows nearly infinite flexibility. Here is a quick description of the uploader physics tab. This is redundant but is needed to illustrate the importance and usefulness of the Analyze button.

Step 1: Level of Detail
*You can assign any of your LOD levels as the physics shape.
*Or insert a new file for the physics shape.
*Or generate the physics shape right there in the uploader.

Step 2: Analyze
IMPORTANT
*A mesh physics shape uploaded without using the Analyze button will result in the faces being double sided inworld. For instance: a single plane will upload as a double sided wall. A cube will upload as a hollow box. This is useful for creating simple shapes, but also risky as it can create areas that will trap avatars and other physical objects.
*Pressing the Analyze button changes all those double sided faces into single sided with respect to the normal. It also creates a physics shape that acts as a volume. Much like a prim, an Avatar or physical object interpolated with an Analyzed physics shape is neatly pushed out of the volume by Havok.

Step 3: Simplify
*From here you can simplify.
*close holes in more complex shapes. This is useful when using an LOD level for the physics shape.
etc and generate the efficient physics shape that you are after.

The goal should always be a the simplest physics shape possible. Using the uploader tools here to keep the geometry and physics count as low as possible.

==UV mapping==

Anyone who has used the Build Tools inside of Second Life already understands UV mapping, but perhaps under different terminology. UV mapping is simply setting texture repeats(U and V) and offsets. If you look closely at the Build Tools Texture tab you'll see that U and V are used for the texture offset values already. Lean on that familiarity and this concept will come more easily.
(world map image illustrating unwrapped earth)

==General UV mapping techniques==

==Standard UV mapping==
The most common UV map technique divides the mesh surface into neatly flattened sections. Most 3D modeling software packages have this functionality built in. The result is familiar to us and looks like this:
(image of SL face UV map)

UV mapping this way has advantages and disadvantages.
*The shapes created usingthis UV mapping technique makes it easier to visualize how the texture will apply inworld, which makes modifying and drawing on the texture easier.
*Most 3D modeling software packages can be used to generate beautiful textures using this mapping technique(in conjunction with Projection mapping, scene lighting, etc.).
*The disadvantages come in to play with larger or very complex objects. One simple runs out of pixels(or texture space) if trying to flatten a complex object onto one UV map. Large objects often need a seamless repeatable texture.

(image of theater UV with zanny blurry wallpaper.)

==Projection UV mapping==
Projection UV mapping is much like applying textures to a prim object inworld, the goal of UV mapping this way is to scale, rotate, and offset a diffuse texture so the object wears it perfectly.
*The advantage of mapping this way for Second Life is versatility. A house UV mapped this way can wear any number of standard wall, roof, or trim textures.
*The texture can be repeat and offset.
*The texture can be animated.

*disadvantages:
**potential for texture size overuse inworld.
**Models uploaded with projection UV maps can not take advantage of modeling softwares texture baking capability.
(image of wall wearing obvious square textures)

==Baking textures==
An advanced feature of most modeling software packages uses both the Standard UV map and the Projection maps to render an image is sometimes referred to as Baking a texture. The goal is to use all the texture information stored in the Projection maps to create an image that fits the Standard UV map. This render can influenced by any lighting or other objects in the scene.

==Texture Faces==?<11:13, 17 October 2012 (PDT)[[User:Sylvan Mole|Sylvan Mole]] 11:13, 17 October 2012 (PDT)that cant be the right terminology

*Second Life's COLLADA mesh uploader supports up to 8 separate texture faces.
*Each LOD model must all have the same number of Texture faces.
*All the separate faces need to use the same UV map.
*Each modeling software handles this slightly differently. Assigning different areas to different materials archives separate Texture faces on an uploaded Mesh in some modelers, and assigning areas to separate textures achieves this in others. Application specific information [http://wiki.secondlife.com/wiki/Mesh/Uploading_a_multi-face_mesh]

==Normals==
Normal is an adjective that describes something that is perpendicular to a plane. [http://en.wikipedia.org/wiki/Normal_%28geometry%29]
For the scope of this article, normal describes the direction a face is pointing. Most 3d renderers, the Second Life Viewer included, smartly render only one side of a face. This saves cycles. But, assumes models are Manifold, enclosed in a way that won't encourage views inline with the normal, or are double sided where needed.

[[File:normal and flipped normal sphere.png]]

==Smooth Normals==
In the case of a round or curved multiple face surface, a Normal average can be used; which allows an inexpensive surface smoothing. Commonly known as Smooth Normals or Smooth shading, it is an invaluable tool when creating low poly Second Life content.
Smooth Normals allow fewer faces to achieve a visually smooth surface. Far far fewer faces.
For example, a five sided cylinder with smooth normals can appear completely round in Second Life. In some cases, a three sided cylinder will appear perfectly round.

[[File:smooth cylinder next to not smooth.png]]

Applying Smooth Normals to some areas and not to others is another useful for adding detail or highlighting edges.

[[File:candlestick.png]]

==Low poly modeling==

We are not making the next Avatar movie, we are streaming triangles and data near the speed of light. Make sure each and every poly and bit counts.
There are many low poly modeling techniques and software specific tutorials and tools available around the web. [http://en.wikipedia.org/wiki/Low_poly]

The goal should always be to save every triangle everywhere you can on the model you plan to upload. *Ensure that any flat surface uses the least amount of faces as possible.
*Use Smooth Normals to fake smooth curved surfaces.
*Use a low poly rendering tricks to bake detailed textures.

==Low Poly Texture baking tricks==
The idea is to create a very highly detailed model and use it to render gorgeous textures on to a very simple low poly Second Life friendly version.
Making the name low poly modeling slightly deceptive. As you will most likely model and render a very high poly scene. But, the result is a very efficient model with very detailed textures, well poised for incoming Normal and Specular maps.

Most modeling software packages have features built in to facilitate this technique. Look up your favorites', it will be time very well spent.

==Best practices hit list==
*Low poly count.
*Smart UV mapping for efficient texture use and size.
*Smart LOD settings and files.
*Smart appropriately Analyzed simple physic shapes.

File:Mesh Image640.png

2012-10-16T19:49:08Z

Sylvan Mole: mesh image

mesh image

File:Mesh elements.png

2012-10-16T19:45:35Z

Sylvan Mole: mesh elements

mesh elements

File:Quad640.png

2012-10-16T19:38:28Z

Sylvan Mole: quad

quad

File:Triangle6401.png

2012-10-16T19:37:42Z

Sylvan Mole: triangle

triangle

File:Triangle face.jpg

2012-10-16T19:32:59Z

Sylvan Mole: triangle

triangle

File:Edges 640.png

2012-10-16T19:32:39Z

Sylvan Mole: Edges

Edges

File:Vertices black640.png

2012-10-16T19:32:08Z

Sylvan Mole: Vertices

Vertices

Second Life Railroad/SLRR Switch

2010-08-30T16:05:08Z

Sylvan Mole: /* Switch stand signaling diagram */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]

</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train, as the sensors fire only once per second.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.
*I would like to publish the sensor code here, so everyone can verify that their trains are being sensed. Also i would like to post some code showing some examples of data wrangling from the Switch Stand Description.
*Once approved, actual Switch code will be placed here as well.(Sylvan Mole)

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}. Thank You very much Stryker! Information confirmed and minor edits added by {{User2|Sylvan Mole}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Talk:Second Life Railroad/SLRR Switch

2010-08-30T16:02:44Z

Sylvan Mole: /* problem about being noob proof */

On this page you can voice your comments and your own idea about the SLRR Switch concept

--[[User:Stryker Jenkins|Stryker J]] 21:15, 28 December 2009 (UTC)
----
<b>CORRECTION: While desirable, the ability to switch from one track to another on the SLRR is NOT essential. Our locomotives are made of 0s and 1s, not 100 tons of iron, they can be easily moved from one track to another. Also, switches such as the one described here have been available from private SL residents for years. </b>Jer Straaf

<b>CORRECTION TO THE CORRECTION</b>
>>...While desirable, the ability to switch from one track to another on the SLRR is NOT essential...<< <p>
You're right. it isn't essential, but tedious to move the trains by editing them. It is killing a lot of the experience
[[User:Everest Piek|Everest Piek]] 21:36, 29 August 2010 (UTC)

== problem about being noob proof ==

In RL, the switches are signalled as they are built, means, there are always a straight track and a branching track.
the arrow is always showing to the branching track, thats not necessarily a branching <b>Line</b>.
For that, having the signals once this way, once the other way, might be confusing to noobs.
I would plead for having them in a universal way set as the switches are built, as they are signalled in RL.
[[User:Everest Piek|Everest Piek]] 21:43, 29 August 2010 (UTC)

:*There is a little bit of education to be done. I agree with the principle of making sure the switches are all setup the same way. In order to make the switches more Noob friendly the dwarflights are also installed. --[[User:Stryker Jenkins|Stryker J]] 09:32, 30 August 2010 (UTC)

:* Thanks Guys. I will redact my statment under the Signal diagram and build tham as Everest advises. Sylvan
:

Second Life Railroad/SLRR Switch

2010-08-29T16:39:11Z

Sylvan Mole: /* Source */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train, as the sensors fire only once per second.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.
*I would like to publish the sensor code here, so everyone can verify that their trains are being sensed. Also i would like to post some code showing some examples of data wrangling from the Switch Stand Description.
*Once approved, actual Switch code will be placed here as well.(Sylvan Mole)

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}. Thank You very much Stryker! Information confirmed and minor edits added by {{User2|Sylvan Mole}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:36:54Z

Sylvan Mole: /* Scripts */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train, as the sensors fire only once per second.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.
*I would like to publish the sensor code here, so everyone can verify that their trains are being sensed. Also i would like to post some code showing some examples of data wrangling from the Switch Stand Description.
*Once approved, actual Switch code will be placed here as well.(Sylvan Mole)

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}. Confirmed and minor edits added by {{User2|Sylvan Mole}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:27:45Z

Sylvan Mole: /* Source */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train, as the sensors fire only once per second.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}. Confirmed and minor edits added by {{User2|Sylvan Mole}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:25:12Z

Sylvan Mole: /* Sensors and mainline resets */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train, as the sensors fire only once per second.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:23:07Z

Sylvan Mole: /* Switch stand Prim/linkset parameters and changes and data string */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the Switch Stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:22:42Z

Sylvan Mole: /* Basics */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once per second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the switch stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:21:37Z

Sylvan Mole: /* Basics */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train. As sensors fire only once a second.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the switch stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Second Life Railroad/SLRR Switch

2010-08-29T16:19:28Z

Sylvan Mole: /* Switch stand signaling diagram */

{{Help
|Avatar=
|Object=
|LandSim=
|Viewer=
|Community=
|Communication=
|Multimedia=
|Navigation=
|Wiki=
|Glossary=*
|Misc=*
|BugFixes=
|Disclaimer=
|OldInfo=
}}

{{hint
|mode=note
|desc=As with all wiki.secondlife pages that are not [[KB2Wiki#What_is_the_Linden_Lab_Official_namespace.3F | LL Official pages]], this article is open to edit as and when a resident feels it is appropriate (see [[Editing Guidelines]]). If however you simply wish to ask or make a suggestion about or discuss the railroad or the content of this article, please use the [[Talk:Second_Life_Railroad/SLRR_Switch|Talk page]]. The talk page is also where any disputes over proposed page content should be discussed. This Wiki (being a document of an ever changing world) is constantly in need of updating and improvement. If you are aware of information this article should have added/changed please go ahead and do so. If you do not feel confident about editing make the suggestion on the talk page and another contributor may be able to assist.
}}

{|style="width: 100%; font-size: 100%; background: #ffffff; border:1px solid #c0c0c0;"
| align="left"|__TOC__
| <div align="center">
[[Image:Points_ani.gif‎|500px|center]]
</div>
|}
<br />
<div id="box">
==Description==
<div style="padding:0.5em">
The following page describes the working and standards used on the LDPW switch. The SLRR switch is part of the greater SLRR rail network and will be implemented over the next months.
</div></div>

<div id="box">

==Background information==

<div style="padding:0.5em">
On the Northern Continent (Heterocera Atoll) there are a few sections of railway line (see [[Second_Life_Railroad|SLRR Map]] ). Some are under construction and other are in full operation. The [[LDPW]] has started work to get the 'Branch lines' and 'Passing tracks' connected to each other. In order to do this a rail switch was designed by {{User2|Sylvan Mole}}.

The basis for the design of the switch was the concept; "''The switch should work for the greatest number of existing rolling stock''". For that reason the switch is design without active scripts inside the guide rail prims. Most of the parts of the switch are mostly cosmetics. The actual switching is done by changing the (invisible) center guide rail. This is done in such a way that physical trains as well as sensor driven train can use the switch. (see below for more details).

Some SL merchants already have made commercial version of a switch for the Guide rail available. Due to legal reasons the LDPW is not able to use these and therefor opted to make their own system.
</div></div>

<div id="box">

==Drawing==

<div style="padding:0.5em">
====Diagram of Switch parts====

[[File:Points_expl.png|600px|center|Drawing semi automated switch]]
* Guide rail (normally invisible but as example colored in)
*# white normal [[Second_Life_Railroad/SLRR_standards#Standards|Guide rail]]
*# green normal Guide rail on the switch named "'''Guide'''" made '''not phantom''', in other words, made solid
*# red switched off Guide rail and renamed "'''Alternate Guide'''" and made '''phantom'''
* Switch stand
* Sensors
*# A for trains going down the main line, from the merge side toward the heading of the switch
*# B for trains going down the branch line, from the merge side toward the heading of the switch
* Touch start Prim to allow SL Residents to change the switch setting
* Dwarf Signal Lights

====Switch stand signaling diagram====

[[File:SLRR_Switch_Signaling_1024.png|600px|center|Drawing of Swtich stand signaling]]
*In an attempt to keep signaling consistent, all Switch Stand signals will be on the Mainline side of the Switch. Resulting in a Red Switch Stand signal always meaning Mainline and a Yellow signal meaning branch line. This may need to be amended once switches are deployed. (Sylvan Mole)
</div></div>

<div id="box">

==System description==

<div style="padding:0.5em">

===Basics===

*A Guide rail in use (direction of travel, depicted in green)
prim attributes
- prim name: 'Guide'
- NOT phantom
- Material: Glass
- Texture: Transparent
*A Guide rail not in use (switched off, depicted in red)
prim attributes
- prim name: 'Alternate Guide'
- phantom
- Material: Glass
- Texture: Transparent
*Switch Stand Signal rotates 90deg. to reveal appropriate signal. It houses the main scripts that talk to the Guide rail sections as well as the train sensors A and B.
*Sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the [[Second_Life_Railroad/SLRR_standards#SLRR_track_standards|Loading Gauge]]. If a train is detected it will automatically switch to the appropriate setting. However, If you go too fast into a merge they may miss detecting the train.
*Dwarf Signal Lights on the Merge side of the switch display a Green or Red light. A green Dwarf Signal on the side of the merge you are on, means the switch is set correctly. A red Dwarf Signal on the side of the merge you are on, mean switch set incorrectly. Going on past a red light may cause trains to derail.

===Touch Start===

To provide touch support to each switch, there is a larger invisible cube placed over each switch (see drawing: purple box over the switch).<BR>
Simply hover your mouse over the area and click. These are very large and not part of the linkset to avoid LOD and distance rendering issues.

prim attributes
- prim name: 'switch controler'
- prim description: 'say "main" or "branch" on 133' (channel may vary)
- phantom
- size: larger enough to cover the tracks and the 'switch stand'
- Texture: Transparent

===Switch stand Prim/linkset parameters and changes and data string===

prim attributes
- prim name: 'switch stand'
- prim description: (see details below)
- phantom
- linked set: includes switch stand and dwarf signals
- Texture: multiple
- Texture: full bright in parts

Object Description of the switch stand root holds a data string. This data will make it possible for train builders to semi-automate trains / train routes, as well as get enough information to message switches appropriately. i.e. control switches by sending messages 'main' or 'branch' to it.<BR>
String format -Identifier~Status~Heading Name~Mainline Name~Branch Name~messaging channel<BR>
Format uses ~ to separate fields of data and "." to designate hierarchies within fields

Notation example:
SimName.x.y.z~Main~Heading~Mainline~branch~channel

Live example:
Tuliptree.30.42.30~Branch~Calleta Station~TulipTree Station~VRC Yard~133

explanation of the live example:
* The switch is located in Tuliptree/30/42/30
* It is currently set to the branch
* The heading side goes to Calleta Station
* The main side goes to Tuliptree Station
* The branch side goes to VRC Yard
* It listens and talks on channel 133

So in this example the switch is set to the branch line that links the VRC-Yard in Tuliptree to the Calleta Station.

If the switch was turned the other way (to mainline going straight ahead) it would read:
Tuliptree.30.42.30~Main~Calleta Station~TulipTree Station~VRC Yard~133

The data string changes only the Status field during normal operation. The 'Status' field will display "Main" or "Branch" for train builders/scripters to sense and react.

===System messaging===

*All switch systems message on a unique channel published in the Object Description of the switch stand linkset.
*All switch systems listen for the message "main" OR(not and) "branch" on appropriate channel.
*All switch systems [[llShout]] (100 meter) "main" or "branch" on the same channel once switch has completed changes.

This allows signal changes up to 100 meters further up and down line. Including communication between LDPW construct and private installations.

===Sensors and mainline resets===

*Each switch installed on a mainline will reset to the mainline position 2.5 minutes after it is put in the branch position.
*On the merge side of each switch are two sensors. One for each side of the merge. These effectively "Spring" the switch correctly for traffic heading into the merge. When tripped they messages the switch and set it to the correct position.
*The [[llSensor]] scripts are placed in a prim 1.0x0.5x0.5 meter and positioned on/inside the guide rail.
*These sensors look straight up for 4 meters, sensing ACTIVE unflagged, with an arc as wide as the Loading Gauge. However, If you go too fast into a merge they may miss detecting the train.

</div></div>

<div id="box">

==Scripts==

<div style="padding:0.5em">

It is the intention of the LDPW to publish scripts used in the switch setup here in the future.

</div></div>

<div id="box">

==Source==
<div style="padding:0.5em">
The above information was provided by LDPW {{User2|Sylvan Mole}} and edited for the wiki by {{User2|Stryker Jenkins}}.
</div></div>

<div id="box">

==Also See==
<div style="padding:0.5em">
* [[Second_Life_Railroad]] (main page)
* [[Second_Life_Railroad/SLRR_History|SLRR History]]
* [[Second_Life_Railroad/SLRR_standards|SLRR standards]]
* [http://en.wikipedia.org/wiki/Rail_gauge Wikipedia: Rail gauge]
</div></div>

Parks and Recreation Directory

2010-06-28T20:37:30Z

Sylvan Mole:

== Bay City Sites : Urban hangouts for your must-see list! ==

[[Image:Bay_City_Industrial_Park.jpg|right|100px]]
=== Bay City Industrial Park ===
The heart of industry in Bay City for rail to boat traffic.

{{SLURL2|http://slurl.com/secondlife/Inner%20Harbor/32/27/24}}

[[Image:Bay_City_Municipal_Airport.jpg|right|100px]]
=== Bay City Municipal Airport, Hau Koda ===
Hangar, terminal and a runway; the airship mooring tower is just to the south in the Bay City - Docklands Region.

{{SLURL2|http://slurl.com/secondlife/Hau%20Koda/153/23/24}}

[[Image:New_Port_Yacht_Club.jpg|right|100px]]
=== Bay City Yacht Harbor, New Port ===
Yacht club, seaplane ramp, and boat sales slips for lease.

{{SLURL2|http://slurl.com/secondlife/New%20Port/127/236/24}}

[[Image:Bayjou_Theater.jpg|right|100px]]
=== Bayjou Theater, Bay City ===
A home for machinima movies in Bay City.

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Rollers/55/25/24}}

[[Image:Cafe_Deco.jpg|right|100px]]
=== Cafe Deco, Bay City ===
Classy Art Deco Cafe. Cool place to relax, listen to music and have a free coffee!

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Molesworth/73/153/24}}

[[Image:Canal_Park_Municipal_Wading_Pool.jpg|right|100px]]
=== Canal Park and Municipal Wading Pool, Bay City ===
Peaceful park and wading pool in Bay City - Morton

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20 Morton/201/196/24}}

[[Image:Asylum.jpg|right|100px]]
=== Channel Island Asylum, Bay City ===
For all the mad people. Very Scary!!

{{SLURL2|http://slurl.com/secondlife/South%20Channel/169/247/27}}

[[Image:farpoint.jpg|right|100px]]
=== Far Point Park, Bay City Molesworth ===
A geometric park of leafy tranquility, remotely situated for your pleasure and relaxation

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Molesworth/214/199/25}}

[[Image:Hot_Balls_Bowling_Alley.jpg|right|100px]]
=== Hot Balls, Bay City Handa ===
Knock 'em down in Bay City's own bowling alley

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Handa/52/233/25}}

[[Image:The_Lab_in_Bay_City_Moloch.jpg|right|100px]]
=== The Lab in Bay City Moloch ===
A mysterious, abandoned lab. what sort of foul experiments took place here?

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Moloch/133/67/25}}

[[Image:Molexandria.jpg|right|100px]]
=== Molexandria ===
Archeological site in Bay City - Imaginario featuring the Mole-azer, the labryinth, and other fun pursuits

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Imaginario/247/141/24}}

[[Image:Moose_Beach.jpg|right|100px]]
=== Moose Beach Infohub ===
Enjoy the local ambience at Squishybottoms Rock and Roadhouse or grab a table at Scales 'n' Tails.

{{SLURL2|http://slurl.com/secondlife/Moose%20Beach/57/57/24}}

== Route 1 (East-West Heterocera Link Road) : Unmissable items for your travelogue ! ==

[[Image:leafminerdock.jpg|right|100px]]
=== Route 1 sea dock, Leafminer ===

A small access point to the Route 1 highway and Mole Mart

{{SLURL2|http://slurl.com/secondlife/Leafminer/57/16/23}}

[[Image:Mole Mart.jpg|right|100px]]

=== Route 1 Mole Mart, Leafminer ===

Mole Mart ... for all your mole needs
{{SLURL2|http://slurl.com/secondlife/Leafminer/201/138/34}}

[[Image:leafminerpicnic.jpg|right|100px]]

=== Route 1 picnic area ===

A spur off the Route 1 highway near the Mole Mart for Munchies !

{{SLURL2|http://slurl.com/secondlife/Leafminer/246/129/37}}

[[Image:Apple Cart.jpg|right|100px]]

=== Route 1 Apple Cart ===
Try a bucket of apples from the apple cart

{{SLURL2|http://slurl.com/secondlife/Clearwing/136/180/33}}

[[Image:butterfly.jpg|right|100px]]

=== Route 1 Butterfly and Tropical House ===

A calming place to sit amongst the victorian ironwork, dripping with steam and condensation, and consider the exotic butterflies and flowers

{{SLURL2|http://slurl.com/secondlife/Clearwing/112/223/32}}

[[Image:peach pit.jpg|right|100px]]
=== Route 1 Peach Pit ===

Visit the Diner in Peach

{{SLURL2|http://slurl.com/secondlife/Peach/206/164/33}}

[[Image:reservoir.jpg|right|100px]]

=== Route 1 Reservoir, Spini ===

The Molesford Municipal Water company really needs to spend some cash cleaning up this slightly toxic yet still impressive edifice - lots of litter and a few really worrying looking fish - if your keen on angling you'd be advised to just throw them back !

{{SLURL2|http://slurl.com/secondlife/Spini/202/142/31}}

[[Image:parvapicnic.jpg|right|100px]]
=== Route 1 Picnic by the Pond, Parva ===

One of the many minor picnic spots along Route 1 however this one has a few points of interest to explore

{{SLURL2|http://slurl.com/secondlife/Parva/127/62/31}}

[[Image:mormopicnic.jpg|right|100px]]
=== Route 1 Picnic lay-by, Mormo ===

Another example of places to break your journey along the East-West highway, you can park here too !

{{SLURL2|http://slurl.com/secondlife/Mormo/21/135/31}}

[[Image:viewing.jpg|right|100px]]
=== Route 1 Viewing Platform, Sociaria ===

A small platform to enjoy the views.

{{SLURL2|http://slurl.com/secondlife/Sociaria/190/101/34}}

[[Image:town square.jpg|right|100px]]
=== Route 1 Town Square, Menophra ===

Enjoy space of the Town Square.

{{SLURL2|http://slurl.com/secondlife/Menophra/102/103/38}}

[[Image:park.jpg|right|100px]]
=== Route 1 Small roadside park, Menophra ===

A quiet place to sit.

{{SLURL2|http://slurl.com/secondlife/Menophra/245/22/35}}

== Route 2 (North Heterocera Coast Road) : Unmissable items for your travelogue ! ==
Route 2 is just over 13km long. So get out there and explore it today!

[[Image:snoutpoint.jpg|right|100px]]
=== Route 2 Pier and Picnic area, Snout ===

A pier and dock linking the highway to the sea at remote Snout Point, a place to sit at your journey's end (or beginning) and gaze out across the wide ocean

{{SLURL2|http://slurl.com/secondlife/Snout/206/172/22}}

[[Image:satellite-market.jpg|right|100px]]
=== Route 2 Market Square, Satellite ===

A historic market area, currently under regeneration, several traders are trying their hand here already, with doubtless more to come as the highways converge upon this prime location, don't steal from the stalls, you may end up in the stocks !

{{SLURL2|http://slurl.com/secondlife/Satellite/155/13/31}}

[[Image:sallowpicnic.jpg|right|100px]]
=== Route 2 Junction and Picnic Glade, Sallow ===

An island of greenery delineated by a triangular road junction, have a romantic picnic here, screened by the trees

{{SLURL2|http://slurl.com/secondlife/Sallow/173/154/32}}

[[Image:seaviewspur.jpg|right|100px]]
=== Route 2 Seaview Spur, Sallow ===

A turning area and access point to the ocean at the end of a tree-lined cul-de-sac, picnic facilities of course !

{{SLURL2|http://slurl.com/secondlife/Sallow/208/236/32}}

[[Image:tawnybridge.jpg|right|100px]]
=== Route 2 Bridge and pools, Tawny ===

The watercourse has been dammed here in the past, so for the moment the river stream trickles through choked pools and rusty culverts as it passes beneath the arching span of the old bridge

{{SLURL2|http://slurl.com/secondlife/Tawny/233/188/34}}

[[Image:eggarviaduct.jpg|right|100px]]
=== Route 2 Old Viaduct, Eggar ===

Development has raised the level of the land here, and the small valley spanned by the viaduct shows few clues as to it's original purpose, however the arches still provide shelter from the elements for flora and fauna, and it might appear, tramps too !

{{SLURL2|http://slurl.com/secondlife/Eggar/83/107/31}}

[[Image:buffseafront.jpg|right|100px]]
=== Route 2 Great Seawall, Buff ===

Just around the corner from a picnic parking lay-by with panoramic views across Buff Bay, stretches the long stone line of Buff sim's coastal defences. You can stroll onto the short pier and along the boardwalk promenade which offers a bracing ocean breeze on wilder days.

{{SLURL2|http://slurl.com/secondlife/Buff/215/208/30}}

[[Image:buffbridge.jpg|right|100px]]
=== Route 2 River Bridge, Buff ===

Spanning the estuary into Buff Bay, this bridge offers further views from it's relative elevation above the rushing waters

{{SLURL2|http://slurl.com/secondlife/Buff/125/211/32}}

[[Image:arbor.jpg|right|100px]]
=== Route 2 Arboreal Roundabout, Buff ===

Three roads converge here at an old tree of such character and antiquity that a roundabout was constructed around it to preserve it's majesty for all to admire, quite what species it represents has been open to much controversy !

{{SLURL2|http://slurl.com/secondlife/Buff/79/227/29}}

[[Image:quakerironbridge.jpg|right|100px]]
=== Route 2 Iron Bridge, Quaker ===

Although lost in modern development, this relic from the industrial revolution, now spanning little more than a dried up canal basin, has been fully restored and shined up to something of it's former glory, even passing a health and safety audit recently with flying colours !

{{SLURL2|http://slurl.com/secondlife/Quaker/127/20/33}}

[[Image:Ginsberg-zebra.jpg|right|100px]]
=== Route 2 Zebra Crossing, Ginsberg ===

Abbey Road anyone ? ... well, not many zebra crossings in SL but this one links the adjacent gallery and shopping areas either side of the road in Ginsberg, so that prospective visitors are safe from being mown down by cars, juggernauts, mole-tanks, whatever other powered object may be passing through on the busy highway !

{{SLURL2|http://slurl.com/secondlife/Ginsberg/172/181/33}}

[[Image:Ran-boulevard.jpg|right|100px]]
=== Route 2 Ocean Boulevard, Ranunculus ===

The Route 2 highway widens here into a wide boulevard through a large commercial area, close to the ocean, in the far north of the Atoll continent.

{{SLURL2|http://slurl.com/secondlife/Ranunculus/254/32/32}}

[[Image:fillip.jpg|right|100px]]
=== Route 2 Reef Dive, Fillip ===

When you hit the traffic circle in Fillip, put on your swim gear and head north. Explore the fish filled coral reef and a sunken ship, catch a ride with a friendly sea turtle, and possibly even find some treasure!

{{SLURL2|http://slurl.com/secondlife/Fillip/204/187/17}}

[[Image:ROUNDABOUT FILLIP_001.png|right|100px]]
=== Route 2 Warning, Fillip ===

Watch Your Step! As you aproach Fillip Roundabout there are multiple sim crossings!

{{SLURL2|http://slurl.com/secondlife/Fillip/255/10/29/}}

[[Image:AMBROSIA DRIVE_003.png|right|100px]]
=== Route 2 Rezz Zone, Ambrosia ===

Enjoy the various dock areas along the road when you come to rezz your vehicle.

{{SLURL2|http://slurl.com/secondlife/Ambrosia/190/81/30/}}

[[Image:HYDRANGEA BRIDGE RD_006.png|right|100px]]
=== Route 2 Bridge Road, Hydrangea ===

Take a shortcut on the fun bridge road.

{{SLURL2|http://slurl.com/secondlife/Hydrangea/195/216/42/}}

[[Image:HUMMINGBIRD REZZ_007.png|right|100px]]

=== Route 2 Rezz zone, Hummingbird ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Hummingbird/42/64/38/}}

[[Image:DOCKS MOURNFUL-HUCKLEBERRY_008.png|right|100px]]
=== Route 2 Docks, Mournful ===

Enjoy the Docks on the border of Mournful and Huckleberry.

{{SLURL2|http://slurl.com/secondlife/Mournful/19/226/30/}}

[[Image:TIMBER BRIDGE CONSULAR_009.png|right|100px]]
=== Route 2 Timber Bridge, Consular ===

Drive the timber bridge, or enjoy the secret places beneath.

{{SLURL2|http://slurl.com/secondlife/Consular/154/156/32/}}

[[Image:WATER & LAND REZZ ZONES OAKWORM_010.png|right|100px]]
=== Route 2 Rezz Zone, Oakworm ===

Rezz Zones available here for both land and water.

{{SLURL2|http://slurl.com/secondlife/Oakworm/131/161/32/}}

[[Image:PARK OAKWORM-SEDGE_011.png|right|100px]]
=== Route 2 Park, Oakworm ===

Enjoy the park on the border or Oakworm and Sedge.

{{SLURL2|http://slurl.com/secondlife/Oakworm/168/10/33/}}

[[Image:ROCKY OUTCROP SCOOPWING.png|right|100px]]
===Route 2 Park, Scoopwing ===

A rocky outcrop on the water.

{{SLURL2|http://slurl.com/secondlife/Scoopwing/245/204/28/}}

[[Image:WATERFALL DAHANA.png|right|100px]]
=== Route 2 Waterfall, Dahana ===

Quench your thirst along your journey.

{{SLURL2|http://slurl.com/secondlife/Dahana/61/212/32/}}

[[Image:DOCK ECHO.png|right|100px]]
=== Route 2 Dock, Echo ===

A small dock with land and water Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Echo/35/216/29/}}

[[Image:Girdler-bridge.jpg|right|100px]]
=== Route 2 Coastal Falls Crossing, Girdler ===

The coast is broken and steep here, and a bridge takes the highway over a high falls tumbling down from above the road level.

{{SLURL2|http://slurl.com/secondlife/Girdler/104/138/32}}

[[Image:Girdler-view.jpg|right|100px]]
=== Route 2 Ocean View, Girdler ===

The highway turns sharply round the coast here, forming a natural viewpoint over the ocean. A viewpoint and rez zone is here for your use.

{{SLURL2|http://slurl.com/secondlife/Girdler/139/89/31}}

[[Image:Tiger-tunnel.jpg|right|100px]]
[[Image:Tunnel.jpg|right|100px]]
=== Route 2 Tiger - Togata Tunnel, Tiger/Moma/Togata ===

Difficult terrain here necessitated a deep bore through the hillside to link the regions, and a substantial stone lined tunnel exists here to allow free passage. Excavations also opened up a surprise in the hillside !

{{SLURL2|http://slurl.com/secondlife/Tiger/39/18/29}}

{{SLURL2|http://slurl.com/secondlife/Togata/229/239/29}}

[[Image:Togata-view.jpg|right|100px]]
=== Route 2 Ocean Panorama, Togata ===

Another sharp turn in the road to follow the coast opens up a wide vista across open ocean. Travellers may stop and tarry a while here at the viewpoint.

{{SLURL2|http://slurl.com/secondlife/Togata/74/182/29}}

[[Image:Togata-bridge.jpg|right|100px]]
=== Route 2 Oriental Bridge, Togata ===

A wide ocean estuary ravine here requires a bridge to span the gap and an elegant span of vaguely oriental outline performs this task.

{{SLURL2|http://slurl.com/secondlife/Togata/118/97/34}}

[[Image:Emmelia-viaduct.jpg|right|100px]]
=== Route 2 Stone Viaduct, Emmelia ===

A stone viaduct carries the road securely across the ravine into the ocean at Emmelia. A small decrepit dock lies in the waters below for those wishing to go boating.

{{SLURL2|http://slurl.com/secondlife/Emmelia/32/82/31}}

[[Image:R2-west.jpg|right|100px]]
=== Route 2 Western End, Emmelia ===

The western end of the Route 2 link road lies here at a small picnic area, near junction of two roads coming up from the south in Brithys.

{{SLURL2|http://slurl.com/secondlife/Emmelia/26/3/31}}

[[Image: REZZ ZONE MANDUCA.png|right|100px]]
=== Route 2 Rezz Zone, Manduca ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Manduca/189/89/63/}}

[[Image: WOOLYBEAR INTERSECTION.png|right|100px]]
=== Route 2 Intersections, Woolybear ===

A lovely landscaped area in the midst of many intersections.

{{SLURL2|http://slurl.com/secondlife/Woolybear/99/234/88/}}

[[Image: REZZ ZONE AZALEA.png|right|100px]]
=== Route 2 Rezz Zone, Azalea ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Azalea/93/189/79/}}

[[Image: REZZ ZONE ELLO.png|right|100px]]
=== Route 2 Rezz Zone, Ello ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Ello/28/227/65/ }}

== Route 3 (North Heterocera Inland Link) : Unmissable items for your travelogue ! ==

This road lies mainly incomplete at the time of writing, however some sections have so far been completed to provide additional transport links. An example of this is a section joining the major junction at Woolybear in the north to Emmelia on Route 2. This section required some considerable gradient engineering to overcome the differences in altitude between these regions.

[[Image:Emmelia-junc.jpg|right|100px]]
=== Route 3/Route 2 Southern Junction, Emmelia ===

The two routes merge here in a T junction adjacent to the viaduct spanning the ravine.

{{SLURL2|http://slurl.com/secondlife/Emmelia/35/123/32}}

[[Image:Luna-rise.jpg|right|100px]]
=== Route 3 Lower Bank, Lunaris ===

The road ascends a steep bank here rises with the terrain, excellent spot for sledging if it would only snow !

{{SLURL2|http://slurl.com/secondlife/Lunaris/86/12/41}}

[[Image:Luna-bank.jpg|right|100px]]
=== Route 3 Upper Bank, Lunaris ===

A second rise requires a large stone embankment in order to prevent subsidence of the hillside below the woodland above.

{{SLURL2|http://slurl.com/secondlife/Lunaris/181/196/61}}

[[Image:Moma-woods.jpg|right|100px]]
=== Route 3 Hilltop Woodlands, Moma & Tridens ===

The high hill crest at Moma, as well as offering panoramic views of the surrounding area and not-so-distant coast, retains some natural woodland across its border with Tridens. The park also contains small lakes and a pagoda summerhouse in which weary travellers may take a breather. There is a rezzing area here too.

{{SLURL2|http://slurl.com/secondlife/Moma/238/59/75}}

[[Image:Tridens-bridge.jpg|right|100px]]
=== Route 3 Oriental Bridge, Tridens ===

The red oriental bridge at Tridens gracefully mimics its surrounding oriental architecture as does its twin down the ravine in Togata. From the bridge, the road heads due north across undulating terrain towards Woolybear Junction.

{{SLURL2|http://slurl.com/secondlife/Tridens/19/133/77}}

[[Image:woolybear.jpg|right|100px]]
=== Route 3 Main Road ===

The main road along Route 3 begins at the Woolybear intersection and continues to Tussock where the SLRR intersects. This Road is 4.3km long. Below is a list of features you can find along the way.

{{SLURL2|http://slurl.com/secondlife/Woolybear/111/230/86}}

[[Image:Polkadot.jpg|right|100px]]

=== Route 3 Polkadot Park, Polkadot ===

Small stone pathway leads to sunken garden beyond. A place for rest and contemplation.

{{SLURL2|http://slurl.com/secondlife/Polkadot/156/74/98}}

[[Image:riddings_001.jpg|right|100px]]
=== Route 3 Roundabout, Riddings ===

The Roundabout at Riddings provides access to the link road to the Southwest leading to Congrua or a continuation of the main road to Tussock to the East.

{{SLURL2|http://slurl.com/secondlife/Riddings/80/199/101}}

[[Image:riddings_002.jpg|right|100px]]
=== Route 3 Intersection, Riddings ===

This intersection provides access to sims to the South ending at Nitida. This intersection is also a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Riddings/212/181/121}}

[[Image:cisseps.jpg|right|100px]]
=== Route 3 Intersection, Cisseps ===

This intersection provides access to sims to the North ending at Turnip. This intersection is also a Rezz Zone and has a small public square and fountain.

{{SLURL2|http://slurl.com/secondlife/Cisseps/96/33/124}}

[[Image:MUSLIN.jpg|right|100px]]
=== Route 3 Factory, Muslin ===

This intersection includes the Coach and Carriage Company Factory and a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Muslin/180/45/121}}

[[Image:herald.jpg|right|100px]]
=== Route 3 Rezz Zone, Herald ===

Rezz Zone along the Road.

{{SLURL2|http://slurl.com/secondlife/Herald/124/54/119}}

[[Image:Pavonia.jpg|right|100px]]

=== Route 3 Community Hall, Pavonia ===

There is a Community Hall in Pavonia with a Rezz Zone next Door.

{{SLURL2|http://slurl.com/secondlife/Pavonia/182/235/118/}}

[[Image:tussock.jpg|right|100px]]

=== Route 3 Catch the train, Tussock ===

Park your vehicle and catch a train here.

{{SLURL2|http://slurl.com/secondlife/Tussock/89/119/119/}}

[[Image:morrison.jpg|right|100px]]
=== Route 3 Riddings to Congrua connection, Morrison ===

This Road is 840m long with a Rezz Zone along the Road.

{{SLURL2|http://slurl.com/secondlife/Morrison/226/134/99}}

[[Image:astylus.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Astylus ===

This Road is 1.5km with a Rezz Zone along the Road at Astylus.

{{SLURL2|http://slurl.com/secondlife/Astylus/62/43/121}}

[[Image:muralis.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Muralis ===

Muralis contains a few little parks, the largest of these contains a creek for your enjoyment.

{{SLURL2|http://slurl.com/secondlife/Muralis/86/120/125}}

[[Image:Nitida.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Nitida ===

Nitida is currently the end of this road and hosts a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Nitida/86/20/122}}

[[Image:orache.jpg|right|100px]]
=== Route 3 Cisseps to Turnip connection, Orache ===

A Rezz Zone along the road.

{{SLURL2|http://slurl.com/secondlife/Orache/61/242/100}}

== Route 5 : Coastal Byway ==
[[Image:RT5_001.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Xanthorhoe/120/254/31}}

=== Route 5 Public Rez Zones ===
=== Xanthorhoe Train Station ===
[[Image:RT5Rez_001.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Xanthorhoe/136/241/32}}

=== Denrolimus ===
[[Image:RT5Rez_002.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Denrolimus/61/155/31}}

=== Lasiocampa ===
[[Image:RT5Rez_003.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Lasiocampa/93/154/31}}

=== Myron ===
[[Image:RT5Rez_004.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Myron/158/68/32}}

=== Cisthene ===
[[Image:RT5Rez_005.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Cisthene/23/138/33}}

=== Ufeus ===
[[Image:RT5Rez_006.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Ufeus/64/110/32}}

=== Mocis ===
[[Image:RT5Rez_007.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Mocis/91/137/31}}

=== Route 5 Public Boating Areas ===

=== Public Launch area in Xanthorhoe ===
[[Image:RT5_002.jpg|right|100px]]
{{SLURL2|http://slurl.com/secondlife/Xanthorhoe/201/164/31}}

=== Sailing and Surfing Launch area, Scotopteryx ===
[[Image:RT5_05.png|right|100px]]
{{SLURL2|http://slurl.com/secondlife/Scotopteryx/29/134/31}}

== Route 7 (Ring Road around Gaeta) : Take a tour around the whole island ! ==

[[Image:Libestus Pier.jpg|right|100px]]
=== Route 7 Libestus Pier, Libestus ===

Follow the road itself or put in a boat at the end of the pier and explore by sea!

{{SLURL2|http://slurl.com/secondlife/Libestus/236/18/26}}

[[Image:Squall Beach.jpg|right|100px]]
=== Route 7 Squall Public Beach, Squall ===

Relax by the waves or head up the beach to explore Magellan Linden's campsite

{{SLURL2|http://slurl.com/secondlife/Squall/177/207/21}}

[[Image:Hellfell.jpg|right|100px]]
=== Route 7 Helfell Infohub, Helfell ===

Mediterranean vistas abound around this new InfoHub

{{SLURL2|http://slurl.com/secondlife/Helfell/187/123/76}}

[[Image:Gaeta dock.jpg|right|100px]]
=== Route 7 Gaeta docks, (various) ===

These mark the transitions between improved roads and open water canals. Pick up a free LDPW boat here for easy sailing along the canals or other Linden seas.

== Route 8/8A/8B/8C and the Old Wagon Road (The "Japanese" Continent) : Konichiwa! ==

Because of it's shape many call this the "Japanese" continent. With that in mind the roads and public buildings along these roads have an eastern stylistic flair. Originally the roads were supposed to connect, but due to mistakes when the land was divided as the regions were brought online many of the routes end in abrupt dead ends. A system of false tunnels and billboards at dead ends will offer teleports when touched to allow travelers to easily keep exploring the road network without having to backtrack or search the map for where the road picks up again.

[[Image:Bagheera Shelter.jpg|right|100px]]
=== Route 8 Bagheera shelter, Bahheera ===

The Bagheera shelter at the end of the road is the perfect starting point for any exploration of the land. On the back wall is a large map of the continent showing the location of all the main routes; 8, 8A, 8B, 8C, and the Old Wagon Road. Smaller versions of this building exist all along the routes at various points to give explores an idea where they are on the overall map and to provide "rest stops".

{{SLURL2|http://slurl.com/secondlife/Bagheera/63/126/56}}

[[Image:Davros RT8-8C Jct.jpg|right|100px]]
=== Route 8 RT8-8C Junction, Davros ===
Turnoff point for RT8C (still under construction)

{{SLURL2|http://slurl.com/secondlife/Davros/81/71/27}}

[[Image:DavrosFenric bridge.jpg|right|100px]]
=== Route 8 Bridge Out!, Davros/Fenric ===
Look out! The bridge is out! Can you drive fast enough to make the jump? Go ahead and try! ;D

{{SLURL2|http://slurl.com/secondlife/Fenric/178/45/30}}

[[Image:Richfield RT8-8A Jct.jpg|right|100px]]
=== Route 8 RT8-8A Junction, Richfield ===
Southern junction with RT8A. Small rest stop with a lighted lamppost, sitting area and map kiosk.

{{SLURL2|http://slurl.com/secondlife/Richfield/153/186/69}}

[[Image:Cipactli RT8-8B Jct.jpg|right|100px]]
=== Route 8 RT8-8B Junction, Cipactli ===
Connection with RT8B, just south of the Furki Rest Stop on RT8B/8A.

{{SLURL2|http://slurl.com/secondlife/Cipactli/247/58/73}}

[[Image:Toroge Kiosk.jpg|right|100px]]
=== Route 8 Toroge Kiosk, Toroge ===
Westernmost point on the roadmap. Tight curve with an example of one of the small map kiosks.

{{SLURL2|http://slurl.com/secondlife/Toroge/43/85/54}}

[[Image:Bletschorn Tunnel.jpg|right|100px]]
=== Route 8 Bletschorn Tunnel, Bletschorn ===
False tunnel used to bypass Damastock. Touching the lanterns at the tunnel entrance will take you to the other side in Finsteraarhorn.

{{SLURL2|http://slurl.com/secondlife/Bietschhorn/33/47/55}}

[[Image:Finsteraarhorn Tunnel.jpg|right|100px]]
=== Route 8 Finsteraarhorn Tunnel, Finsteraarhorn ===
Mate to the Bletschorn Tunnel. Touching the lanterns at the tunnel entrance will take you to the other side in Bletschorn.

{{SLURL2|http://slurl.com/secondlife/Finsteraarhorn/223/114/29}}

[[Image:Nadelhorn RT8-8A Jct.jpg|right|100px]]
=== Route 8 RT8-8A Junction, Nadelhorn ===
Northern end of RT8A.

{{SLURL2|http://slurl.com/secondlife/Nadelhorn/250/65/50}}

[[Image:Soulgiver Tunnel.jpg|right|100px]]
=== Route 8 Soulgiver Tunnel, Soulgiver ===
End of RT8. Touching the lanterns at the tunnel entrance will take you to RT8C in Ogilvie.

{{SLURL2|http://slurl.com/secondlife/Soulgiver/175/91/65}}

[[Image:Furki Rest Area.jpg|right|100px]]
=== Route 8A Furki Rest Area, Furki ===
Rest area along the junction between RT8A and RT8B in Furki. Plenty of places to sit, relax, and discuss which direction you want to go next! Even has a working traffic light in the intersection.

{{SLURL2|http://slurl.com/secondlife/Furki/47/3/100}}

[[Image:Aragonese Tunnel.jpg|right|100px]]
=== Route 8A Aragonese Tunnel, Aragonese ===
Yep, another false tunnel. This one connects the broken halves of RT8A between Aragonese and Ellingson.

{{SLURL2|http://slurl.com/secondlife/Aragonese/76/183/88}}

[[Image:Horns of Hattin.jpg|right|100px]]

=== Route 8A Falling Rocks, Horns of Hattin ===
One of the most difficult tasks in constructing roads is figuring out what to do in "four corner" areas where the road runs through a spot where 4 regions meet. The region crossings can be very tricky in these spots. It's best to go slow and take the crossings one at a time. In this spot, the fallen rocks divert travelers in a way to guide them through the crossing along the best and least likely to end up crashing the client fashion.

{{SLURL2|http://slurl.com/secondlife/Horns%20of%20Hattin/5/3/68}}

[[Image:Tawa.jpg|right|100px]]
=== Route 8A Tawa Rest Stop, Tawa ===
Small rest area with a couple of benches, a map kiosk and some trees.

{{SLURL2|http://slurl.com/secondlife/Tawa/8/7/82}}

[[Image:Camazotz.jpg|right|100px]]
=== Route 8B Dead end, Camazotz ===
RT8B dead ends in Camazotz with a billboard sign that acts as a teleport link to the Old Wagon Road in Rethymno

{{SLURL2|http://slurl.com/secondlife/Camazotz/12/94/91}}

[[Image:Rethymno.jpg|right|100px]]
=== Old Wagon Road, Rethymno ===
The Old Wagon Road is a two-track unimproved roadway that only spans two regions. At either end are Billboard teleporters to take you other parts of RT8.

{{SLURL2|http://slurl.com/secondlife/Rethymno/18/179/92}}

[[Image:Ellingson.jpg|right|100px]]
=== Route 8A dead end, Ellingson ===
The southern half of Route 8A ends in Eliingson where you will find two teleport billboards offering to let you continue on Route 8A in Aragonese or you can choose to go to Sababurg and take the Old Wagon Road.

{{SLURL2|http://slurl.com/secondlife/Ellingson/193/245/85}}

[[Image:Ogilvie.jpg|right|100px]]
=== Route 8C Ogilvie, Valeyard/Davros ===
False tunnel that allows travelers to connect to RT8 in Soulgiver (if they touch the lantern on the left) or the Old Wagon Road in Sababurg (if they touch the lantern on the right).

{{SLURL2|http://slurl.com/secondlife/Valeyard/83/151/26}}

[[Image:Valeyard.jpg|right|100px]]
=== Route 8C Valeyard/Davros Waterway, Valeyard/Davros ===
Rez a boat and you can travel between Valeyard and Davros just before RT8C meets RT8.

{{SLURL2|http://slurl.com/secondlife/Valeyard/83/151/26}}

== Route 9: Miles of Motoring Fun ==

Still under construction, but already with many interesting sights!

=== Route 9 Lordshore Lookout Point ===

The picnic platform gives a stunning view of the new Lordshore suspension bridge. Built with the latest materials, the bridge is over 400 meters long, with 40 meters of clearance below the main span.

{{SLURL2|http://slurl.com/secondlife/Lordshore/60/61/55}}

== Wellington Road ==
[[Image:WR1_004_001.png|center|thumb]][[Image:WR1_004_002.png|center|thumb]]

Wellington Road begins in Chongno, travels through some lovely mainland areas, and ends in Hangflame Ridge.

{{SLURL2|http://slurl.com/secondlife/Chongno/241/254/77}}

{{SLURL2|http://slurl.com/secondlife/Hangflame%20Ridge/128/70/82}}

----

=== The Great Hill ===
Come try your skateboarding skills!
[[Image:WR1_002.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Noguri/237/196/76}}

Rez zone: {{SLURL2|http://slurl.com/secondlife/Noguri/5/77/99}}

=== Contemplation Bridge ===
Relax and visit with friends.
[[Image:WR1_003.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Pongsonhwa/98/120/105}}

=== Wellington Road Public Rez Zones ===
Lupoff
[[Image:WR1_004_003.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Lupoff/200/154/79}}

Molesworth
[[Image:WR1_004_004.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Molesworth/65/121/73}}

Quoll
[[Image:WR1_004_005.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Quoll/105/80/93}}

Cairnlow
[[Image:WR1_004_006.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Cairnlow/233/66/104}}

Chebi
[[Image:WR1_004_007.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Chebi/189/37/102}}

Noguri
[[Image:WR1_004_008.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Noguri/12/79/98}}

----

----
== Old Route 11 ==
[[Image:Route_11,_Vaktarin_(179,_227,_61).png|right|100px]]
----

A small section of Old Route 11 was discovered in late `09. Wander this raised wooden walkway from Valtarin to Kwaito for a neat surprise.

{{SLURL2|http://slurl.com/secondlife/Vaktarin/15/131/56}}
to

{{SLURL2|http://slurl.com/secondlife/Kwaito/243/239/42}}

----

== Route 11 ==
A wonky wooden and rough cobble stone tree lined road meandering though the continent. Rising from water level to over 100 meters high, Route 11 gives a variety of interesting views. From coastal to high mountains, from bridges to boat ramps, Route 11 has it all!

== Route 11 rez zone and boat ramp ==
[[Image:Route_11_(rez_zone),_Passendale.png|right|100px]]
Though Route 11 does start a bit further South West, it has long been flooded. Here is the first rez zone and boat ramp.

{{SLURL2|http://slurl.com/secondlife/Passendale/85/138/41}}

== Route 11 Amphibious Vehicle dunking zone ==
[[Image:Route_11_Gorgonzola_001.png|right|100px]]
Bring your amphibious vehicle, due to wildlife and oceanfront living, the road gets a bit wet here =D

{{SLURL2|http://slurl.com/secondlife/Gorgonzola/73/53/19}}

== Route 11 Down Hill Race Start ==
[[Image:Route_11_Blacksticks.png|right|100px]]
Top of the first rise. Ready to be raced down in either direction. =)

{{SLURL2|http://slurl.com/secondlife/Blacksticks/159/106/113}}

== Route 11 Rez Zone ==
[[Image:Route_11_Castlederg.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Castlederg/11/101/110}}

== Route 11 Rez Zone in Ironstorm ==
[[Image:Route_11_Ironstorm.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Ironstorm/13/19/70}}

== Route 11 Intersection to Magellan Pass ==
[[Image:Route_11_Muskeg.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Muskeg/153/126/53}}

== Route 11 Magellan Pass ==
[[Image:Route_11_Magellan_Pass.png|right|100px]]
A fast shortcut over the top of the mountains, discovered by our intrepid explorer himself.

{{SLURL2|http://slurl.com/secondlife/Sweet%20Morass/172/115/74}}

== Route 11 Moley's Fruit Stand and Nature Walk==
[[Image:Route_11_Fruit_Stand.png|right|100px]]
Moley says, Eat your fruit! While relaxing in the nature area.

{{SLURL2|http://slurl.com/secondlife/Westerlay/230/192/34}}

== Route 11 Floating Road and Drawbridge ==
[[Image:Route_11_Bogatanta.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Bogatanta/180/219/21}}

== Route 11 Magellan Pass (other end) ==
[[Image:Route_11_Mordus_Hall.png|right|100px]]
The Western end of Magellan Pass

{{SLURL2|http://slurl.com/secondlife/Mordus%20Hall/206/89/62}}

== Route 11 Downhill Race Start Two ==
[[Image:Route_11_Roclaren.png|right|100px]]
Yet another fun hill to race down =D

{{SLURL2|http://slurl.com/secondlife/Claremorris/194/140/116}}

== Route 11 Boat Ramp and End ==
[[Image:Route_11_Paneer.png|right|100px]]
Though Route 11 does continue to the South, it has long been flooded and re-purposed into waterways. Launch your boat here to continue the adventure!

{{SLURL2|http://slurl.com/secondlife/Paneer/184/47/22}}
----

== Route 12 ==
[[Image:RT12 Overview Map.png|right|100px]]
Route 12 is made for exploring from sea to shining sea, from the sandy beaches of the shore to the grassy hills of the interior to the rough mountain trails of the northern penninsula. This road is calling out for adventurous avatars looking to explore a continent. Along that way you will find billboards like the one here. These maps give a topographical overview of the continent and the road itself. A red star indicates your current location. The gold stars indicate points to which you can teleport. Touching the gold star will open the map. This give explorers the ability to easily navigate to parts of the route not yet explored.

[[Image:Beatrice RT12.png|right|100px]]
=== Route 12 Beatrice Rest Stop, Beatrice ===

Close to the shores of the southwestern penninsula the rest stop in Beatrice is spartan. Little more than a few trees and a bench it is a turn around point and place to sit and contemplate which part of the continent you want to visit next.

{{SLURL2|http://slurl.com/secondlife/Beatrice/134/184/34}}

[[Image:Dreyfus RT12.png|right|100px]]
=== Route 12 Dreyfus Crossroads, Dreyfus ===

The interesection in Dreyfus is nestled in the green hills of the continent. West is the road along the western shore to Beatrice. North is the climb over the hills toward the hairpin curve in Jaxipun and on to the off road trail on the northern point.

{{SLURL2|http://slurl.com/secondlife/Dreyfus/29/171/50}}

[[Image:Clinker RT12.png|right|100px]]
=== Route 12 Clinker END OF PAVED ROAD, Clinker ===

Just over the bridge in Elsa is the end of paved road. The rest of RT12 to the north is an unimproved dirt trail with steep hills, rocks, and undergrowth blocking the way. A pleasant walking or horseback riding trail the route is not recommended for large vehicles with a wide track or low clearance. 4x4 trucks and off road vehicles should do fine. Test your offroading skill on this one!

{{SLURL2|http://slurl.com/secondlife/Clinker/166/121/68}}

[[Image:Pouncival RT12.png|right|100px]]
=== Route 12 Pouncival Roundabout, Pouncival ===

In Pouncival RT12 double backs on itself as the trail from Clinker snakes around the hilly terrain that makes up the northwest penninsula. To the north is a hill that will give even the best SL 4x4 a run for its money as you try to navigate around the switchback of boulders strewn in your path. Crest the hill and you're on your way through around the circuit of shear drops and undulating hills and back around to where you started.

{{SLURL2|http://slurl.com/secondlife/Pouncival/165/63/44}}

[[Image:Donalbain RT12.png|right|100px]]
=== Route 12 Donalbain Crossroads, Donalbain ===

The only other crossroads on RT12 Donalbain is rougly the halfway point. To the south is the short route leading to the endpoint at Camorro.

{{SLURL2|http://slurl.com/secondlife/Donalbain/27/209/47}}

[[Image:Camorro RT12.png|right|100px]]
=== Route 12 Camorro End, Camorro ===

Endpoint of the southern branch of RT12 from Donalbain.

{{SLURL2|http://slurl.com/secondlife/Camorro/250/12/50}}

[[Image:Fenstriano RT12.png|right|100px]]
=== Route 12 Fenstriano Curve, Fenstriano ===

Rest point between the western half of RT12 and the east, Fenstriano is a good place to take stock in your transcontinental journey.

{{SLURL2|http://slurl.com/secondlife/Fenstriano/157/7/38}}

[[Image:Rannveig RT12.png|right|100px]]
=== Route 12 Rannveig End, Rannveig ===

Final endpoint of RT12 in the east. Now to decide if you telport to another part RT12 or do you once more navigate the hills and curves backtoward the west.

{{SLURL2|http://slurl.com/secondlife/Rannveig/205/12/36}}

== Miscellaneous Mainland Points of Interest for Intrepid Explorers ==

=== Playground Ship on DaBoom ===

big maritime playground with freebies

{{SLURL2|http://slurl.com/secondlife/Da%20Boom/165/134/35}}

=== Playground on Rivula ===

cute little playground

{{SLURL2|http://slurl.com/secondlife/Rivula/195/56/34}}

=== Juice Bar, Brownlee ===

Keeping residents healthy with a Contemporary Juice Bar. Free Smoothies!

{{SLURL2|http://slurl.com/secondlife/Brownlee/209/150/105}}

=== The Volcano Island, Ichelus ===

A tropical Tiki village and exploding Volcano!!

{{SLURL2|http://slurl.com/secondlife/Ichelus/142/192/23}}

=== LDPW Showcase Conference Center, Boardroom ===

For the business types of the grid. Two modern style buildings ready to accomodate medium to large meetings/conferences.

{{SLURL2|http://slurl.com/secondlife/Boardroom/113/113/25/}}

=== Castle Valeria ===

A romantic interpretation of a medieval German castle; also, a pirate lair!

{{SLURL2|http://slurl.com/secondlife/Castle%20Valeria/175/196/68}}

=== Mos Ainsley ===

In space, no one can hear you type ... experience the far future at the base on Mos Ainsley. Spacesuits available for all!

{{SLURL2|http://slurl.com/secondlife/Mos%20Ainsley/134/131/48}}

[[Image:Pruni.jpg|right|100px]]
=== Pruni Park ===

Small wild and overgrown area with pool, treehouse and campfire areas.

{{SLURL2|http://slurl.com/secondlife/Pruni/73/217/62}}

[[Image:Bhima.jpg|right|100px]]
=== Bhima Lido Hall ===

Lido Hall with music, and patio with conversational areas.

{{SLURL2|http://slurl.com/secondlife/Bhima/143/97/39}}

[[Image:Ahab's_Haunt.jpg|right|100px]]
=== Ahab's Haunt ===

This is a tropical beach crowned by the skeleton of a giant beast. Hammocks and inner tubes, undersea treasure and lots to explore for divers, places to rezz your boats, and more!

{{SLURL2|http://slurl.com/secondlife/Ahab's%20Haunt/116/143/22}}

== Nautilus ==

This ancient city has recently been discovered. Mysterious crystals, a temple, assembly hall, and palace surround a large pool.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Malchus/9/29/72}}

... and a large park:

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Baal/72/140/23}}

... and a harbor, with a nearby market:

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Yamm/114/205/22}}

=== Highlights around the Great City of Nautilus ===

[[Image:Pharos.jpg|right|100px]]
[[Image:Pharos1.jpg|right|100px]]
[[Image:Pharos2.jpg|right|100px]]
[[Image:Pharos3.jpg|right|100px]]

=== The Pharos, Nautilus-Byth ===

As intrepid seafarers approach the great water channel leading to the ancient city; strange flickering beams in the sky, followed by a sighting of a lofty tower, alert them to the presence of the treacherous Nautilean coast. This large beam-house is The Pharos, and was constructed as a navigational aid replacing a much smaller crystal beacon, the ruins of which may still be seen on a nearby outcrop. Statues of sea creatures festoon the terraces of the Pharos, whilst a large idol of Hydraea, Goddess of the Sea, faces out to the Western Sea, both embracing friend and threatening foe with upraised hands. At the top of the tower rests the main lamp house where crystal energy passes through deflection grids to be streamed out to the cardinal points of the compass, clearly visible for many miles. Halfway up the tower, within a small open chamber at the top of the great stairway, is a focussing relay crystal which controls the nature of the Pharos' beam to suit the prevailing weather conditions.

Inside the great hall at the foot of the structure lies the main crystal reactor, within a deep containment pit surrounded by an energy screen. On one side of the barriers stands the console containing the control array and spectral coolant rods. As a protection against power overload, the reactor is gated to the sea via an internal pool and underwater tunnel, so that in the event of such an emergency, it may be flooded with seawater and extinguished. This pool should be empty and serene, however the Pharos has gained an 'unofficial' resident during some phase of it's existence. A rogue scientist fell from favour with the council of Nautilean elders due to his somewhat aggressive and more than a little xenophobic attitudes toward foreign trade, building crystal powered mechanical sea boats to disrupt passing trade and seize wealth for himself. Exiled from the main citadel he barricaded himself inside the Pharos, settling inside the main chamber where he constructed a new vessel within the confines of the coolant pool, periodically venturing forth from his lair via the sea tunnel to harry vulnerable shipping and steal supplies. This undoubtedly resourceful individual was apparently not immune to the mysterious cataclysm which afflicted Nautilus in the distant past, indeed some enigmatic writings discovered within the chamber suggest he may actually have been instrumental in hastening its effects, and all that may now be seen to mark his occupancy are his last and greatest undersea vessel, a variety of somewhat incongruously added docking structures, and a scatter of books dealing with a variety of arcane and eclectic topics. Judging by the compact size of his vessel, the physical stature of the Professor did not in any way match that of his mind !

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Byth/3/191/23}}

[[Image:Baal.jpg|right|100px]]

=== Baal Public Park, Nautilus-Baal ===

Nautilus sports a pair of public parks adjacent to the canal bank. Furthest east lies Baal Park, which contains a small seating area where one may sit and watch crystal particle beam displays, and also a small secluded pool for relaxation and contemplation known as 'The Eye of Baal', the reason for which may be clearly seem when viewing the feature from the air.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Baal/69/176/22}}

[[Image:Kothar.jpg|right|100px]]

=== Kothar Public Park, Nautilus-Kothar ===

The second park is located immediately adjacent within the Kothar district and contains a large outdoor public pool and thermal spa area alongside stone walkways. This location, in addition to the wild vegetation and arboreta common to both parks, also features a large outdoor mechanical chess set, the workings of which have yet to be precisely discovered, and a natural pool within which sits a small island upon which is sited a monument of unknown assignation.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Kothar/3/186/22}}

[[Image:Nautilus-gate.jpg|right|100px]]

=== City Sea Gate, Nautilus-Melqart ===

Two enormous bronze gates close the sea channel against hazards where it enters the great citadel wall. These may be swung open and shut, forming a bright star in the centre which acts as a night beacon when they are closed against entry.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Melqart/83/228/25}}

[[Image:Nautilus-canal.jpg|right|100px]]

=== The Canal, Nautilus ===

The deep channel of The Great Canal extends from the Citadel due east, and straight as a die, to the ocean, which it meets at the turbulent waters surrounding the Pharos. The channel has become home to various flora and fauna over the years.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Elissa/129/6/10}}

=== Magellan Linden's Mole Tank, Nautilus-Mysehi ===

Technically his "atomic boring machine". This 4000 ton vehicle was constructed by the LDPW moles to Magellan's specifications; powered by a 500 megawatt fission reactor, it can slowly burrow below the terrain surface. Magellan used it only once, to cross under the strange dome or shield which hid and protected the city of Nautilus.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Mysehi/110/40/23}}

== The Blake Sea ==

Connecting the Mainland to the United Sailing Sims is the Blake Sea, venue for exciting boat races and other nautical activity! A few islands exist in the Blake Sea; some of them are:

=== Half Hitch ===

A picturesque fishing village.

{{SLURL2|http://slurl.com/secondlife/Blake%20Sea%20-%20Half%20Hitch/120/136/22}}

=== Windlass ===

Tropical resort.

{{SLURL2|http://slurl.com/secondlife/Blake%20Sea%20-%20Windlass/176/42/25}}

Other islands in the Blake Sea harbor smugglers, castaways, and sea creatures galore!

[[Image:Wikitipi.gif|Save to wikiTiPi]]
[http://www.wikitipi.com/cgi-bin/wp.cgi?http://wiki.secondlife.com/wiki/Parks_and_Recreation_Directory Copy all locations to my wikiTiPi HUD]

[[Category:LDPW]]

Parks and Recreation Directory

2010-06-28T20:34:38Z

Sylvan Mole: /* Route 11 Downhill Race Start Two */

File:Route 11 Paneer.png

2010-06-28T20:33:43Z

Sylvan Mole:

Parks and Recreation Directory

2010-06-28T20:28:15Z

Sylvan Mole: /* Route 11 Downhill Race Start Two */

== Bay City Sites : Urban hangouts for your must-see list! ==

[[Image:Bay_City_Industrial_Park.jpg|right|100px]]
=== Bay City Industrial Park ===
The heart of industry in Bay City for rail to boat traffic.

{{SLURL2|http://slurl.com/secondlife/Inner%20Harbor/32/27/24}}

[[Image:Bay_City_Municipal_Airport.jpg|right|100px]]
=== Bay City Municipal Airport, Hau Koda ===
Hangar, terminal and a runway; the airship mooring tower is just to the south in the Bay City - Docklands Region.

{{SLURL2|http://slurl.com/secondlife/Hau%20Koda/153/23/24}}

[[Image:New_Port_Yacht_Club.jpg|right|100px]]
=== Bay City Yacht Harbor, New Port ===
Yacht club, seaplane ramp, and boat sales slips for lease.

{{SLURL2|http://slurl.com/secondlife/New%20Port/127/236/24}}

[[Image:Bayjou_Theater.jpg|right|100px]]
=== Bayjou Theater, Bay City ===
A home for machinima movies in Bay City.

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Rollers/55/25/24}}

[[Image:Cafe_Deco.jpg|right|100px]]
=== Cafe Deco, Bay City ===
Classy Art Deco Cafe. Cool place to relax, listen to music and have a free coffee!

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Molesworth/73/153/24}}

[[Image:Canal_Park_Municipal_Wading_Pool.jpg|right|100px]]
=== Canal Park and Municipal Wading Pool, Bay City ===
Peaceful park and wading pool in Bay City - Morton

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20 Morton/201/196/24}}

[[Image:Asylum.jpg|right|100px]]
=== Channel Island Asylum, Bay City ===
For all the mad people. Very Scary!!

{{SLURL2|http://slurl.com/secondlife/South%20Channel/169/247/27}}

[[Image:farpoint.jpg|right|100px]]
=== Far Point Park, Bay City Molesworth ===
A geometric park of leafy tranquility, remotely situated for your pleasure and relaxation

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Molesworth/214/199/25}}

[[Image:Hot_Balls_Bowling_Alley.jpg|right|100px]]
=== Hot Balls, Bay City Handa ===
Knock 'em down in Bay City's own bowling alley

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Handa/52/233/25}}

[[Image:The_Lab_in_Bay_City_Moloch.jpg|right|100px]]
=== The Lab in Bay City Moloch ===
A mysterious, abandoned lab. what sort of foul experiments took place here?

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Moloch/133/67/25}}

[[Image:Molexandria.jpg|right|100px]]
=== Molexandria ===
Archeological site in Bay City - Imaginario featuring the Mole-azer, the labryinth, and other fun pursuits

{{SLURL2|http://slurl.com/secondlife/Bay%20City%20-%20Imaginario/247/141/24}}

[[Image:Moose_Beach.jpg|right|100px]]
=== Moose Beach Infohub ===
Enjoy the local ambience at Squishybottoms Rock and Roadhouse or grab a table at Scales 'n' Tails.

{{SLURL2|http://slurl.com/secondlife/Moose%20Beach/57/57/24}}

== Route 1 (East-West Heterocera Link Road) : Unmissable items for your travelogue ! ==

[[Image:leafminerdock.jpg|right|100px]]
=== Route 1 sea dock, Leafminer ===

A small access point to the Route 1 highway and Mole Mart

{{SLURL2|http://slurl.com/secondlife/Leafminer/57/16/23}}

[[Image:Mole Mart.jpg|right|100px]]

=== Route 1 Mole Mart, Leafminer ===

Mole Mart ... for all your mole needs
{{SLURL2|http://slurl.com/secondlife/Leafminer/201/138/34}}

[[Image:leafminerpicnic.jpg|right|100px]]

=== Route 1 picnic area ===

A spur off the Route 1 highway near the Mole Mart for Munchies !

{{SLURL2|http://slurl.com/secondlife/Leafminer/246/129/37}}

[[Image:Apple Cart.jpg|right|100px]]

=== Route 1 Apple Cart ===
Try a bucket of apples from the apple cart

{{SLURL2|http://slurl.com/secondlife/Clearwing/136/180/33}}

[[Image:butterfly.jpg|right|100px]]

=== Route 1 Butterfly and Tropical House ===

A calming place to sit amongst the victorian ironwork, dripping with steam and condensation, and consider the exotic butterflies and flowers

{{SLURL2|http://slurl.com/secondlife/Clearwing/112/223/32}}

[[Image:peach pit.jpg|right|100px]]
=== Route 1 Peach Pit ===

Visit the Diner in Peach

{{SLURL2|http://slurl.com/secondlife/Peach/206/164/33}}

[[Image:reservoir.jpg|right|100px]]

=== Route 1 Reservoir, Spini ===

The Molesford Municipal Water company really needs to spend some cash cleaning up this slightly toxic yet still impressive edifice - lots of litter and a few really worrying looking fish - if your keen on angling you'd be advised to just throw them back !

{{SLURL2|http://slurl.com/secondlife/Spini/202/142/31}}

[[Image:parvapicnic.jpg|right|100px]]
=== Route 1 Picnic by the Pond, Parva ===

One of the many minor picnic spots along Route 1 however this one has a few points of interest to explore

{{SLURL2|http://slurl.com/secondlife/Parva/127/62/31}}

[[Image:mormopicnic.jpg|right|100px]]
=== Route 1 Picnic lay-by, Mormo ===

Another example of places to break your journey along the East-West highway, you can park here too !

{{SLURL2|http://slurl.com/secondlife/Mormo/21/135/31}}

[[Image:viewing.jpg|right|100px]]
=== Route 1 Viewing Platform, Sociaria ===

A small platform to enjoy the views.

{{SLURL2|http://slurl.com/secondlife/Sociaria/190/101/34}}

[[Image:town square.jpg|right|100px]]
=== Route 1 Town Square, Menophra ===

Enjoy space of the Town Square.

{{SLURL2|http://slurl.com/secondlife/Menophra/102/103/38}}

[[Image:park.jpg|right|100px]]
=== Route 1 Small roadside park, Menophra ===

A quiet place to sit.

{{SLURL2|http://slurl.com/secondlife/Menophra/245/22/35}}

== Route 2 (North Heterocera Coast Road) : Unmissable items for your travelogue ! ==
Route 2 is just over 13km long. So get out there and explore it today!

[[Image:snoutpoint.jpg|right|100px]]
=== Route 2 Pier and Picnic area, Snout ===

A pier and dock linking the highway to the sea at remote Snout Point, a place to sit at your journey's end (or beginning) and gaze out across the wide ocean

{{SLURL2|http://slurl.com/secondlife/Snout/206/172/22}}

[[Image:satellite-market.jpg|right|100px]]
=== Route 2 Market Square, Satellite ===

A historic market area, currently under regeneration, several traders are trying their hand here already, with doubtless more to come as the highways converge upon this prime location, don't steal from the stalls, you may end up in the stocks !

{{SLURL2|http://slurl.com/secondlife/Satellite/155/13/31}}

[[Image:sallowpicnic.jpg|right|100px]]
=== Route 2 Junction and Picnic Glade, Sallow ===

An island of greenery delineated by a triangular road junction, have a romantic picnic here, screened by the trees

{{SLURL2|http://slurl.com/secondlife/Sallow/173/154/32}}

[[Image:seaviewspur.jpg|right|100px]]
=== Route 2 Seaview Spur, Sallow ===

A turning area and access point to the ocean at the end of a tree-lined cul-de-sac, picnic facilities of course !

{{SLURL2|http://slurl.com/secondlife/Sallow/208/236/32}}

[[Image:tawnybridge.jpg|right|100px]]
=== Route 2 Bridge and pools, Tawny ===

The watercourse has been dammed here in the past, so for the moment the river stream trickles through choked pools and rusty culverts as it passes beneath the arching span of the old bridge

{{SLURL2|http://slurl.com/secondlife/Tawny/233/188/34}}

[[Image:eggarviaduct.jpg|right|100px]]
=== Route 2 Old Viaduct, Eggar ===

Development has raised the level of the land here, and the small valley spanned by the viaduct shows few clues as to it's original purpose, however the arches still provide shelter from the elements for flora and fauna, and it might appear, tramps too !

{{SLURL2|http://slurl.com/secondlife/Eggar/83/107/31}}

[[Image:buffseafront.jpg|right|100px]]
=== Route 2 Great Seawall, Buff ===

Just around the corner from a picnic parking lay-by with panoramic views across Buff Bay, stretches the long stone line of Buff sim's coastal defences. You can stroll onto the short pier and along the boardwalk promenade which offers a bracing ocean breeze on wilder days.

{{SLURL2|http://slurl.com/secondlife/Buff/215/208/30}}

[[Image:buffbridge.jpg|right|100px]]
=== Route 2 River Bridge, Buff ===

Spanning the estuary into Buff Bay, this bridge offers further views from it's relative elevation above the rushing waters

{{SLURL2|http://slurl.com/secondlife/Buff/125/211/32}}

[[Image:arbor.jpg|right|100px]]
=== Route 2 Arboreal Roundabout, Buff ===

Three roads converge here at an old tree of such character and antiquity that a roundabout was constructed around it to preserve it's majesty for all to admire, quite what species it represents has been open to much controversy !

{{SLURL2|http://slurl.com/secondlife/Buff/79/227/29}}

[[Image:quakerironbridge.jpg|right|100px]]
=== Route 2 Iron Bridge, Quaker ===

Although lost in modern development, this relic from the industrial revolution, now spanning little more than a dried up canal basin, has been fully restored and shined up to something of it's former glory, even passing a health and safety audit recently with flying colours !

{{SLURL2|http://slurl.com/secondlife/Quaker/127/20/33}}

[[Image:Ginsberg-zebra.jpg|right|100px]]
=== Route 2 Zebra Crossing, Ginsberg ===

Abbey Road anyone ? ... well, not many zebra crossings in SL but this one links the adjacent gallery and shopping areas either side of the road in Ginsberg, so that prospective visitors are safe from being mown down by cars, juggernauts, mole-tanks, whatever other powered object may be passing through on the busy highway !

{{SLURL2|http://slurl.com/secondlife/Ginsberg/172/181/33}}

[[Image:Ran-boulevard.jpg|right|100px]]
=== Route 2 Ocean Boulevard, Ranunculus ===

The Route 2 highway widens here into a wide boulevard through a large commercial area, close to the ocean, in the far north of the Atoll continent.

{{SLURL2|http://slurl.com/secondlife/Ranunculus/254/32/32}}

[[Image:fillip.jpg|right|100px]]
=== Route 2 Reef Dive, Fillip ===

When you hit the traffic circle in Fillip, put on your swim gear and head north. Explore the fish filled coral reef and a sunken ship, catch a ride with a friendly sea turtle, and possibly even find some treasure!

{{SLURL2|http://slurl.com/secondlife/Fillip/204/187/17}}

[[Image:ROUNDABOUT FILLIP_001.png|right|100px]]
=== Route 2 Warning, Fillip ===

Watch Your Step! As you aproach Fillip Roundabout there are multiple sim crossings!

{{SLURL2|http://slurl.com/secondlife/Fillip/255/10/29/}}

[[Image:AMBROSIA DRIVE_003.png|right|100px]]
=== Route 2 Rezz Zone, Ambrosia ===

Enjoy the various dock areas along the road when you come to rezz your vehicle.

{{SLURL2|http://slurl.com/secondlife/Ambrosia/190/81/30/}}

[[Image:HYDRANGEA BRIDGE RD_006.png|right|100px]]
=== Route 2 Bridge Road, Hydrangea ===

Take a shortcut on the fun bridge road.

{{SLURL2|http://slurl.com/secondlife/Hydrangea/195/216/42/}}

[[Image:HUMMINGBIRD REZZ_007.png|right|100px]]

=== Route 2 Rezz zone, Hummingbird ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Hummingbird/42/64/38/}}

[[Image:DOCKS MOURNFUL-HUCKLEBERRY_008.png|right|100px]]
=== Route 2 Docks, Mournful ===

Enjoy the Docks on the border of Mournful and Huckleberry.

{{SLURL2|http://slurl.com/secondlife/Mournful/19/226/30/}}

[[Image:TIMBER BRIDGE CONSULAR_009.png|right|100px]]
=== Route 2 Timber Bridge, Consular ===

Drive the timber bridge, or enjoy the secret places beneath.

{{SLURL2|http://slurl.com/secondlife/Consular/154/156/32/}}

[[Image:WATER & LAND REZZ ZONES OAKWORM_010.png|right|100px]]
=== Route 2 Rezz Zone, Oakworm ===

Rezz Zones available here for both land and water.

{{SLURL2|http://slurl.com/secondlife/Oakworm/131/161/32/}}

[[Image:PARK OAKWORM-SEDGE_011.png|right|100px]]
=== Route 2 Park, Oakworm ===

Enjoy the park on the border or Oakworm and Sedge.

{{SLURL2|http://slurl.com/secondlife/Oakworm/168/10/33/}}

[[Image:ROCKY OUTCROP SCOOPWING.png|right|100px]]
===Route 2 Park, Scoopwing ===

A rocky outcrop on the water.

{{SLURL2|http://slurl.com/secondlife/Scoopwing/245/204/28/}}

[[Image:WATERFALL DAHANA.png|right|100px]]
=== Route 2 Waterfall, Dahana ===

Quench your thirst along your journey.

{{SLURL2|http://slurl.com/secondlife/Dahana/61/212/32/}}

[[Image:DOCK ECHO.png|right|100px]]
=== Route 2 Dock, Echo ===

A small dock with land and water Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Echo/35/216/29/}}

[[Image:Girdler-bridge.jpg|right|100px]]
=== Route 2 Coastal Falls Crossing, Girdler ===

The coast is broken and steep here, and a bridge takes the highway over a high falls tumbling down from above the road level.

{{SLURL2|http://slurl.com/secondlife/Girdler/104/138/32}}

[[Image:Girdler-view.jpg|right|100px]]
=== Route 2 Ocean View, Girdler ===

The highway turns sharply round the coast here, forming a natural viewpoint over the ocean. A viewpoint and rez zone is here for your use.

{{SLURL2|http://slurl.com/secondlife/Girdler/139/89/31}}

[[Image:Tiger-tunnel.jpg|right|100px]]
[[Image:Tunnel.jpg|right|100px]]
=== Route 2 Tiger - Togata Tunnel, Tiger/Moma/Togata ===

Difficult terrain here necessitated a deep bore through the hillside to link the regions, and a substantial stone lined tunnel exists here to allow free passage. Excavations also opened up a surprise in the hillside !

{{SLURL2|http://slurl.com/secondlife/Tiger/39/18/29}}

{{SLURL2|http://slurl.com/secondlife/Togata/229/239/29}}

[[Image:Togata-view.jpg|right|100px]]
=== Route 2 Ocean Panorama, Togata ===

Another sharp turn in the road to follow the coast opens up a wide vista across open ocean. Travellers may stop and tarry a while here at the viewpoint.

{{SLURL2|http://slurl.com/secondlife/Togata/74/182/29}}

[[Image:Togata-bridge.jpg|right|100px]]
=== Route 2 Oriental Bridge, Togata ===

A wide ocean estuary ravine here requires a bridge to span the gap and an elegant span of vaguely oriental outline performs this task.

{{SLURL2|http://slurl.com/secondlife/Togata/118/97/34}}

[[Image:Emmelia-viaduct.jpg|right|100px]]
=== Route 2 Stone Viaduct, Emmelia ===

A stone viaduct carries the road securely across the ravine into the ocean at Emmelia. A small decrepit dock lies in the waters below for those wishing to go boating.

{{SLURL2|http://slurl.com/secondlife/Emmelia/32/82/31}}

[[Image:R2-west.jpg|right|100px]]
=== Route 2 Western End, Emmelia ===

The western end of the Route 2 link road lies here at a small picnic area, near junction of two roads coming up from the south in Brithys.

{{SLURL2|http://slurl.com/secondlife/Emmelia/26/3/31}}

[[Image: REZZ ZONE MANDUCA.png|right|100px]]
=== Route 2 Rezz Zone, Manduca ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Manduca/189/89/63/}}

[[Image: WOOLYBEAR INTERSECTION.png|right|100px]]
=== Route 2 Intersections, Woolybear ===

A lovely landscaped area in the midst of many intersections.

{{SLURL2|http://slurl.com/secondlife/Woolybear/99/234/88/}}

[[Image: REZZ ZONE AZALEA.png|right|100px]]
=== Route 2 Rezz Zone, Azalea ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Azalea/93/189/79/}}

[[Image: REZZ ZONE ELLO.png|right|100px]]
=== Route 2 Rezz Zone, Ello ===

Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Ello/28/227/65/ }}

== Route 3 (North Heterocera Inland Link) : Unmissable items for your travelogue ! ==

This road lies mainly incomplete at the time of writing, however some sections have so far been completed to provide additional transport links. An example of this is a section joining the major junction at Woolybear in the north to Emmelia on Route 2. This section required some considerable gradient engineering to overcome the differences in altitude between these regions.

[[Image:Emmelia-junc.jpg|right|100px]]
=== Route 3/Route 2 Southern Junction, Emmelia ===

The two routes merge here in a T junction adjacent to the viaduct spanning the ravine.

{{SLURL2|http://slurl.com/secondlife/Emmelia/35/123/32}}

[[Image:Luna-rise.jpg|right|100px]]
=== Route 3 Lower Bank, Lunaris ===

The road ascends a steep bank here rises with the terrain, excellent spot for sledging if it would only snow !

{{SLURL2|http://slurl.com/secondlife/Lunaris/86/12/41}}

[[Image:Luna-bank.jpg|right|100px]]
=== Route 3 Upper Bank, Lunaris ===

A second rise requires a large stone embankment in order to prevent subsidence of the hillside below the woodland above.

{{SLURL2|http://slurl.com/secondlife/Lunaris/181/196/61}}

[[Image:Moma-woods.jpg|right|100px]]
=== Route 3 Hilltop Woodlands, Moma & Tridens ===

The high hill crest at Moma, as well as offering panoramic views of the surrounding area and not-so-distant coast, retains some natural woodland across its border with Tridens. The park also contains small lakes and a pagoda summerhouse in which weary travellers may take a breather. There is a rezzing area here too.

{{SLURL2|http://slurl.com/secondlife/Moma/238/59/75}}

[[Image:Tridens-bridge.jpg|right|100px]]
=== Route 3 Oriental Bridge, Tridens ===

The red oriental bridge at Tridens gracefully mimics its surrounding oriental architecture as does its twin down the ravine in Togata. From the bridge, the road heads due north across undulating terrain towards Woolybear Junction.

{{SLURL2|http://slurl.com/secondlife/Tridens/19/133/77}}

[[Image:woolybear.jpg|right|100px]]
=== Route 3 Main Road ===

The main road along Route 3 begins at the Woolybear intersection and continues to Tussock where the SLRR intersects. This Road is 4.3km long. Below is a list of features you can find along the way.

{{SLURL2|http://slurl.com/secondlife/Woolybear/111/230/86}}

[[Image:Polkadot.jpg|right|100px]]

=== Route 3 Polkadot Park, Polkadot ===

Small stone pathway leads to sunken garden beyond. A place for rest and contemplation.

{{SLURL2|http://slurl.com/secondlife/Polkadot/156/74/98}}

[[Image:riddings_001.jpg|right|100px]]
=== Route 3 Roundabout, Riddings ===

The Roundabout at Riddings provides access to the link road to the Southwest leading to Congrua or a continuation of the main road to Tussock to the East.

{{SLURL2|http://slurl.com/secondlife/Riddings/80/199/101}}

[[Image:riddings_002.jpg|right|100px]]
=== Route 3 Intersection, Riddings ===

This intersection provides access to sims to the South ending at Nitida. This intersection is also a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Riddings/212/181/121}}

[[Image:cisseps.jpg|right|100px]]
=== Route 3 Intersection, Cisseps ===

This intersection provides access to sims to the North ending at Turnip. This intersection is also a Rezz Zone and has a small public square and fountain.

{{SLURL2|http://slurl.com/secondlife/Cisseps/96/33/124}}

[[Image:MUSLIN.jpg|right|100px]]
=== Route 3 Factory, Muslin ===

This intersection includes the Coach and Carriage Company Factory and a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Muslin/180/45/121}}

[[Image:herald.jpg|right|100px]]
=== Route 3 Rezz Zone, Herald ===

Rezz Zone along the Road.

{{SLURL2|http://slurl.com/secondlife/Herald/124/54/119}}

[[Image:Pavonia.jpg|right|100px]]

=== Route 3 Community Hall, Pavonia ===

There is a Community Hall in Pavonia with a Rezz Zone next Door.

{{SLURL2|http://slurl.com/secondlife/Pavonia/182/235/118/}}

[[Image:tussock.jpg|right|100px]]

=== Route 3 Catch the train, Tussock ===

Park your vehicle and catch a train here.

{{SLURL2|http://slurl.com/secondlife/Tussock/89/119/119/}}

[[Image:morrison.jpg|right|100px]]
=== Route 3 Riddings to Congrua connection, Morrison ===

This Road is 840m long with a Rezz Zone along the Road.

{{SLURL2|http://slurl.com/secondlife/Morrison/226/134/99}}

[[Image:astylus.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Astylus ===

This Road is 1.5km with a Rezz Zone along the Road at Astylus.

{{SLURL2|http://slurl.com/secondlife/Astylus/62/43/121}}

[[Image:muralis.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Muralis ===

Muralis contains a few little parks, the largest of these contains a creek for your enjoyment.

{{SLURL2|http://slurl.com/secondlife/Muralis/86/120/125}}

[[Image:Nitida.jpg|right|100px]]
=== Route 3 Riddings to Nitida connection, Nitida ===

Nitida is currently the end of this road and hosts a Rezz Zone.

{{SLURL2|http://slurl.com/secondlife/Nitida/86/20/122}}

[[Image:orache.jpg|right|100px]]
=== Route 3 Cisseps to Turnip connection, Orache ===

A Rezz Zone along the road.

{{SLURL2|http://slurl.com/secondlife/Orache/61/242/100}}

== Route 5 : Coastal Byway ==
[[Image:RT5_001.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Xanthorhoe/120/254/31}}

=== Route 5 Public Rez Zones ===
=== Xanthorhoe Train Station ===
[[Image:RT5Rez_001.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Xanthorhoe/136/241/32}}

=== Denrolimus ===
[[Image:RT5Rez_002.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Denrolimus/61/155/31}}

=== Lasiocampa ===
[[Image:RT5Rez_003.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Lasiocampa/93/154/31}}

=== Myron ===
[[Image:RT5Rez_004.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Myron/158/68/32}}

=== Cisthene ===
[[Image:RT5Rez_005.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Cisthene/23/138/33}}

=== Ufeus ===
[[Image:RT5Rez_006.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Ufeus/64/110/32}}

=== Mocis ===
[[Image:RT5Rez_007.png|right|100px]]
{{SLURL2|http://maps.secondlife.com/secondlife/Mocis/91/137/31}}

=== Route 5 Public Boating Areas ===

=== Public Launch area in Xanthorhoe ===
[[Image:RT5_002.jpg|right|100px]]
{{SLURL2|http://slurl.com/secondlife/Xanthorhoe/201/164/31}}

=== Sailing and Surfing Launch area, Scotopteryx ===
[[Image:RT5_05.png|right|100px]]
{{SLURL2|http://slurl.com/secondlife/Scotopteryx/29/134/31}}

== Route 7 (Ring Road around Gaeta) : Take a tour around the whole island ! ==

[[Image:Libestus Pier.jpg|right|100px]]
=== Route 7 Libestus Pier, Libestus ===

Follow the road itself or put in a boat at the end of the pier and explore by sea!

{{SLURL2|http://slurl.com/secondlife/Libestus/236/18/26}}

[[Image:Squall Beach.jpg|right|100px]]
=== Route 7 Squall Public Beach, Squall ===

Relax by the waves or head up the beach to explore Magellan Linden's campsite

{{SLURL2|http://slurl.com/secondlife/Squall/177/207/21}}

[[Image:Hellfell.jpg|right|100px]]
=== Route 7 Helfell Infohub, Helfell ===

Mediterranean vistas abound around this new InfoHub

{{SLURL2|http://slurl.com/secondlife/Helfell/187/123/76}}

[[Image:Gaeta dock.jpg|right|100px]]
=== Route 7 Gaeta docks, (various) ===

These mark the transitions between improved roads and open water canals. Pick up a free LDPW boat here for easy sailing along the canals or other Linden seas.

== Route 8/8A/8B/8C and the Old Wagon Road (The "Japanese" Continent) : Konichiwa! ==

Because of it's shape many call this the "Japanese" continent. With that in mind the roads and public buildings along these roads have an eastern stylistic flair. Originally the roads were supposed to connect, but due to mistakes when the land was divided as the regions were brought online many of the routes end in abrupt dead ends. A system of false tunnels and billboards at dead ends will offer teleports when touched to allow travelers to easily keep exploring the road network without having to backtrack or search the map for where the road picks up again.

[[Image:Bagheera Shelter.jpg|right|100px]]
=== Route 8 Bagheera shelter, Bahheera ===

The Bagheera shelter at the end of the road is the perfect starting point for any exploration of the land. On the back wall is a large map of the continent showing the location of all the main routes; 8, 8A, 8B, 8C, and the Old Wagon Road. Smaller versions of this building exist all along the routes at various points to give explores an idea where they are on the overall map and to provide "rest stops".

{{SLURL2|http://slurl.com/secondlife/Bagheera/63/126/56}}

[[Image:Davros RT8-8C Jct.jpg|right|100px]]
=== Route 8 RT8-8C Junction, Davros ===
Turnoff point for RT8C (still under construction)

{{SLURL2|http://slurl.com/secondlife/Davros/81/71/27}}

[[Image:DavrosFenric bridge.jpg|right|100px]]
=== Route 8 Bridge Out!, Davros/Fenric ===
Look out! The bridge is out! Can you drive fast enough to make the jump? Go ahead and try! ;D

{{SLURL2|http://slurl.com/secondlife/Fenric/178/45/30}}

[[Image:Richfield RT8-8A Jct.jpg|right|100px]]
=== Route 8 RT8-8A Junction, Richfield ===
Southern junction with RT8A. Small rest stop with a lighted lamppost, sitting area and map kiosk.

{{SLURL2|http://slurl.com/secondlife/Richfield/153/186/69}}

[[Image:Cipactli RT8-8B Jct.jpg|right|100px]]
=== Route 8 RT8-8B Junction, Cipactli ===
Connection with RT8B, just south of the Furki Rest Stop on RT8B/8A.

{{SLURL2|http://slurl.com/secondlife/Cipactli/247/58/73}}

[[Image:Toroge Kiosk.jpg|right|100px]]
=== Route 8 Toroge Kiosk, Toroge ===
Westernmost point on the roadmap. Tight curve with an example of one of the small map kiosks.

{{SLURL2|http://slurl.com/secondlife/Toroge/43/85/54}}

[[Image:Bletschorn Tunnel.jpg|right|100px]]
=== Route 8 Bletschorn Tunnel, Bletschorn ===
False tunnel used to bypass Damastock. Touching the lanterns at the tunnel entrance will take you to the other side in Finsteraarhorn.

{{SLURL2|http://slurl.com/secondlife/Bietschhorn/33/47/55}}

[[Image:Finsteraarhorn Tunnel.jpg|right|100px]]
=== Route 8 Finsteraarhorn Tunnel, Finsteraarhorn ===
Mate to the Bletschorn Tunnel. Touching the lanterns at the tunnel entrance will take you to the other side in Bletschorn.

{{SLURL2|http://slurl.com/secondlife/Finsteraarhorn/223/114/29}}

[[Image:Nadelhorn RT8-8A Jct.jpg|right|100px]]
=== Route 8 RT8-8A Junction, Nadelhorn ===
Northern end of RT8A.

{{SLURL2|http://slurl.com/secondlife/Nadelhorn/250/65/50}}

[[Image:Soulgiver Tunnel.jpg|right|100px]]
=== Route 8 Soulgiver Tunnel, Soulgiver ===
End of RT8. Touching the lanterns at the tunnel entrance will take you to RT8C in Ogilvie.

{{SLURL2|http://slurl.com/secondlife/Soulgiver/175/91/65}}

[[Image:Furki Rest Area.jpg|right|100px]]
=== Route 8A Furki Rest Area, Furki ===
Rest area along the junction between RT8A and RT8B in Furki. Plenty of places to sit, relax, and discuss which direction you want to go next! Even has a working traffic light in the intersection.

{{SLURL2|http://slurl.com/secondlife/Furki/47/3/100}}

[[Image:Aragonese Tunnel.jpg|right|100px]]
=== Route 8A Aragonese Tunnel, Aragonese ===
Yep, another false tunnel. This one connects the broken halves of RT8A between Aragonese and Ellingson.

{{SLURL2|http://slurl.com/secondlife/Aragonese/76/183/88}}

[[Image:Horns of Hattin.jpg|right|100px]]

=== Route 8A Falling Rocks, Horns of Hattin ===
One of the most difficult tasks in constructing roads is figuring out what to do in "four corner" areas where the road runs through a spot where 4 regions meet. The region crossings can be very tricky in these spots. It's best to go slow and take the crossings one at a time. In this spot, the fallen rocks divert travelers in a way to guide them through the crossing along the best and least likely to end up crashing the client fashion.

{{SLURL2|http://slurl.com/secondlife/Horns%20of%20Hattin/5/3/68}}

[[Image:Tawa.jpg|right|100px]]
=== Route 8A Tawa Rest Stop, Tawa ===
Small rest area with a couple of benches, a map kiosk and some trees.

{{SLURL2|http://slurl.com/secondlife/Tawa/8/7/82}}

[[Image:Camazotz.jpg|right|100px]]
=== Route 8B Dead end, Camazotz ===
RT8B dead ends in Camazotz with a billboard sign that acts as a teleport link to the Old Wagon Road in Rethymno

{{SLURL2|http://slurl.com/secondlife/Camazotz/12/94/91}}

[[Image:Rethymno.jpg|right|100px]]
=== Old Wagon Road, Rethymno ===
The Old Wagon Road is a two-track unimproved roadway that only spans two regions. At either end are Billboard teleporters to take you other parts of RT8.

{{SLURL2|http://slurl.com/secondlife/Rethymno/18/179/92}}

[[Image:Ellingson.jpg|right|100px]]
=== Route 8A dead end, Ellingson ===
The southern half of Route 8A ends in Eliingson where you will find two teleport billboards offering to let you continue on Route 8A in Aragonese or you can choose to go to Sababurg and take the Old Wagon Road.

{{SLURL2|http://slurl.com/secondlife/Ellingson/193/245/85}}

[[Image:Ogilvie.jpg|right|100px]]
=== Route 8C Ogilvie, Valeyard/Davros ===
False tunnel that allows travelers to connect to RT8 in Soulgiver (if they touch the lantern on the left) or the Old Wagon Road in Sababurg (if they touch the lantern on the right).

{{SLURL2|http://slurl.com/secondlife/Valeyard/83/151/26}}

[[Image:Valeyard.jpg|right|100px]]
=== Route 8C Valeyard/Davros Waterway, Valeyard/Davros ===
Rez a boat and you can travel between Valeyard and Davros just before RT8C meets RT8.

{{SLURL2|http://slurl.com/secondlife/Valeyard/83/151/26}}

== Route 9: Miles of Motoring Fun ==

Still under construction, but already with many interesting sights!

=== Route 9 Lordshore Lookout Point ===

The picnic platform gives a stunning view of the new Lordshore suspension bridge. Built with the latest materials, the bridge is over 400 meters long, with 40 meters of clearance below the main span.

{{SLURL2|http://slurl.com/secondlife/Lordshore/60/61/55}}

== Wellington Road ==
[[Image:WR1_004_001.png|center|thumb]][[Image:WR1_004_002.png|center|thumb]]

Wellington Road begins in Chongno, travels through some lovely mainland areas, and ends in Hangflame Ridge.

{{SLURL2|http://slurl.com/secondlife/Chongno/241/254/77}}

{{SLURL2|http://slurl.com/secondlife/Hangflame%20Ridge/128/70/82}}

----

=== The Great Hill ===
Come try your skateboarding skills!
[[Image:WR1_002.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Noguri/237/196/76}}

Rez zone: {{SLURL2|http://slurl.com/secondlife/Noguri/5/77/99}}

=== Contemplation Bridge ===
Relax and visit with friends.
[[Image:WR1_003.jpg|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Pongsonhwa/98/120/105}}

=== Wellington Road Public Rez Zones ===
Lupoff
[[Image:WR1_004_003.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Lupoff/200/154/79}}

Molesworth
[[Image:WR1_004_004.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Molesworth/65/121/73}}

Quoll
[[Image:WR1_004_005.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Quoll/105/80/93}}

Cairnlow
[[Image:WR1_004_006.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Cairnlow/233/66/104}}

Chebi
[[Image:WR1_004_007.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Chebi/189/37/102}}

Noguri
[[Image:WR1_004_008.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Noguri/12/79/98}}

----

----
== Old Route 11 ==
[[Image:Route_11,_Vaktarin_(179,_227,_61).png|right|100px]]
----

A small section of Old Route 11 was discovered in late `09. Wander this raised wooden walkway from Valtarin to Kwaito for a neat surprise.

{{SLURL2|http://slurl.com/secondlife/Vaktarin/15/131/56}}
to

{{SLURL2|http://slurl.com/secondlife/Kwaito/243/239/42}}

----

== Route 11 ==
A wonky wooden and rough cobble stone tree lined road meandering though the continent. Rising from water level to over 100 meters high, Route 11 gives a variety of interesting views. From coastal to high mountains, from bridges to boat ramps, Route 11 has it all!

== Route 11 rez zone and boat ramp ==
[[Image:Route_11_(rez_zone),_Passendale.png|right|100px]]
Though Route 11 does start a bit further South West, it has long been flooded. Here is the first rez zone and boat ramp.

{{SLURL2|http://slurl.com/secondlife/Passendale/85/138/41}}

== Route 11 Amphibious Vehicle dunking zone ==
[[Image:Route_11_Gorgonzola_001.png|right|100px]]
Bring your amphibious vehicle, due to wildlife and oceanfront living, the road gets a bit wet here =D

{{SLURL2|http://slurl.com/secondlife/Gorgonzola/73/53/19}}

== Route 11 Down Hill Race Start ==
[[Image:Route_11_Blacksticks.png|right|100px]]
Top of the first rise. Ready to be raced down in either direction. =)

{{SLURL2|http://slurl.com/secondlife/Blacksticks/159/106/113}}

== Route 11 Rez Zone ==
[[Image:Route_11_Castlederg.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Castlederg/11/101/110}}

== Route 11 Rez Zone in Ironstorm ==
[[Image:Route_11_Ironstorm.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Ironstorm/13/19/70}}

== Route 11 Intersection to Magellan Pass ==
[[Image:Route_11_Muskeg.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Muskeg/153/126/53}}

== Route 11 Magellan Pass ==
[[Image:Route_11_Magellan_Pass.png|right|100px]]
A fast shortcut over the top of the mountains, discovered by our intrepid explorer himself.

{{SLURL2|http://slurl.com/secondlife/Sweet%20Morass/172/115/74}}

== Route 11 Moley's Fruit Stand and Nature Walk==
[[Image:Route_11_Fruit_Stand.png|right|100px]]
Moley says, Eat your fruit! While relaxing in the nature area.

{{SLURL2|http://slurl.com/secondlife/Westerlay/230/192/34}}

== Route 11 Floating Road and Drawbridge ==
[[Image:Route_11_Bogatanta.png|right|100px]]

{{SLURL2|http://slurl.com/secondlife/Bogatanta/180/219/21}}

== Route 11 Magellan Pass (other end) ==
[[Image:Route_11_Mordus_Hall.png|right|100px]]
The Western end of Magellan Pass

{{SLURL2|http://slurl.com/secondlife/Mordus%20Hall/206/89/62}}

== Route 11 Downhill Race Start Two ==
[[Image:Route_11_Roclaren.png|right|100px]]
Yet another fun hill to race down =D

{{SLURL2|http://slurl.com/secondlife/Claremorris/194/140/116}}

----

== Route 12 ==
[[Image:RT12 Overview Map.png|right|100px]]
Route 12 is made for exploring from sea to shining sea, from the sandy beaches of the shore to the grassy hills of the interior to the rough mountain trails of the northern penninsula. This road is calling out for adventurous avatars looking to explore a continent. Along that way you will find billboards like the one here. These maps give a topographical overview of the continent and the road itself. A red star indicates your current location. The gold stars indicate points to which you can teleport. Touching the gold star will open the map. This give explorers the ability to easily navigate to parts of the route not yet explored.

[[Image:Beatrice RT12.png|right|100px]]
=== Route 12 Beatrice Rest Stop, Beatrice ===

Close to the shores of the southwestern penninsula the rest stop in Beatrice is spartan. Little more than a few trees and a bench it is a turn around point and place to sit and contemplate which part of the continent you want to visit next.

{{SLURL2|http://slurl.com/secondlife/Beatrice/134/184/34}}

[[Image:Dreyfus RT12.png|right|100px]]
=== Route 12 Dreyfus Crossroads, Dreyfus ===

The interesection in Dreyfus is nestled in the green hills of the continent. West is the road along the western shore to Beatrice. North is the climb over the hills toward the hairpin curve in Jaxipun and on to the off road trail on the northern point.

{{SLURL2|http://slurl.com/secondlife/Dreyfus/29/171/50}}

[[Image:Clinker RT12.png|right|100px]]
=== Route 12 Clinker END OF PAVED ROAD, Clinker ===

Just over the bridge in Elsa is the end of paved road. The rest of RT12 to the north is an unimproved dirt trail with steep hills, rocks, and undergrowth blocking the way. A pleasant walking or horseback riding trail the route is not recommended for large vehicles with a wide track or low clearance. 4x4 trucks and off road vehicles should do fine. Test your offroading skill on this one!

{{SLURL2|http://slurl.com/secondlife/Clinker/166/121/68}}

[[Image:Pouncival RT12.png|right|100px]]
=== Route 12 Pouncival Roundabout, Pouncival ===

In Pouncival RT12 double backs on itself as the trail from Clinker snakes around the hilly terrain that makes up the northwest penninsula. To the north is a hill that will give even the best SL 4x4 a run for its money as you try to navigate around the switchback of boulders strewn in your path. Crest the hill and you're on your way through around the circuit of shear drops and undulating hills and back around to where you started.

{{SLURL2|http://slurl.com/secondlife/Pouncival/165/63/44}}

[[Image:Donalbain RT12.png|right|100px]]
=== Route 12 Donalbain Crossroads, Donalbain ===

The only other crossroads on RT12 Donalbain is rougly the halfway point. To the south is the short route leading to the endpoint at Camorro.

{{SLURL2|http://slurl.com/secondlife/Donalbain/27/209/47}}

[[Image:Camorro RT12.png|right|100px]]
=== Route 12 Camorro End, Camorro ===

Endpoint of the southern branch of RT12 from Donalbain.

{{SLURL2|http://slurl.com/secondlife/Camorro/250/12/50}}

[[Image:Fenstriano RT12.png|right|100px]]
=== Route 12 Fenstriano Curve, Fenstriano ===

Rest point between the western half of RT12 and the east, Fenstriano is a good place to take stock in your transcontinental journey.

{{SLURL2|http://slurl.com/secondlife/Fenstriano/157/7/38}}

[[Image:Rannveig RT12.png|right|100px]]
=== Route 12 Rannveig End, Rannveig ===

Final endpoint of RT12 in the east. Now to decide if you telport to another part RT12 or do you once more navigate the hills and curves backtoward the west.

{{SLURL2|http://slurl.com/secondlife/Rannveig/205/12/36}}

== Miscellaneous Mainland Points of Interest for Intrepid Explorers ==

=== Playground Ship on DaBoom ===

big maritime playground with freebies

{{SLURL2|http://slurl.com/secondlife/Da%20Boom/165/134/35}}

=== Playground on Rivula ===

cute little playground

{{SLURL2|http://slurl.com/secondlife/Rivula/195/56/34}}

=== Juice Bar, Brownlee ===

Keeping residents healthy with a Contemporary Juice Bar. Free Smoothies!

{{SLURL2|http://slurl.com/secondlife/Brownlee/209/150/105}}

=== The Volcano Island, Ichelus ===

A tropical Tiki village and exploding Volcano!!

{{SLURL2|http://slurl.com/secondlife/Ichelus/142/192/23}}

=== LDPW Showcase Conference Center, Boardroom ===

For the business types of the grid. Two modern style buildings ready to accomodate medium to large meetings/conferences.

{{SLURL2|http://slurl.com/secondlife/Boardroom/113/113/25/}}

=== Castle Valeria ===

A romantic interpretation of a medieval German castle; also, a pirate lair!

{{SLURL2|http://slurl.com/secondlife/Castle%20Valeria/175/196/68}}

=== Mos Ainsley ===

In space, no one can hear you type ... experience the far future at the base on Mos Ainsley. Spacesuits available for all!

{{SLURL2|http://slurl.com/secondlife/Mos%20Ainsley/134/131/48}}

[[Image:Pruni.jpg|right|100px]]
=== Pruni Park ===

Small wild and overgrown area with pool, treehouse and campfire areas.

{{SLURL2|http://slurl.com/secondlife/Pruni/73/217/62}}

[[Image:Bhima.jpg|right|100px]]
=== Bhima Lido Hall ===

Lido Hall with music, and patio with conversational areas.

{{SLURL2|http://slurl.com/secondlife/Bhima/143/97/39}}

[[Image:Ahab's_Haunt.jpg|right|100px]]
=== Ahab's Haunt ===

This is a tropical beach crowned by the skeleton of a giant beast. Hammocks and inner tubes, undersea treasure and lots to explore for divers, places to rezz your boats, and more!

{{SLURL2|http://slurl.com/secondlife/Ahab's%20Haunt/116/143/22}}

== Nautilus ==

This ancient city has recently been discovered. Mysterious crystals, a temple, assembly hall, and palace surround a large pool.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Malchus/9/29/72}}

... and a large park:

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Baal/72/140/23}}

... and a harbor, with a nearby market:

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Yamm/114/205/22}}

=== Highlights around the Great City of Nautilus ===

[[Image:Pharos.jpg|right|100px]]
[[Image:Pharos1.jpg|right|100px]]
[[Image:Pharos2.jpg|right|100px]]
[[Image:Pharos3.jpg|right|100px]]

=== The Pharos, Nautilus-Byth ===

As intrepid seafarers approach the great water channel leading to the ancient city; strange flickering beams in the sky, followed by a sighting of a lofty tower, alert them to the presence of the treacherous Nautilean coast. This large beam-house is The Pharos, and was constructed as a navigational aid replacing a much smaller crystal beacon, the ruins of which may still be seen on a nearby outcrop. Statues of sea creatures festoon the terraces of the Pharos, whilst a large idol of Hydraea, Goddess of the Sea, faces out to the Western Sea, both embracing friend and threatening foe with upraised hands. At the top of the tower rests the main lamp house where crystal energy passes through deflection grids to be streamed out to the cardinal points of the compass, clearly visible for many miles. Halfway up the tower, within a small open chamber at the top of the great stairway, is a focussing relay crystal which controls the nature of the Pharos' beam to suit the prevailing weather conditions.

Inside the great hall at the foot of the structure lies the main crystal reactor, within a deep containment pit surrounded by an energy screen. On one side of the barriers stands the console containing the control array and spectral coolant rods. As a protection against power overload, the reactor is gated to the sea via an internal pool and underwater tunnel, so that in the event of such an emergency, it may be flooded with seawater and extinguished. This pool should be empty and serene, however the Pharos has gained an 'unofficial' resident during some phase of it's existence. A rogue scientist fell from favour with the council of Nautilean elders due to his somewhat aggressive and more than a little xenophobic attitudes toward foreign trade, building crystal powered mechanical sea boats to disrupt passing trade and seize wealth for himself. Exiled from the main citadel he barricaded himself inside the Pharos, settling inside the main chamber where he constructed a new vessel within the confines of the coolant pool, periodically venturing forth from his lair via the sea tunnel to harry vulnerable shipping and steal supplies. This undoubtedly resourceful individual was apparently not immune to the mysterious cataclysm which afflicted Nautilus in the distant past, indeed some enigmatic writings discovered within the chamber suggest he may actually have been instrumental in hastening its effects, and all that may now be seen to mark his occupancy are his last and greatest undersea vessel, a variety of somewhat incongruously added docking structures, and a scatter of books dealing with a variety of arcane and eclectic topics. Judging by the compact size of his vessel, the physical stature of the Professor did not in any way match that of his mind !

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Byth/3/191/23}}

[[Image:Baal.jpg|right|100px]]

=== Baal Public Park, Nautilus-Baal ===

Nautilus sports a pair of public parks adjacent to the canal bank. Furthest east lies Baal Park, which contains a small seating area where one may sit and watch crystal particle beam displays, and also a small secluded pool for relaxation and contemplation known as 'The Eye of Baal', the reason for which may be clearly seem when viewing the feature from the air.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Baal/69/176/22}}

[[Image:Kothar.jpg|right|100px]]

=== Kothar Public Park, Nautilus-Kothar ===

The second park is located immediately adjacent within the Kothar district and contains a large outdoor public pool and thermal spa area alongside stone walkways. This location, in addition to the wild vegetation and arboreta common to both parks, also features a large outdoor mechanical chess set, the workings of which have yet to be precisely discovered, and a natural pool within which sits a small island upon which is sited a monument of unknown assignation.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Kothar/3/186/22}}

[[Image:Nautilus-gate.jpg|right|100px]]

=== City Sea Gate, Nautilus-Melqart ===

Two enormous bronze gates close the sea channel against hazards where it enters the great citadel wall. These may be swung open and shut, forming a bright star in the centre which acts as a night beacon when they are closed against entry.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Melqart/83/228/25}}

[[Image:Nautilus-canal.jpg|right|100px]]

=== The Canal, Nautilus ===

The deep channel of The Great Canal extends from the Citadel due east, and straight as a die, to the ocean, which it meets at the turbulent waters surrounding the Pharos. The channel has become home to various flora and fauna over the years.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Elissa/129/6/10}}

=== Magellan Linden's Mole Tank, Nautilus-Mysehi ===

Technically his "atomic boring machine". This 4000 ton vehicle was constructed by the LDPW moles to Magellan's specifications; powered by a 500 megawatt fission reactor, it can slowly burrow below the terrain surface. Magellan used it only once, to cross under the strange dome or shield which hid and protected the city of Nautilus.

{{SLURL2|http://slurl.com/secondlife/Nautilus%20-%20Mysehi/110/40/23}}

== The Blake Sea ==

Connecting the Mainland to the United Sailing Sims is the Blake Sea, venue for exciting boat races and other nautical activity! A few islands exist in the Blake Sea; some of them are:

=== Half Hitch ===

A picturesque fishing village.

{{SLURL2|http://slurl.com/secondlife/Blake%20Sea%20-%20Half%20Hitch/120/136/22}}

=== Windlass ===

Tropical resort.

{{SLURL2|http://slurl.com/secondlife/Blake%20Sea%20-%20Windlass/176/42/25}}

Other islands in the Blake Sea harbor smugglers, castaways, and sea creatures galore!

[[Image:Wikitipi.gif|Save to wikiTiPi]]
[http://www.wikitipi.com/cgi-bin/wp.cgi?http://wiki.secondlife.com/wiki/Parks_and_Recreation_Directory Copy all locations to my wikiTiPi HUD]

[[Category:LDPW]]