MLPV2 questions & bug reports

I have the problem, that my positions are not on the same places after I made a restart.
First I copied from mem dump into the note, then pos set and after restart its gone. But its funny, not all the positions are on anöther place only about 10%.
Who can help me with this?

Not sure what you mean by "then pos set".

One thing to check is, did what you wrote to the notecard actually get saved.... ?

Perhaps she means "Reset Pos". If so, after the pos reset, were all the poses correct? When you say "restart", do you mean using the menu restart, or just when the pos reset is done?

But I didn't quite follow what you're trying to say. Do you mean that 10% were wrong, or 10% were right?

How many .POSITIONS cards are you using?

How many position entries do you expect to have, and how many does the bed report after a pos reset?

(If you have another .POSITIONS card you're forgetting about, that could cause these symptoms.)

Thanks for catch up my problem. I try to explain it again. I have only one positions notecard. After I changed the positions (adjust, save position) I said mem dump, copied from the chat into the positions note, saved the note .
Everything is ok until that, but after I said shutdown or reset, about 10 positions from 100 are at another place. It does'nt matter if I say pos reset or not. What I would like to know, maybe I do this not in the right way. Do I have to say "pos reset" ?. And how many animations can I put into the menu? Thanks for your answer

Aha, I have a suspicion.

First, though, Pos Reset is the best way to test whether a changed notecard worked properly. It causes the .POSITIONS notecards to be reread, same as they would be on a complete Restart or shutdown and startup, but it's considerably faster since the menu isn't reread.

General rule: if you changed a .MENUITEMS card, do Menu reset. If you changed a .POSITIONS or .PROPS card, do Pos Reset.

Restart shouldn't ever be required, but is handy if things seem borked (as in your case!) or if you've replaced or edited some of the scripts. (There are shortcuts when replacing scripts, but they're not documented, and it depends on which scripts.)

When your bed is reading .POSITIONS card, do you get a warning about a duplicate? I bet you do. Fix that and I bet your problem goes away. I *think* I fixed that in a later MLPV2 version (perhaps 2.2), but maybe not. What happens is that after the duplicate pose, every 4th position is wrong because it's using a position for a different pose. The code didn't recover from the duplicate correctly.

Pay attention to warnings! (I believe I also made that warning more obvious.)

I hope this is your problem, because it would explain everything and also be very easy to fix. I spent a *lot* of time working with someone on this problem once, and nearly pulled my hair out to find out that they were ignoring the warnings, didn't even mention them when trying to debug the problem. Arrgh!

This would be a good one to add to the Wiki. It doesn't happen for original MLP, just MLPV2 up through perhaps MLPV2.2. (And the fix might have gotten lost -- I have too many copies sitting around that I work on, arrgh.)

How many animations? Until it runs out of memory. As a guide, I suggest you leave at least 500 bytes for every script that reports available memory.

But you should be able to have on the order of 80 animations and say, 60 poses before getting close to the limits, depending on a bunch of factors like animation name length, button name length, and total number of menu buttons (including non-pose ones).

IIRC, all versions up to MLPV2.2 beta 1 are compiled using "old LSL". Starting with one of the MLPV2.2 betas, it's compiled using Mono, so the memory limits go away. For Mono, the hassle of dealing with an object with so many items in inventory will probably kill you before running out of script memory will!

thank you so much for the information. I started now from the beginning with the MLPV2.1c. , put the poses in, made new notecards and it works with memdump and also with pos reset and restart. Maybe the prob I had before was, because I copied everything from the old version and maybe there was a mistake, whatever or I had too many poses in. I tried now with 10 poses and its ok, I hope it will stay like this after some more. Lots of work to adjust each pose (( again, but it this is ok after.....I'm very happy. Thanks again for your help.

yw; glad it's sorted out!

I have looked all over to find the answer to my problem and I can't find it or I am totally missing it. I am trying to figure out where I put the menus and what I put. Example, I have the name of the menu but I do not know where to put it and where as well as where to put the animations or any of that. Basically how do I set up these menus? I am sorry if this was explained somewhere but I truly can't find it and I am a total noob to scripting. Please help!

The XStreet entry for MLPV2 has a link to a tutorial webpage explaining how to set up a new item:

http://xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=692115 - where to get MLPV2

https://wiki.secondlife.com/wiki/MLPV2_Tutorial - Tutorial

Got a newbie question.

I would like to have a wearable object to have a menu like this for the poses. Can the MLP be used for that? Or do I have to look for a different tool?

It should work, though it's been a while since it's been tested that way, as far as I know.

Thanks! I will give that a try.

I have the following problem and i was hoping on your help... i make some beds using the MLP menu... but after testing them...

When i test them they seem all right
the next day by clicking on one of them the balls that come up are moving to the bed next to it and again to the correct one... as i am clicking on other options the balls move like crazy back and forth and right and left sometime the pink ball stays to the one bed and the blue goes to the other what i have to do to fix this problem? does the distance that those 2 beds have matters? the beds have deffirent names and the prim (the matress) that has the script has also different name...

I am so confused...

ps: i havent saw there is already a subject with this script and i had made it also as topic so sorry!!!

Fuku, are you using MLP or MLPV2, and which version?

This is a well-known problem for old MLP. I'd fixed it in MLPV2, but in the earliest released versions the fix was missing.

If you're using old MLP, or an early version of MLPV2, the Restart button fixes it.

Hello,

I'm having a problem with the MLP2.3f - I am using it in a bed I'm building and am trying to get the xcite functions working.

I can get almost everything to work properly. The arousal levels and intervals seem to work fine. What I can't get to work is the "tilt" settings in the notecard.

I have tried many different times and no matter what I try the "tilt" does not seem to have any affect.

Anyone else seeing this problem and have any advice. I would appreciate it.

Thanks,
Sparkly

Cue the viagra jokes :}

I believe this is an xcite problem. I saw it myself, but did not see it with an alt or with another scripter who was working with this.

I believe my test gear was an X2 upgraded to X3. Don't know if that's significant.

Please recreate the problem. Turn on debugging in the MLP xcite adaptor to show the LMs sent to xcite partner script. If you see the messages you'd expect (from the xcite partner instructions notecard), please report this to xcite. (They were unable to reproduce the problems we reported.)

If the debug output shows incorrect LMs, then the MLP adaptor is at fault, so please post back here ASAP and we should be able to get it sorted out.

Please let us know either way.

I have recreated the problem with an alt - same thing happened.

With the debug settings on I do see LM's being sent and they seem to work fine for all the xcite functions except the tilt like I said.

I am not completely sure what LM should be activating the tilt functions, so I can only assume the ones I see that seem to be sending the correct message are indeed sending the right message.

I tested it with an X2 that was upgraded to X3 and a brand new X3 - both failed to respond to the tilt message.

I will contact xcite about the problem and see if they have an answer. I am assuming that there aren't many people using it based on the lack of responses here either way.

Thanks for the reply.

I was testing it with someone who couldn't get it up. Never did figure it out. Yet my alt could even.

Well -

I contacted Xcite and found out I had an outdated set of partner scripts. They sent me the new partner kit which actually support the "tilt" feature.

Things seem to be working "ok" now. Sometimes it seems slow to respond to the Tilt commands, but that is probably just SL Lag causing communication slowdowns.

I am working on a new bed containing two threesome menus and a foursome menu, in addition to various 2 person menus. The issue is that after adding the foursome menu, I find that clicking the button labelled "MMF" I get the following script error.
"New Bed: llDialog: button labels must be 24 or fewer characters long"
The button is 3 Characters long. The MMF TOMENU is the only one that throws up this error, and it only happened after adding the 4 person menu. Any feedback would be appreciated.

Memo to self: Always finish troubleshooting BEFORE asking for help. I forgot a | in a POSE line. So it was counting the Button name and the first animation name as the button name. MY BAD.
Sorry... *smiles sheepishly*

Did that myself, just the other day.

I'm thinking of putting a check in, so it catches it during config rather than later. The error you get certainly gives little clue of what the problem is. Fortunately you know which button you pushed, so that narrows it down to one menu.

In my case, however, it was junk at the beginning of the next notecard that caused the problem. Good thing I remembered what I'd changed.

Okay, I tried reading through everything here and everything in the readme file on the MLP thing, but I can't figure out how the hell to add the poses! Will someone please help?