User:Becky Pippen - Revision history

Becky Pippen: Remove link to page of obsolete script timing measurements.

2011-09-02T18:06:39Z

Remove link to page of obsolete script timing measurements.

← Older revision		Revision as of 11:06, 2 September 2011
Line 37:		Line 37:
	* '''''C# and other languages:''''' probably added at some future time.		* '''''C# and other languages:''''' probably added at some future time.


	~~== LSL Timings and Rates ==~~
	~~Updated and [[User:Becky_Pippen/LSL_Performance\|moved to this page]].~~

Becky Pippen: Add links to new pages CloudBeGone and RuthCloudScript.

2011-02-14T01:22:34Z

Add links to new pages CloudBeGone and RuthCloudScript.

← Older revision		Revision as of 18:22, 13 February 2011
Line 109:		Line 109:
	[[User:Becky_Pippen/Shared_Media_LSL_Recipes\|See here]]		[[User:Becky_Pippen/Shared_Media_LSL_Recipes\|See here]]

			==Cloud Be Gone!==
			Tired of being a Ruth Cloud? See [[User:Becky_Pippen/CloudBeGone\|this article]] for the technical reasons why
			various solutions work or not.

			For fun, [[User:Becky_Pippen/RuthCloudScript\|see here for a Ruth Cloud LSL script]].

	== Links ==		== Links ==

Becky Pippen: remove a couple of obsolete links.

2011-02-14T01:18:27Z

remove a couple of obsolete links.

← Older revision		Revision as of 18:18, 13 February 2011
Line 111:		Line 111:

	== Links ==		== Links ==
	* [http://slurl.com/secondlife/Nevia/128/128/23 The Community of the Nevia Archipelago] [http://www.inkwelle.com Website]
	* [http://jira.secondlife.com/ JIRA Issue Tracker]		* [http://jira.secondlife.com/ JIRA Issue Tracker]
	* [https://wiki.secondlife.com/wiki/About_AWG Architecture Working Group]		* [https://wiki.secondlife.com/wiki/About_AWG Architecture Working Group]
	* [https://wiki.secondlife.com/wiki/Mono Mono wiki]
	{{skills		{{skills
	\|Builder=*		\|Builder=*

Becky Pippen: Add link to User:Becky_Pippen/Shared_Media_LSL_Recipes

2010-03-22T23:01:58Z

Add link to User:Becky_Pippen/Shared_Media_LSL_Recipes

← Older revision		Revision as of 16:01, 22 March 2010
Line 104:		Line 104:
	* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]		* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
	* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]		* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]


			==Shared Media-on-a-Prim LSL recipes ==
			[[User:Becky_Pippen/Shared_Media_LSL_Recipes\|See here]]


	== Links ==		== Links ==

Becky Pippen: Moved the LSL performance data to User:Becky_Pippen/LSL_Performance

2010-02-17T18:42:22Z

Moved the LSL performance data to User:Becky_Pippen/LSL_Performance

Show changes

Becky Pippen: minor formatting

2010-01-06T22:36:58Z

minor formatting

← Older revision		Revision as of 15:36, 6 January 2010
Line 450:		Line 450:
	* [[User:Becky_Pippen/Script_Memory_Limits\| A checklist for scripters -- techniques for reducing memory usage]]		* [[User:Becky_Pippen/Script_Memory_Limits\| A checklist for scripters -- techniques for reducing memory usage]]
	* [[User:Becky_Pippen/New_LSL_Functions\| New LSL functions llGetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast()]]		* [[User:Becky_Pippen/New_LSL_Functions\| New LSL functions llGetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast()]]
	* [[User:Becky_Pippen/~~Key_Storage~~\| Scripting techniques for ~~storing lots of keys (UUIDs)~~]]		* [[User:Becky_Pippen/Hashing\| Scripting techniques for hashing data to conserve memory]]
	* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]		* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]
	* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]		* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]
	* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]		* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
	* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]		* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]



	== Links ==		== Links ==

Becky Pippen at 21:51, 2 January 2010

2010-01-02T21:51:14Z

← Older revision		Revision as of 14:51, 2 January 2010
Line 452:		Line 452:
	* [[User:Becky_Pippen/Key_Storage\| Scripting techniques for storing lots of keys (UUIDs)]]		* [[User:Becky_Pippen/Key_Storage\| Scripting techniques for storing lots of keys (UUIDs)]]
	* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]		* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]
			* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]
	* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]		* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
	* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]		* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]

