OpenSimWorld @opensimworld

Offline

Visit OpenSimWorld to get the latest versions of the OpenSimWorld beacon, the SatyrFarm, SFposer and SFsail


ActiveNPCs: An interactive-NPC controller

<h1>ActiveNPCs NPC Controller</h1>
<p>This is a full-featured controller for creating interactive NPCs , scripting them (through notecards) and creating waypoints of your region so that the NPCs can walk around your region. The controller is extremely lightweight (a single script manages all the NPCs) and the NPCs are interactive (i.e. you can give them commands through the local chat).</p>
<p>You can get the latest package from the OpenSimWorld region:</p>
<p><a href="http://opensimworld.com/hop/74730-OpenSimWorld">http://opensimworld.com/hop/74730-OpenSimWorld&lt;/a&gt;&l...
<p>Hypergrid: hg.osgrid.org:80:OpenSimWorld</p>
<h1>Quickstart</h1>
<p>The controller requires OSSL functions to work. You need to have permission to use the osNpc*() functions and, additionally: , osGetNotecard(), osGetNotecardLines(), osMessageAttachments(), osSetSpeed(). The controller uses the channel 68 to communicate.</p>
<p>To start using the controller:</p>
<ul>
<li>Rez the OSW NPC Controller object somewhere in your region. Make sure your avatar is within distance of 20m or less from the controller</li>
<li>Wear the OSW NPC Listener object (it should attach automatically to your Right Pec!)</li>
<li>Edit the <code>__npc_names</code> notecard, and place first name and last names of each of your NPCs in a line by itself. Example:
<pre><code>Bob TheRobot
Alice TheNPC
</code></pre>
</li>
<li>Touch the controller -> ReConfig</li>
<li>Touch the controller, SaveNPC -> Bob (You should see a message "Saved appearance xxx-xxx -> APP_bob"</li>
<li>Touch the controller -> LoadNPC -> Bob</li>
</ul>
<p>Your npc should now be responding to commands , e.g. "Bob come"</p>
<h1>Controller object Contents</h1>
<ul>
<li>The controller script (..Controller). This is the single script that runs everything.</li>
<li>An example extension script (..Extension). This can be used to add commands to the system (explained below).</li>
<li>The Listener object. All our NPCs must wear this invisible object on their Right Pec. This object listens for commands from the local chat and forwards them to the controller script for processing.</li>
<li>The __npc_names notecard. This notecard contains the names of the NPCs, one in each line . After making changes to this notecard, select "Reconfig" from the controller menu.</li>
<li>The __initcommands notecard. This is a notecard with the commands that are executed when you click "InitCmds" on the controller menu.</li>
<li>The <strong>waypoints notecard. This contains a list of points in your region. The NPCs can walk from one point to the other, if they are connected (via the </strong>links notecard) . <em>You do not need to edit this by hand. There is an HUD for editing the map</em></li>
<li>The __links notecard. This contains a list of pairs of connected points. I.e. if you want to link point 1 to point 2, there will be a line "1,2" in the notecard. <em>You do not need to edit this by hand. There is an HUD for editing the map</em></li>
<li>The __config notecard. This contains configuration ootions.</li>
<li>Command notecards. You can put any list of commands for NPCs a notecard named [command-name].scr. You can then order your NPCs to execute the notecards from the local chat. E.g. if you create a notecard "dance.scr", you can say "Bob dance" to execute it.</li>
<li>Waypoint notecards. Notecards named _1.scr , _2.scr etc are executed automatically when the NPCs reach the waypoint number 1, number 2 etc.</li>
<li>The appearance notecards are stored as APP_[firstname] for each NPC. You can also have multiple appearances per NPC (see below).</li>
<li>The Waypoint HUD is used to edit the map and create/update the <strong>waypoints and </strong>links notecards</li>
</ul>
<h1>Overview of commands</h1>
<p>The NPCs respond to commands that you give to them through the local chat.</p>
<p>Assuming your NPC is named "Bob", you can say the following in the local chat:</p>
<pre><code> Bob come
Bob leave
Bob stop
Bob follow me
Bob fly with me
Bob say hi
...
etc.
</code></pre>
<p>You can put these commands in notecards in order to create complex scenarios.</p>
<p>For more complex behavior, the following control commands are supported in notecards: if, if-not, jump</p>
<p>Example of a scenario notecard:</p>
<pre><code> if name-is Bob Alice
say hi
say I am either Bob or Alice
jump outofhere
end-if
say i am not bob or alice
@outofhere
if-not name-is Bob
say I am definitely not Bob
end-if
say ... and i 'm now leaving
leave
</code></pre>
<p>You can add these commands to a notecard named "test.scr" inside the controller object, and then ask the Bob to execute them by saying "Bob test" in the local chat.</p>
<h1>List of NPC commands</h1>
<p>When giving commands through the local chat, commands must be preceded by the first name of the NPC. Here we assume our NPC is called "Bob"</p>
<pre><code> Bob come : "Come here ". Bob will move close to you
Bob moveto 23 : Walk towards waypoint #23
Bob movetov <23,24,25> : walk towards point with coordinates <23,24,25> (Note, no spaces between vector coordinates)
Bob runtov <23,24,25> : run towards point with coordinates <23,24,25>
Bob flytov <23,24,25> : fly towards point <23,24,25> in region
Bob movetovr <23,24,25> <33,34,25> : walk to a random point between the points <23,24,25> <33,34,25>
Bob runtovr <23,24,25> <33,34,25> : same as above, but run
</code></pre>
<ul>
<li>
<ul>
<li>Note: never leave spaces in coordinate vectors, i.e. <23,24,25> NOT <23, 24, 25> **</li>
</ul>
</li>
</ul>
<pre><code>Bob say hi : Says "hi" on public channel
Bob saych 90 blablah : say "blablah" on channel 90
Bob shout Blah bleh
Bob teleport <23,30,40> : Teleports to a point. REMEMBER: no spaces inside the vector brackets
Bob lookat me : attempts to look at you
Bob lookat <x,y,z> : look towards point x,y,z
Bob anim dance : play animation "dance" . the animation must be in the inventory of the controller object
Bob sound 1c8a3af2-6e5a-4807-a7a3-a42e5744217c 1.0 : The NPC will trigger the sound with the given UUID at the volume specified by the second parameter (1.0 is max volume)
Bob light : turn on/off a light the NPCs have on them
Bob give Apple : Give the object "Apple" from the controller's inventory to the user. For security, only Objects can be given.
Bob follow me
Bob follow Alice : follow the avatar whose first name is 'Alice'
Bob fly with me
Bob fly with alice : fly with another user
Bob stop : Stops his animation and his movement, and stops following you
</code></pre>
<h3>Waypoint and Pathfinding commands</h3>
<p>You need to have set up the map of your region for these commands. That is described elsewhere. The NPC can automatically try to find how to walk from waypoint A to B. Because this is computationally intensive, only paths with less than 15 connections between them are supported.</p>
<pre><code>Bob leave : Start walking randomly between connected waypoints
Bob teleport Bar : Teleports bob to the waypoint named "Bar"
Bob lookat Bar : look towards the waypoint named "Bar"
Bob moveto 1 : Walk to waypoint #1
Bob nearest : Tell me which is the nearest waypoint
Bob setpath 0:1:3:5:1:0 : Walk through the given waypoints, i.e. walk to waypoint 0 , then to 1, then to 3, then to 5 etc.
Bob goto 13 : Will walk between connected waypoints to waypoint #13
Bob go to Bar : Will walk between connected waypoints to the waypoint named "Bar"
: BEWARE! "goto" and "go to" (with space) are different commands
Bob go to : without a destination, Bob will print the names of waypoints he knows
</code></pre>
<h2>Command Notecards</h2>
<p>Multiple commands can be appended to a notecard, and then the NPC can execute them.</p>
<pre><code>Bob run-notecard my_script.scr : Execute the contents of the notecard my_script.scr (the notecard must be in the controller inventory
Bob my_script : Simpler syntax. Same as run-notecard: Starts executing the notecard "my_script.scr"
Bob batch say hi ; wait 10; say bye : Executes multiple commands one after the other. Commands are separated by ";" The commands will be executed as if they were in a notecard
Bob stop-script : Stop executing the notecard script
</code></pre>
<h2>Multiple appearances</h2>
<p>You can have multiple appearance notecards for an NPC by renaming them. The default notecard for NPC Bob is stored in the APP_bob notecard. You can rename the notecard to, e.g. APP_bob_swimming, and then ask bob to load that notecard:</p>
<pre><code>Bob dress swimming : load the appearance from notecard "APP_bob_swimming"
Bob dress : load the NPC's default appearance from notecard "APP_bob"
</code></pre>
<h2>Sitting on objects</h2>
<p>The NPCs can sit on objects with the "use" command.</p>
<pre><code>Bob use chair
</code></pre>
<p>Bob will attempt to find a SCRIPTED object (e.g. a poseball) named "chair" (You can change the Object Name from the properties box when editing it) near him and try to sit on it if its transparency (alpha) is less than 100%. Since by convention poseballs change their transparency to 100% when users sit on them, this ensures that Bob will not sit on an already-occupied poseball. If you just say "Bob use", the NPC will sit on the nearest scripted object.</p>
<pre><code>Bob stand : Bob will stand up if he is sitting
</code></pre>
<h2>Variables</h2>
<p>Variables can be used with IF commands in notecards for more complex behavior.Variables are global and shared between notecards and NPCs.</p>
<pre><code>Bob setvar foo 13 : set variable foo to be "13". Only string variables are supported. Variables can be used with IF blocks
Bob setvar foo : set variable foo to the empty string. (The empty string is the default value if a variable does not exist)
Bob say $foo : Bob says "13"
if var-is foo 13
say foo is thirteen
end-if
if var-is foo
say foo is empty string or not set
end-if
waitvar foo 13 : wait (and do nothing) until the variable foo becomes 13
</code></pre>
<p>The following commands increase and decrease a variable by 1. They are useful in cases where you want 2 or more avatars to be present to proceed:</p>
<pre><code>increase totalAvatarsHere : Increase the variable "totalAvatarsHere" by 1
decrease totalAvatarsHere : Decrease the variable "totalAvatarsHere" by 1
zero totalAvatarsHere : Set variable totalAvatarsHere to 0 (same as setvar totalAvatarsHere 0)
</code></pre>
<p>Example usage in a notecard:</p>
<pre><code>increase totalAvatarsHere
waitvar totalAvatasHere 2
say Now there are 2 of us
anim dance
wait 10
stop
...
say Time to depart
decrease totalAvatarsHere
</code></pre>
<h2>IF commands</h2>
<p>There is support for multiple levels of IF blocks. Blocks must end with "end-if". There is no "else" command, but you can achieve the same effect with "jump" commands</p>
<pre><code>if name-is bob alice : if the npc's name is Bob or alice
say I am either Bob or Alice
if-not name-is Bob
say I must be Alice
end-if
end-if : always end IF blocks with end-if. You can nest if blocks
if-not name-is Bob : Example of negative if
say I am not Bob
end-if
if-prob 0.3 : IF block will be executed with probabilty 0.3 (the if block will be executed 30% of the time)
say This will be heard 30% of the times
end-if
if var-is party 1 : Will execute the IF block if the variable party is "1"
say We are having a party already!
end-if
if var-is party : Will execute the IF block if the variable party is empty or not set
say No party yet, let's start one!
setvar party 1
end-if
</code></pre>
<p>Jump command. You can use the syntax @label to create labels in your notecards. The syntax is:</p>
<pre><code>@myLabel : a label
say This will loop forever
jump myLabel : like "jump" in LSL or "goto" in other languages. the label should be on a line by itself prefixed with '@'
</code></pre>
<h2>WAIT commands</h2>
<pre><code>wait 200 : wait (don't do anything) for 200 seconds
wait 200 300 : wait between 200 and 300 second before executing the next command
waitvar foo 13 : wait until the variable foo gets the value 13
waitvar foo : wait until the variable foo is empty.
</code></pre>
<h2>Other commands</h2>
<pre><code>Bob msgatt attachment_command 12 13 14 15
</code></pre>
<p>Uses osMessageAttachments to send the message "attachment_command" to attachments at attach points 12 13 14 15. This can be useful for scripting NPC attachments. Read the OSSL docs of osMessageAttachments() for more.</p>
<h2>Custom command notecards</h2>
<p>You can extend the list of commands with notecards. To create a command notecard, enter the commands for the NPC to execute in a notecard, and save it into the controller's inventory with the name [command-name].scr</p>
<p>E.g. a dance command notecard would be named "dance.scr" and contain the following</p>
<pre><code>say I love to dance!
anim RockDance
wait 600 800
say oops, I am tired...
stop
</code></pre>
<p>You can then say "Bob dance" to have bob execute the notecard</p>
<h2>Interactive menus</h2>
<p>With interactive menus, your NPCs can ask your visitors to make a choice from a menu in the local chat. The following notecard asks the user if they want apple or an orange and gives an object to them:</p>
<pre><code>say Welcome to the shop!
@prompt
prompt Do you want an [apple] or an [orange]?
say I didn't catch that. Starting over.
jump prompt
@apple
say Here is an apple
give Apple
jump end
@orange
say Here is your orange
give Orange
jump end
@end
say Goodbye
</code></pre>
<p>Here is how it works:</p>
<ul>
<li>The options of the menu are specified in the prompt string itself, in square brackets:
<pre><code>prompt Do you want an [apple] or an [orange]?
</code></pre>
</li>
<li>Bob will say "Do you want an [apple] or an [orange]?" to the local chat, and it will expect to read the words "apple" or "orange" in the local chat from your visitor.</li>
<li>If he hears "apple", he will jump to the label "@apple" in the notecard.</li>
<li>If he hears "orange", he will jump to label "@orange" in the notecard.</li>
<li>If he hears something else, he will not jump, but continue normally to the next notecard line after the "prompt" line. (In our case, he asks again).</li>
<li>The menu options can only be single words (e.g. "orange", or "apple"). They are case-insensitive, and the menu will work even if the word is said in a phrase (I.e. "I want an apple" will still jump to @apple)</li>
</ul>
<h2>Waypoints and Pathfinding</h2>
<p>You can use the controller to create waypoints and links between them in your region. Bob can then walk between the connected points when you say 'Bob leave'</p>
<p>Each waypoint has a number (starting from 0) and optionally a name. Waypoints can be connected to other waypoints, thus creating a map (graph) between them. Bob can then wander between the waypoints (Say "Bob leave" to start walking), and you can also ask him to find his way from point A to point B (say Bob go to [destination]).</p>
<p>The waypoint data are stored in the <strong>waypoints notecard, one in each line, and the links data is stored in the </strong>links notecard. You do not need to edit these notecards by hand however, as you can use the included Waypoint Editor HUD.</p>
<p>To create a map, first wear the WaypointEditor HUD. If you already have created a map before, click RezPegs from the HUD menu. This will rez a peg in each waypoint you have already created. If you are starting with an empty map, you do not need to do this.</p>
<p>To add a waypoint, move your avatar to the desired position, and select "AddPeg" from the HUD menu. A peg should appear in front of you. To create a second waypoint, move to another position, and repeat.</p>
<p>To link the two waypoints X and Y, click on the first one (X), then click on the second one (Y). The pop up dialog should say "Current peg: Y, previous: X". To link them, select "LinkPegs" from the popup dialog. To unlink two waypoints, again, click on the first one, then click on the second one and select "UnlinkPegs" from the popup. Be careful to disregard all other dialogs that have popped up.</p>
<p>You can give a name to waypoints. Click the peg, select "SetName", and enter the name (E.g. "Bar"). You can use this name to give commands to your NPCs later (e.g. "Bob go to bar").</p>
<p>You can move the waypoints around to correct their positions. Important: After you move pegs to new positions click "ScanPegs" from the editor HUD. If you don't do this your changes will be lost.</p>
<p>After you have created/edited your waypoints, click the WaypointEditor HUD and select "SaveCards". This will update/create the <strong>waypoints and the </strong>links notecards inside the controller to match your new map. To test that all went well, clear the pegs and rez them again.</p>
<p>Note! Removing waypoints is not supported, as it would break the numbering and would mess up the notecard naming scheme. Although deleting is not supported, you can unlink a waypoint from all other waypoints, in which case the NPCs will never go there when wandering. If you want to start over with an empty map, edit the <strong>waypoints and </strong>links notecards, remove all their contents, and then select "Reconflg" from the controller.</p>
<h2>Configuration</h2>
<p>Configurable options for the controller are added in the __config notecard:</p>
<pre><code>AutoLoadOnReset=0
</code></pre>
<p>Change AutoLoadOnReset=0 to AutoLoadOnReset=1 to make the controller rez the NPCs automatically on region restart or script reset. Please note that autoloading NPCs may not always work well with some opensim versions.</p>
<h2>Permissions</h2>
<p>Permissions allow you to limit access to NPCs , and to specific commands to certain users or to all users. An access control list is specified in the __permissions notecard which is inside the controller object.</p>
<p>Each line in the __permissions notecard has the format</p>
<pre><code><npc-name> <command-name> = <RULE> <avatar name>
</code></pre>
<p>Where RULE is ALLOW, DENY, ALLOWID, DENYID or ALLOWSAMEGROUP (read below for usage).</p>
<p>The following line blocks (denies) avatar "Bad Hombre" from issuing the "bob come" command:</p>
<pre><code>bob come = DENY Bad Hombre
</code></pre>
<p>You can substitute the name of the NPC or the name of the command or the name of the avatar with the wildcard character '*'. for example, this blocks any avatar from using the command:</p>
<pre><code>bob come = DENY *
</code></pre>
<p>you can block any avatar from issuing the "come" command to any NPC:</p>
<pre><code>* come = DENY *
</code></pre>
<p>you can block any avatar from issuing any command to Bob:</p>
<pre><code>Bob * = DENY *
</code></pre>
<p>you can block a specific avatar from using any command on any npc:</p>
<pre><code>* * = DENY Bad Hombre
</code></pre>
<p>you can also use the DENYID command to block an avatar by UUID</p>
<pre><code>* * = DENYID d37a3f5b-562a-4bfd-b780-68c0b9b940b1
</code></pre>
<p>and you can block any avatar from using any command with any NPC!</p>
<pre><code>* * = DENY *
</code></pre>
<p>The rules specified in the notecard are executed from top to bottom, therefore you can add exceptions for specific users with the ALLOW and ALLOWID commands at the end of the list:</p>
<pre><code>* come = ALLOW Good User
* come = ALLOWID d37a3f5b-562a-4bfd-b780-68c0b9b940b1
</code></pre>
<p>You can also use the keyword ALLOWSAMEGROUP, which allows any avatar that is in the same group as the controller object.</p>
<pre><code>* come = ALLOWSAMEGROUP
</code></pre>
<p>You can use the wildcard '*' with the ALLOW commands as well</p>
<pre><code>Bob come = ALLOW *
* come = ALLOW *
Bob * = ALLOW *
</code></pre>
<p>An example __permissions notecard is given below which blocks any avatar from controlling the NPC "Alice" and disallows the "exec" command, but allows exceptions to certain users. It also blocks "evil user" from any command:</p>
<pre><code>Alice * = DENY *
* exec = DENY *
Alice * = ALLOW Good User
Alice * = ALLOWSAMEGROUP
* exec = ALLOW Good User
* exec = Allow Another Gooduser
* * = DENY Evil User
</code></pre>
<ul>
<li>Note that the ALLOW, DENY, ALLOWID etc. rules need to be in CAPITALS. Also, There must always be a space before and after the '=' character.</li>
<li>The owner of the controller is always able to use all commands with all NPCs regardless of access list.</li>
<li>If you make changes to the __permissions notecard, please click on the controller ->ReConfig to reload the permissions list.</li>
</ul>
<h2>Initialization commands</h2>
<p>The notecard <strong>initcommands contains initial commands to give to the NPCs. If AutoLoadOnReset is enabled, the notecard contents are executed automatically after loading. You can also manually execute the notecard by clicking "InitCmds" from the controller menu. You can use the </strong>initcommands to add any command that sets your NPCs in motion. Typically you would tell them to "leave" so that they start walking between waypoints. An example of __initcommands is :</p>
<pre><code>Bob say I am rezzed!
Bob teleport <64,64,22>
Alice teleport <128,64,22>
Bob leave
Alice leave : Start walking!
</code></pre>
<h2>Extension scripts</h2>
<p>You can extend the functionality of the controller with extension scripts. Extensions are LSL scripts that you create and add inside the controller object. If a command given to an NPCs is not understood by the NPC controller, the NPC controller will send a link_message to the extension scripts to process it. The extensions can also use link_message to send back commands to the NPC controller (the "number" parameter must be greater than 0) . The OSW NPC Controller object already contains an extension that implements the "help" command (look at the "..Extension" script). The script in it shows how extensions parse the data sent from the controller (sent through link_message) and how they can respond back.</p>
<p>The number parameter of the link_message is -1 if it comes from the controller script. The key parameter of the link_message is the UUID of the NPC. The string parameter of the link_message (or through channel 68) is of the format:</p>
<pre><code>! [uuid] Bob Bob help
</code></pre>
<p>Where:</p>
<ul>
<li>[uuid] is the UUID of the user who gave the command</li>
<li>Bob is the name of the NPC. The name is repeated once again.</li>
<li>What follows is the rest of the command that the NPC heard (e.g. "help")</li>
</ul>
<p>You can easily split the string with llParseString2List. Look into the ..Extension script for an example.</p>
<h2>Sending commands from other objects</h2>
<p>You can send commands directly to the NPC controller from any object. The NPC controller listens on channel 68. You have to remember to send the command using llRegionSay region-wide, so that the controller can hear it. The syntax is the same as the one used in link_message:</p>
<pre><code>llRegionSay(68, "! 0000-0000-0000-0000 Bob Bob say hello");
</code></pre>
<p>The UUID can be zero, and the name of the NPC must be repeated twice, as shown above</p>
<ul>
<li>ONLY scripts owned by the owner of the controller can send commands this way *</li>
</ul>
<h2>Setting controller variables from other objects</h2>
<p>Another way to interact with the controller is by setting variables from other objects by sending SETVAR [variable name] [value] from other objects to channel 68. This is the syntax:</p>
<pre><code>llRegionSay(68, "SETVAR foo 1");
</code></pre>
<p>(SETVAR must be in capitals. This example will set the variable "foo" to "1").</p>
<p>The variables can be used normally in notecards. In this example notecard, the NPC will waits for the variable "foo" to become '1' before starting to dance:</p>
<pre><code>@start
say Waiting for variable foo to become 1...
waitvar foo 1
say Variable foo is now 1! Let's dance!
anim dance1
wait 10
stop
setvar foo 0 : Reset var foo to 0 before waiting again
jump start
</code></pre>
<h2>Technical Notes</h2>
<p>The controller runs a single timer, that updates the states of all the NPCs every 5 seconds. This allows it to be extremely lightweight, as it does not block any script processing, but it may also cause delays when executing commands.</p>
<p>The controller checks the number of visitors in your region every 2 minutes. If there are no visitors in the region for 2 minutes, it will stop executing commands to avoid creating unnecessary load to the region.</p>
<h1>Bugs</h1>
<p>The controller was tested with version 0.8.2.1 . There may be multiple issues with other versions. Please add an issue, or get in touch with Satyr Aeon @ hypergrid.org:8002</p>
<h1>Thanks</h1>
<p>Thanks goes to Spax Orion for testing out lots of features and giving feedback</p>

👍 8 like

1 comment

SatyrFarm farming system

<strong>A unique Farm and breedables system for OpenSim</strong><br>
<br>
Learn more about the SatyrFarm farming system: <a href="https://opensimworld.com/farm/5">https://opensimworld.com/farm/5&lt;/a&gt;

👍 6 like

0 comments

Bulletsim single-script car

You just need to define the link numbers for the wheels and the sit target.

👍 1 like

3 comments

Fountain with synchronized jets

Create one box per jet of water you want to have (at least 5 for example). Link them together, and put this script in the root . Touch it to begin.

👍 1 like

2 comments

Loud Clock

Root prim must contain this script . Link #2 is the minutes digit, Link #3 is the hours digit , and link #4 is the seconds digit. <br />
<br />
Put your timezone in the object's description. e.g. if your timezone is GMT-10, then enter "-10" in the object's description, and reset the script. <br />
<br />
Add a sound to the object's content and rename it to "bell1". <br />
<br />
The clock rings on the hour and also every 15 minutes.<br />
<br />

👍 like

0 comments

BulletSim Helicopter with pitch & roll

A helicopter that can pitch and roll. <br />
<br />

👍 2 like

1 comment

Simplest AO

Minimal AO<br />
<br />
Drop in animations for every action you want to override. <br />
Rename them as "Standing1", "Standing2" etc ...<br />
<br />
E.g. to override the Walking animation, rename the animations to to "Walking1", "Walking2" etc.<br />
etc...<br />
<br />
Then reset this script

👍 2 like

1 comment

OpenSimWorld Beacon

This is the code of the OSW teleporter/beacon

👍 2 like

3 comments

Keyframe motion car for trains/lifts/rollercoasters etc

<p>Add this to an object, reset scripts, and then click to start adding points (ADD point). </p><p>At the end of the route , select save card. This will create a notecard</p><p>Then select RIDE to test it. <br>
<br>The notecard "RIDE" contains the information about the ride. </p><p>You can modify the  third column between the '|' to change the speed at which the ride will approach the specific point</p><p>You can optionally change the  fourth column to contain a number larger than zero. Then the ride will stop for that number of seconds at the specific point<br><br>
</p>

👍 9 like

30 comments

SFPOSER / PMAC remove unused animations

just drop the script in the PMAC object and say "remove" to delete all unused animations in the object. The script will also delete itself in the end<br>
<br>

👍 like

0 comments

SFPoser Animation Controller

<img src="https://opensimworld.com/data/p/87/87/62087.jpg" style="width: 325px; height: 325px; display: block; margin-left: auto; margin-right: auto;"><br><p><br></p>
<br><br>
<b>WHAT IS SF POSER</b><br><br>

SF Poser is a General-Purpose Animation Controller for up to <strong>99</strong> avatars. It can be used to create furniture from scratch and quickly without editing notecards at all. It allows on-the-fly adjustments of poses and change of animations, automatic timers, prop rezzing, NPC rezzing, RLV, expressions, and other built-in powerful utilities.<br>
It uses the same notecard format of the wonderful PMAC system, which means that it works right away with existing PMAC furniture. <br><p><br></p><p><br>
<strong>QUICKSTART WITH SF POSER</strong><br><br>

You can get the SFposer package from the opensimworld region: <a href="https://opensimworld.com/hop/74730">https://opensimworld.com/hop/74730&lt;/a&gt;&lt;br&gt;
The package contains an empty SFposer Template. <br><br>

- Rez the template and add your animations in its contents <br>
- Click on it and select OPTIONS->New Menu to create a new poses menu. A new empty pose (Pose1) will automatically be added to the new menu<br>
- Click OPTIONS -> EDIT POSE to adjust the pose. The positioning handles will appear. <br>- Touch each handle to select an animation from inventory<br>
- Move the handles to position the avatars<br>
- When done, click Save Pose, and then Save Menu<br><strong>Congratulations, you just created your first menu card and pose!</strong></p><br><br>
<strong>SF POSER FEATURE SET</strong><br><p><br></p><ul><li><strong>Fully Automated</strong> editing. SF Poser allows you to create new notecards and poses on the fly, and save them without ever creating or editing notecards and without the need to stand up/reset the script</li><li>Animation <strong>switching</strong>: Clicking the positioning handle allows to experiment with different sets of animations</li><li><strong>Adjust </strong>menu: Users can make temporary finetuning to their position on-the-fly in order to perfectly match the pose</li><li><strong>Expressions</strong>: emote using a facial expression at any time</li><li>Built in support for <strong>LockGuard </strong>chains</li><li>Built-in support for <strong>RLV</strong></li><li>Built-in support for Rezzing <strong>NPCs
</strong></li><li>Built-in Object <strong>Giver</strong></li><li>Built-in <strong>Props </strong>rezzer with ability to rez/derez/move objects</li><li>Built-in utilities such as sending chat channel <strong>messages</strong>, OSSL messages, attachment messages and more </li><li>Configurable via the '.<strong>SFconfig</strong>' notecard</li><li>Create custom Button commands with a single line in the .SFconfig notecard using powerful <strong>Shortcodes </strong>(see below) </li><li><strong>OSSL-native </strong>script, meaning that you can control up to <strong>99</strong> avatars with a single script. It requires that the owner has enabled OSSL permissions.</li><li>Small footprint: A <strong>single </strong>script for everything. The script uses as little resources as possible, and resets when unused, minimizing memory usage. Loading time is instantaneous</li><li>Link-message and dataserver-<strong>API </strong>for fully remote operation. SFposer can become the animation-controlling part of another object such as a vehicle or a game</li><li><strong>Permission </strong>system for limiting access to menus.</li><li><strong>Snappy </strong>operation and uncluttered menu dialogs</li></ul><strong>TO CONVERT AN EXISTING PMAC OBJECT</strong><br><br>
- Remove all the existing scripts from the object<br>
- Drop the ~positioner, the ~baseAnim and the ..SFposer script in the contents of the PMAC object. You will find those inside the SFposer Template object<br>
- That's all!  If you need to convert existing PMAC plugin options to SFposer, <a href="https://opensimworld.com/tools/pmac">use this converter</a><br><br><br>
<strong>TO CONVERT FROM OTHER SYSTEMS (AvSitter/MLP)<p><br></p></strong>There is an online converter system that you can use to convert MLP and AVsitter cards to the SFposer/PMAC format: <a href="https://opensimworld.com/tools">https://opensimworld.com/tools&lt;/a&gt;&lt;br&gt;&lt;p&gt... AND POSES</strong></p><p>A POSE is a set of avatars playing animations in specific positions. SFposer organizes the poses in MENUS (groups of poses), and each of  the menus is saved in a separate notecard inside the object. Each menu notecard line describes one POSE, and all the poses in the menu support the same maximum number of avatars. The notecards are automatically created and saved by SFposer, but you will need to edit the notecards to add Shortcodes, which provide additional functionality.</p><p><br></p><br><br>
<strong>USING SHORTCODES{}<p><br></p></strong>Shortcodes are strings of the form <strong>SHORTCODE{argument1; argument2} </strong>which are added to notecards to instruct SFposer to do something while playing an animation. They can also be invoked through add-on buttons in the OPTIONS  menu, from other scripts via llMessageLinked() and remotely from other objects using the SFposer dataserver-API. <p><br></p><p>To add a shortcode to a pose, insert it in the specially reserved second column of the .menu notecards, right after the pose name. The column is usually occupied with "NO COM" or "NOCODE".  Replace those with your shortcode(s):</p><code>Dance Together2|<strong>NO COM</strong>|danceLeft2|...<br>Dance Together|<strong>EXPR{smile;3;smile;4} SAY{Hello!} SAY{Hello again}</strong>|danceLeft|...<br>Dance Together3|<strong>SHORTCODE_GOES_HERE</strong>|danceLeft3|...</code><br><p><br></p><p>You can add multiple shortcodes{} simply separating them with spaces</p><p>There is additionally a configuration notecard for SFposer named '.SFconfig' where you can also add shortcodes, one per line (more on this later)</p><p>A shortcode{} can be executed via a button in the OPTIONS  menu. To create a button, add a <strong>Button </strong>line in the .SFconfig notecard as follows:</p><p><em><strong><span style="font-family: monospace;">Button=ButtonLabel=SHORTCODE{arg1;arg2;arg3}</span></strong></em></p><p>After editing notecards, you need to stand up and sit again, to force the script to reset and reload them.</p><br>
<br><br>
<strong>ADDING EXPRESSIONS<p><br></p></strong>For each avatar participating in the pose, you can specify an expression animation to play and the time it takes to repeat the expression (in seconds -- if you dont want repeats , enter 0). The Expressions Shortcode is:<br><br>
<code><strong>EXPR</strong>{expression1;repeatTime1;expression2;repeatTime2;expression3;repeatTime3 ... and so on for every avatar of the pose}</code> <br><br>

The expressions and repeatTimes can be left empty, but be sure to include the required ';' separators for all avatars in the pose. <br>
For example, the following notecard line defines expressions for the pose "WatchMovie" which is for 3 avatars:<br><br>
<code>WatchMovie|<strong>EXPR{laugh_emote;4;open_mouth;3;frown;0}</strong>|chair_sit|<0.2112.... [the rest of the pose line]</code><br><br>
In this case, avatar1 will play the animation express_laugh_emote every 4 seconds; avatar2 will play express_open_mouth every 3 seconds and avatar3 will play express_frown only once.<br>
For brevity, the "express_" part of the animation name is omitted (so you only enter "frown" for animation "express_frown") . The full list of available expressions is: <br><br>
<span style="font-family: monospace;">open_mouth, surprise_emote, tongue_out,smile, toothsmile, wink_emote, cry_emote,kiss, laugh_emote,disdain, repulsed_emote, anger_emote, bored_emote,sad_emote, embarrassed_emote, frown,shrug_emote, afraid_emote, worry_emote</span><br><p><br></p><p>If you wish to use a custom expression animation (e.g. a bento animation called bentoanim), you need to add the animation inside the SFposer object and rename it to "express_bentoanim". You can then use it as: EXPR{bento_anim;3}  </p><br>
<br><br>
<strong>REZZING PROPS <p><br></p></strong>

"Props" are objects to be rezzed with specific poses or via a button. All props objects must contain the <em>SFposer Prop script</em> so that they can be deleted after use. <a href="https://opensimworld.com/library?viewcode=104&amp;raw=1&am...">Click here to get the script</a><br><br>After adding the script to the prop, drop it in the contens of the object and rename it to "MyProp".<p>
Add the following Shortcode to a pose to rez the prop:<br><br>
<code><strong>PROP</strong>{MyProp;<1,1,1>;<0,0,0,1>}</code>  </p><p><br>This will rez MyProp at position <1,1,1> and rotation <0,0,0,1> relative to the object. You do not need to edit the position and rotation manually instead you can position the props correctly by editing the pose (read below).</p><p>If you need to rez multiple props, add multiple PROP{} shortcodes, separating them by space: <em>PROP{Prop1... } PROP{Prop2...} PROP{Prop3...} ....</em></p><p>Sit and re-sit on the SFposer to reload the notecards, and then select the pose again. The prop should rez in the position <1,1,1>, as instructed. </p><p>Now, edit the prop to position it to its final position, and then select <em> Options -> Edit Pose -> Save Pose</em>. The system will save the new PROP{} positions and also print them out in local chat.</p><p><br></p><p>Additional shortcodes for props are supported. You can use them to create Buttons that rez/derez props:</p><p><code><strong>TOGGLEPROP</strong>{MyProp;<1,1,1>;<0,0,0,1>}</code>   When the button is pressed, it rezzes the prop, when pressed again, it deletes it. <br><br>
<code><strong>DELPROP</strong>{MyProp}</code>  Deletes the prop
</p><p>For example, you can  define a rez/unrez button in the .SFconfig notecard as follows:</p><p><code>Button=Rez/Unrez=<strong>TOGGLEPROP</strong>{MyProp;<1,1,1>;<0,0,0,1>}</code></p><p>(remember to re-sit in order to reload the card)</p><p><br></p><p><strong>Attachment Props: </strong>You can use the "SFposer attachment prop script" (<a href="https://opensimworld.com/library?viewcode=106&amp;raw=1&am...">get it here</a>) to create props that auto-attach to a user (for example, a gym bench could use them to attach dumbbells to the sitter's hands). Use the following procedure to create attachment prop shortcodes:</p><p>- Wear the attachment, adjust it to its final position and add the "SFposer Attachment Prop script" inside it. <br>- RESET THE SCRIPTS in the attachment to record its position
<br>- Detach the attachment,  add it in the contents of the SFposer object, make it full permissions, and give it a name (e.g. MyPropName)</p><p>Add the following shortcode to a pose to rez the prop and requests to attach to avatar sitting at position 0 (first avatar)</p><p><code><strong>PROPATT</strong>{MyProp;0}</code> </p><p>When you select that pose, the attachment prop will rez  and request to attach to the first sitting avatar.</p><p>If instead you wish to attach the prop to the avatar that is currently using the menu, use a simple PROP{} code: </p><p><code><strong>PROP</strong>{MyProp;<0,0,0>;<0,0,0,1>}</code> </p><p>Attachment props are not detached when switching positions, they will detach when you stand up. </p><p><strong>Note that Attachment props are temporary and cannot be detached by right clicking, instead the user will have to click on them to detach.</strong></p><p><br></p><p><br></p>

<p><strong>RLV SUPPORT </strong></p><p>SFPoser has built-in support for RLV and uses shortcodes to implement it. </p><p>Add the following lines to your .SFconfig notecard to create an "RLV Capture" and  an "RLV Release" button:</p><code> Button=RLV Capture=<strong>RLVCAPTURE</strong>{20}<br> Button=RLV Release=<strong>RLVRELEASE</strong>{}</code><p><br></p><p>RLVCAPTURE{20} indicates that 20 is the maximum distance  (in meters) within which to search for avatars to capture. RLVRELEASE{} does not have any arguments </p><p>You can send RLV commands in specific poses with the RLV{} shortcode: </p><p><br></p><p><code><strong>RLV</strong>{avatarNumber; @rlvCommand1 ; @rlvCommand2; @rlvCommand3 ... }</code></p><p><br></p><p>avatarNumber is the position of the avatar (0 is the first avatar). You can send multiple RLV commands with a single RLV{} shortcode, but remember to separate them with ';'</p><p><em>RLV support works with osCollar 7. You can <a href="http://wiki.secondlife.com/wiki/LSL_Protocol/RestrainedLov...">read more about the RLV protocol here</a>.</em></p><p><br></p><br><p><br></p>
<strong>BUILT-IN GIVER<p><br></p></strong>

To give an object (e.g. Popcorn) to the user who is currently using the system, create a Button in the .SFconfig notecard with the GIVE{} shortcode as shown below:<br>
<br>
<code>Button=Get Popcorn=<strong>GIVE</strong>{Popcorn}</code><br><br>
The button "Get Popcorn" will be added to the Main menu's OPTIONS  screen. Make sure the Popcorn object is inside the contents of the SFposer object and that it is copyable or else the command will fail silently<br><p><br></p><br><br>
<strong>NPC REZZING SUPPORT<p><br></p></strong>
You can add NPCs to SFposer by adding appearance notecards inside the object. Each NPC appearance notecard must use the naming convention of PMAC:<span style="font-family: monospace;"> <strong>".NPC00A Firstname Lastname"</strong></span>. Appearance Notecards created for PMAC should work right away. Add the NPC notecards and reset the object by re-sitting. The NPCs submenu is in the OPTIONS menu<p><br></p><p>You can use the shortcode<strong> ADDNPC{firstname lastname}</strong> in .SFconfig to rez NPCs during startup or after region restart. You can also use the shortcodes <strong>ADDNPC{..} </strong>and <strong>DELNPC{..</strong>} in poses. </p><p><br></p><br>
<strong>LOCKGUARD CHAINS SUPPORT</strong><br>
SFposer supports LockGuard V2 cuffs for chains and ropes. In order to add lockguard settings to a pose, use the LG{} Shortcode:<br><br>
<code><strong>LG</strong>{0;rightwrist;rightHook}</code><br>
<br>
This sends a lockguard command to the cuffs worn by the avatar sitting at position <strong>0 </strong>(the first position) to link to the child prim named "<strong>rightHook</strong>". It uses the lockguard command "<strong>rightwrist</strong>" which is understood by the wrist cuff. You can add more  lockguard options to the "rightwrist" command , such as "rightwrist gravity 4 life 1.5 color 1 0 0", but DO NOT INCLUDE the "link" and "unlink" commands. These are added automatically by the system. You can <a href="http://wiki.secondlife.com/wiki/LSL_Protocol/LockGuard#Loc...">read more about the LockGuard protocol options here</a>.<br>You can add multiple LG{} Shortcodes for multiple cuffs. An example notecard line is:<br><br>
<code>UseCableMachine| <strong>LG{0;rightwrist life 1;righthook} LG{0;leftwrist life 1;lefthook}</strong> |cables|<1.3282,1.8789,0.8556>|<0.0001,-0.0002,0,1.></code><br><br>
Chains are unlinked automatically when someone stands.<br>
<p><br></p><p><br></p><br><strong>RUNNING EXTRA ANIMATIONS<p><br></p></strong>
You can create a Button that runs a set of animations ON TOP OF the currently playing animations. For example you can create a Button that makes everybody laugh at any time by adding the following line to .SFconfig notecard:<br><br>

<code>Button=All Laugh=<strong>ANIM</strong>{express_laugh;express_laugh;express_laugh}</code><br><br>

to create a button to stop those animations, use the STOPANIM Shortcode instead of ANIM: <br><br>

<code>Button=Stop Laugh=<strong>STOPANIM</strong>{express_laugh;express_laugh;express_laugh}</code><br><br>
Note that, unlike EXPR{} , you have to specify the full animation name here, and there is no repeat-time since the animations here are not repeatable<p><br></p><br>
<br><strong>ANIMATION SWITCHING WITH A TIMER</strong><br><br>
SFposer supports an auto-timer that switches to the next pose every X seconds. The menu TIMER is under OPTIONS. <br>
You can specify the default auto timer duration (in seconds) for all menus in the .SFconfig notecard:<br><code>autoTimer=60 </code><br><br><p>You can set the auto-timer for individual poses by adding the shortcode <strong>TIMER{50}</strong>, which will set the animation timer every 50 seconds.<strong>TIMER{0}  </strong>will stop the auto-timer.</p><p><br></p><br>
<strong>ADVANCED SHORTCODES</strong><br><br>
Shortcodes like GIVE{... }, can be used either via Buttons (shown in the the OPTIONS  menu) or by adding them to the pose line in a notecard. <p>Note: Shortcodes must appear <em>before </em>any other custom configuration strings you use</p>The Shortcode-section of a notecard can contain multiple Shortcodes separated by space. <p><br></p>For example, if you want a pose to rez a PROP{} and also run some animation, add the following Shortcodes:<br><br>
<code><strong>PROP</strong>{MyProp;<1,0,0>;<0,0,0,1>} ANIM{clap;clap;clap;clap}</code><br><br>

The same Shortcodes can be used via a Button. The button is defined in the .SFconfig notecard with a single line as follows:<br><br>

<code>Button=MyButtonLabel=PROP{MyProp;<1,0,0>;<0,0,0,1>} ANIM{clap;clap;clap;clap}</code><br><br><br>

In addition to the Shortcodes described so far, the following Shortcodes are supported:<br><br>

<code></code><code><strong>MSGPROP</strong>{MyProp;Hello, prop}</code> Sends the dataserver message "Hello, prop" to the already-rezzed prop MyProp using osMessageObject()<br><br>
<code><strong>MSGATT</strong>{0;Hello, avatar1 attachment;19,4}</code> Sends the dataserver message "Hello, avatar1 attachment" to the attachments attached on attach points 19 or 4 of the avatar sitting on position 0 of the pose (first position) using osMessageAttachments(). You can read more on <a href="http://opensimulator.org/wiki/OsMessageAttachments">the documentation of osMessageAttachment online </a>. You can also <a href="http://wiki.secondlife.com/wiki/ATTACH_HEAD">view the full list of attachment point numbers</a>.<p><br></p><p><code><strong>MSGOBJ</strong>{<object-uuid>;Hello object}</code> Sends the dataserver message "Hello object" to the object with <object-uuid> using osMessageObject(). This can be used to send shortcodes to another SFposer, <strong>however </strong>you will have to replace <strong>'{'</strong> and '<strong>}</strong>' with '<strong>[</strong>' and '<strong>]</strong>' in the shortcodes for this to work. This example changes the pose in another sfposer object:</p><p><em>MSGOBJ{<object-uuid>; SAY[Changing pose] SWITCHTOPOSE[MyPose]}</em></p><br>

<code><strong>MSGLINK</strong>{4;Hello link number 4}</code> Uses osMessageObject to send the dataserver message "Hello link number 4" to the linked prim at link number 4<br><br>

<code><strong>SAYCH</strong>{21;Hello, channel 21}</code> Uses llSay() to say the string "Hello, channel 21" to the local chat channel 21. The string can contain the special codes %<strong>USER00, %USER01, %USER02</strong> etc which are replaced witht the Name of the user sitting at position 1, position 2 etc. For example:<span style="font-family: monospace;"> <strong>SAYCH{0; The user %USER00 is sitting with %USER01} </strong></span><br>
<p><br></p><p><code><strong>SAY</strong>{Hello public channel}</code> Like SAYCH, but for the local chat</p><p><code><strong>REGIONSAY</strong>{21; Hello channel 21 in the whole region}</code> Like SAYCH, but region-wide</p><p><code><strong>USAY</strong>{Hello dialog user}</code> Say something to the user currently using the dialog</p><br>
<code><strong>LINKMSG</strong>{-1;99;Hello, all prims}</code> Uses llMessageLinked(-1,99, "Hello, all prims" , <list-of-avatarIds> ) to send a link message. Note that LINK_SET = -1, LINK_THIS=-4<p><br></p><p><code><strong>TRIGGERSND</strong>{My sound}</code> Play the sound "My sound" using llTriggerSound</p><p><code><strong>PLAYSND</strong>{My sound}</code> Play the sound "My sound" with llPlaySound (e.g. to accompany an animation)</p><p><code><strong>LOOPSND</strong>{My sound}</code> Start playing a sound loop with sound "my sound"</p><p><code><strong>STOPSND</strong>{}</code> Stop sounds</p><p><code><strong>SLEEP</strong>{0.5}</code> Add a delay (sleep) for 0.5 seconds</p><p><br></p><p><br></p><p><strong>Changing linked prim  properties on the fly</strong></p><p><br></p><p><code><strong>SHOW</strong>{MyChildPrim; <1 or 0>}</code> Show or hide the child prim named MyChildPrim (1 = show)</p><p><br></p><code><strong>SETPRIM</strong>{MyPrimName; <specially-encoded-list> }</code><p><br></p><p>This shortcode can be used to change the properties of the linked prim(s) named "MyPrimName"  using the list of prim properties as in llSetPrimitiveParams(). It is essentially a way to call llSetLinkPrimitiveParams() without adding another script in the object. To use this shortcode, you must encode the list of parameters to llSetLinkPrimitiveParams() in a special format that can be pasted into the notecard. Use the script "SFposer encoder for SETPRIM" (<a href="https://opensimworld.com/library?viewcode=107&amp;raw=1&am...">link at the end of this page</a>) to generate the shortcode. </p><p>Example: Changing the color of a child prim named MyPrim and making it transparent</p><p> The LSL list for llSetPrimitiveParams() would be <em><strong>[PRIM_COLOR, ALL_SIDES, <1,1,1>, 0.0]</strong>. </em>Using the shortcode encoder script, it prints out in local chat the SETPRIM shortcode containing the encoded version of this list:</p><p><span style="font-family: monospace;"><strong>SETPRIM{MyPrim; I;18;I;-1;V;<1,1,1>;F;0.0}</strong></span></p><p><br></p><p> </p><p><strong>Creating particle effects</strong></p><p>Similar to SETPRIM, SETPARTICLES{} is used to set the particle system in any named prim in the link set. </p><p><code><strong>SETPARTICLES</strong>{MyPrimName; <specially-encoded-list> }</code></p><p>The parameters list to be passed to llLinkParticleSystem() must be a specially-encoded encoded with the <a href="https://opensimworld.com/library?viewcode=107&amp;raw=1&am...">same script as above</a>, but remember to replace SETPRIM with SETPARTICLES in the output of the script.</p>
<p><br></p><p><br></p><p><strong>Presets of  shortcodes</strong></p><p>Presets are shortcuts (macros) to a multiple shortcodes. Presets are defined in .SFconfig. The syntax for defining a Preset is:</p><p><br></p><p><code><strong>Preset = MyCommand = SHOW{myPriml;1} TRIGGERSND{bang}</strong></code>  This defines the preset  "MyCommand"  as the series of shortcodes SHOW and TRIGGERSND</p><p>To use a Preset, use the PRESET{} shortcode in a pose line or anywhere:</p><p><code><strong>PRESET</strong>{MyCommand}</code> </p><p><br></p><p>Presets can be used to group together shortcodes that are shared by multiple poses. For example, a Shower object may contain poses that with water running and and others that don't. The two preset states (WaterOn and WaterOff) could be defined in .SFconfig as follows:</p><p><span style="font-family: monospace;"><strong>Preset = WaterOn = LOOPSND{watersound} SETPARTICLES{ShowerHead; <encoded list>}</strong></span></p><p><span style="font-family: monospace;"><strong>Preset = WaterOff = STOPSND{} SETPARTICLES{ShowerHead;;}</strong></span></p><p>Individual poses could be configured to use the presets as follows:</p><p><span style="font-family: monospace;">Pre Shower| PRESET{WaterOff} |<1,2,3>.... <br>Shower| PRESET{WaterOn} |<1,2,3>.... <br>AfterShower| PRESET{WaterOff} |<1,2,3>.... </span></p><p><br></p><p>When switching between poses that use the same preset, the preset will not be restarted, instead it will continue running. If you explicitly want a preset to be restarted, add another, empty PRESET{} code before:</p><p><span style="font-family: monospace;">PRESET{} PRESET{WaterOn} </span></p><p><br></p><p><strong>Creating Sequences</strong></p><p>Using shortcodes, it is possible to turn an animation menu notecard to a sequence of poses. Use the TIMER{} code to set  the duration of each pose, and use Shortcodes or Presets to add effects such as props, sounds etc. to each pose. To prevent looping the whole sequence, use TIMER{0} at the last pose. </p><p>An example notecard for a boxing match would be:</p><p><br></p><p><span style="font-family: monospace; color: rgb(17, 85, 204);">Warmup| <strong>TIMER{30} SAY{%USER00 is preparing to fight %USER01}</strong> | prepare1| <0.012....<br>Fight | <strong>TIMER{30} PRESET{Fighting}</strong> <strong>SAY{Fight!}</strong> | fight1 | <0.012....<br>Victory| <strong>TIMER{0} TRIGGERSND{victory} SAY{%USER00 won! } </strong> | victory1 | <0.012....</span></p><p><br></p><p><br></p><strong>Creating OPTIONS Buttons with shortcodes</strong><p><br></p><p>Any shortcode can be added to an add-on button in the OPTIONS menu with the <strong>Button </strong>option in .SFconfig: </p><p><code><strong>Button</strong>=My Button=SAYCH{0; Hello,world}</code></p><p><br></p><p><strong>Running shortcodes in .SFconfig</strong></p><p>You can execute shortcodes in .SFconfig which will be executed every time SFposer is reset (whenever everyone stands up). Just add the shortcode on a single line by itself . This can be used for example to change the properties of prims when the system is reset using SETPRIM{}, to rez NPCs etc.</p><p><br></p><br>
<strong>API COMMANDS & REMOTE OPERATION</strong><br><br>
The <strong>API </strong>allows you to trigger most of the Shortcodes described above in the SFposer object through <strong>link messages </strong>and through <strong>dataserver </strong>messages.  <p><br></p>To send commands from another script through link_messages use :<p><br></p><p><strong><span style="font-family: monospace;">llMessageLinked(LINK_THIS, -1, "SHORTCODE{...}", NULL_KEY);</span></strong></p><p><br></p><p>To send through dataserver messages, use: </p><p><br></p><p><strong><span style="font-family: monospace;">osMessageObject("<SFposer object UUID>", "SHORTCODE{...}");</span></strong></p><p><br></p>In order to enable dataserver messages, the <strong>allowRemote </strong>option needs to be set in the .SFconfig notecard. This option determines how the SFposer can be accessed by avatars and dataserver messages, and takes the following values: <br><p><br></p><p><strong>allowRemote=0  </strong>Only <strong>sitting </strong>avatars can use the menus, the object does <strong>not  </strong>accept dataserver commands</p><p><strong>allowRemote=1  </strong><strong>All </strong>avatars, sitting or not, can touch the object to use the menus, the object does <strong>not  </strong>accept dataserver commands</p><p><strong>allowRemote=2  </strong>Only <strong>sitting </strong>avatars can use the menus, and the object <strong>accepts </strong>dataserver commands</p><p><strong>allowRemote=3  </strong><strong>All </strong>avatars, sitting or not, can use the menus, and the object <strong>accepts </strong>dataserver commands</p><p><strong>allowRemote=4  </strong><strong>Disable all menu dialogs</strong>, and the object <strong>accepts </strong>dataserver commands. Use this in case you want to control SFposer remotely-only, in which case SFposer will not generate any dialog when touched. This is useful if you want to host SFposer and another menu-driven script in the same root prim. </p><p><br></p><p>In order to allow changing poses and animation menus remotely, the following shortcodes are available for remote operation:</p><p><strong><span style="font-family: monospace;">SWITCHTOMENU{My Menu} </span></strong>Switches to the animation menu "My Menu"</p><p><strong><span style="font-family: monospace;">SWITCHTOPOSE{My Posename} </span></strong>Switches to the pose "My Posename" which must be in the currently selected animation menu.</p><p><strong><span style="font-family: monospace;">UNSIT{<avatarNumber>}</span> </strong>Unsits the avatar in position <avatarNumber> (first position is 0)</p><p><strong><span style="font-family: monospace;">ADDNPC</span></strong><strong><span style="font-family: monospace;">{firstname lastname} </span></strong>Adds an NPC from the inventory</p><p><strong><span style="font-family: monospace;">DELNPC</span></strong><strong><span style="font-family: monospace;">{firstname lastname}</span> </strong>Deletes the NPC</p><p><strong><span style="font-family: monospace;">SWAP</span></strong><strong><span style="font-family: monospace;">{pos1; pos2} </span></strong>Swaps the users in pos1 and pos2 (first position is 0)</p><p><br></p><p>It is possible to use the API to add Buttons  to the OPTIONS menu. In this case, instead of a shortcode, the message sent to SFposer has the same format as the .SFconfig configuration line for creating a button:</p><p><span style="font-family: monospace;">osMessageObject("<object-uuid>",</span><strong><span style="font-family: monospace;"> "Button=Say Hi=SAY{Hello, world}" </span></strong><span style="font-family: monospace;">);</span></p><p><br></p><p>For deleting a button from the OPTIONS menu, there is the shortcode DELBUTTON{}:</p><p><strong><span style="font-family: monospace;">DELBUTTON{Help me}</span></strong></p><p>e.g. <span style="font-family: monospace;">osMessageObject("<object-uuid>",</span><strong><span style="font-family: monospace;"> "DELBUTTON{Say Hi}" </span></strong><span style="font-family: monospace;">);</span></p><p><br></p><p>Buttons with <strong>arbitrary</strong>-string codes can also be created. This is meant to be used for sending messages to other scripts. The syntax is: </p><p><strong><span style="font-family: monospace;">Button = Send code = MyCodeIsHere</span></strong></p><p><br></p><p>When pressed, the button will send a link_message as follows:</p><p><span style="font-family: monospace;">llMessageLinked(LINK_THIS, 0,</span><strong><span style="font-family: monospace;"> "MyCodeIsHere|<current-user-uuid>", "<uuid1>|<uuid2>|...");</span></strong></p><p><br></p><p>The API command  <strong>GETSTATUS</strong> can be used to retrieve the current state of the SFposer object. Send the string GETSTATUS through dataserver or link_message to retrieve the status (Note this is not a shortcode so {}  are not added): <em> </em></p><p><em>llMessageLinked(LINK_ROOT, -1, "GETSTATUS", "");  </em> or  <em>osMessageObject("<sfposer-uuid>" , "GETSTATUS");</em></p><p>SFposer will respond a link_message or dataserver message respectively, with a string containing the current state of sfposer:</p><p><em>osMessageObject("<sender-uuid>", "SFSTATUS|<current-menu-user-uuid>|<current-menu-name>|<current-pose-name>|<auto-timer>|<internal status>|<current-pose-shortcodes>|<user1-uuid>,<user2-uuid>,<user3-uuid>...");</em></p><p><br></p><p><br></p><p><strong>EVENTS</strong></p><p>SFposer sends <strong>link_message </strong>notifications to the root prim for any significant event. You can listen to those events by creating addon scripts. The names of the link_message events are the same as the ones used by PMAC. </p><p>This is the list of events that are sent:<strong> </strong></p><p><span style="font-family: monospace;"><strong>GLOBAL_ANIMATION_SYNCH_CALLED <br>GLOBAL_NEXT_AN <br>GLOBAL_NEW_USER_ASSUMED_CONTROL <br>GLOBAL_SYSTEM_RESET <br>GLOBAL_START_USING <br>GLOBAL_USER_SAT <br>GLOBAL_USER_STOOD <br>GLOBAL_SYSTEM_GOING_DORMANT <br>GLOBAL_NOTICE_ENTERING_EDIT_MODE <br>GLOBAL_NOTICE_LEAVING_EDIT_MODE  <br>GLOBAL_STORE_ADDON_NOTICE <br>GLOBAL_EDIT_STORE_TO_CARD</strong></span></p><p>Look into the source code to see the arguments sent with each event. The events are sent via llMessageLinked() to LINK_THIS (the root object), with numeric Value=0. The 'key' argument is replaced with a concatenated list of the currently sitting avatar uuids (Just like PMAC). An example of the event messages sent out is: </p><p><span style="font-family: monospace;">llMessageLinked( LINK_THIS, 0,</span><strong><span style="font-family: monospace;"> "GLOBAL_USER_SAT|0|1111-111-111", "111-111-111|000-000-000|000-000-000"</span></strong><span style="font-family: monospace;"> );</span></p><p><br></p><p><br></p><p><strong>Triggering Shortcodes with Event Filters</strong></p><p>You can define Shortcodes that will be triggered automatically when an event matches a pattern using OnEvent configuration lines. </p><p>The Event filters are defined in the .SFconfig notecard as follows:</p><p><strong><span style="font-family: monospace;">OnEvent = <Event filter> = SHORTCODE{} SHORTCODE2{} ...</span></strong></p><p><Event filter> is replaced with the part of the of the event string that is to be matched.</p><p><br></p><p>Example: When the first user sits on the object , SFposer emits the event "GLOBAL_USER_SAT|0|<user-uuid>" </p><p>The following OnEvent filter matches the substring "GLOBAL_USER_SAT|0", and triggers the shortcode SAYCH:</p><p><strong><span style="font-family: monospace;">OnEvent = GLOBAL_USER_SAT|0 = SAYCH{0; Hello, first user}</span></strong></p><p><br></p><p>The different events contain different kinds of information in their event strings. It is possible for example, to use the the event string to trigger a shortcode when a specific avatar position is being filled or emptied. It is also possible to trigger a shortcode when a specific user-id sits on the object. Examples:</p><p><span style="font-family: monospace;"><strong>OnEvent</strong> <strong>= GLOBAL_USER_STOOD|3 = </strong>SAYCH{0; Goodbye, user 3}</span></p><p><span style="font-family: monospace;"><strong>OnEvent </strong><strong>= GLOBAL_USER_SAT|0|2ae39a9c-13  = </strong>SAY{Hello, %USER00, i recognized you sitting in first position}</span></p><p><span style="font-family: monospace;"><strong>OnEvent </strong><strong>= GLOBAL_SYSTEM_GOING_DORMANT =</strong> SAY{Thanks for using me}</span></p><p><br></p><p><br></p><p><br></p><p><strong>LIST OF .SFconfig NOTECARD OPTIONS</strong></p><p>The following configuration options are supported in the .SFconfig notecard:</p><p><strong>allowRemote= 0  </strong>or 1, 2,3,4 . Controls who can access the menus. See above for details</p><p><strong>autoTimer=90   </strong>Set the auto-timer (seconds)</p><p><strong>defaultGroup=Sit  </strong>Name of the default menu when a user first sits in the object</p><p><strong>adjusterStep=0.03  </strong> Set the adjustment step (in meters) for the ADJUST menu (X-, X+ etc)</p><p><strong>mainMenuTitle=Hello users  </strong>  Set a custom message to show in the MENUS dialog instead of the default</p><p><strong>autoSwitchGroup=1   </strong>Automagically switch to a bigger or smaller size animation menu  when more people sit on the object or when they stand up. The system will switch to the first available animation menu that can accomodate the number of sitters</p><p><strong>showDialogOnSit=1</strong>  Automatically show the menu dialog as soon as the first user sits</p><p><strong>showMenusOnStart=1  </strong>When first showing the dialog, show the list of Menus first, rather than the list of poses</p><p><strong>showOptionsAgain=1</strong>  Show the Options dialog again after selecting an option from the Options menu instead of dismissing it. The user will have to click ignore to dismiss</p><p><strong>allowSoloNpc=0  </strong>This forces the system to remove the rezzed NPCs when all humans have stood up (default is 1)</p><p><strong>offsetPos = <x,y,z></strong>  Move all poses by the vector <x,y,z> , i.e. add a global position offset to all positions</p><p><strong>offsetRot = <x,y,z></strong>  Rotate all the poses by the euler vector <x,y,z> (in *degrees*), i.e. add a global rotation to all positions</p><p><br></p><p><strong>lockMenus=A </strong>Unlocked menus to all users (the default). Other options:</p><p>lockMenus=O Lock all menus to owner  only</p><p>lockMenus=G Lock all menus to users who have activated the same group as the object</p><p>lockMenus=S Lock all menus until the owner has seated</p><p><br></p><p><strong>lockSit=A </strong>Everyone can sit (the default). Other options:</p><p>lockSit=O Only the owner can sit</p><p>lockSit=G Only members of the same group can sit</p><p>lockSit=S The owner must sit first before other users can sit</p><p><br></p><p><strong>Preset=Dumbbell=PROP{dumbbell;<0,0,0>;<0,0,0,1>}   </strong>Creates a preset (shortcut to a series of shortcodes) that can be used in poses (See above)</p><p><strong>Button=Hello=SAY{Hello} SAY{Hello again}   </strong>Creates a button in the OPTIONS menu that executes shortcodes (See above)</p><p><strong>OnEvent=GLOBAL_SYSTEM_GOING_DORMANT=SAY{Bye} </strong> Creates an event filter (See above)</p><p>In addition any number of shortcodes can be added to the .SFconfig notecard , one at a line. They will be executed every time the script is reset</p><p><br></p><p><br></p><p><br></p>
<strong>OSSL PERMISSIONS</strong><br><br>

If you already have PMAC in your region, then you have already enabled all the functions that SFposer requires to operate<br><br>
In case you need to update your .ini files here are some recommended settings. Depending on the opensim version, these need to be added either in <span style="font-family: monospace;">config-include/osslEnable.ini or config-include/osslDefaultEnable.ini . </span><p><br></p><code>Allow_osGetNotecard = true<br>
Allow_osMessageObject = true<br>
Allow_osMessageAttachments = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osAvatarPlayAnimation = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osAvatarStopAnimation = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osMakeNotecard = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osNpcCreate = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osNpcRemove = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osNpcSit = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
Allow_osSetPrimitiveParams = ESTATE_OWNER,ESTATE_MANAGER,PARCEL_OWNER<br>
</code><br><br><p><br></p><br>
<b>SF POSER SYSTEM PARTS:</b><br><br>
- The .SFposer script<br>
- The ~positioner handle object <br>
- The ~baseAnim hip-fix animation<br>
- The .SFconfig configuration notecard (optional)<br><br>
<br><p><br></p><br>
<strong>MENU NOTECARDS FORMAT</strong><br><br>

SFposer uses the same notecard format as PMAC. Each set of animations (menu) goes in its own notecard which is named with the following convention:<p><br></p><p><strong>.menu0005A Dance Together</strong></p><p>where</p><code>.menu : All pose notecards must begin with .menu<br>
00: Used for ordering of menus. Can be between 00-99<br>05: Means this menu notecard contains poses for 5 avatars<br>
A: Menu is for use by (A)ll. Can also be (G)roup or (O)owner, or (S) in which case the owner must sit first before the menu can be accessed by other users<br>
Dance Together: The label shown in the button is "Dance Together"</code><br>
<p><br></p>You do not need to create your own notecards , as they are created for you automatically via the menus. <br><br><p><br></p><br>
<strong>NOTES</strong><br>- Despite the name, SF poser is a generic animation controller and is not specific to SatyrFarm, i.e. it can be used for anything.<p>- Thanks to Aaack Aardvark @ osgrid for beta testing</p><br><br>
<strong>LICENSE</strong><br>
(c) 2020 Satyr Aeon<p><br></p>Licensed under<strong> GPL-3.0-or-later <a href="https://www.gnu.org/licenses/gpl-3.0-standalone.html"></a></strong><a href="https://www.gnu.org/licenses/gpl-3.0-standalone.html">https://www.gnu.org/licenses/gpl-3.0-standalone.html&lt;/a... href="https://www.gnu.org/licenses/gpl-3.0-standalone.html"></a><p><br></p><p><br></p><br><br>
<p><strong><br></strong></p><br>
<p><br></p>

👍 8 like

21 comments

SatyrP

👍 like

0 comments

SFsail Sailing Engine

<p style="text-align: center;"><a href="https://opensimworld.com/data/p/550/50/75550.jpg"></a><a href="https://opensimworld.com/data/p/550/50/75550.jpg"></a><img src="https://opensimworld.com/data/p/549/49/75549.jpg" alt="" style="width: 300px;"></p><p><br></p><p><strong>SFSAIL sailing engine</strong></p>
<p>-----------------------------------</p><p>Learn more at https://opensimworld.com/sfsail&lt;/p&gt;
<p style="text-align: left;">SFsail is a new sailing engine written from scratch for OpenSim. It
works similarly to BWind and has mostly similar commands. Sit on a boat and say
'help' for a list of commands.</p><p><strong><span style="color: rgb(106, 168, 79);">You can find the SFsail boats in the OpenSimWorld Region: hg.osgrid.org:80:OpenSimWorld</span></strong></p>
<p><br></p><p><br></p><p><a href="https://opensimworld.com/data/p/550/50/75550.jpg"><img src="https://opensimworld.com/data/p/550/50/75550.jpg" style="width: 589px; display: block; margin-left: auto; margin-right: auto; height: 463px;"></a></p><p><br></p>
<p><strong>HOW TO USE THE BOATS:</strong></p>
<p>- Boats are tuned to BulletSim by default. If you use ubODE,
edit the .SFsail script and change the setting IS_UBODE=1</p>
<p>- The first avatar who sits on a boat is the commander. If
the commander stands up the boat moors. Another person can then sit to
operate<span>  </span>the boat</p>
<p>- You can operate the boat with left/right arrows
(steering), forward/back arrows (trim of the sails) and PgUp/PgDown to rotate
the Spinnaker</p>
<p>- Say 'raise' to raise mainsail + jib</p>
<p>- Say 'lower' to lower all sails</p>
<p>- Say 'moor' to stop and anchor the boat</p>
<p>- Say 'jib' to hoist/lower the jib</p>
<p>- Say 'genoa' to hoist/lower genoa (if available)</p>
<p>- Say 'spin' to hoist/lower spinnaker (if available)</p>
<p>- Say 'trim' to engage Autotrim which automatically trims
the sails to their optimal angles</p>
<p>- Say 'hold' to keep the boat pointing at the same angle</p>
<p>- Say 'flip' when the boat is moored to flip the boat
(useful when stuck on a dock)</p>
<p>- Say 'motor' to turn on the motor. Then use the up/down
arrows to change throttle. Say 'moor' to stop<span> 
</span>the boat</p>
<p>- Say one of n,s,e,w,nw,ne,sw,se to set the Wind direction</p>
<p>- Say 8,11,15,18,21,25<span> 
</span>to set the Wind speed</p>
<p>- Say 'hud' to turn on/off the hover text of the boat</p>
<p>- Say 'adv' to turn on/off advanced hud text</p>
<p>- Say 'milesreset' to reset the miles counter (shown in the
hud)</p>
<p>- Say 'setter' to enable/disable listening to the region
wind setter (or SFsail Manager)</p>
<p>- Say 'dest x y' to engage the autopilot to steer towards the region coordinates x,y</p>
<p>- Say 'dest x1 y1 x2 y2 x3 y3 ...'  to engage autopilot to follow the route from region points x1 y1 ...  Say 'stop' to stop autopilot</p><p>- Say 'follow <avatar name or object name>' to engage autopilot to follow another avatar or another boat. Say 'stop' to stop following</p><p>- Say 'route <route-name>' to begin a rout (requires Sail Manager / See below)</p>
<p>- Say 'stop' to stop the autopilot / stop following</p>
<p> </p>
<p><strong>ROUTES MANAGER / WIND SETTER</strong></p>
<p> </p>
<p>The 'SFsail Manager' object is a wind setter (creates wind for the 'setter' command), and a
place to rez and store your boat routes. If you don't already have a wind
setter, touch it and select 'Setter ON'.</p>
<p>Boat routes are stored in the notecard '.Sailroutes' inside the manager object, which
contains lines with routes. In each line, the x y coordinates of a route are defined (similar to the 'dest' command).</p>
<p>Each line is as follows:</p>
<p><span style="color: rgb(17, 85, 204);"><Route Name>=x1 y1 x2 y2 x3 y3  x4 y4 
...</span></p>
<p>For example a  route named 'Tour' line could be:</p>
<p><span style="color: rgb(17, 85, 204);">Tour=150 160 270 380 200 100 160 160</span></p>
<p>You can then engage the autopilot to join this route from any boat by saying:</p>
<p><span style="color: rgb(17, 85, 204);">route Tour</span></p>
<p>The boat will join the route at the nearest
point of the route and continue until the end. You can stop the autopilot at any time by saying 'stop'</p>
<p>You can use the object "SFsail Route helper" to help you make a route quickly. Rez it over water, and then, for each point, move it and then touch it. The route will be printed in the chat for you.</p>
<p> (Note: routes are approximate, the boat will try to reach within 10 meters of each route point. You will have to correct the boat if it goes against the wind)</p><p><br></p><p><strong>REZ A BOAT WITH NPC THAT FOLLOWS YOU</strong></p><p><span>You can use a second boat and an NPC to follow your boat. Rez a second boat that will follow you. Edit .SFconfig and change "Firstname Lastname" to your own avatar name, for example:</span><br><br><span>Button=FollowMe=LINKMSG{-4;889;follow Satyr Aeon}</span><br><br><span>Then sit and unsit to reload the configuration. Then Right click to touch the boat (without sitting) and select Options ->NPCs->ADD->Sailor. The NPC "Sailor" should sit on the boat now. </span><span>Touch the boat again and select Options -> FollowMe , then select Options -> Autotrim and then select Options->Raise. The boat with the NPC will now follow you. You can sit on your own boat and sail together.</span></p> <p><br></p> <p> </p>
<p><strong>CONFIGURATION</strong></p>
<p>You can change the configuration variables at the top of the
.SFsail script to tune your boat. </p>

<p>IS_UBODE=0<span>  </span>// Change
this to 1 if you are using UBode</p>
<p>ACCESS = "A";<span> 
</span>// Change who can drive the boat. the setting can be:
"A"=All<span>  </span>"G"=Group
"O"=Owner only</p>
<p>MAX_ANGLE = 70;<span>    
</span>Maximum allowed boom angle</p>
<p>HUD_ON=1<span>     </span>// Change
this to 0 if you don't want the Hover text by default</p>
<p>ADV_HUD=1<span>     </span>//
Change this to 0 if you don't want want advanced info in the Hover text</p>
<p>THROTTLE_MAX=5 // Change this to the maximum throttle of the
motor</p>
<p>SPEEDUP=0.9;<span>        </span>//
Change this to larger or lower values to make the boat overall faster / slower</p>
<p>ENABLE_DYCAM = 1;<span>  </span>//
Change this to 0 to<span>  </span>disable the dynamic
camera</p>
<p>KEELING = 0.2;<span>    
</span>//<span>  </span>Change this to larger or lower
values to make the boat keel more or less</p>
<p>LEEWAY = 0.2;<span>     
</span>//<span>  </span>Change this to larger or lower
values to make the boat to have more leeway (sideways drift)</p>
<p> </p>
<p><strong>SFposer BUTTONS</strong></p>
<p>The SFsail boats use SFposer<span> 
</span>to handle the animations. SFposer Buttons are added to the Options menu to send commands
to the boat.<span>  </span>The boat accepts commands through link_messages with num=889</p>
<p>To add an SFposer button, add a Button line to the
.SFconfig notecard. For example to add a button to hoist the genoa, add the following line to .SFconfig:</p>
<p><em>Button=Genoa=LINKMSG{-4;889;genoa}</em></p>
<p>Similarly, you can create a route for a boat by sending an appropriate 'dest' command:</p>
<p><em>Button=Start Route=LINKMSG{-4;889;dest 150 160 270 380 200 100
160 160}</em></p><p>The SFsail boats contain a button for the boat to follow you. You need to edit .SFconfig to replace "Firstname Lastname" in the Button's configuration line with your own avatar's name:</p><p><em>Button=FollowMe=LINKMSG{-4;889;follow Satyr Aeon}</em></p><p>The SFsailboats come preloaded with one NPC named 'Sailor'. To rez the NPC to follow you with his boat, click Options->NPCs->Add NPC->Sailor, then Options->AutoTrim, then Options->FollowMe, and finally Options->Raise.</p>
<p> </p>
<p><strong>WARNINGS</strong></p>
<p>The boats do not support crossing regions, unless you have
OSSL permissions in both regions.</p>
<p> </p>
<p><strong>COPYRIGHT</strong></p>
<p>SFsail is licensed under the GNU General Public Licence v3 (GPLv3)</p><p>SFsail is inspired by the BWind engine, but it does not contain any parts of it.<br></p>
<p>Copyright (c) Satyr Aeon</p>
<p><br></p>

👍 12 like

2 comments

Bulletsim Seaplane

<p>A Seaplane for  opensim / bulletsim. </p><p>Drop the script in the root prim</p><p>Add 3 sounds called "Startup", "Engine" and "Shutdown" to use as sound effects when the engine starts/runs/stops</p><p>Also add a sound called "Splash" for when the airplane lands on water</p><p>The driver animation is called "driveS"</p><p><br></p>

👍 like

0 comments

Random Wanderers with KeyframeMotion

<p>Keyframe Wanderers - Randomly wander on ground or over water or above water using keyframe motion
</p><p>They can be used to make animesh animals that wanders randomly in the region</p><p>Change the animations and sounds in the script to match your animal.</p><p>(you can link poseballs with these objects to fly with them)</p>

👍 5 like

3 comments