MLPV2 questions & bug reports

Hello all, and heya Jeff especially.. thanks for all the work youve put into this ^^!

Im being dumb, but ive been searching for a way to NOT have that swirling particle effect each time a pose gets changed.
What Ive tried:
Looking for it in the scripts to disable... but its not there...
Putting in a 'object' reset script to remove any inherent particle effect.... didnt work..
Googling .. didnt work...
So now Im here!

Any advice from anyone appreciated!
Thanks in advance ^^^^^
Regards -Zed

As far as I know, there's SFA you can do. It was introduced a few years ago; happens whenever a prim chats (I think -- I'm just so used to it now I tune it out.)

The only way is to turn off chatting the new pose when poses change. Find this in .MENUITEMS:

CHAT ChatInfo | ON

change it to

CHAT ChatInfo | OFF

I may have details incorrect here; just change the ON to OFF in the line similar to this.

The swirlies can be annoying, but it's often very important to know which object is chatting so it's a good feature in general.

I find that, in Emerald, I often see the swirlies even when I don't see the chat (e.g., it's IMing to some other av or something -- not talking about MLP here). That's annoying and not particularly helpful.

In any case, there's probably a nerd-knob to turn them off for yourself in your viewer, but that wouldn't affect what others see.

I keep seeing beds advertised with 400, 600 and now 1200. What exactly are they using to determine such large volumes. My bed is pretty loaded with 150 positions, 304 menu items. Is this then a 600 bed with the swaps? Im confused on what the mark is people use.

Filler.

So they use filler.. but what would the beds state when loading..100 positions set or 1200

They can't have that many using unmodified MLPV2.

The DevPose system only loads a subset of the menus at a time, and may be able to handle significantly more -- but at the cost of having to read some of the config when you move to a new menu.

I've seen advertisers double the number of poses because of the "swap" button, which I think is particularly sleazy.

Finally, anyone who buys a bed loaded with that many poses is doing themselves a disfavor, as they'll find when script memory limits kick in. I advise creators to focus on quality and variety rather than quantity, and do their customers a favor. And who really wants to sift through hundreds of poses to find the dozen or so they'd actually enjoy? Ah well, some folks, I guess. But some folks simply look at the numbers -- we can't really defend ourselves against stupid consumers and the merchants who prey on them. IMHO, they deserve each other, and no worries for me.

I suggest advertising the number of poses, the number of animations, and possibly, whether or how many of the animations are original/unique.

The scripts don't count these. If you don't have extra entries in .POSITIONS, you can subtract two (for default and stand) from the number of positions reported. MLP Tools box contains a script to check animation permissions, which also reports the number of them -- drop it in and it deletes itself when done. It also has a script to report the animations that aren't used in any pose; and it would be best to delete these first. (I use a version that simply deletes them, but I don't remember whether I put that in MLP-Tools -- probably not, because I don't want someone wailing to me about how all their animations got deleted -- irreparably.)

I believe Chaz has a script (probably posted on the wiki) that provides useful counts.

Hi, thanks so much for your help on clearing that up. I have always assumed there was a lot of manipulation going on with it. I think I may be nearing the max as I am now having stack heap errors. What should I look for to fix stack heaps..been trying to fix this for 2 days. Works fine til I add in the last .positions card. I have 149 positions loaded, 363 menu items.

thanks again for a great product.

Hi, thanks I had no idea as I had purchased a package early on. Craig Altman's I know I have full perm as I spent a fortune in his store buying all I could. The others I will just delete as I have many animations now and having my own content stolen, I have no desire to do it to others. Sadly I did not know I was til I read this post. Thank you. I will however drop a donation to those I have taken from, and a note of apology. Hopefully others will follow suit.

A couple of minor things I've noticed with q

- the config check hangs at around 60 couples positions (ymmv). It doesn't appear to time out as I've seen it struggle on ages afterwards when I've done a cleanup/reload of the positions notecard.

- Non owners can click on the shutdown button and brings up the dialogue saying that it's only for owner use but it also triggers stop for some reason.

- and of course that dialogue that turns up if you touch the item too quickly after a restart.

apart from those little niggles it runs lovely for my purposes. (Imagine a blowing kisses emoticon here)

my wish list is really simple;

- I'd like a line in the notecard that specifies the max no of balls for the item which is read as part of the load and means that the ~poser scripts can be reduced. TBH I don't care where the indicator is as long as I can have it.

- I'd also like to be able to go back to the old days when the inbuilt swaps would take care of couples swaps as that would remove another script when I'm not using more than 2 balls.

- would it help with script limits if the give script code can be incorporated into one of the other scripts like the sounds code is? that way it's there if people want to use it or can be ignored if not. Even if it doesn't help with that, the script is so useful that it would be good if it could be incorporated into the base script set.

Yeah, I noticed that it's no longer working. Nice to hear that someone's actually trying to use it. Since this is the first report I heard, I assumed it's not a popular feature.

It's due to the order of processing. I always do a STOP before a shutdown to help avoid avatars getting stuck animated, and the test for the ability to shutdown happens later. I don't consider this much of a bug.

