Difference between revisions of "MLPV2 FAQ"
(+{{Navbox/MLPV2}}) |
|||
| Line 5: | Line 5: | ||
Yes, per-pose, starting with MLPV2.1. At most one "prop" object per pose. Use PROPS.* notecard to configure; see the reference manual for details. | Yes, per-pose, starting with MLPV2.1. At most one "prop" object per pose. Use PROPS.* notecard to configure; see the reference manual for details. | ||
== Can props be rezzed as worn objects? == | === Can props be rezzed as worn objects? === | ||
Not really. You could rez an object that the participants can copy, take, or click to get an object that they can then wear. | Not really. You could rez an object that the participants can copy, take, or click to get an object that they can then wear. | ||
Alternatively, it's possible to write an add-on script that, when a given pose is selected, gives an object to whoever's on a particular ball. This is a bit advanced; I'd recommend studying the MLPT-xciteadaptor4 script which tracks who's on which ball and knows when poses are selected. Remove the timer stuff, which could be laggy. | Alternatively, it's possible to write an add-on script that, when a given pose is selected, gives an object to whoever's on a particular ball. This is a bit advanced; I'd recommend studying the MLPT-xciteadaptor4 script which tracks who's on which ball and knows when poses are selected. Remove the timer stuff, which could be laggy. | ||
== Can props stay rezzed rather than disappearing when you select the next pose? === | === Can props stay rezzed rather than disappearing when you select the next pose? === | ||
Nope, sorry! You could use a "holodeck" script in a button to rez props independently of the MLPV2 menu. | Nope, sorry! You could use a "holodeck" script in a button to rez props independently of the MLPV2 menu. | ||
Revision as of 12:44, 10 December 2009
MLPV2 FAQ
Can it rez objects?
Yes, per-pose, starting with MLPV2.1. At most one "prop" object per pose. Use PROPS.* notecard to configure; see the reference manual for details.
Can props be rezzed as worn objects?
Not really. You could rez an object that the participants can copy, take, or click to get an object that they can then wear.
Alternatively, it's possible to write an add-on script that, when a given pose is selected, gives an object to whoever's on a particular ball. This is a bit advanced; I'd recommend studying the MLPT-xciteadaptor4 script which tracks who's on which ball and knows when poses are selected. Remove the timer stuff, which could be laggy.
Can props stay rezzed rather than disappearing when you select the next pose?
Nope, sorry! You could use a "holodeck" script in a button to rez props independently of the MLPV2 menu.
What do I do about balls that are sunk into the mattress?
[tbd]
Does MLPV2 support chains?
Search for CISS.
This applies equally to MLP and MLP2. You have to do some scripting.
Look at the touch_passer script (in MLP-tools, for MLPV2). This script sends a link-message causing MLP to post its menu. It's intended for use when MLP isn't in the root prim; you put this script in the prim you want people to be able to touch to get the menu.
If you want the menu to come up some other way, just modify this script to do what you want. For example, if you want the menu to open from a chat message, modify it to listen and send the link-message when it receives the proper command.
Can I play a sound from a sequence?
Make a button for the sound, the normal way. (It can be in a hidden menu.) Use the button name as the sequence step.
Can we get more than 6 avatars?
Nope. You can put two MLPV2 prims in the same object and they'll get along just fine, independently. But if you need coordinated poses with more than 6 avatars, use XPOSE.