Second Life Wiki - User contributions [en]

Environment Sounds

2012-07-16T03:11:48Z

Hyper Mole:

==Environmental Sounds==

There's a handful of ways to generate sound without an avatar in Second Life.
* [[Sound_Clips|Sound clips]]
* a parcel's music stream
* a web page displayed on a prim

You can change all of them via scripting. The latter two can be set up without using scripts.

=== Soundtrack ===

If your build has a soundtrack or theme music that you want heard clearly across the parcel, consider using [[Streaming_Music|streaming music]]. It can be set in the About Land window. The [[LlSetParcelMusicURL|llSetParcelMusicURL()]] call lets you change it via script.

You can play a series of sound clips in order, but there's no guarantee that the "song" will be heard as seamless.

=== Looping ===

Looping a sound clip can add ambiance. Consider it for nighttime bugs by a lake, a crowd murmuring, or the hum of electric signs.

<lsl>
default
{
state_entry()
{
llLoopSound( llGetInventoryName( INVENTORY_SOUND, 0 ), 0.5 );
}
}
</lsl>

Shift-drag will allow you to create multiple copies of an object that will have their looping sounds synched together.

=== Synchronized ===

Do you want your ocean wave sounds to all synch up? Does your surreal build have a slow steady heartbeat?

Try this [[Script:Synch_Sound|synchronized sound script]].

=== Random ===

Short ambient sounds played randomly can make a space feel more alive.

Some good choices for this would be frogs, underbrush rustles and snaps, a distant car horn or squealing brakes.

Try this [[Script:Random_Sounds|random sounds script]].

=== Day/Night ===

Some sounds are best played during certain times of day. Consider birdsong, or bats and owls. If your build is taking advantage of a region's natural day/night cycle, you can alter your ambient sound selection by the time of day your region shows.

<lsl>
integer IsSunUp()
{
vector sunPosition = llGetSunDirection();
return ( sunPosition.z > 0 );
}

integer IsTwilight()
{
vector sunPosition = llGetSunDirection();
if ( sunPosition.z > 0.0 && sunPosition.z < 0.15 )
return TRUE;
return FALSE;
}
</lsl>

Try this [[Script:Day_Random_Sounds|daytime random sounds script]].

=== Wind activated ===

Do your bushes rustle more or louder when the wind blows? What about wind chimes?

<lsl>
float GetWindStrength()
{
return llVecMag(llWind(ZERO_VECTOR));
}
</lsl>

Try this [[Script:Wind_Powered_Random_Sounds|wind powered sounds script]].

=== Loud ===

Using llTriggerSound multiple times in a row can make a sound seem much louder than calling it once. This can be useful for tower bells and explosions. Be careful using this; too many times can cause an unpleasant echo-like effect.

<lsl>
integer n;
for (n = 0; n < 5; ++n)
{
llTriggerSound(soundname, 1.0);
}
</lsl>

=== Scripting comments ===

==== Sound clips ====
*[[LlTriggerSound|llTriggerSound()]]
** Unattached - sounds occur where they're triggered.
** Cannot be stopped with [[LlStopSound|llStopSound()]].
*[[LlPlaySound|llPlaySound()]]
** Attached - sounds follow the object they are in if it moves.
** Only one at a time per prim. Playing another will stop the current sound.
*[[LlLoopSound|llLoopSound()]]
** Attached - sounds follow the object they are in if it moves.
** This continuously loops the sound.
** Only one at a time per prim. Playing another will stop the current sound.
----
Return to [[Good_Building_Practices]]

Physics Optimization

2012-06-25T13:59:41Z

Hyper Mole:

'''Physics Optimization:'''

(See handy script at bottom of page)

'''NOTE: Setting prims to Phantom does not stop them from being calculated by the physics engine!'''

*The less the [[Physics_engine|physics engine]] has to calculate, the smoother your [[Region#Region|region]] will perform. Creating clean [http://en.wikipedia.org/wiki/Low_poly low poly] physics shapes for your complicated meshes is helpful, but you can also remove prim, mesh, and sculpted objects from the physics calculations completely.

*Physics Optimization also helps with [[Pathfinding_in_Second_Life|Pathfinding]]. Pathfinding objects will only have to calculate to go around simple objects instead of complex builds, making everything work smoother and faster without sacrificing looks.

<gallery>
File:Physics_trees.jpg|Two trees set to Prim
File:Physics_shapes.jpg|Physical shape of trees
File:Physics_in_navmesh.jpg|Results in the navmesh
</gallery>

*The way to Physics Optimize is to link your complicated builds to a simple shape like a cube or cylinder. The simple shape should be the [[Link#Root_Prim|root prim]] and then set all [[Link#Child_Prim|child prims]] to [[PRIM_PHYSICS_SHAPE_NONE]] (in Edit > Features > Physics Shape Type)

'''Manual Instructions:'''

1. Build your object as you normally would

2. Create a simple shape, such as a cube or cylinder

3. Right click on your object, hold down shift and select the simple shape last

4. Press control and L to link it all (the simple shape should now be the root prim highlighted in yellow)

5. Tick edit linked parts

6. Hold down shift and de-select the root prim (the simple shape)

7. Under the edit menu, in the features tab, select physics shape type, and from the drop down menu select, physics type '''none'''. This will set all the child prims to none.

8. Select the root prim (the simple shape) and make it transparent.

'''Using the script below:'''

Or to make it even simpler just follow the above instructions 1 to 4 and then use the handy script attached below. Just drop it in the root prim (The new simple shape you just linked your build to)

'''Tip:''' Cubes, spheres, and circular cylinders are the cheapest shapes to use. Up to 14 cubes equates to the same value as one cut hollowed cube. Other shapes, such as pyramids, with no cuts, twists, hollows, or holes, or any shape set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) r for its physics shape type are more expensive. Any shape that contains holes, cuts, twists, or hollows (such as a torus) fall into the most expensive category.

Here we linked a tree to a cube and set all child prims to physics shape type None (in Edit > Features > Physics Shape Type):

<gallery>
File:Physics_no_physics.jpg|No physics on trees
File:Physics_set_to_none.jpg|Navmesh sees only cube set to Prim
</gallery>

'''Collision:'''

When you are physics optimizing you need to plan where you want the [[Physics_engine#Collision_Geometry|collision]] to be, because all the individual shapes set to physics none will act as though they are phantom. In this example we are using a tree. The actual original tree will be set to physics none and act as though it is phantom so an avatar will be able to walk through it. The root prim, which in this case is a cylinder, will be the only solid part of the whole linked set. By putting the root prim/simple shape around the tree trunk, you simulate a solid and avatars will collide with it.

Here we used a cylinder, but we could have also used a stretched cube to achieve a similar effect.

For more complicated builds you can set certain parts to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_PRIM]] and others to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_NONE]]. The parts set to prim will act solid, and the parts set to physics shape type none will act as phantom. Alternatively, all prims could be set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) result. This still produces a physics shape significantly simpler than the default. However, this second option will have no effect on sculpts.

<gallery>
File:Physics_add_physics.jpg|Adding physics
File:Physics_007.jpg|As seen by physics engine
File:Physics_added_physics_in_navmesh.jpg|As seen by the navmesh
</gallery>

----
'''More Examples:'''

*Here is another example scenario. This is a sculpted prim fence. The physics shape is not as clean as it could be, and the edges don't cover all edges of the fence itself. To fix it, I created a cube physics shape, linked the fence to the cube with the cube as the root prim, and set the fence to None. As you can see, the resulting physics shape is lower in polygons and better covers the fence area.
<gallery>
File:Sculpty_optimization_001.jpg|Sculpted fence physics shape
File:Sculpty_optimization_002.jpg|Adding cube physics shape
File:Sculpty_optimization_003.jpg|Final Static Object physics shape
</gallery>

*This is a tree comprised of many sculpted pieces. Keep in mind that the physics engine needs to calculate every part of the physics shape in the second picture. Here I created a cylinder for the physics shape to fit on the bottom of the tree trunk. By linking the cylinder to the tree, and setting the tree to physics shape None, I have a much cleaner static object.
<gallery>
File:Sculpty_optimization_004_001.jpg|Sculpted Tree
File:Sculpty_optimization_004_002.jpg|Un-optimized sculpted tree physics shape
File:Sculpty_optimization_004_003.jpg|Adding simplified physics to tree, setting to root
File:Sculpty_optimization_004_004.jpg|Final tree physics set to static obstacle
</gallery>

