MLPV2 Troubleshooting Tips

From Second Life Wiki
Revision as of 15:31, 19 September 2009 by Chaz Longstaff (Talk | contribs)

Jump to: navigation, search
Keyword Explanation
Animation xyx not found

1. Check that the animation is indeed in the prim;
2. Check the spelling;
3. If you are using expression suffixes, check that you didn't put a space before the expression suffix;

4. Check that as a separator in POSE lines you have used only
(in theory, you can also use spacespace|spacespace
You cannot use three spaces; the superfluous space is not stripped away while reading the notecard; instead, it gets treated as part of the animation name, and voila! An animation name it can't find. Also check for invisible soft-returns that may have come in if you were doing your work in another programme such as Microsoft Word.
Animation won't remember its position It can occur that even though you've triple-checked all your work, there will be an animation that sometimes will come out in the right position, sometimes not. After a bit of head-banging, you realize it all depends on which animation you played just before it. If the creator of that animation did not set a hip position for it, you will get different results depending on which pose you ran last. That is, if you have 3 animations, 2 with hip positions and one without, the hip position for the one without will be left over from whichever of the last two animations you used. Which may throw your pose all off. There is nothing you can do except abandon use of the animation; the problem is in the animation itself, and it's not suitable for use with MLP-like scripts though it may work fine as sold in a static poseball.
"Animate me" permission popup not happening You won't get the animate permission popup if you were the last person on a particular poseball. It keeps your permission. You also don't get animate permission for yourself when MLP is used as a HUD, because worn items give permission automatically. (So do sat-upon items, but in the case of MLP, the script that takes permission is in the furniture, not the ball.)
avatar != perm key This is some debugging code that Lear had left exposed by mistake in some versions. It can be ignored; it is not really an error
Balls rez on top of each other, even though you are sure you have positions right. Check for duplicate stored positions. *Any* duplicate stored positions, even those not related to the pose in question, can cause this.
Balls: not enough rezzing -- you have a Menu with poses that have 4 animations to them, but only 2 balls are rezzing. Check that you didn't tell the pose to only rez 2 balls. Example:
MENU Cuddles | ALL | BLUE | PINK
for 4 animations should be something like
(or whatever) . Easy mistake for tired eyes to make!

Also, check that you didn't drop the permission parameter. For instance, if you say

MENU Cuddles | PINK | BLUE 

forgetting to put in there the [ALL | GROUP | OWNER] parameter, MLP will get mixed up, think that PINK is the permission parameter, and only rez the blue ball.

if you say

MENU Cuddles | PINK 

No balls will rez at all.

Fix: put a permission parameter back in.

Booting up: MLP starts, gets a bit of the way, then goes no further (1) Check that you have both a .MENUITEMS and .POSITIONS notecard in there.

"Couldn't find (script)" error If you get a message like this upon first dragging and dropping the MLPv2 scripts into a prim, disregard it. It occurs because a prim contents are very slow to refresh in SL, and one script thinks another one is not there yet. Do nothing; it will sort itself out in a few seconds.
Deeding to group If you deed an MLPV2 bed, you lose the OPTIONS menu unless you remember to change all the OWNER menus to GROUP menus, and even then you won't be able to use full shutdown.
llDialog: button labels must be 24 or fewer characters long You have almost certainly forgotten a
in a POSE line. Consequently, the scripts were counting the Button name and the first animation name as the button name, making the button name too long.
Notecards: I set my notecards to full-perm but customers can't open them to save positions, etc. Dime to a doughnut you sold the object that the MLP notecards are in as no-modify. You can't open notecards in a no-modify object. SL limitation.
"No Unused TOMENU" Getting this msg but I know that's not right Check the top of your main MENUITEMS card, referring to the help in this section
Props don't rez and I have everything right (1) Make sure you have the ~Props script in the MLP object.

(2) MLP is very case sensitive. CHAT 2 in .MENUITEMS does not equal Chat 2 in the props notecard. Check to make sure the case matches.

(3) Watch the prim count on the parcel where you are working. If the available prim count is going down, then your prop is rezzing -- just not somewhere where you are seeing it.

"Script run-time error / Stack-Heap Collision" This is a clue that, sadly, there are too many items in your or notecards for the script memory to handle. Congratulations, you've just been initiated into the battle-scarred club like the rest of us.

First, make sure you have no unused positions stored in any .positions notecards. See tidying tip here Tidy, restart and see if that helps.

The next step is more drastic. You must give up on some poses, and cull their POSE lines from the .menuitems card, and their position settings from the .positions card. You may leave the actual animations in the MLPv2 prim, but you might as well remove them as they won't be used anyway.

Sequence just wont run

Q: Heres what I have setup in the .sequences notecard:

SEQUENCE | Romantic
MENU | Romance
POSE | standing
AVWAIT | 0 | Waiting for someone to sit on ball
WAIT | 10
POSE | Kiss
WAIT | 10
POSE | Enter
WAIT | 15...

It shows up in the menu selection, but no poseballs are rezzed when you select the sequence. Here's what I have in the .MENUITEMS notecard pertaining to the sequence-

MENU Romantic
LINKMSG Romantic | 0,-4,-12001,SEQUENCE Romantic

A: Your problem is simple: you have two buttons with the same label, which isn't allowed.

Xcite! features such as tilt just don't seem to work Contact Xcite! to make sure you have the latest set of partner scripts. Make sure your own Xcite! bits aren't horribly out of date.