Becky Pippen: added a few links to resources about script memory limits

2009-12-31T20:40:23Z

added a few links to resources about script memory limits

← Older revision		Revision as of 13:40, 31 December 2009
Line 442:		Line 442:
	The last two forces mentioned above work against each other, so the challenge for animators is to find a balance. The animation needs to be made with a high enough frame rate to describe the movements the way you want them to appear, yet it needs to be as low a frame rate as possible to avoid having the client discard small movements on upload. It depends on the animation, but a good starting point might be around 10 FPS for the animation. Try a lower animation frame rate if the animation appears ok with fewer frames, relying more on the linear interpolation by the client to smooth it out. Use a higher animation frame rate if the linear interpolation doesn't look quite right and you need finer resolution to describe more complex or non-linear movements.		The last two forces mentioned above work against each other, so the challenge for animators is to find a balance. The animation needs to be made with a high enough frame rate to describe the movements the way you want them to appear, yet it needs to be as low a frame rate as possible to avoid having the client discard small movements on upload. It depends on the animation, but a good starting point might be around 10 FPS for the animation. Try a lower animation frame rate if the animation appears ok with fewer frames, relying more on the linear interpolation by the client to smooth it out. Use a higher animation frame rate if the linear interpolation doesn't look quite right and you need finer resolution to describe more complex or non-linear movements.


			== Script Memory Limits ==
			Script Memory limits are coming in 2010! Here's some information to help you prepare;
			* [[User:Becky_Pippen/Memory_Limits_FAQ\| FAQ about script memory limits]]
			* [[User:Becky_Pippen/Measure_Script_Memory_Usage\|Measuring your script memory usage]]
			* [[User:Becky_Pippen/Memory_Efficiency\|Calculating memory needed and memory usage efficiency]]
			* [[User:Becky_Pippen/Script_Memory_Limits\| A checklist for scripters -- techniques for reducing memory usage]]
			* [[User:Becky_Pippen/New_LSL_Functions\| New LSL functions llGetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast()]]
			* [[User:Becky_Pippen/Key_Storage\| Scripting techniques for storing lots of keys (UUIDs)]]
			* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]
			* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
			* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]

Becky Pippen at 19:53, 22 April 2009

2009-04-22T19:53:08Z