*These gates are nice clean and simple except for the hippo on the top. We can remove the hippo from the physics engine calculations.
<gallery>
File:Sculptedlamp_2_003.png|Hippo gates
File:Sculptedlamp_2_004.png|Hippo physics
File:Sculptedlamp_2_005.png|Hippo set to NONE (yes, it's really still there!)
</gallery>

*This entrance has a lot of complicated geometry in one linkset. We only need simple physics here for avatars and pathfinding characters to collide with.
<gallery>
File:Aquarium_physics_001.png|Complicated geometry
File:Aquarium_physics_002.png|Physics reduced to the minimum necessary
</gallery>

*Streetlamp optimization:
<gallery>
File:Streetlamp_physics_001.png|Complicated geometry
File:Streetlamp_physics_002.png|Simplified
</gallery>

Use the following script to set all child prims to None. Be sure to check what physics are needed for your linkset prior to using, and/or add a simple cube as the root prim.
<lsl>
default
{
state_entry()
{
llShout(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>

*For more detailed information, have a look at this [http://community.secondlife.com/t5/English-Knowledge-Base/Best-practices-for-creating-efficient-collision-volumes/ta-p/984115 Havok Technical Artist Optimization Guide], a direct excerpt from Havok's documentation. (Havok is the physics and AI engine provider used by Second Life for its physics and pathfinding simulations.) This guide provides details on the best way to optimize your collision shapes and is used by leading artists throughout the games industry.

----
Back to [[Good_Building_Practices]]

File:Streetlamp physics 002.png

2012-06-25T13:59:15Z

Hyper Mole:

File:Streetlamp physics 001.png

2012-06-25T13:58:45Z

Hyper Mole:

Talk:Physics Optimization

2012-06-25T13:44:46Z

Hyper Mole:

===Spammy Example? ===
In the example
<lsl>
default
{
state_entry()
{
llShout(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>
why use llShout and not llOwnerSay?
I can't see why every avatar in 100 metres needs to know the child prims are being set to PRIM_PHYSICS_SHAPE_NONE.
[[User:Innula Zenovka|Innula Zenovka]] 11:35, 6 June 2012 (PDT)

----

Not sure, so I changed it. :) [[User:Hyper Mole|Hyper Mole]] 18:31, 21 June 2012 (PDT)

Script doesn't compile correctly with llOwnerSay. [[User:Hyper Mole|Hyper Mole]] 06:44, 25 June 2012 (PDT)

Talk:Physics Optimization

2012-06-25T13:44:35Z

Hyper Mole:

===Spammy Example? ===
In the example
<lsl>
default
{
state_entry()
{
llShout(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>
why use llShout and not llOwnerSay?
I can't see why every avatar in 100 metres needs to know the child prims are being set to PRIM_PHYSICS_SHAPE_NONE.
[[User:Innula Zenovka|Innula Zenovka]] 11:35, 6 June 2012 (PDT)

----

Not sure, so I changed it. :) [[User:Hyper Mole|Hyper Mole]] 18:31, 21 June 2012 (PDT)
Script doesn't compile correctly with llOwnerSay. [[User:Hyper Mole|Hyper Mole]] 06:44, 25 June 2012 (PDT)

Physics Optimization

2012-06-25T13:43:57Z

Hyper Mole:

'''Physics Optimization:'''

(See handy script at bottom of page)

'''NOTE: Setting prims to Phantom does not stop them from being calculated by the physics engine!'''

*The less the [[Physics_engine|physics engine]] has to calculate, the smoother your [[Region#Region|region]] will perform. Creating clean [http://en.wikipedia.org/wiki/Low_poly low poly] physics shapes for your complicated meshes is helpful, but you can also remove prim, mesh, and sculpted objects from the physics calculations completely.

*Physics Optimization also helps with [[Pathfinding_in_Second_Life|Pathfinding]]. Pathfinding objects will only have to calculate to go around simple objects instead of complex builds, making everything work smoother and faster without sacrificing looks.

<gallery>
File:Physics_trees.jpg|Two trees set to Prim
File:Physics_shapes.jpg|Physical shape of trees
File:Physics_in_navmesh.jpg|Results in the navmesh
</gallery>

*The way to Physics Optimize is to link your complicated builds to a simple shape like a cube or cylinder. The simple shape should be the [[Link#Root_Prim|root prim]] and then set all [[Link#Child_Prim|child prims]] to [[PRIM_PHYSICS_SHAPE_NONE]] (in Edit > Features > Physics Shape Type)

'''Manual Instructions:'''

1. Build your object as you normally would

2. Create a simple shape, such as a cube or cylinder

3. Right click on your object, hold down shift and select the simple shape last

4. Press control and L to link it all (the simple shape should now be the root prim highlighted in yellow)

5. Tick edit linked parts

6. Hold down shift and de-select the root prim (the simple shape)

7. Under the edit menu, in the features tab, select physics shape type, and from the drop down menu select, physics type '''none'''. This will set all the child prims to none.

8. Select the root prim (the simple shape) and make it transparent.

'''Using the script below:'''

Or to make it even simpler just follow the above instructions 1 to 4 and then use the handy script attached below. Just drop it in the root prim (The new simple shape you just linked your build to)

'''Tip:''' Cubes, spheres, and circular cylinders are the cheapest shapes to use. Up to 14 cubes equates to the same value as one cut hollowed cube. Other shapes, such as pyramids, with no cuts, twists, hollows, or holes, or any shape set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) r for its physics shape type are more expensive. Any shape that contains holes, cuts, twists, or hollows (such as a torus) fall into the most expensive category.

Here we linked a tree to a cube and set all child prims to physics shape type None (in Edit > Features > Physics Shape Type):

<gallery>
File:Physics_no_physics.jpg|No physics on trees
File:Physics_set_to_none.jpg|Navmesh sees only cube set to Prim
</gallery>

'''Collision:'''

When you are physics optimizing you need to plan where you want the [[Physics_engine#Collision_Geometry|collision]] to be, because all the individual shapes set to physics none will act as though they are phantom. In this example we are using a tree. The actual original tree will be set to physics none and act as though it is phantom so an avatar will be able to walk through it. The root prim, which in this case is a cylinder, will be the only solid part of the whole linked set. By putting the root prim/simple shape around the tree trunk, you simulate a solid and avatars will collide with it.

Here we used a cylinder, but we could have also used a stretched cube to achieve a similar effect.

For more complicated builds you can set certain parts to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_PRIM]] and others to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_NONE]]. The parts set to prim will act solid, and the parts set to physics shape type none will act as phantom. Alternatively, all prims could be set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) result. This still produces a physics shape significantly simpler than the default. However, this second option will have no effect on sculpts.

<gallery>
File:Physics_add_physics.jpg|Adding physics
File:Physics_007.jpg|As seen by physics engine
File:Physics_added_physics_in_navmesh.jpg|As seen by the navmesh
</gallery>

----
'''More Examples:'''

*Here is another example scenario. This is a sculpted prim fence. The physics shape is not as clean as it could be, and the edges don't cover all edges of the fence itself. To fix it, I created a cube physics shape, linked the fence to the cube with the cube as the root prim, and set the fence to None. As you can see, the resulting physics shape is lower in polygons and better covers the fence area.
<gallery>
File:Sculpty_optimization_001.jpg|Sculpted fence physics shape
File:Sculpty_optimization_002.jpg|Adding cube physics shape
File:Sculpty_optimization_003.jpg|Final Static Object physics shape
</gallery>

*This is a tree comprised of many sculpted pieces. Keep in mind that the physics engine needs to calculate every part of the physics shape in the second picture. Here I created a cylinder for the physics shape to fit on the bottom of the tree trunk. By linking the cylinder to the tree, and setting the tree to physics shape None, I have a much cleaner static object.
<gallery>
File:Sculpty_optimization_004_001.jpg|Sculpted Tree
File:Sculpty_optimization_004_002.jpg|Un-optimized sculpted tree physics shape
File:Sculpty_optimization_004_003.jpg|Adding simplified physics to tree, setting to root
File:Sculpty_optimization_004_004.jpg|Final tree physics set to static obstacle
</gallery>

*These gates are nice clean and simple except for the hippo on the top. We can remove the hippo from the physics engine calculations.
<gallery>
File:Sculptedlamp_2_003.png|Hippo gates
File:Sculptedlamp_2_004.png|Hippo physics
File:Sculptedlamp_2_005.png|Hippo set to NONE (yes, it's really still there!)
</gallery>

*This entrance has a lot of complicated geometry in one linkset. We only need simple physics here for avatars and pathfinding characters to collide with.
<gallery>
File:Aquarium_physics_001.png|Complicated geometry
File:Aquarium_physics_002.png|Physics reduced to the minimum necessary
</gallery>

Use the following script to set all child prims to None. Be sure to check what physics are needed for your linkset prior to using, and/or add a simple cube as the root prim.
<lsl>
default
{
state_entry()
{
llShout(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>

*For more detailed information, have a look at this [http://community.secondlife.com/t5/English-Knowledge-Base/Best-practices-for-creating-efficient-collision-volumes/ta-p/984115 Havok Technical Artist Optimization Guide], a direct excerpt from Havok's documentation. (Havok is the physics and AI engine provider used by Second Life for its physics and pathfinding simulations.) This guide provides details on the best way to optimize your collision shapes and is used by leading artists throughout the games industry.

----
Back to [[Good_Building_Practices]]

Physics Optimization

2012-06-25T13:20:15Z

Hyper Mole:

'''Physics Optimization:'''

(See handy script at bottom of page)

'''NOTE: Setting prims to Phantom does not stop them from being calculated by the physics engine!'''

*The less the [[Physics_engine|physics engine]] has to calculate, the smoother your [[Region#Region|region]] will perform. Creating clean [http://en.wikipedia.org/wiki/Low_poly low poly] physics shapes for your complicated meshes is helpful, but you can also remove prim, mesh, and sculpted objects from the physics calculations completely.

*Physics Optimization also helps with [[Pathfinding_in_Second_Life|Pathfinding]]. Pathfinding objects will only have to calculate to go around simple objects instead of complex builds, making everything work smoother and faster without sacrificing looks.

<gallery>
File:Physics_trees.jpg|Two trees set to Prim
File:Physics_shapes.jpg|Physical shape of trees
File:Physics_in_navmesh.jpg|Results in the navmesh
</gallery>

*The way to Physics Optimize is to link your complicated builds to a simple shape like a cube or cylinder. The simple shape should be the [[Link#Root_Prim|root prim]] and then set all [[Link#Child_Prim|child prims]] to [[PRIM_PHYSICS_SHAPE_NONE]] (in Edit > Features > Physics Shape Type)

'''Manual Instructions:'''

1. Build your object as you normally would

2. Create a simple shape, such as a cube or cylinder

3. Right click on your object, hold down shift and select the simple shape last

4. Press control and L to link it all (the simple shape should now be the root prim highlighted in yellow)

5. Tick edit linked parts

6. Hold down shift and de-select the root prim (the simple shape)

7. Under the edit menu, in the features tab, select physics shape type, and from the drop down menu select, physics type '''none'''. This will set all the child prims to none.

8. Select the root prim (the simple shape) and make it transparent.

'''Using the script below:'''

Or to make it even simpler just follow the above instructions 1 to 4 and then use the handy script attached below. Just drop it in the root prim (The new simple shape you just linked your build to)

'''Tip:''' Cubes, spheres, and circular cylinders are the cheapest shapes to use. Up to 14 cubes equates to the same value as one cut hollowed cube. Other shapes, such as pyramids, with no cuts, twists, hollows, or holes, or any shape set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) r for its physics shape type are more expensive. Any shape that contains holes, cuts, twists, or hollows (such as a torus) fall into the most expensive category.

Here we linked a tree to a cube and set all child prims to physics shape type None (in Edit > Features > Physics Shape Type):

<gallery>
File:Physics_no_physics.jpg|No physics on trees
File:Physics_set_to_none.jpg|Navmesh sees only cube set to Prim
</gallery>

'''Collision:'''

When you are physics optimizing you need to plan where you want the [[Physics_engine#Collision_Geometry|collision]] to be, because all the individual shapes set to physics none will act as though they are phantom. In this example we are using a tree. The actual original tree will be set to physics none and act as though it is phantom so an avatar will be able to walk through it. The root prim, which in this case is a cylinder, will be the only solid part of the whole linked set. By putting the root prim/simple shape around the tree trunk, you simulate a solid and avatars will collide with it.

Here we used a cylinder, but we could have also used a stretched cube to achieve a similar effect.

For more complicated builds you can set certain parts to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_PRIM]] and others to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_NONE]]. The parts set to prim will act solid, and the parts set to physics shape type none will act as phantom. Alternatively, all prims could be set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) result. This still produces a physics shape significantly simpler than the default. However, this second option will have no effect on sculpts.

<gallery>
File:Physics_add_physics.jpg|Adding physics
File:Physics_007.jpg|As seen by physics engine
File:Physics_added_physics_in_navmesh.jpg|As seen by the navmesh
</gallery>

----
'''More Examples:'''

*Here is another example scenario. This is a sculpted prim fence. The physics shape is not as clean as it could be, and the edges don't cover all edges of the fence itself. To fix it, I created a cube physics shape, linked the fence to the cube with the cube as the root prim, and set the fence to None. As you can see, the resulting physics shape is lower in polygons and better covers the fence area.
<gallery>
File:Sculpty_optimization_001.jpg|Sculpted fence physics shape
File:Sculpty_optimization_002.jpg|Adding cube physics shape
File:Sculpty_optimization_003.jpg|Final Static Object physics shape
</gallery>

*This is a tree comprised of many sculpted pieces. Keep in mind that the physics engine needs to calculate every part of the physics shape in the second picture. Here I created a cylinder for the physics shape to fit on the bottom of the tree trunk. By linking the cylinder to the tree, and setting the tree to physics shape None, I have a much cleaner static object.
<gallery>
File:Sculpty_optimization_004_001.jpg|Sculpted Tree
File:Sculpty_optimization_004_002.jpg|Un-optimized sculpted tree physics shape
File:Sculpty_optimization_004_003.jpg|Adding simplified physics to tree, setting to root
File:Sculpty_optimization_004_004.jpg|Final tree physics set to static obstacle
</gallery>

*These gates are nice clean and simple except for the hippo on the top. We can remove the hippo from the physics engine calculations.
<gallery>
File:Sculptedlamp_2_003.png|Hippo gates
File:Sculptedlamp_2_004.png|Hippo physics
File:Sculptedlamp_2_005.png|Hippo set to NONE (yes, it's really still there!)
</gallery>

*This entrance has a lot of complicated geometry in one linkset. We only need simple physics here for avatars and pathfinding characters to collide with.
<gallery>
File:Aquarium_physics_001.png|Complicated geometry
File:Aquarium_physics_002.png|Physics reduced to the minimum necessary
</gallery>

Use the following script to set all child prims to None. Be sure to check what physics are needed for your linkset prior to using, and/or add a simple cube as the root prim.
<lsl>
default
{
state_entry()
{
llOwnerSay(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>

*For more detailed information, have a look at this [http://community.secondlife.com/t5/English-Knowledge-Base/Best-practices-for-creating-efficient-collision-volumes/ta-p/984115 Havok Technical Artist Optimization Guide], a direct excerpt from Havok's documentation. (Havok is the physics and AI engine provider used by Second Life for its physics and pathfinding simulations.) This guide provides details on the best way to optimize your collision shapes and is used by leading artists throughout the games industry.

----
Back to [[Good_Building_Practices]]

File:Aquarium physics 002.png

2012-06-25T13:18:36Z

Hyper Mole:

File:Aquarium physics 001.png

2012-06-25T13:18:01Z

Hyper Mole:

Material Volumes

2012-06-24T16:51:35Z

Hyper Mole:

==About Material Volumes==
*The Material Volume [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|attribute]] for [[Pathfinding]] creates phantom objects that can be set to change the walkability coefficients of an area of the navmesh. Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Pathfinding characters will choose the fastest and closest path available to them. (add video of PF cube choosing 100% walkability path around a MV)
*Material Volumes are visible in the [[Pathfinding_NavMesh|navigation mesh view]] as opaque purple objects.

[[File:Material_volume_001.png|none|300x225px]]

----
Return to [[Good_Building_Practices]]

Visual Guide to Pathfinding

2012-06-24T16:51:04Z

Hyper Mole:

==Setup Pathfinding==

* A new [[Pathfinding]] region has three types of objects. The terrain is set to [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Walkable]] (by default and cannot be changed), existing objects are set to [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Movable Obstacle]], and existing phantom objects are set to Movable Phantom.
<pre style="color:red">Begin by naming every object in your region! It's difficult to know what to set objects to if they are all named "Object".</pre>
* Movable Obstacle and Movable Phantom objects will not show up in your [[Pathfinding_NavMesh|navigation mesh]] view, so your initial view of your region will be the smooth green mesh of the terrain. Be sure to check the Walkable box in the Pathfinding Debug window (formerly the Edit/Test window).
* Begin by making obstacles Static in the Linksets window. Many of these will be obvious, such as trees, fences, and walls.
* Another obvious set of objects are your Walkables like floors, roads, and docks.
* Objects that need to move yet need to be solid should be left as Movable Obstacles. An example would be scripted doors.
* Objects that don't need to be obstacles at all, should be set to Movable Phantom.
* Objects that avatars can navigate but Pathfinding characters cannot should be set to Exclusion Volume.

<gallery>
File:Pathfinding_002.png|Initial Pathfinding view
File:Pathfinding_003.png|Adding Static Obstacles and Walkables
File:Pathfinding_004.png|Adding more of each type
</gallery>

* Many linksets will need to be changed to work properly with Pathfinding. For instance, if your building is all one object or linkset and you wish to make the floor Walkable, you will need to unlink the floor so you can set the building to Static Obstacle and the floor to Walkable. Alternatively, you can place an exclusion volume around the walls/roof. Just be sure it doesn't include any areas that should be walkable!

<gallery>
File:Pathfinding_2_003.png|Floor linked to building, set to Static Obstacle
File:Pathfinding_2_002.png|Floor and building not linked, floor set to Walkable, building set to Static Obstacle
</gallery>

* This linkset needs the railings set to Static Obstacle, and the stairs themselves set to Walkable. Originally it was all one linkset and set to Static Obstacle.
<gallery>
File:Pathfinding_2_004.png|Stair and railing linkset, set to Static Obstacle
File:Pathfinding_2_005.png|Stairs and railing unlinked, stairs set to Walkable
File:Pathfinding_2_006.png|Walkable ramp added for better navigation of pathfinding characters
</gallery>

* If you have a lot of trees, shrubs and other greenery, it's best to give it one simple physics shape for pathfinding characters to navigate around. Not to mention it lowers the load on the physics engine.
<gallery>
File:Sculptedlamp_005.png|Thick undergrowth for a pathway area
File:Sculptedlamp_006.png|As seen by the navmesh and physics engine
File:Sculptedlamp_007.png|Adding simple physics
File:Sculptedlamp_2_002.png|Final linkset as seen by the physics engine
</gallery>

* Exclusion Volumes are handy for areas where you need avatar interaction but where pathfinding characters will likely get stuck.
<gallery>
File:Sculptedlamp_2_006.png|Excluded rock area
File:Sculptedlamp_2_007.png|Excluded rock area
File:Exclusion_use_001.png|Exclusion Volumes used to keep characters on the dock, yet avatars can fall off
</gallery>

==Optimize for Pathfinding==
* Sculpted prims can easily be optimized for Pathfinding. Because sculpted prims have a messy physics shape, pathfinding characters will have difficulty navigating around or under them. Create the simplest [[Physics_Optimization|physics shape]] necessary for these objects.
* Note that setting the sculpted prim to phantom and creating a separate physics shape will work, but the sculpted object will still be seen by the physics engine. The method below is more efficient.

<gallery>
File:Pathfinding_3_002.png|Sculpted bench with bad physics shape
File:Pathfinding_3_003.png|Prim added for clean physics, bench set to Physics type NONE
</gallery>

----
Return to [[Good_Building_Practices]]
__FORCETOC__

Pathfinding Overview

2012-06-24T16:50:04Z

Hyper Mole:

[[Pathfinding]] is a method content creators can use to create moving and interactive characters within Second Life. Characters can use LSL functions to avoid obstacles, move around corners, climb inclines, and move across region boundaries: things that are very difficult or even impossible before. Pathfinding will also enable new gameplay mechanics, such as creating food that attracts monsters.

==Terminology==
*Character - an object that uses a Pathfinding LSL function.
*NavMesh - Short for Navigation Mesh. It's a map for characters.

==Functions==
*Evade - Run (and or hide) from a specified avatar or object.
*Flee - Move a specified distance from a specified location.
*Hop
*Navigate - Move to a specified location.
*Patrol - Move along a specified path specified by patrol points.
*Pursue - Follow specified avatar or object.
*Wander - Randomly wander a specified distance from a specified central point.

----
Return to [[Good_Building_Practices]]

Good Building Practices

2012-06-24T16:49:26Z

Hyper Mole: /* Pathfinding */

== Welcome to Good Building Practices ==
This page is all about how to be creative and efficient at the same time!

{| width="100%"
|-
|valign="top"|
<div id="box">

== Animation ==
<div style="padding: 0.5em">
* '''[[Animation Streamlined]]''' - Let's make Second Life move, without dragging it to a crawl!
</div>
</div>

<div id="box">

== Mesh ==
<div style="padding: 0.5em">
* '''[[Making Mesh Physics]]''' - Why and How.
* '''[[Making Mesh for Pathfinding]]''' - Pathfinding friendly mesh.
</div>
</div>

<div id="box">

== Pathfinding ==
<div style="padding: 0.5em">
*'''[[Pathfinding_Overview]]''' - Pathfinding explained.
*'''[[Pathfinding_Tools_in_the_Second_Life_Viewer]]''' - The Pathfinding tools.
*'''[[Pathfinding_Quick_Start_Guide]]''' - The best way to get up and running with Pathfinding.
*'''[[Visual_Guide_to_Pathfinding|A Visual Guide]]''' - Watch how easy it is!
*'''[[Walkability_Coefficients]]''' - Control the speed of your Walkable areas.
*'''[[Material_Volumes]]''' - Control the speed of your characters.

</div>
</div>
<div id="box">

== Physics ==
<div style="padding: 0.5em">
* '''[[Physics Optimization]]''' - Not everything needs physics, learn how to add the least load necessary to the physics engine.
* '''[[PRIM_PHYSICS_SHAPE_NONE]]''' - Additional information on this important attribute.

</div>
</div>
|valign="top" width="50%"|
<div id="box">

== Scripting ==
<div style="padding: 0.5em">
* '''[[Debugging Tips]]''' - how to work out what your code is doing without a conventional development toolkit
* '''[[Scripting for Pathfinding]]''' - Pathfinding scripting help.
** '''[[Modular Pathfinding Kit]]''' - code snippets designed to be plugged together to quickly build unique behaviours.
** '''[[Holistic Pathfinding Management]]''' - Strategies for managing large numbers of pathfinding objects.
</div>
</div>

<div id="box">

== Sculpted Prims ==
<div style="padding: 0.5em">
*'''[[Sculpted Prim Usage]]''' - What you need to know about how sculpted prims effect Second Life.
</div>
</div>

<div id="box">

== Textures ==
<div style="padding: 0.5em">
* '''[[Texture Usage]]''' - What size to use, and what to avoid.
</div>
</div>

|}
__NOTOC__

Good Building Practices

2012-06-24T16:49:14Z

Hyper Mole: /* Pathfinding */

== Welcome to Good Building Practices ==
This page is all about how to be creative and efficient at the same time!

{| width="100%"
|-
|valign="top"|
<div id="box">

== Animation ==
<div style="padding: 0.5em">
* '''[[Animation Streamlined]]''' - Let's make Second Life move, without dragging it to a crawl!
</div>
</div>

<div id="box">

== Mesh ==
<div style="padding: 0.5em">
* '''[[Making Mesh Physics]]''' - Why and How.
* '''[[Making Mesh for Pathfinding]]''' - Pathfinding friendly mesh.
</div>
</div>

<div id="box">

== Pathfinding ==
<div style="padding: 0.5em">
*'''[[Pathfinding_Overview]]''' - Pathfinding explained.
*'''[[Pathfinding_Tools_in_the_Second_Life_Viewer]] - The Pathfinding tools.
*'''[[Pathfinding_Quick_Start_Guide]]''' - The best way to get up and running with Pathfinding.
*'''[[Visual_Guide_to_Pathfinding|A Visual Guide]]''' - Watch how easy it is!
*'''[[Walkability_Coefficients]]''' - Control the speed of your Walkable areas.
*'''[[Material_Volumes]]''' - Control the speed of your characters.

</div>
</div>
<div id="box">

== Physics ==
<div style="padding: 0.5em">
* '''[[Physics Optimization]]''' - Not everything needs physics, learn how to add the least load necessary to the physics engine.
* '''[[PRIM_PHYSICS_SHAPE_NONE]]''' - Additional information on this important attribute.

</div>
</div>
|valign="top" width="50%"|
<div id="box">

== Scripting ==
<div style="padding: 0.5em">
* '''[[Debugging Tips]]''' - how to work out what your code is doing without a conventional development toolkit
* '''[[Scripting for Pathfinding]]''' - Pathfinding scripting help.
** '''[[Modular Pathfinding Kit]]''' - code snippets designed to be plugged together to quickly build unique behaviours.
** '''[[Holistic Pathfinding Management]]''' - Strategies for managing large numbers of pathfinding objects.
</div>
</div>

<div id="box">

== Sculpted Prims ==
<div style="padding: 0.5em">
*'''[[Sculpted Prim Usage]]''' - What you need to know about how sculpted prims effect Second Life.
</div>
</div>

<div id="box">

== Textures ==
<div style="padding: 0.5em">
* '''[[Texture Usage]]''' - What size to use, and what to avoid.
</div>
</div>

|}
__NOTOC__

Debugging Tips

2012-06-24T14:17:22Z

Hyper Mole:

One of the hardest things with scripting anything non trivial in LSL, especially if you come from an software development environment where you're used to combined editor and debugger, is the seeming inability to debug LSL code.

==Simple Example==

The solution is to define a simple debugging utility function as follows.

<lsl>
notify(string msg)
{
llOwnerSay(msg);
}
</lsl>

then whenever we need to check the value of a variable simple call

<lsl>
notify("your debug message here");
</lsl>

don't forget to typecast as necessary, for example:

<lsl>
integer a = 3;
integer b = 4;
integer result = a * b;
notify((string)result);
</lsl>

This allows us to reuse the same function for reporting anything to the owner of the object, rather than using public chat. The advantage to doing this is we can comment out a single line in the code function as follows to disable all debugging, or we can search and replace and instance of "notify" with "//notify".

<lsl>
notify(string msg)
{
//llOwnerSay(msg);
}
</lsl>

if you're working with list use something along the lines of:

notify(llList2String(listName, integerIndex)); // notification contains one list element
or
notify(llDumpList2String(listName, ",")); notification contains entire list as a string

==Error Reporting and Debugging==
We can use the same concept for tracking issues after the code is complete as follows

<lsl>
notify(string genus, string msg)
{
key creator = "a822ff2b-ff02-461d-b45d-dcd10a2de0c2";
//genus = "off" //uncoment this line to turn notifications off
if (genus == "dbg")
{
llInstantMessage(creator, "DEBUG: " + msg); //coment out this line to turn off debugging
}
else if (genus == "err")
{
llOwnerSay("ERROR: " + msg);
llInstantMessage(creator, "ERROR: " + msg + " in object " + llGetObjectName() + " that belongs to " + llKey2Name(llGetOwner()) + " in region " + llGetRegionName());
}
else if (genus == "info")
{
llOwnerSay(msg); //no prepend because it's a normal message
}
else
{
//do nothing, notifications were turned off
}
}
</lsl>

We're doing a number of things here: handling different kids of messages, informational for normal running, error reporting to the owner and creator and debug messages. To turn off debug simply comment out the debug line as shown in the code, and uncomment the genus="off" line to disable all notifications.

We're using llOwner for the current owner and llInstantMessage for contacting the script creator that will continue to work after ownership has passed - you just have insert your own key at the top.

Other mechanisms that could be used include llEmail or llHTTPRequest to post a message to an external logging system perhaps.

You define your own custome message types and communicate using the most appropriate method.

==More Reuse==
We can extend the reuse even further by making this a discreet script on it's own within the object as follows:

<lsl>
notify(string genus, string msg)
{
key creator = "a822ff2b-ff02-461d-b45d-dcd10a2de0c2";
//genus = "off" //uncoment this line to turn notifications off
if (genus == "dbg")
{
llInstantMessage(creator, "DEBUG: " + msg); //coment out this line to turn off debugging
}
else if (genus == "err")
{
llOwnerSay("ERROR: " + msg);
llInstantMessage(creator, "ERROR: " + msg + " in object " + llGetObjectName() + " that belongs to " + llKey2Name(llGetOwner()) + " in region " + llGetRegionName());
}
else if (genus == "info")
{
llOwnerSay(msg); //no prepend because it's a normal message
}
else
{
//do nothing, notifications were turned off
}
}

default
{
state_entry()
{
notify("info", "notification system ready");
}
link_message(integer source, integer num, string str, key id)
{
notify(str, key); //we're using the key as a second string parameter
}
}
</lsl>

To send a notification you simply use in your implementation:

<lsl>
default
{
touch_start(integer c)
{
string msg = llKey2Name(llDetectedKey(0)) + " attempted to steal Mjölnir!";
llMessageLinked(LINK_SET, 0, "info", msg);
//this may seem odd but it's valid to use the key paramter of llMessageLinked as a second string passing facility if not actually used for a key
}
}
</lsl>

----
Return to [[Good_Building_Practices]]

Talk:Physics Optimization

2012-06-22T01:31:47Z

Hyper Mole:

Physics Optimization

2012-06-22T01:30:17Z

Hyper Mole:

'''Physics Optimization:'''

(See handy script at bottom of page)

'''NOTE: Setting prims to Phantom does not stop them from being calculated by the physics engine!'''

*The less the [[Physics_engine|physics engine]] has to calculate, the smoother your [[Region#Region|region]] will perform. Creating clean [http://en.wikipedia.org/wiki/Low_poly low poly] physics shapes for your complicated meshes is helpful, but you can also remove prim, mesh, and sculpted objects from the physics calculations completely.

*Physics Optimization also helps with [[Pathfinding_in_Second_Life|Pathfinding]]. Pathfinding objects will only have to calculate to go around simple objects instead of complex builds, making everything work smoother and faster without sacrificing looks.

<gallery>
File:Physics_trees.jpg|Two trees set to Prim
File:Physics_shapes.jpg|Physical shape of trees
File:Physics_in_navmesh.jpg|Results in the navmesh
</gallery>

*The way to Physics Optimize is to link your complicated builds to a simple shape like a cube or cylinder. The simple shape should be the [[Link#Root_Prim|root prim]] and then set all [[Link#Child_Prim|child prims]] to [[PRIM_PHYSICS_SHAPE_NONE]] (in Edit > Features > Physics Shape Type)

'''Manual Instructions:'''

1. Build your object as you normally would

2. Create a simple shape, such as a cube or cylinder

3. Right click on your object, hold down shift and select the simple shape last

4. Press control and L to link it all (the simple shape should now be the root prim highlighted in yellow)

5. Tick edit linked parts

6. Hold down shift and de-select the root prim (the simple shape)

7. Under the edit menu, in the features tab, select physics shape type, and from the drop down menu select, physics type '''none'''. This will set all the child prims to none.

8. Select the root prim (the simple shape) and make it transparent.

'''Using the script below:'''

Or to make it even simpler just follow the above instructions 1 to 4 and then use the handy script attached below. Just drop it in the root prim (The new simple shape you just linked your build to)

'''Tip:''' Cubes, spheres, and circular cylinders are the cheapest shapes to use. Up to 14 cubes equates to the same value as one cut hollowed cube. Other shapes, such as pyramids, with no cuts, twists, hollows, or holes, or any shape set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) r for its physics shape type are more expensive. Any shape that contains holes, cuts, twists, or hollows (such as a torus) fall into the most expensive category.

Here we linked a tree to a cube and set all child prims to physics shape type None (in Edit > Features > Physics Shape Type):

<gallery>
File:Physics_no_physics.jpg|No physics on trees
File:Physics_set_to_none.jpg|Navmesh sees only cube set to Prim
</gallery>

'''Collision:'''

When you are physics optimizing you need to plan where you want the [[Physics_engine#Collision_Geometry|collision]] to be, because all the individual shapes set to physics none will act as though they are phantom. In this example we are using a tree. The actual original tree will be set to physics none and act as though it is phantom so an avatar will be able to walk through it. The root prim, which in this case is a cylinder, will be the only solid part of the whole linked set. By putting the root prim/simple shape around the tree trunk, you simulate a solid and avatars will collide with it.

Here we used a cylinder, but we could have also used a stretched cube to achieve a similar effect.

For more complicated builds you can set certain parts to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_PRIM]] and others to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_NONE]]. The parts set to prim will act solid, and the parts set to physics shape type none will act as phantom. Alternatively, all prims could be set to [[PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_CONVEX_HULL]] for a potentially more accurate (albeit more expensive) result. This still produces a physics shape significantly simpler than the default. However, this second option will have no effect on sculpts.

<gallery>
File:Physics_add_physics.jpg|Adding physics
File:Physics_007.jpg|As seen by physics engine
File:Physics_added_physics_in_navmesh.jpg|As seen by the navmesh
</gallery>

----
'''More Examples:'''

*Here is another example scenario. This is a sculpted prim fence. The physics shape is not as clean as it could be, and the edges don't cover all edges of the fence itself. To fix it, I created a cube physics shape, linked the fence to the cube with the cube as the root prim, and set the fence to None. As you can see, the resulting physics shape is lower in polygons and better covers the fence area.
<gallery>
File:Sculpty_optimization_001.jpg|Sculpted fence physics shape
File:Sculpty_optimization_002.jpg|Adding cube physics shape
File:Sculpty_optimization_003.jpg|Final Static Object physics shape
</gallery>

*This is a tree comprised of many sculpted pieces. Keep in mind that the physics engine needs to calculate every part of the physics shape in the second picture. Here I created a cylinder for the physics shape to fit on the bottom of the tree trunk. By linking the cylinder to the tree, and setting the tree to physics shape None, I have a much cleaner static object.
<gallery>
File:Sculpty_optimization_004_001.jpg|Sculpted Tree
File:Sculpty_optimization_004_002.jpg|Un-optimized sculpted tree physics shape
File:Sculpty_optimization_004_003.jpg|Adding simplified physics to tree, setting to root
File:Sculpty_optimization_004_004.jpg|Final tree physics set to static obstacle
</gallery>

*These gates are nice clean and simple except for the hippo on the top. We can remove the hippo from the physics engine calculations.
<gallery>
File:Sculptedlamp_2_003.png|Hippo gates
File:Sculptedlamp_2_004.png|Hippo physics
File:Sculptedlamp_2_005.png|Hippo set to NONE (yes, it's really still there!)
</gallery>

Use the following script to set all child prims to None. Be sure to check what physics are needed for your linkset prior to using, and/or add a simple cube as the root prim.
<lsl>
default
{
state_entry()
{
llOwnerSay(0, "Setting all child prims to PRIM_PHYSICS_SHAPE_NONE");
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
llRemoveInventory(llGetScriptName());
}
}
</lsl>

*For more detailed information, have a look at this [http://community.secondlife.com/t5/English-Knowledge-Base/Best-practices-for-creating-efficient-collision-volumes/ta-p/984115 Havok Technical Artist Optimization Guide], a direct excerpt from Havok's documentation. (Havok is the physics and AI engine provider used by Second Life for its physics and pathfinding simulations.) This guide provides details on the best way to optimize your collision shapes and is used by leading artists throughout the games industry.

----
Back to [[Good_Building_Practices]]

Pathfinding Overview

2012-06-21T23:11:10Z

Hyper Mole:

Pathfinding is a method content creators can use to create moving and interactive characters within Second Life. Characters can use LSL functions to avoid obstacles, move around corners, climb inclines, and move across region boundaries: things that are very difficult or even impossible before. Pathfinding will also enable new gameplay mechanics, such as creating food that attracts monsters.

==Terminology==
*Character - an object that uses a Pathfinding LSL function.
*NavMesh - Short for Navigation Mesh. It's a map for characters.

==Functions==
*Evade - Run from a specified avatar or object.
*Flee - Move a specified distance from a specified location.
*Hop
*Navigate - Move to a specified location.
*Patrol - Move along a specified path specified by patrol points.
*Pursue - Follow specified avatar or object.
*Wander - Randomly wander a specified distance from a specified central point.

----
Return to [[Good_Building_Practices]]

Pathfinding Overview

2012-06-21T15:54:59Z

Hyper Mole:

Pathfinding is a method content creators can use to create moving and interactive characters within Second Life. Characters can use LSL functions to avoid obstacles, move around corners, climb inclines, and move across region boundaries: things that are very difficult or even impossible before. Pathfinding will also enable new gameplay mechanics, such as creating food that attracts monsters.

==Terminology==
*Character - an object that uses a Pathfinding LSL function.
*NavMesh - Short for Navigation Mesh.

==Functions==
*Evade - Run from a specified avatar or object.
*Flee - Move a specified distance from a specified location.
*Hop
*Navigate - Move to a specified location.
*Patrol - Move along a specified path specified by patrol points.
*Pursue - Follow specified avatar or object.
*Wander - Randomly wander a specified distance from a specified central point.

----
Return to [[Good_Building_Practices]]

Pathfinding Overview

2012-06-19T19:58:22Z

Hyper Mole: Created page with "Pathfinding is a method content creators can use to create moving and interactive characters within Second Life. Characters can use LSL functions to avoid obstacles, move around…"

Pathfinding is a method content creators can use to create moving and interactive characters within Second Life. Characters can use LSL functions to avoid obstacles, move around corners, climb inclines, and move across region boundaries: things that are very difficult or even impossible before. Pathfinding will also enable new gameplay mechanics, such as creating food that attracts monsters.

==Terminology==
*Character - an object that uses a Pathfinding LSL function.
*NavMesh - Short for Navigation Mesh.

==Functions==
*Evade - Run from a specified avatar or object.
*Flee - Move a specified distance from a specified location.
*Hop
*Navigate - Move to a specified location.
*Patrol - Move along a specified path specified by patrol points.
*Pursue - Follow specified avatar or object.
*Wander - Randomly wander a specified distance from a specified central point.

Walkability Coefficients

2012-06-19T17:34:43Z

Hyper Mole:

<pre style="color:red">Note: Coefficients are currently buggy.</pre>
*Walkable objects can take advantage of coefficients in the [[Pathfinding_NavMesh|navigation mesh]].
*Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Some examples of use would be: Hard road switching to gravel, terrain switching to sandy ruts, deep snow areas, etc.
*You can have four different coefficients per region, controlling character type A, B, C, or D.
*Coefficients can be mixed with [[Material_Volumes|Material Volumes]] to further control character speed and behavior.
*Example: You have a tar pit that character type A can navigate freely, but character type B cannot navigate at all. The tar pit objects would be set to coefficient 100% for type A and 0% for type B.

<gallery>
File:Coefficients_2.png|Coefficients are found in the Linkset floater
File:Coefficients3_001.png|Different speed coefficients mixed with a material volume
</gallery>

----
Return to [[Good_Building_Practices]]

Walkability Coefficients

2012-06-19T17:25:55Z

Hyper Mole:

*Walkable objects can take advantage of coefficients in the [[Pathfinding_NavMesh|navigation mesh]].
*Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Some examples of use would be: Hard road switching to gravel, terrain switching to sandy ruts, deep snow areas, etc.
*You can have four different coefficients per region, controlling character type A, B, C, or D.
*Coefficients can be mixed with [[Material_Volumes|Material Volumes]] to further control character speed and behavior.
*Example: You have a tar pit that character type A can navigate freely, but character type B cannot navigate at all. The tar pit objects would be set to coefficient 100% for type A and 0% for type B.

<gallery>
File:Coefficients_2.png|Coefficients are found in the Linkset floater
File:Coefficients3_001.png|Different speed coefficients mixed with a material volume
</gallery>

----
Return to [[Good_Building_Practices]]

Walkability Coefficients

2012-06-19T17:25:37Z

Hyper Mole:

*Walkable objects can take advantage of coefficients in the [[Pathfinding_NavMesh|navigation mesh]].
*Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Some examples of use would be: Hard road switching to gravel, terrain switching to sandy ruts, deep snow areas, etc.
*You can have four different coefficients per region, controlling character type A, B, C, or D.
*Coefficients can be mixed with [[Material_Volumes|Material Volumes]] to further control character speed and behavior.
*Example: You have a tar pit that character type A can navigate freely, but character type B cannot navigate at all. The tar pit objects would be set to coefficient 100% for type A and 0% for type B.

<gallery>
File:Coefficients_2.png|Coefficients are found in the Linkset floater
Coefficients3_001.png|Different speed coefficients mixed with a material volume
</gallery>

----
Return to [[Good_Building_Practices]]

File:Coefficients3 001.png

2012-06-19T17:24:56Z

Hyper Mole:

Good Building Practices

2012-06-19T17:17:27Z

Hyper Mole: /* Pathfinding */

== Welcome to Good Building Practices ==
This page is all about how to be creative and efficient at the same time!

{| width="100%"
|-
|valign="top"|
<div id="box">

== Animation ==
<div style="padding: 0.5em">
* '''[[Animation Streamlined]]''' - Let's make Second Life move, without dragging it to a crawl!
</div>
</div>

<div id="box">

== Mesh ==
<div style="padding: 0.5em">
* '''[[Making Mesh Physics]]''' - Why and How.
* '''[[Making Mesh for Pathfinding]]''' - Pathfinding friendly mesh.
</div>
</div>

<div id="box">

== Pathfinding ==
<div style="padding: 0.5em">
*'''[[Pathfinding_Overview]]''' - Pathfinding explained.
*'''[[Pathfinding_Quick_Start_Guide]]''' - The best way to get up and running with Pathfinding.
*'''[[Visual_Guide_to_Pathfinding|A Visual Guide]]''' - Watch how easy it is!
*'''[[Walkability_Coefficients]]''' - Control the speed of your Walkable areas.
*'''[[Material_Volumes]]''' - Control the speed of your characters.

</div>
</div>
<div id="box">

== Physics ==
<div style="padding: 0.5em">
* '''[[Physics Optimization]]''' - Not everything needs physics, learn how to add the least load necessary to the physics engine.
* '''[[PRIM_PHYSICS_SHAPE_NONE]]''' - Additional information on this important attribute.

</div>
</div>
|valign="top" width="50%"|
<div id="box">

== Scripting ==
<div style="padding: 0.5em">
* '''[[Smart Scripting]]''' - No lag scripting tips.
*'''[[Scripting for Pathfinding]]''' - Pathfinding scripting help.
</div>
</div>

<div id="box">

== Sculpted Prims ==
<div style="padding: 0.5em">
*'''[[Sculpted Prim Usage]]''' - What you need to know about how sculpted prims effect Second Life.
</div>
</div>

<div id="box">

== Textures ==
<div style="padding: 0.5em">
* '''[[Texture Usage]]''' - What size to use, and what to avoid.
</div>
</div>

|}
__NOTOC__

Making Mesh for Pathfinding

2012-06-17T21:32:40Z

Hyper Mole: Created page with "See Physics_Optimization for ways to make your pathfinding areas efficient. ---- Return to Good_Building_Practices"

See [[Physics_Optimization]] for ways to make your pathfinding areas efficient.

----
Return to [[Good_Building_Practices]]

Material Volumes

2012-06-17T21:25:07Z

Hyper Mole:

==About Material Volumes==
*The Material Volume [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|attribute]] for Pathfinding creates phantom objects that can be set to change the walkability coefficients of an area of the navmesh. Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Pathfinding characters will choose the fastest and closest path available to them. (add video of PF cube choosing 100% walkability path around a MV)
*Material Volumes are visible in the [[Pathfinding_NavMesh|navigation mesh view]] as opaque purple objects.

[[File:Material_volume_001.png|none|300x225px]]

----
Return to [[Good_Building_Practices]]

Material Volumes

2012-06-17T21:24:39Z

Hyper Mole:

==About Material Volumes==
*The Material Volume [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|attribute]] for Pathfinding creates phantom objects that can be set to change the walkability coefficients of an area of the navmesh. Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Pathfinding characters will choose the fastest and closest path available to them. (add video of PF cube choosing 100% walkability path around a MV)
*Material Volumes are visible in the [[Pathfinding_NavMesh|navigation mesh view]] as opaque purple objects.

[[File:Material_volume_001.png|none|400x300px]]

----
Return to [[Good_Building_Practices]]

Walkability Coefficients

2012-06-17T21:20:57Z

Hyper Mole:

*Walkable objects can take advantage of coefficients in the [[Pathfinding_NavMesh|navigation mesh]].
*Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Some examples of use would be: Hard road switching to gravel, terrain switching to sandy ruts, deep snow areas, etc.
*You can have four different coefficients per region, controlling character type A, B, C, or D.
*Coefficients can be mixed with [[Material_Volumes|Material Volumes]] to further control character speed and behavior.

[[File:Coefficients_2.png|none|800x322px]]

*Example: You have a tar pit that character type A can navigate freely, but character type B cannot navigate at all. The tar pit objects would be set to coefficient 100% for type A and 0% for type B.

----
Return to [[Good_Building_Practices]]

Material Volumes

2012-06-17T21:20:34Z

Hyper Mole:

Walkability Coefficients

2012-06-17T21:16:36Z

Hyper Mole:

*Walkable objects can take advantage of coefficients in the [[Pathfinding_NavMesh|navigation mesh]].
*Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.
*Some examples of use would be: Hard road switching to gravel, terrain switching to sandy ruts, deep snow areas, etc.
*You can have four different coefficients per region, controlling character type A, B, C, or D.
*Coefficients can be mixed with [[Material_Volumes|Material Volumes]] to further control character speed and behavior.

[[File:Coefficients_2.png|none|800x322px]]

*Example: You have a tar pit that character type A can navigate freely, but character type B cannot navigate at all. The tar pit objects would be set to coefficient 100% for type A and 0% for type B.

Walkability Coefficients

2012-06-17T21:09:25Z

Hyper Mole:

Walkability Coefficients

2012-06-17T21:07:59Z

Hyper Mole: Created page with "*Walkable objects can take advantage of coefficients in the navigation mesh. *Walkability coefficients are multipliers that may be applied to the speed of…"

File:Coefficients 2.png

2012-06-17T21:03:31Z

Hyper Mole:

File:Coefficients.png

2012-06-17T21:02:50Z

Hyper Mole: uploaded a new version of "File:Coefficients.png"

File:Coefficients.png

2012-06-17T21:00:16Z

Hyper Mole: uploaded a new version of "File:Coefficients.png"

File:Coefficients.png

2012-06-17T20:59:05Z

Hyper Mole:

Good Building Practices

2012-06-17T20:19:13Z

Hyper Mole: /* Pathfinding */

== Welcome to Good Building Practices ==
This page is all about how to be creative and efficient at the same time!

{| width="100%"
|-
|valign="top"|
<div id="box">

== Animation ==
<div style="padding: 0.5em">
* '''[[Animation Streamlined]]''' - Let's make Second Life move, without dragging it to a crawl!
</div>
</div>

<div id="box">

== Mesh ==
<div style="padding: 0.5em">
* '''[[Making Mesh Physics]]''' - Why and How.
* '''[[Making Mesh for Pathfinding]]''' - Pathfinding friendly mesh.
</div>
</div>

<div id="box">

== Pathfinding ==
<div style="padding: 0.5em">
*'''[[Pathfinding_Quick_Start_Guide]]''' - The best way to get up and running with Pathfinding.
*'''[[Visual_Guide_to_Pathfinding|A Visual Guide]]''' - Watch how easy it is!
*'''[[Walkability_Coefficients]]''' - Control the speed of your Walkable areas.
*'''[[Material_Volumes]]''' - Control the speed of your characters.

</div>
</div>
<div id="box">

== Physics ==
<div style="padding: 0.5em">
* '''[[Physics Optimization]]''' - Not everything needs physics, learn how to add the least load necessary to the physics engine.
* '''[[PRIM_PHYSICS_SHAPE_NONE]]''' - Additional information on this important attribute.

</div>
</div>
|valign="top" width="50%"|
<div id="box">

== Scripting ==
<div style="padding: 0.5em">
* '''[[Smart Scripting]]''' - No lag scripting tips.
*'''[[Scripting for Pathfinding]]''' - Pathfinding scripting help.
</div>
</div>

<div id="box">

== Sculpted Prims ==
<div style="padding: 0.5em">
*'''[[Sculpted Prim Usage]]''' - What you need to know about how sculpted prims effect Second Life.
</div>
</div>

<div id="box">

== Textures ==
<div style="padding: 0.5em">
* '''[[Texture Usage]]''' - What size to use, and what to avoid.
</div>
</div>

|}
__NOTOC__

Material Volumes

2012-06-17T20:15:08Z

Hyper Mole:

Material Volumes

2012-06-17T19:35:01Z

Hyper Mole:

Material Volumes

2012-06-17T18:53:31Z

Hyper Mole: Created page with "==About Material Volumes== *The Material Volume attribute for Pathfinding are phantom objects that can be set to cha…"

==About Material Volumes==
*The Material Volume [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|attribute]] for Pathfinding are phantom objects that can be set to change the walkability coefficients of an area of the navmesh. Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.

Good Building Practices

2012-06-17T18:16:13Z

Hyper Mole: /* Pathfinding */

== Welcome to Good Building Practices ==
This page is all about how to be creative and efficient at the same time!

{| width="100%"
|-
|valign="top"|
<div id="box">

== Animation ==
<div style="padding: 0.5em">
* '''[[Animation Streamlined]]''' - Let's make Second Life move, without dragging it to a crawl!
</div>
</div>

<div id="box">

== Mesh ==
<div style="padding: 0.5em">
* '''[[Making Mesh Physics]]''' - Why and How.
* '''[[Making Mesh for Pathfinding]]''' - Pathfinding friendly mesh.
</div>
</div>

<div id="box">

== Pathfinding ==
<div style="padding: 0.5em">
*'''[[Pathfinding_Quick_Start_Guide]]''' - The best way to get up and running with Pathfinding.
*'''[[Visual_Guide_to_Pathfinding|A Visual Guide]]''' - Watch how easy it is!
*'''[[Material_Volumes]]''' - Control the speed of your characters.

</div>
</div>
<div id="box">

== Physics ==
<div style="padding: 0.5em">
* '''[[Physics Optimization]]''' - Not everything needs physics, learn how to add the least load necessary to the physics engine.
* '''[[PRIM_PHYSICS_SHAPE_NONE]]''' - Additional information on this important attribute.

</div>
</div>
|valign="top" width="50%"|
<div id="box">

== Scripting ==
<div style="padding: 0.5em">
* '''[[Smart Scripting]]''' - No lag scripting tips.
*'''[[Scripting for Pathfinding]]''' - Pathfinding scripting help.
</div>
</div>

<div id="box">

== Sculpted Prims ==
<div style="padding: 0.5em">
*'''[[Sculpted Prim Usage]]''' - What you need to know about how sculpted prims effect Second Life.
</div>
</div>

<div id="box">

== Textures ==
<div style="padding: 0.5em">
* '''[[Texture Usage]]''' - What size to use, and what to avoid.
</div>
</div>

|}
__NOTOC__

Pathfinding NavMesh

2012-06-17T18:14:09Z

Hyper Mole:

= Basic Overview =

A look at the Navigation Mesh view of your region can quickly show you exactly how the navmesh system works and help troubleshoot potential problems.

This is the basic view:
<gallery>
File:Navmesh_001.jpg|Show Navmesh ticked on
File:Navmesh_002_002.jpg|Show Navmesh and Static Obstacles ticked on
File:Navmesh1_001.png|Navmesh, Static Obstacles, and Walkables on
File:Navmesh1_002.png|Navmesh, Static Obstacles, Walkables, and World on
</gallery>

The active Navmesh areas are in light grey, with the static obstacle areas outlined in red. The blank void spaces outlined in red are areas where your pathfinding creatures cannot go. These areas can be easily seen when you turn Static Obstacles on.

<gallery>
File:Navmesh_002_003.jpg|Non navigable area in the navmesh
File:Navmesh_002_004.jpg|Non navigable area in the navmesh, static obstacles on
File:Navmesh_002_005.jpg|Non navigable area in the navmesh
File:Navmesh_002_006.jpg|Non navigable area in the navmesh, static obstacles on
</gallery>

In the Test tab of the Edit/Test pathfinding window you can test walkable pathways. Control-click to start your path (pink capsule). Shift-click and drag to see your path (orange capsule and pathway).
Pathfinding characters will calculate the '''fastest''' way to navigate from point A to point B in the navmesh.

<gallery>
File:Navmesh1_004.png|Beginning point of path
File:Navmesh1_005.png|Shift-click and drag to see good pathways
</gallery>

Material Volumes will appear in the navmesh as opaque purple objects. These are phantom objects that can be set to change the walkability coefficients of an area of the navmesh. Walkability coefficients are multipliers that may be applied to the speed of a pathfinding character.

<gallery>
File:Material_volume_001.png|Purple Material Volume added to a walkable surface.
</gallery>

Exclusion Volumes show up as transparent yellow objects. These objects are phantom and pathfinding characters will not move in those area, yet avatars can.

<gallery>
File:Exclusion_001.png|Objects set to Exclusion Volume.
File:Exclusion_use_001.png|Used to keep pathfinding characters on the docks.
File:Exclusion_use_002.png|Used here to keep characters from getting stuck on rocks.
</gallery>

Walkable areas show up in green, and turning the world tick box off with walkables on will give you a good quick view all the walkable surfaces in the navigation mesh.

<gallery>
File:Walkable_001.png|Walkable areas only
File:Walkable_002.png|Walkable with navmesh and world turned on
</gallery>

= Other Notes =
* A pathfinding region will share its nav mesh with its immediate neighbors, which allows cross-region pathfinding.
* The navmesh view that you see in the viewer is from when the simulator last baked the navmesh and only takes permanent objects into account. Movable obstacles, such as avatars or linksets set to "Movable Obstacle" can block characters' paths but are not visible in this navmesh view.
* The minimum size allowed for a nav mesh 'island' (such as an isolated walkable platform which is disconnected from the rest of the nav mesh) is approximately 100m^2.

Pathfinding Quick Start Guide

2012-06-17T18:13:28Z

Hyper Mole:

<span style="color:red">'''Begin by naming all objects in your region! A list of objects named "Object" is not helpful.</span>

'''You will need to use the [[Pathfinding_Tools_in_the_Second_Life_Viewer|linkset tools]] to change the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|pathfinding attributes]] of the objects on your region to improve region performance! See a the [[Visual_Guide_to_Pathfinding]] for more help.

'''By default, all objects are set to Walkable (terrain), Movable Obstacle, or Movable Phantom (phantom objects). You will need to set walls, trees, fences, etc to Static Obstacle. Set floors and other areas that need to be walkable to Walkable.

'''Don't forget to click apply! Then FREEZE your changes for the navigation mesh to update.

[[File:Linksets.png|none|400x187px|left]]

*Terrain is always set to walkable. To prevent characters from entering areas of the terrain, use an [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Exclusion Volume]]
*All objects that you want pathfinding characters to walk upon will need to be set to walkable in the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Pathfinding_Linksets_Floater|Linkset tools]] floater. Walkable objects are green in the navmesh view.
[[File:Pathfinding_003.png|none|400x202px]]

*You will need to Unfreeze before you can make any linkset changes to objects. Basic Setup > Unfreeze.
*Pathfinding Character orientation will always be positive X.
*All objects that are NOT going to be set to walkable should be set according to need:

Walls, fences, trees, gates etc. - '''Static Obstacle'''. Static Obstacles are red in the navigation mesh view.

[[File:Navmesh_002_004.jpg|none|300x255px]]

Movable doors, swinging gates, scripted moving objects that pathfinding characters cannot pass through - '''Movable Obstacle''' (not visible in the navigation mesh view).

Objects that you want ignored by the pathfinding characters - '''Movable Phantom''' (not visible in the navigation mesh view).

Avatars can move through or on, pathfinding characters cannot (this is also good for trouble spots where characters consistently get stuck) - '''Exclusion Volume''' seen as yellow opaque objects in the navigation mesh view.

[[File:Exclusion_use_001.png|none|300x255px]]

*Remember to Apply your linkset object attributes, or the setting won't stick.
*Freeze your changes (edit/test window) to queue the regeneration of the navmesh and "bake" in the changes you have made. The text will change to "Navmesh is up to date" when it's finished.
*Use the Show: [[Pathfinding_NavMesh|navmesh]] tick box (and the world tickbox) to view the navigation mesh and see where you may need to make changes.

For the beta you'll need to disable (or make phantom) objects that change scale, volume parameters, or positon/rotation of child prims to get acceptable sim performance.
For help tracking down problems use:
*Estate tools: Get top colliders and Get top scripts.
*Pathfinding Linkset tools: search for the name of the object and teleport to it, take, delete, take copy, or turn on a beacon.

----
Full Pathfinding tools information can be found [[Pathfinding_Tools_in_the_Second_Life_Viewer|here]].

A quick guide to Good Building Practices can be found [[Good_Building_Practices|here]].

Find helpful Pathfinding scripts [[Pathfinding_Scripts|here]].

The Navigation Mesh explained [[Pathfinding_NavMesh|here]].

Pathfinding Quick Start Guide

2012-06-17T18:00:10Z

Hyper Mole:

<span style="color:red">'''Begin by naming all objects in your region! A list of objects named "Object" is not helpful.</span>

'''You will need to use the [[Pathfinding_Tools_in_the_Second_Life_Viewer|linkset tools]] to change the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|pathfinding attributes]] of the objects on your region to improve region performance! See a the [[Visual_Guide_to_Pathfinding]] for more help.

'''By default, all objects are set to Walkable (terrain), Movable Obstacle, or Movable Phantom (phantom objects). You will need to set walls, trees, fences, etc to Static Obstacle. Set floors and other areas that need to be walkable to Walkable.

'''Don't forget to click apply! Then FREEZE your changes for the navigation mesh to update.

[[File:Linksets.png|none|400x187px|left]]

*Terrain is always set to walkable. To prevent characters from entering areas of the terrain, use an [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Exclusion Volume]]
*All objects that you want pathfinding characters to walk upon will need to be set to walkable in the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Pathfinding_Linksets_Floater|Linkset tools]] floater. Build > Pathfinding.
*You will need to Unfreeze before you can make any linkset changes to objects. Basic Setup > Unfreeze.
*Pathfinding Character orientation will always be positive X.
*All objects that are NOT going to be set to walkable should be set according to need:

Walls, fences, trees, gates etc. - '''Static Obstacle'''

Movable doors, swinging gates, scripted moving objects that pathfinding characters cannot pass through - '''Movable Obstacle'''

Objects that you want ignored by the pathfinding characters - '''Movable Phantom'''

Avatars can move through or on, pathfinding characters cannot (this is also good for trouble spots where characters consistently get stuck) - '''Exclusion Volume'''

*Remember to Apply your linkset object attributes, or the setting won't stick.
*Freeze your changes (edit/test window) to queue the regeneration of the navmesh and "bake" in the changes you have made. The text will change to "Navmesh is up to date" when it's finished.
*Use the Show: [[Pathfinding_NavMesh|navmesh]] tick box (and the world tickbox) to view the navigation mesh and see where you may need to make changes.

For the beta you'll need to disable (or make phantom) objects that change scale, volume parameters, or positon/rotation of child prims to get acceptable sim performance.
For help tracking down problems use:
*Estate tools: Get top colliders and Get top scripts.
*Pathfinding Linkset tools: search for the name of the object and teleport to it, take, delete, take copy, or turn on a beacon.

----
Full Pathfinding tools information can be found [[Pathfinding_Tools_in_the_Second_Life_Viewer|here]].

A quick guide to Good Building Practices can be found [[Good_Building_Practices|here]].

Find helpful Pathfinding scripts [[Pathfinding_Scripts|here]].

The Navigation Mesh explained [[Pathfinding_NavMesh|here]].

File:Linksets.png

2012-06-17T17:48:33Z

Hyper Mole:

Pathfinding Quick Start Guide

2012-06-17T17:44:41Z

Hyper Mole:

<span style="color:red">'''Begin by naming all objects in your region! A list of objects named "Object" is not helpful.</span>

'''You will need to use the [[Pathfinding_Tools_in_the_Second_Life_Viewer|linkset tools]] to change the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|pathfinding attributes]] of the objects on your region to improve region performance! See a the [[Visual_Guide_to_Pathfinding]] for more help.

'''By default, all objects are set to Walkable (terrain), Movable Obstacle, or Movable Phantom (phantom objects). You will need to set walls, trees, fences, etc to Static Obstacle. Set floors and other areas that need to be walkable to Walkable.

'''Don't forget to click apply! Then FREEZE your changes for the navigation mesh to update.

*Terrain is always set to walkable. To prevent characters from entering areas of the terrain, use an [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Exclusion Volume]]
*All objects that you want pathfinding characters to walk upon will need to be set to walkable in the Linkset tools window. Build > Pathfinding.
*You will need to Unfreeze before you can make any linkset changes to objects. Basic Setup > Unfreeze.
*Pathfinding Character orientation will always be positive X.
*All objects that are NOT going to be set to walkable should be set according to need:

Walls, fences, trees, gates etc. - '''Static Obstacle'''

Movable doors, swinging gates, scripted moving objects that pathfinding characters cannot pass through - '''Movable Obstacle'''

Objects that you want ignored by the pathfinding characters - '''Movable Phantom'''

Avatars can move through or on, pathfinding characters cannot (this is also good for trouble spots where characters consistently get stuck) - '''Exclusion Volume'''

*Remember to Apply your linkset object attributes, or the setting won't stick.
*Freeze your changes (edit/test window) to queue the regeneration of the navmesh and "bake" in the changes you have made. The text will change to "Navmesh is up to date" when it's finished.
*Use the Show: navmesh tick box (and the world tickbox) to view the navmesh wireframe and see where you may need to make changes. If you have aqua/blue wireframe lines, you have walkable areas.

For the beta you'll need to disable (or make phantom) objects that change scale, volume parameters, or positon/rotation of child prims to get acceptable sim performance.
For help tracking down problems use:
*Estate tools: Get top colliders and Get top scripts.
*Pathfinding Linkset tools: search for the name of the object and teleport to it, take, delete, take copy, or turn on a beacon.

----
Full Pathfinding tools information can be found [[Pathfinding_Tools_in_the_Second_Life_Viewer|here]].

A quick guide to Good Building Practices can be found [[Good_Building_Practices|here]].

Find helpful Pathfinding scripts [[Pathfinding_Scripts|here]].

The Navigation Mesh explained [[Pathfinding_NavMesh|here]].

Animation Streamlined

2012-06-17T17:37:35Z

Hyper Mole:

==Animating Streamlined==

Your creations are on the move. Congratulations!

What? Now you want their wings flapping and their legs moving?

===What are my options?===

You've got some choices to make. All the methods described here involve tradeoffs, and no one method is best in all situations.

They work with [[Pathfinding|pathfinding-enabled]] and non-pathfinding creations.

====Method: Animated Textures====

[[Image: Animated_hippofly.gif]]

Animate 2D textures on a model to simulate movement.

Most of the time a framed texture is what you'd want, but for something like a millipede's legs you might want to use a tiling texture instead. Here's a 2x2 framed texture next to a picture of it [[LlSetTextureAnim|animated]].

[[Image: Eye Frame.jpg]] [[Image: Eye Frame.gif]]

* This is very low server and viewer lag.
* This is 2D, so it's best for small or flat things.
* SL won't allow you to upload a texture larger than 1024x1024 pixels so resolution may be an issue for textures with a lot of frames.
* Animated textures on a prim can be on one face, or all faces with one direction, so sometimes you have to break a moving section up. (point out Sylvan's flipped UV wheel trick here)

The hippo flies are an example of using model design and animated textures together. The model has several sets of wings. The different frames of the texture each have one pair of wings visible, so when animated the hippo flies seem to flap their wings. Mesh models don't look glitched like a sculpt does when a texture with transparency is applied.

====Method: Flexible Prims====

[[Image: Animated flexibird.gif|100px]]

[[Flex|Flexi]] can be used to simulate smooth movement. Sadly, I couldn't capture how smooth it looks using snapshots.

* A large number of flexi prims in a scene can lag the viewer. Viewer graphic settings can impact how flexi prims are displayed.
* A flexi prim's values can be set in the edit window or changed via script.

====Method: Alpha Animation====

[[Image: Animated_ray.gif|200px]]

Show different pieces of your model at different times to simulate movement.

Make several models of your creature (or parts of your creature) in different poses. Join them into one linkset, usually at the torso. Alternate which parts of the linkset are visible.

* Higher LI/prim count than other methods.
* It induces less server lag than moving the prims, but the viewer receives a message for every alpha change.

====Method: Prim Movement====

[[Image: Animated_bunny.gif|200px]]

This method repositions and resizes pieces to simulate movement.

* Lower LI/prim count than alpha animation.
* Moving prims that have a [[PRIM_PHYSICS_SHAPE_TYPE]] other than [[PRIM_PHYSICS_SHAPE_NONE]] can cause '''extreme''' server lag
* The viewer receives a message for each prim change.
* Using the edit window to resize a creature that uses prim movement can break the creature.

====Method: Sculpt Map Swap====

[[Image: Animated flock.gif]][[Image: Animated_pigeon.gif]]

Swap the prim's sculpt map to simulate movement.

* Lower LI/prim count than alpha animation. Beware of LI when using sculpts!
* It generates a LOT of viewer lag. The viewer receives a message for each prim change. The viewer recalculates the sculpt mesh with each change. Consider hidden prims in your creature showing the next "frame" or having a flock out.
** The impact of the recalculating can be softened by having prims within loading range showing the same sculpt shapes
** If the sculpt map texture isn't currently in the scene, it may be removed from the viewer's cache, so it may be end up being sent to the viewer multiple times. The blue-outlined cube behind the pigeon has the sculpt map textures on its sides, so the viewer doesn't remove them from the cache while the bird is in sight.

===How do I make it happen?===

====Physics Shape Type: None====

This value allows you to tell the physics engine to [[Physics_Optimization|ignore prims]] when it is doing calculations. Your creature will explore much more efficiently if there's no need to calculate whether each toenail might be colliding with that rock!

You can't set this to none on a root prim.

If you select an object and toggle it to none in the edit window, all the child prims will be set.

You can set this via script using [[LlSetLinkPrimitiveParamsFast|llSetLinkPrimitiveParamsFast]] with [[PRIM_PHYSICS_SHAPE_TYPE]] set to [[PRIM_PHYSICS_SHAPE_NONE]].

====Getting the link number====

A lot of the scripting calls used here expect you to have the link ID number.

What's a [http://wiki.secondlife.com/wiki/Link| linkset or link ID? ]

[[Image: Bunny_in_a_hat.png|right]]

You can find the absolute link ID of a prim in your linkset, but those numbers are only reliable until the next time you decide to add or remove a prim from your build. Naming the prims in your creature useful things like "leg" or "wing" things will prevent your scripts from breaking when you decide your bunny needs a top hat.

Code snippets for finding [[http://wiki.secondlife.com/wiki/LinksetIndexing| link IDs via prim name]] can be found here.

====Animating a texture====

Use [[llSetTextureAnim|llSetTextureAnim]] and [[llSetLinkTextureAnim|llSetLinkTextureAnim]] with a texture to simulate movement.

====Setting flexible prim values====

Use [[LlSetLinkPrimitiveParamsFast|llSetLinkPrimitiveParamsFast]] and the [[PRIM_FLEXIBLE]] flag.

====Setting alpha values====

Use [[llSetLinkAlpha|llSetLinkAlpha]] to change which pieces are visible at any one time.

====Moving prims====

Use [[LlSetLinkPrimitiveParamsFast|llSetLinkPrimitiveParamsFast]] with the prim position, rotation, and size flags.

====Swapping sculpt maps====

Use [[LlSetLinkPrimitiveParamsFast|llSetLinkPrimitiveParamsFast]] with the [[PRIM_TYPE_SCULPT]] flag to set a prim's sculpt map.

----
Return to [[Good_Building_Practices]]

Pathfinding Quick Start Guide

2012-06-16T22:19:04Z

Hyper Mole:

'''Begin by naming all objects in your region! A list of objects named "Object" is not helpful

'''You will need to use the [[Pathfinding_Tools_in_the_Second_Life_Viewer|linkset tools]] to change the [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|pathfinding attributes]] of the objects on your region to improve region performance! See a the [[Visual_Guide_to_Pathfinding]] for more help.

'''By default, all objects are set to Walkable (terrain), Movable Obstacle, or Movable Phantom (phantom objects). You will need to set walls, trees, fences, etc to Static Obstacle. Set floors and other areas that need to be walkable to Walkable.

'''Don't forget to click apply! Then FREEZE your changes for the navigation mesh to update.

*Terrain is always set to walkable. To prevent characters from entering areas of the terrain, use an [[Pathfinding_Tools_in_the_Second_Life_Viewer#Example_use_3|Exclusion Volume]]
*All objects that you want pathfinding characters to walk upon will need to be set to walkable in the Linkset tools window. Build > Pathfinding.
*You will need to Unfreeze before you can make any linkset changes to objects. Basic Setup > Unfreeze.
*Pathfinding Character orientation will always be positive X.
*All objects that are NOT going to be set to walkable should be set according to need:

Walls, fences, trees, gates etc. - '''Static Obstacle'''

Movable doors, swinging gates, scripted moving objects that pathfinding characters cannot pass through - '''Movable Obstacle'''

Objects that you want ignored by the pathfinding characters - '''Movable Phantom'''

Avatars can move through or on, pathfinding characters cannot (this is also good for trouble spots where characters consistently get stuck) - '''Exclusion Volume'''

*Remember to Apply your linkset object attributes, or the setting won't stick.
*Freeze your changes (edit/test window) to queue the regeneration of the navmesh and "bake" in the changes you have made. The text will change to "Navmesh is up to date" when it's finished.
*Use the Show: navmesh tick box (and the world tickbox) to view the navmesh wireframe and see where you may need to make changes. If you have aqua/blue wireframe lines, you have walkable areas.

For the beta you'll need to disable (or make phantom) objects that change scale, volume parameters, or positon/rotation of child prims to get acceptable sim performance.
For help tracking down problems use:
*Estate tools: Get top colliders and Get top scripts.
*Pathfinding Linkset tools: search for the name of the object and teleport to it, take, delete, take copy, or turn on a beacon.

----
Full Pathfinding tools information can be found [[Pathfinding_Tools_in_the_Second_Life_Viewer|here]].

A quick guide to Good Building Practices can be found [[Good_Building_Practices|here]].

Find helpful Pathfinding scripts [[Pathfinding_Scripts|here]].

The Navigation Mesh explained [[Pathfinding_NavMesh|here]].