Most of the time when MST tools aren’t working and this seems mysterious, it is usually due to permission issues or centerpoint finding issues. These are easy to fix once you know which piece needs adjusting. Below I’ve listed the recommended steps that will help you isolate and fix most issues that seem mysterious at first.
If you are using the MST Performance Engine and it’s not acting as expected…
- Move your MST Performance Engine 1m higher up in the air just so you can prove it will move, then click the performance engine, click “more rez”, then click “center”. If your Performance Engine does NOT move itself on top of a centerpoint, follow the rest of the suggestions below until it does center.
- Make sure that an MST Centerpoint is rezzed somewhere in the area, on the same parcel.
- If the centerpoint is not owned by you, make sure that you had the correct land group active, then try re-rezzing your MST Performance Engine. Sometimes a centerpoint is only configured to authorize people with a particular group active. The owner of the centerpoint may also have to add you to an allowed list.
- If you are using chat commands, make sure you are either within 20m of the MST Performance Engine, or within 100m if you are using the “shout” chat style.
- Make sure that the centerpoint’s name exactly matches the VENUE name set in the MST Performance Engine’s ~MST_CONFIG notecard. If in doubt, copy-paste the centerpoint’s name into the notecard on the VENUE line. You can use the “ALL” venue to match any centerpoint, but this can be unpredictable if there are multiple centerpoints nearby.
- Try reseting scripts on your MST Performance Engine and make sure no errors pop up.When you reset scripts you should see a message like the following ” INFO: Configuring to venue YourCenterPointName” where “YourCenterPointName” is the name of the MST Centerpoint you’re using.
If you are getting double effects or double-rezzing…
- Usually this is due to having more than one active MST performance engine out in the same area listening to the same centerpoint. To avoid this you can scan for duplicates using the MST Choreo HUD. Use the gear button and then choose “Scan for MST”. Pick up any duplicate MST Performance Engines, move them out of chat range, or pick one and choose “stagederez” from its menu to deactivate it.
If you are using the MST Mover and it’s not asking you for animation permission when you sit on it…
- Make sure that you have an MST Performance Engine rezzed nearby or are wearing an MST ChoreoHUD.
- If you want to use the MST Performance Engine to handle animations, check its “MST_CONFIG” notecard and make sure that “EVENTLIST_ACTIVE” is set to “YES”.
- Make sure that the MST Performance Engine’s ~EVENTLIST notecard contains a group that includes the exact name of the MST mover you are trying to sit on.
- Check the mover’s ~MOVELIST notecard. The “MSTCONTROLLER=” line should be set to the name of the performance engine you are using or “ALL”.
- Check that the Performance Engine is centered.
- Make sure you’re not blocking permissions dialogs.
- Make sure your viewer is not configured to reject or revoke animation requests. If you are using Firestorm, in the Preferences / Firestorm / Protection tab, you should have Revoke Permissions set to “Never (original behavior)”.
If you are using the MST Mover and it stops moving or rotating unexpectedly….
- Make sure you are not moving “too slow” or rotating too slowly. In general, avoid moving slower than 0.05 meters per second. This is an SL limitation.
If You Are Using MST Performance Engine with Cameras and You Can Not See Camera Commands…
- Make sure you’re sitting in an MST theater seat
- Make sure the theater seat has a ~seatconfig notecard, where the VENUE option matches your centerpoint name.
- Check that your performance engine is centered. Re-center it to be sure and try again.
- Reset scripts on the theater seat and watch your nearby chat. You should see a message that the seat configured itself to the centerpoint.
- Make sure you tap the “escape” key a few times, and control-9 to reset the zoom
- Make sure your bandwith is good, and you’re not streaming or downloading large files at the same time
If your MST Camera views are jerky, blurry, or slow…
- Ensure that you don’t have two different camera-controlling gadgets active at the same time. Don’t wear an MST Camera HUD while sitting on an MST Seat, and don’t wear an MST Camera HUD while sitting on an MST Mover.
- Camera effects are dependent on bandwidth. If you experience signs of low bandwidth to SL such as — mesh objects not rezzing, newly rezzed objects not appearing, textures staying grey for long periods, stuttering streams — your bandwidth may be too low for a good scripted camera experience.
- Camera effects are dependent on sim performance, particularly simulator “Script run” less than 50%. Try on a faster region and see if your experience improves.
If you are using MST Outfitter and every time you try to create an #RLV folder it disappears…
- Check your viewer preferences to make sure you do not have the option “Hide Empty System Folders” enabled.
If you are trying animations and you see your avatar pause or fail to animate…
- Your animations may need to be “cached”. Run each animation at least once (or use the pre-cache feature in MST Performance Engine or MST ChoreoHUD).
If while using the Performance Engine, you choose “saverez” to save positions of items for use in the rezzer, and some items you are trying to save do not print out a ‘REZME’ line…
- Reset the “rezTracker” script you placed in your prop, or reset scripts on the entire prop. Then try using “saverez” again. Resetting this script in the prop will cause it to “forget” its previous configuration and act like it is a new prop to be packaged.