← Older revision		Revision as of 12:53, 22 April 2009
Line 394:		Line 394:

	== Animation Frame Rate ==		== Animation Frame Rate ==
			=== The Problem ===
	You may have heard rumors that animations (BVH files) get reduced to 12 FPS when uploaded or played, and there's no need to make an animation faster than 12 frames per second (FPS). Other rumors say that fast animation frame rates give smoother animations, while other rumors say that you should use the lowest animation frame rate possible. Confused? Here's some information that might help.		You may have heard rumors that animations (BVH files) get reduced to 12 FPS when uploaded or played, and there's no need to make an animation faster than 12 frames per second (FPS). Other rumors say that fast animation frame rates give smoother animations, while other rumors say that you should use the lowest animation frame rate possible. Confused? Here's some information that might help.
			=== The SL Viewer Interpolates ===
	Part of the confusion is that the term "frame rate" means different things in different contexts. The SL viewer renders frames of the scene, including any animations in the scene, as fast as it can. You can always see how fast the client is rendering frames by looking for the FPS number in the Basic section in the Statistics Bar (Ctrl-Shift-1). The frame rate in an animation file is just there to establish the time scale of the animation information. It's a different kind of "frame." So how do the two "frame rates" relate and how does it all work? It's simple -- when the viewer renders a frame, it determines how far along it is in the animation and interpolates the avatar's bone rotations based on the nearest two frames in the animation file.		Part of the confusion is that the term "frame rate" means different things in different contexts. The SL viewer renders frames of the scene, including any animations in the scene, as fast as it can. You can always see how fast the client is rendering frames by looking for the FPS number in the Basic section in the Statistics Bar (Ctrl-Shift-1). The frame rate in an animation file is just there to establish the time scale of the animation information. It's a different kind of "frame." So how do the two "frame rates" relate and how does it all work? It's simple -- when the viewer renders a frame, it determines how far along it is in the animation and interpolates the avatar's bone rotations based on the nearest two frames in the animation file.

	Refer to the following illustration to see how you can demonstrate this interpolation. Using your favorite animation editor, make an animation file consisting of just three or four frames. The first frame is the requisite reference frame, then frame 2 is the first key frame of the animation that defines the start of a movement. Frame 3 is the last frame of the movement. Optionally you can add a frame 4 that is a copy of frame2 to make a loop. Make a large movement between frames 2 and 3, such as arms straight down in frame 2 and straight up in frame 3. Set the animation for 1 frame per second. Upload the short animation file and set the looping parameters if needed so that the animation loops continuously.		Refer to the following illustration to see how you can demonstrate this interpolation. Using your favorite animation editor, make an animation file consisting of just three or four frames. The first frame is the requisite reference frame, then frame 2 is the first key frame of the animation that defines the start of a movement. Frame 3 is the last frame of the movement. Optionally you can add a frame 4 that is a copy of frame2 to make a loop. Make a large movement between frames 2 and 3, such as arms straight down in frame 2 and straight up in frame 3. Set the animation for 1 frame per second. Upload the short animation file and set the looping parameters if needed so that the animation loops continuously.

	With the animation set to one frame per second, the arms should start at the sides, then one second later be raised above the head, then two seconds after the start of the animation, the arms should be back at the sides, then repeat. What happens if the client ~~renderis~~ frames faster than one per second? If the viewer didn't interpolate, you would expect the avatar's arms to snap suddenly from one position to the other... snap up... snap down... etc. at one-second intervals. But that's not what happens at all. Regardless of your viewer frame rate, you'll see your avatar's hands moving smoothly, up and down, with all the intermediate positions between animation frames interpolated smoothly. To examine the effect in more detail, click Advanced->Character->Slow Motion Animations, then you'll have a whole bunch of interpolated rendered frames to examine.		With the animation set to one frame per second, the arms should start at the sides, then one second later be raised above the head, then two seconds after the start of the animation, the arms should be back at the sides, then repeat. What happens if the client renders frames faster than one per second? If the viewer didn't interpolate, you would expect the avatar's arms to snap suddenly from one position to the other... snap up... snap down... etc. at one-second intervals. But that's not what happens at all. Regardless of your viewer frame rate, you'll see your avatar's hands moving smoothly, up and down, with all the intermediate positions between animation frames interpolated smoothly. To examine the effect in more detail, click Advanced->Character->Slow Motion Animations, then you'll have a whole bunch of interpolated rendered frames to examine.

	[[Image:Animation-interpolation.jpg\|500px\|\|\|Viewer interpolates animation frames]]		[[Image:Animation-interpolation.jpg\|500px\|\|\|Viewer interpolates animation frames]]

			=== Asynchronous Frame Rates ===
	In the following timeline example, the top lines represent the frames in an animation file, and the bottom lines show how fast the viewer renders frames and where the rendered frames correspond in time to the animation file. In this illustration, the animation frames are numbered starting at two, because frame one is the reference frame that never gets rendered. When the client is rendering the first frame of the animation (render frame 0 in the illustration), it corresponds to frame 2 in the animation file. In this illustration, the client is running at a fairly constant rate a little more than three times the rate of frames in the animation file:		In the following timeline example, the top lines represent the frames in an animation file, and the bottom lines show how fast the viewer renders frames and where the rendered frames correspond in time to the animation file. In this illustration, the animation frames are numbered starting at two, because frame one is the reference frame that never gets rendered. When the client is rendering the first frame of the animation (render frame 0 in the illustration), it corresponds to frame 2 in the animation file. In this illustration, the client is running at a fairly constant rate a little more than three times the rate of frames in the animation file:
	<lsl>		<lsl>
Line 429:		Line 429:
	</lsl>		</lsl>
	In this scenario, when it's time for the client to render frame 1, the animation information is interpolated from frames 4 and 5 in the animation file, which means that any quick movement defined in frames 3 and 4 of the animation file will have been ignored that time around. If the animation loops, then perhaps on a subsequent loop the frames will align differently and a different set of animation frames will be ignored.		In this scenario, when it's time for the client to render frame 1, the animation information is interpolated from frames 4 and 5 in the animation file, which means that any quick movement defined in frames 3 and 4 of the animation file will have been ignored that time around. If the animation loops, then perhaps on a subsequent loop the frames will align differently and a different set of animation frames will be ignored.

			=== Other Considerations ===
	There are additional forces at work you need to be aware of:		There are additional forces at work you need to be aware of:

Line 437:		Line 439:
	3. When the viewer interpolates bone rotations from the animation file, it uses a linear interpolation between the nearest frames, which sometimes looks a bit robotic. A higher animation rate lets you specify movements in finer resolution and make the movement start slow, get faster in the middle of the movement, then slow down when it reaches its maximum extent.		3. When the viewer interpolates bone rotations from the animation file, it uses a linear interpolation between the nearest frames, which sometimes looks a bit robotic. A higher animation rate lets you specify movements in finer resolution and make the movement start slow, get faster in the middle of the movement, then slow down when it reaches its maximum extent.

			=== Summary ===
	The last two forces mentioned above work against each other, so the challenge for animators is to find a balance. The animation needs to be made with a high enough frame rate to describe the movements the way you want them to appear, yet it needs to be as low a frame rate as possible to avoid having the client discard small movements on upload. It depends on the animation, but a good starting point might be around 10 FPS for the animation. Try a lower animation frame rate if the animation appears ok with fewer frames, relying more on the linear interpolation by the client to smooth it out. Use a higher animation frame rate if the linear interpolation doesn't look quite right and you need finer resolution to describe more complex or non-linear movements.		The last two forces mentioned above work against each other, so the challenge for animators is to find a balance. The animation needs to be made with a high enough frame rate to describe the movements the way you want them to appear, yet it needs to be as low a frame rate as possible to avoid having the client discard small movements on upload. It depends on the animation, but a good starting point might be around 10 FPS for the animation. Try a lower animation frame rate if the animation appears ok with fewer frames, relying more on the linear interpolation by the client to smooth it out. Use a higher animation frame rate if the linear interpolation doesn't look quite right and you need finer resolution to describe more complex or non-linear movements.

Becky Pippen at 19:48, 22 April 2009

2009-04-22T19:48:47Z

← Older revision		Revision as of 12:48, 22 April 2009
Line 404:		Line 404:

	[[Image:Animation-interpolation.jpg\|500px\|\|\|Viewer interpolates animation frames]]		[[Image:Animation-interpolation.jpg\|500px\|\|\|Viewer interpolates animation frames]]


	In the following timeline example, the top lines represent the frames in an animation file, and the bottom lines show how fast the viewer renders frames and where the rendered frames correspond in time to the animation file. In this illustration, the animation frames are numbered starting at two, because frame one is the reference frame that never gets rendered. When the client is rendering the first frame of the animation (render frame 0 in the illustration), it corresponds to frame 2 in the animation file. In this illustration, the client is running at a fairly constant rate a little more than three times the rate of frames in the animation file:		In the following timeline example, the top lines represent the frames in an animation file, and the bottom lines show how fast the viewer renders frames and where the rendered frames correspond in time to the animation file. In this illustration, the animation frames are numbered starting at two, because frame one is the reference frame that never gets rendered. When the client is rendering the first frame of the animation (render frame 0 in the illustration), it corresponds to frame 2 in the animation file. In this illustration, the client is running at a fairly constant rate a little more than three times the rate of frames in the animation file:

← Older revision		Revision as of 15:36, 6 January 2010
Line 450:		Line 450:
	* [[User:Becky_Pippen/Script_Memory_Limits\| A checklist for scripters -- techniques for reducing memory usage]]		* [[User:Becky_Pippen/Script_Memory_Limits\| A checklist for scripters -- techniques for reducing memory usage]]
	* [[User:Becky_Pippen/New_LSL_Functions\| New LSL functions llGetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast()]]		* [[User:Becky_Pippen/New_LSL_Functions\| New LSL functions llGetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast()]]
	* [[User:Becky_Pippen/~~Key_Storage~~\| Scripting techniques for ~~storing lots of keys (UUIDs)~~]]		* [[User:Becky_Pippen/Hashing\| Scripting techniques for hashing data to conserve memory]]
	* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]		* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]
	* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]		* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]
	* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]		* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
	* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]		* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]



	== Links ==		== Links ==

← Older revision		Revision as of 14:51, 2 January 2010
Line 452:		Line 452:
	* [[User:Becky_Pippen/Key_Storage\| Scripting techniques for storing lots of keys (UUIDs)]]		* [[User:Becky_Pippen/Key_Storage\| Scripting techniques for storing lots of keys (UUIDs)]]
	* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]		* [[User:Becky_Pippen/Numeric_Storage\| Scripting techniques for storing arbitrary binary data without lists]]
			* [[User:Becky_Pippen/Text_Storage\| Scripting techniques for compressing ASCII text in Mono]]
	* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]		* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage Empirical measurements of memory usage by data type and scope (lslwiki.net)]
	* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]		* [[LSL_Script_Memory\|Empirical measurements of memory usage by data type and scope (SL wiki)]]