Evie Moriguchi

While I never upgraded to AVSit2, I still use AVSit1 all the time. It's perfect for synched animations and multi-sitting, and the system does not require rezzing poseballs nor do you get the permissions dialog box like you do with MLP. [Note: anyone who's worked with NPCs can see the benefit of no permission dialogs and a static UUID for "seating", both of which are a problem with using unlinked temp objects to animate an avatar. I've used AVSit with my "crew" (bots) to patrol an island sim in a motorboat...the limits to linked prims may be 54 meters, but sit targets have a limit of 300 meters, which is enough to have a bot "wear" a speedboat (or jetski) and sit on a slowly rotating prim in the middle of the sim.] Once AVSit goes open-source in a few months, there really is not much reason to learn any other system. It's the best sitting/animation system out there, communicates well with customized scripts, allows you to easily convert MLP notecards to AVSit compatible notecards, eliminates the need for poseballs, and is definitely worth its original pricetag of $3000. The best news of all is that Code Violet's AVSitter will be released to the public for free in August 2017. Until then....I really, really recommend learning how to use Neofan Teardrop's already open source SpeedySIT. It's free, and an excellent solution for multiple animations, and seating more than one avatar on a prim (it doesn't really do synced couples animations, though) The biggest advantage for scripters with SpeedySit, is that it returns LSL compatible sit target information. Even if you opt to not use the SpeedySIT.lsl script in your final product, you can still get sit target data to use in your own code.

I have a friend who claims this happened to after a sim restart. Here's the process we went through to troubleshoot it. 1. If you have copies of the HUDs in your inventory (not links) try wearing those and see if those HUDs still work correctly. 2. Try resetting the scripts in the nonworking HUD (but you will probably lose your stored outfits) by selecting the HUD in Edit and then choosing Build > Scripts > Reset Scripts. 3. Ask the creator for a replacement HUD (which again, means you will lose your stored outfits) if you have no working copies of the HUD. Once you have HUDs that work (and you've resaved any outfits that need resaving) detach the HUD when you've saved a new outfit, and keep an extra copy in your inventory.

When you log into Radegast, check to see if you have more than one "Current Outfit" folder. If you do, file a ticket with SL support to have the additional COFs removed from your inventory (since "Current Outfit" is a system folder, you can't remove them yourself.)

I would look at either Corrade or MetaBOLT. MetaBOLT is no longer supported by it's creator, so recent changes in SL have broken a few features (like scripting costume changes) but it has two features that make it easy for operating NPCs. It still interfaces nicely with LSL (with the LSL-API) for the commands/functions that still work (that is if you can still find documentation on the commands available in LSL-API-- I suggest using the Wayback Machine for that information.). However, if you're not an LSL scripter looking for a machinima client, you can use the METAnomy feature to easily set up your scenes. MetaBOLT was originally designed as a text viewer, but as more users asked for NPC/group bot functions, it became very flexible bot client with training wheels: you still have text-based feedback, and a few interesting features available, that easily allow you to monitor your bot's environment. MetaBOLT is a lot lighter (CPU/RAM) to use than any of the graphics viewers. However, if you're looking for light, and need more than just a few NPCs/actors.... Corrade is incredibly lighter and far more flexible than MetaBOLT or Radegast. It's list of commands are overwhelming (NPCs can be scripted to "MARRY" and "DIVORCE", so if you're looking to generate some controversial buzz over your machinima project, Corrade gives you some options). If you're simply looking to animate NPCs you'll only need to be familiar with commands like "SIT", "STAND", "TYPING" (which is useful for handheld props that replace the default typing animations), "WEAR" and "UNWEAR" (for costume changes), TOUCH (for avatar/object interactions), ANIMATION, AUTOPILOT, TURN, and TURNTO (coupled with a good AO). Even though the MP has a few items released by the Corrade team to help you get started, you'll need to really brush up on your LSL skills to get your actors to perform. If you're not a strong scripter, and need NPCs for a short term project, I suggest using MetaBOLT. https://wiki.casperdns.com/index.php/METAbolt#Introduction https://bitbucket.org/METAbolt/metabolt.bitbucket.org/overview and you'll want to download the METAnomy plug-in (which is fairly intuitive and easier to use for simple projects than LSL-API) If you need the LSL-API documentation, use "metabolt.net/METAwiki/lslcommands.ashx" in your search at the Wayback Machine. A quick note: all costume changes will have to be done in a graphics based viewer before using your NPCs in MetaBOLT. If you're planning on creating regular features, take a look at Corrade http://grimore.org/secondlife/scripted_agents/corrade I'd suggest MetaBOLT over Radegast unless you're familiar with RLV programming.

mikka Luik wrote: erm they did inform link you have is from 11th december I think more than a week... try logging in more often as a sentient and merry (insert holiday) kitten They were pretty quiet about the whole thing, and for anyone who's had to set up bot scripts for Meta or any of the other bot services out there, it's going to be a nightmare scrambling around for options to keep it within a reasonable number of messages below the limits. Worse, it's 5000 messages per bot owner. That means 3 NPC bots are pretty much limited to about saying something once per minute. Which means I'll have to go back into my scripts, add a few dozen listeners, sensors and collision detectors to make sure the bots aren't accidentally using up their quota in local when no one's around. The other issue is that they just kind of tacked it on to the old "gaming search with bots" policy without specifying how, or even if, they were enforcing it differently. No indication if they were going to cap messages for going over during a 24 hour period, or start sending out warnings and account suspensions for folks who accidentally went over. Based on what my bots are used for, If they go mute for a couple of hours without putting their existence in jeopardy, the world won't end and it gives me a leeway in tweaking their scripts until they come under the cap. If I have to deal with warnings and threats while I'm adjusting their scripts then it's a major issue. LL needs to clear up the "penalties" for exceeding the limits.