I'll only fix this if it doesn't add memory usage, and I get really bored. Lately I've been having far too much fun creating Spin The Bottle using a hacked MLPV2.

Thanks, I'm very happy to hear that, and enjoying the blown kisses.

It already shuts off unnecessary ~poser* scripts, so there's no need to configure it. Your suggestion would allow reducing the number of items in inventory, but at the cost of more data to pass between the config script and the menu script, taking more memory, and more complexity. This isn't likely to happen.

The ~swap script is needed to avoid a race condition. If someone wants to do a thorough analysis and contribute a protocol that supports configurable swaps without a race condition and allows the ~swap script to be optional, I'd be very interested to see it. Meanwhile, if you don't want configurable swaps, you can use the MLPV2.3 versions. Admittedly, the 2.4 versions have some enhancements I haven't backpatched to 2.3.

Interesting point. When script limits get closer, I'll consider that along with the rest. Meanwhile, use LSL for the give-item script (not Mono). Ditto for other small scripts that aren't numerous.

Thanks again for your input!

well it should be used by everyone as it's incredibly useful. That and the two check scripts save me so much time - you have no idea how grateful I am for that trio.

and I've love a copy to the anim check/delete.. that would save me even more time

The config check works beautifully up until around 50 positions. I have one at 49 positions and it works fine there and on all the smaller ones. On my 66 position and above items it don't work - although interestingly on the 66 one it would work probably 1 time in 4, so I'm assuming it's got something to do with the memory although I don't quite know what because I just clicked it without changing the pose, rebooting or reloading the positions notecard..



I'll fight you on your claim it's not much of a bug. If someone who is not the owner clicks that button they should only get the dialogue box, the item shouldn't be trying to execute the command.

O.O I can't wait to see the finished product

well, blown kisses are pretty tame if you're in the middle of testing your spin the bottle.. you greedy soul.


I must've missed the fix to that problem when they turned back on after a sim restart (?) then. Although I assume they run at the startup/reboot and then switch off, which will cause a spike. (I'm thinking of my shop here - I use your sim restarter (another incredibly useful script.. ta ) and assuming that my current set up survives the script limits then a bulk restart may end up being the sim killer for me)

as an aside.. In my ideal world there'd be no anims in the item, I've spent too long waiting for the contents box to load and then another wait to be able to open notecards and scripts. If I had a magic wand I'd have the ability to put uuid's for the anims in a notecard rather than having to drop the anims in.


my eyes just glazed and started to water.. I'll just saunter off now and leave you geeks to it..

Thanks; that's a big help!

Then hie on over to jPose Island and try it out! I just added orgy support.

A sim restart should no longer have any significant effect. That only ever affected the scripts that keep data in memory; which the poser* scripts don't do. You can reset them at any time and hop on a ball and they work.

Yes, but unfortunately, then our anims would be too easy to steal. In an ideal world, the contents box would pop up quickly, and there would be no theives.

Sorry, what I meant to say is, I originally tried to do it the way you want, but couldn't get it to work reliably.

Many sims in preparation for the script restrictions are now requiring beds to be completely shut off when not in use, not just shutdown. This would also help with stores like mine where I have all sofas and beds running on mlp. If I could completely shut down the scripts,but have them wake on touch would be great. Right now the avg script time for a shutdown bed or sofa is .43. Imagine me on bended knee, palms up begging for this feature..and yes will blow you as many kisses as it takes. Bats my eyes, pretty please.

Thanks and hopes for this miracle.

I'll look into making an extra script for this purpose.

I'm not going to rework MLPV2 for script limits until we have all the facts. Right now, we don't have enough facts to respond correctly to these upcoming changes. We also don't have the new script functions available.

But I think a separate script, or better yet a new version of the MLP-timeout script, could achieve the desired purpose without interfering with MLPV2 very much.

Note that when someone touches a shutdown bed, it'll take a couple minutes before it's ready, and during that startup, the owner will get owner-chat messages. I was thinking about changing those messages to not using llOwnerSay() in order to handle deeding to group better. But first, the new timeout script.

Can't wait for the new script, thanks so much..tosses you a Linden thanks inworld.

In a few days this thread will be history, so have you thought about where you want to move to? a link to our new home as one of the last posts would be really good.

SLU have a scripting sub forum and Cris may even create a sub,sub forum so this could be broken out into problems, wishlists etc - he created the virtual business and put an xsl one in when they closed the xsl forums and also created a forum for all the various viewers so it's certainly possible.

Slapt.me would probably be receptive to it as well and I'm sure most of the others too.

LL haven't been particularly clear on what they plan to do with the blog to accommodate the content creation forums, so unless they do come up with something before hand it could quite easily end up that people who have bookmarked this end up here and don't know where to go for the latest.

Shila, it's ready for trial. You can find it in latest MLPV2.4u2 distribution, or in MLPV2 group notices.

What's the deadline, Couldbe?

I'd like to go wherever most of the scripters go.

Gonna miss this place!