How to Rez and Cleanup Props - Revision history

Arrehn: /* Rezzing Scenes or Groups of Objects Independently of Each Other */

2024-08-09T15:58:39Z

Rezzing Scenes or Groups of Objects Independently of Each Other

← Older revision		Revision as of 15:58, 9 August 2024
Line 240:		Line 240:
	=== Rezzing Scenes or Groups of Objects Independently of Each Other ===		=== Rezzing Scenes or Groups of Objects Independently of Each Other ===

			Sometimes you will want to rez a group of objects at once. This can be use for quick and easy complete stage or theater changes, for example. You may have noticed that in the examples we place our props under the "@main" line in the ~PACKLIST notecard. This is because "@main" is the default scene. To use other scenes you can simply add your own names that start with "@" to the packlist notecard, and move objects under those scene names. Be sure to keep the names short without punctuation. For example:

			'''@main'''
			myHouse, <0,0,0>,<0,0,0,0>
			houseSofa, <0,0,0>,<0,0,0,0>

			'''@scene2'''
			myCastle, <0,0,0>,<0,0,0,0>
			moat, <0,0,0>,<0,0,0,0>

			'''@spaceTheater'''
			spaceSurround, <0,0,0>,<0,0,0,0>
			shootingStars, <0,0,0>,<0,0,0,0>

			In the above example the scene names are highlighted in bold. Now, when you click the Performance Engine and select "Rez [main]", the "myHouse" and "houseSofa" props will be rezzed. If you want to rez the other groups instead, you can click the PE again, select "<More Rez>", then "rez [GROUP]". You will then be shown buttons with all your scenes. Simply click the button for the scene you wish to rez.

			You can rez and derez specific scenes via chat commands. For example:
			/8 rez @scene2
			/8 derez @scene2
			/8 rez @spaceTheater
			/8 rez @main:@scene2

			You can also rez and derez specific scenes in a programmed timeline, as we will demonstrate in the programmed timeline section of the MST docs.

	=== Prevent certain objects from being rezzed with the default "rez" command ===		=== Prevent certain objects from being rezzed with the default "rez" command ===

Arrehn at 13:14, 9 August 2024

2024-08-09T13:14:04Z

← Older revision		Revision as of 13:14, 9 August 2024
Line 238:		Line 238:
	'''''Special Note: To avoid typing or gestures, you can program many of the rez chat commands into scheduled timelines or huds. This is discussed in the the documentation section of timelines, and the "MST Programmable Button HUD".'''''		'''''Special Note: To avoid typing or gestures, you can program many of the rez chat commands into scheduled timelines or huds. This is discussed in the the documentation section of timelines, and the "MST Programmable Button HUD".'''''

	=== Prevent certain objects from being rezzed by default ===		=== Rezzing Scenes or Groups of Objects Independently of Each Other ===


			=== Prevent certain objects from being rezzed with the default "rez" command ===

	If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:		If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:

Arrehn: /* Other Types of Rezzing (scenes, individual objects, chat commands, etc) */

2024-08-02T21:51:35Z

Other Types of Rezzing (scenes, individual objects, chat commands, etc)

← Older revision		Revision as of 21:51, 2 August 2024
Line 236:		Line 236:
	These targeted prop rez and derez commands can sometimes be an alternative to using “hide” transparency scripts. Derezzing in particular is fast and easy even during a busy show. Rezzing during a live performance however, can sometimes be delayed if the sim becomes busy. Additionally if you are rezzing mesh or a richly textured objects, you might notice a delay before the mesh and/or textures can be sent to each nearby viewer.		These targeted prop rez and derez commands can sometimes be an alternative to using “hide” transparency scripts. Derezzing in particular is fast and easy even during a busy show. Rezzing during a live performance however, can sometimes be delayed if the sim becomes busy. Additionally if you are rezzing mesh or a richly textured objects, you might notice a delay before the mesh and/or textures can be sent to each nearby viewer.

	To avoid typing or gestures, you can program ~~these~~ rez commands into scheduled ~~timeline~~. This is discussed in the the documentation section of timelines.		'''''Special Note: To avoid typing or gestures, you can program many of the rez chat commands into scheduled timelines or huds. This is discussed in the the documentation section of timelines, and the "MST Programmable Button HUD".'''''

	=== Prevent certain objects from being rezzed by default ===		=== Prevent certain objects from being rezzed by default ===
Line 242:		Line 242:
	If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:		If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:

	Edit the PACKLIST notecard and find the line for the object you do not want to rez by default.		# Edit the PACKLIST notecard and find the line for the object you do not want to rez by default.
	~~Change~~ the ~~command “REZME” at the start of the line to “NOREZ”. This will allow you~~ to ~~load the object individual~~ as ~~described above, but it will not rez by default~~.		# Move that line from underneath the "@main" group, to a different group such as "@scene2".

	8.~~d Reset locations of inadvertently moved props~~		Now this object will not rez unless you specifically rez that one object or if you use "/8 rez @scene2". Similarly you will have to derez it manually by name or with "/8 derez @scene2"

	~~If you have moved one or more~~ of your props out of its normal position, and you want the prop to return to its normal spot, you can click the performance engine, choose “<more REZ>” and then choose “updaterez”. You may also shout the chat command, “/8 updaterez”.		=== Reset Locations of Accidentally Moved Props ===
	~~8.d Adding No-Mod objects (not recommended)~~

	If you ~~simply must use a no-mod object as a~~ prop, ~~sometimes~~ you can ~~get it to work in~~ the ~~MST Performance Engine~~. ~~Your results~~ may ~~vary. Instead of using saverez (which requires a ~MST reztracker script),~~ shout the chat command “/8 ~~nomodsaverez <name>”~~. ~~For example:~~		If you have moved one or more of your props out of its normal position, and you want the prop to return to its normal spot, you can click the performance engine, choose “<more REZ>” and then choose “updaterez”. You may also shout the chat command, “/8 updaterez”. You could also derez the object and then rez it back.

	~~/8 nomodsaverez pinkcadillac~~		=== Adding No-Mod objects ===

	~~The above command will print out~~ a ~~“REZME=…” line~~ you can ~~add~~ to the ~~~PACKLIST notecard~~, ~~similar to~~ the ~~saverez method from section [2.1]. From here pack the no-modify prop like you would any other prop~~. ~~There are some limitations with this method~~:		If you must use a no-mod object as a prop, sometimes you can get it to work in the MST Performance Engine. Your results may vary. Instead of using saverez (which requires a ~MST reztracker script), shout the chat command “/8 nomodsaverez <name>”. For example:

	~~It only works if the prop will be location < 10m from the stage center.~~		/8 nomodsaverez pinkcadillac
	Sometimes the position or rotation of the saved prim will not be accurate. It may depend on the specific object and the rotation of the stage how accurate the positioning will be. This inaccuracy in some circumstances when rezzing no-mod objects is a known SL bug.
	~~You will have to manually pick up or delete any no-mod rezzed objects from your set when you are finished. They will not be able to listen to “derez” or “stagederez” commands.~~

	8.e Permanently Removing ~MST rezTracker ~~Scripts~~		The above command will print out a line you can add to the ~PACKLIST notecard, similar to the usual saverez method. Now pack the no-modify prop like you would any other prop. There are some limitations with this method:

			* It only works if the prop will be located < 10m from the MST Centerpoint.
			* Sometimes the position or rotation of the saved prim will not be accurate. It may depend on the specific object and the rotation of the stage how accurate the positioning will be. This inaccuracy in some circumstances when rezzing no-mod objects is a known SL bug.
			* You will have to manually pick up or delete any no-mod rezzed objects from your set when you are finished. They will not be able to listen to “derez” or “stagederez” commands.

			=== Permanently Removing ~MST rezTracker ===

	If you ever wish to stop managing your props with the MST Performance Engine and wish for them to stay out permanently, you may use the following command to automatically delete the “~MST reztracker” scripts:		If you ever wish to stop managing your props with the MST Performance Engine and wish for them to stay out permanently, you may use the following command to automatically delete the “~MST reztracker” scripts:

	/8 permrez		/8 permrez

	8.~~f Optimizing contents window load time~~		You can also simply remove the rezTracker script from the prop's contents.

	By default the MST Performance Engine comes with the capability to animate up to 80 avatars at once. You will see 80 “~perm” scripts in the contents of the engine. Do not panic, these scripts are turned off by default and are only turned on when they are used. However, they can make the contents window slower to load at times.		== Optimizing Contents Window Load Time ==

			By default the MST Performance Engine comes with the capability to animate up to 12 avatars at once, with a total capability to handle over 130 avatars with expansions. You will see 12 “~perm” scripts in the contents of the engine. Do not panic, these scripts are turned off by default and are only turned on when they are used. However, they can make the contents window slower to load at times.

	If you wish your contents window to load faster, you may delete the ~perm scripts you are not intending to use +1 spare. For example, if you only need to animate three avatars, keep the scripts ‘~perm0, ~perm1, ~perm2, and ~perm3’ and delete all the others.		If you wish your contents window to load faster, you may delete the ~perm scripts you are not intending to use +1 spare. For example, if you only need to animate three avatars, keep the scripts ‘~perm0, ~perm1, ~perm2, and ~perm3’ and delete all the others.

	~~9. Sleep Mode~~

	Your MST Performance Engine will turn off most of its scripts automatically if it has not been used in 2 hours. It does this to minimize any script load on the region where it is rezzed. It will automatically wake up again whenever an authorized person clicks it to activate the blue popup menu, or tells it to center itself.

	~~If your region is extremely laggy it may take longer than usual for scripts to ‘wake up’. If you are worried about this, simply call up the menu of your performance engine early to wake it up.~~

	~~10.~~ Troubleshooting		== Troubleshooting ==

	If your performance engine isn’t working as you expect, check your nearby chat window for clues. Sometimes it chats warnings or errors that can help you solve the issue.		If your performance engine isn’t working as you expect, check your nearby chat window for clues. Sometimes it chats warnings or errors that can help you solve the issue.

Arrehn: /* Other Commands */

2024-08-02T21:30:57Z

Other Commands

← Older revision		Revision as of 21:30, 2 August 2024
Line 213:		Line 213:
	You are encouraged to customize the appearance of performance engine and make it reflect your personality or brand. Audience members often cam around the theater and make their own ‘backstage tours’, so customizing your performance engine can be a subtle way to build your name recognition.		You are encouraged to customize the appearance of performance engine and make it reflect your personality or brand. Audience members often cam around the theater and make their own ‘backstage tours’, so customizing your performance engine can be a subtle way to build your name recognition.

	== Other ~~Commands~~ ==		== Other Types of Rezzing (scenes, individual objects, chat commands, etc) ==
	=== Chat commands ===		=== Chat commands ===

Line 227:		Line 227:
	/8 derez sofa1		/8 derez sofa1

	You can also rez or derez more than one specific object at a time, like:		You can also rez or derez more than one specific object at a time by separating the object names with colon ":" characters, like this:

	/8 rez largePlant:smallPlant:table		/8 rez largePlant:smallPlant:table
Line 234:		Line 234:
	Any single “rez” or “derez” line can be a maximum of 256 characters. If you have more objects than can fit on one line, just use more then one line.		Any single “rez” or “derez” line can be a maximum of 256 characters. If you have more objects than can fit on one line, just use more then one line.

	These targeted prop rez and derez commands can sometimes be an alternative to using “hide” transparency scripts.		These targeted prop rez and derez commands can sometimes be an alternative to using “hide” transparency scripts. Derezzing in particular is fast and easy even during a busy show. Rezzing during a live performance however, can sometimes be delayed if the sim becomes busy. Additionally if you are rezzing mesh or a richly textured objects, you might notice a delay before the mesh and/or textures can be sent to each nearby viewer.

	~~These shouted commands can be cumbersome to type manually but~~ you can program ~~them~~ into ~~an EVENTLIST later, or use gestures~~.		To avoid typing or gestures, you can program these rez commands into scheduled timeline. This is discussed in the the documentation section of timelines.

	=== Prevent certain objects from being rezzed by default ===		=== Prevent certain objects from being rezzed by default ===

Arrehn: /* Other Commands */

2024-08-02T19:02:57Z

Other Commands

← Older revision		Revision as of 19:02, 2 August 2024
Line 214:		Line 214:

	== Other Commands ==		== Other Commands ==
	~~8.a~~ Chat commands		=== Chat commands ===

	The MST Performance engine can be operated entirely by chat commands, not just the blue popup menu. This can be useful for automation or for kicking off commands from a programmed timeline. For a list of chat commands your MST rezzer supports, use the “/8 help” command, or choose “help” from the performance engine’s menu.		The MST Performance engine can be operated entirely by chat commands, not just the blue popup menu. This can be useful for automation or for kicking off commands from a programmed timeline. For a list of chat commands your MST rezzer supports, use the “/8 help” command, or choose “help” from the performance engine’s menu.

	If you use these commands be sure to shout them if you are further away than 20m. Also be sure that you add ‘ALLOW’ lines for any users other than yourself who should be allowed to operate your performance engine as described in section 5, ‘Collaboration’.		If you use these commands be sure to shout them if you are further away than 20m. Also be sure that you add ‘ALLOW’ lines for any users other than yourself who should be allowed to operate your performance engine as described in section labelled, ‘Collaboration’.
	~~8.b~~ Rezzing and Derezzing Specific Objects
			=== Rezzing and Derezzing Specific Objects ===

	If you wish to rez a single prop or derez a single prop, you can use the chat commands “/8 rez <propname>” and “/8 derez <propname>”. For example:		If you wish to rez a single prop or derez a single prop, you can use the chat commands “/8 rez <propname>” and “/8 derez <propname>”. For example:

	/8 rez largePlant		/8 rez largePlant
	/8 derez sofa1		/8 derez sofa1

	You can also rez or derez more than one specific object at a time, like:		You can also rez or derez more than one specific object at a time, like:

	/8 rez largePlant:smallPlant:table		/8 rez largePlant:smallPlant:table
	/8 derez sheets:pillows		/8 derez sheets:pillows

	Any single “rez” or “derez” line can be a maximum of 256 characters. If you have more objects than can fit on one line, just use more then one line.		Any single “rez” or “derez” line can be a maximum of 256 characters. If you have more objects than can fit on one line, just use more then one line.
Line 236:		Line 237:

	These shouted commands can be cumbersome to type manually but you can program them into an EVENTLIST later, or use gestures.		These shouted commands can be cumbersome to type manually but you can program them into an EVENTLIST later, or use gestures.
	~~8.c~~ Prevent certain objects from being rezzed by default
			=== Prevent certain objects from being rezzed by default ===

	If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:		If you do not want one of your objects to be rezzed by default when you use “rez” or “stagerez” commands:

Arrehn: /* Collaboration with others / Sharing your performance engine */

2024-08-02T18:52:52Z

Collaboration with others / Sharing your performance engine

← Older revision		Revision as of 18:52, 2 August 2024
Line 185:		Line 185:
	== Collaboration with others / Sharing your performance engine ==		== Collaboration with others / Sharing your performance engine ==

	You can optionally allow other users to use the stagerez, stagederez and other MST performance engine commands, especially if you have left your performance engine in a storage location backstage in a theater. To allow another user to be able to click your stage or send chat commands, edit the “~MST_CONFIG” notecard and add a line with your friend’s login name or avatar key. For example:		=== Share Menu Access ===

	~~ALLOW=Arrehn Oberlander~~		You can optionally allow other users to use the stagerez, stagederez and other MST performance engine commands, especially if you have left your performance engine in a storage location backstage in a theater. To allow another user to be able to click your stage or send chat commands, edit the “~MST_CONFIG” notecard and add a line with your friend’s login name or avatar key and re-save the notecard. For example:
	~~ALLOW=SomeoneElse Resident~~

	There should be an example of this line already in ~~the notecard. After you’ve added your own line to~~ the ~MST_CONFIG notecard~~, save the notecard and they will~~ be able to ~~use the blue menu of~~ your ~~performance~~ engine.		ALLOW=Arrehn Oberlander
			ALLOW=SomeoneElse Resident

			There should be an example of this line already in the ~MST_CONFIG notecard. The allowed person should now be able to click your engine and receive its menu.

	Use avatar UUIDs instead of names for the greatest safety and speed. You can find an avatar’s UUID by opening up their profile and looking at the top of the window. It is a good idea to allow a theater’s seating and centerpoint owner by UUID, if that person is not yourself.		Use avatar UUIDs instead of names for the greatest safety and speed. You can find an avatar’s UUID by opening up their profile and looking at the top of the window. It is a good idea to allow a theater’s seating and centerpoint owner by UUID, if that person is not yourself.

			=== Share Object and Notecard Access ===
	If you want other users to be able to update your props, some care must be taken. You will wish to do the following:		If you want other users to be able to update your props, some care must be taken. You will wish to do the following:

	Select the Performance Engine in the build window, ensure the ‘share’ button on the first tab is checked, and that a group is set. Your collaborators should all be members of this group.		#Select the Performance Engine in the build window, ensure the ‘share’ button on the first tab is checked, and that a group is set. Your collaborators should all be members of this group.
	In the Performance Engine’s contents, ~~right-~~click the ~~~PACKLIST notecard~~. ~~Change~~ the ~~permission to allow~~ COPY, MODIFY, TRANSFER and SHARE.		#Grant your collaborators “Object Rights” permissions, if you trust them completely. Be careful with this.
	~~Optionally grant~~ your collaborators ~~“Object Rights” permissions, if you trust them completely. Be careful with~~ this.		#In the Performance Engine’s contents, click the permissions button. Ensure the "notecard" option is selected, along with permissions '''COPY, MODIFY, TRANSFER and SHARE.''' Note: You or your collaborators may have to re-perform this step regularly.
	Your collaborators should now be able to open up your ~PACKLIST notecard in your performance engine, adjust positions, and remove props. It’s likely that due to SL permissions, you will be the only person who can add new props.
			Your collaborators should now be able to open up your ~PACKLIST notecard in your performance engine, adjust positions, and remove props. It’s likely that due to SL permissions, you will be the only person who can add new props.

	If you’re having trouble sharing access to your notecards after doing the above, ensure your collaborators have the same group as the performance engine active. If this still does not allow access, sometimes relogging or leaving the region and returning helps.		If you’re having trouble sharing access to your notecards after doing the above, ensure your collaborators have the same group as the performance engine active. If this still does not allow access, sometimes relogging or leaving the region and returning helps. Sometimes step 2. also needs to be performed again.

	7. Customizing the MST Performance Engine’s appearance		== Customizing the MST Performance Engine’s appearance ==

	You can also change the textures of the MST Performance Engine and make it invisible and/or phantom if you desire. You may also link it to other objects as long as it is always the “root” object in a linkset.		You can also change the textures of the MST Performance Engine and make it invisible and/or phantom if you desire. You may also link it to other objects as long as it is always the “root” object in a linkset.
Line 209:		Line 213:
	You are encouraged to customize the appearance of performance engine and make it reflect your personality or brand. Audience members often cam around the theater and make their own ‘backstage tours’, so customizing your performance engine can be a subtle way to build your name recognition.		You are encouraged to customize the appearance of performance engine and make it reflect your personality or brand. Audience members often cam around the theater and make their own ‘backstage tours’, so customizing your performance engine can be a subtle way to build your name recognition.

	8. Other Commands		== Other Commands ==
	8.a Chat commands		8.a Chat commands

Arrehn: /* Removing Props */

2024-08-02T18:39:48Z

Removing Props

← Older revision		Revision as of 18:39, 2 August 2024
Line 170:		Line 170:
	It is easy to remove an object from your MST performance engine.		It is easy to remove an object from your MST performance engine.

	Open the “~PACKLIST” notecard		# Open the “~PACKLIST” notecard
	Delete the ~~“REZME=”~~ line that contains the name of the prop you wish to remove.		# Delete the line that contains the name of the prop you wish to remove.
	Delete that prop from the contents of the MST performance engine.		# Delete that prop from the contents of the MST performance engine.
			You're done!

	5. Fast Access to the Performance Engine’s Click Menu		== Fast Access to the Performance Engine’s Click Menu ==

	If you wish to access the Performance Engine’s click menu without using your viewer camera to navigate to it’s location, you have a few options.		If you wish to access the Performance Engine’s click menu without using your viewer camera to navigate to it’s location, you have a few options.

	Use your “Area Search” window to find the Performance Engine by its name, then right click it’s line in the search results and choose “touch”.		* Wear the MST quick hud from your show tools inventory folder,then use the "Harp Logo" button to pair it with a Performance Engine if it isn't already piared. From that point forward whenever you click the harp logo button, you will receive that engine's popup menu.
	Wear the MST ChoreoHUD Solo (or any other MST Choreo HUD) and use the gear menu to pair theHUD with your Performance Engine. From this point on, whenever you click the MetaHarper mermaid logo on the MST Choreo HUD, your Performance Engine’s menu will pop up.		* Use your “Area Search” window to find the Performance Engine by its name, then right click it’s line in the search results and choose “touch”.
	Use the chat command “/8 menu”. If you are further away, you may need to use ‘shout’ for your performance engine to hear you. Caution: all MST Performance Engine’s within hearing range will send you their menu. If you only want to access a specific one, you may specify its name. For example: “/8 menu myPerformanceEngineName”		* Use the chat command “/8 menu”. If you are further away, you may need to use ‘shout’ for your performance engine to hear you. Caution: all MST Performance Engine’s within hearing range will send you their menu. If you only want to access a specific one, you may specify its name. For example: “/8 menu myPerformanceEngineName”

	6. Collaboration with others / Sharing your performance engine		== Collaboration with others / Sharing your performance engine ==

	You can optionally allow other users to use the stagerez, stagederez and other MST performance engine commands, especially if you have left your performance engine in a storage location backstage in a theater. To allow another user to be able to click your stage or send chat commands, edit the “~MST_CONFIG” notecard and add a line with your friend’s login name or avatar key. For example:		You can optionally allow other users to use the stagerez, stagederez and other MST performance engine commands, especially if you have left your performance engine in a storage location backstage in a theater. To allow another user to be able to click your stage or send chat commands, edit the “~MST_CONFIG” notecard and add a line with your friend’s login name or avatar key. For example:

Arrehn: /* How to Make Changes to your Props After Adding them to the Performance Engine */

2024-08-02T13:32:41Z

How to Make Changes to your Props After Adding them to the Performance Engine

Arrehn: /* How do I use the Performance Engine as a rezzer? */

2024-08-02T13:18:44Z

How do I use the Performance Engine as a rezzer?

← Older revision		Revision as of 13:18, 2 August 2024
Line 30:		Line 30:
	== How do I use the Performance Engine as a rezzer? ==		== How do I use the Performance Engine as a rezzer? ==

	The MST Performance Engine works similar to most other rezzer systems in SL. At a very high level you need to add a script to all the objects you want it to rez, save their positions into a notecard, and place copies of the objects you wish to rez in the rezzer ~~objects~~ contents. We'll walk through these steps along with some MST-specific details below.		The MST Performance Engine works similar to most other rezzer systems in SL. At a very high level you need to add a script to all the objects you want it to rez, save their positions into a notecard, and place copies of the objects you wish to rez in the rezzer's contents. We'll walk through these steps along with some MST-specific details below.

	=== Check that you have a Performance Engine rezzed, and 'centered' ===		=== Check that you have a Performance Engine rezzed, and 'centered' ===
Line 38:		Line 38:

	You can activate an MST performance engine by clicking on it, and choosing 'center' from the popup menu. The engine should move on top of your centerpoint, the hovertext will disappear, and it will now be active for all commands.		You can activate an MST performance engine by clicking on it, and choosing 'center' from the popup menu. The engine should move on top of your centerpoint, the hovertext will disappear, and it will now be active for all commands.


			''You might ask yourself, "What is this 'centerpoint' business? I have used other rezzers and they do not require a centerpoint prim. What is it for?"'' MST technology uses centerpoints for a few different reasons. It is useful when collaborating with a group of builders. One person can update the centerpoint's location and all the acts that use it, even from other people, will magically work without needing to be changed. Also you can visually see that your act is oriented the right way, before you use it.''


	=== Arrange Your Props ===		=== Arrange Your Props ===

Arrehn: /* What is the MST Performance Engine rezzer? */

2024-08-02T13:04:51Z

What is the MST Performance Engine rezzer?

← Older revision		Revision as of 13:04, 2 August 2024
Line 2:		Line 2:
	== What is the MST Performance Engine rezzer? ==		== What is the MST Performance Engine rezzer? ==

	The "MST Performance Engine" or just "PE" for short, includes many pieces of show technology in one single object. One of the the things it can do is act as rezzer, rezzing and derezzing props. ~~So the PE acts as a rezzer, but it is not only a rezzer.~~		The "MST Performance Engine" or just "PE" for short, includes many pieces of show technology in one single object. One of the the things it can do is act as rezzer, rezzing and derezzing props.

	=== Why is the Performance Engine rezzer special? ===		=== Why is the Performance Engine rezzer special? ===

← Older revision		Revision as of 13:32, 2 August 2024
Line 137:		Line 137:
	If you want to replace one of the props loaded in the MST performance engine without changing where it will appear when it rezzes:		If you want to replace one of the props loaded in the MST performance engine without changing where it will appear when it rezzes:

	* Pick up your new version of the props from the region into your avatar inventory.		# Pick up your new version of the props from the region into your avatar inventory.
	* Derez your current props to clear the stage.		# Derez and/or delete your current props to clear the stage.
	* Delete the older version of the prop from the contents of the performance engine.		# Delete the older version of the prop from the contents of the performance engine.
	* Drag the new version of your prop from your avatar inventory into the performance engine’s inventory.		# Drag the new version of your prop from your avatar inventory into the performance engine’s inventory.
	* Rez your props and check that the new version appears.		# Rez your props and check that the new version appears.

	''Pro Tip: Consider editing the description field of your prop to add a date whenever you update your prep. This can help you quickly check in the future if your prop is updated or not. For example you could change a description to "Updated: 5:43pm 6/22/2024"''		''Pro Tip: Consider editing the description field of your prop to add a date whenever you update your prep. This can help you quickly check in the future if your prop is updated or not. For example you could change a description to "Updated: 5:43pm 6/22/2024"''
Line 151:		Line 151:
	If you want to change the location where an existing prop will rez:		If you want to change the location where an existing prop will rez:

	Rez the prop ~~as usual~~ and then move the prop into the new correct position.		# Rez the prop using your PE and then move the prop into the new correct position.
	Use the “saverez” menu button as described in step 3a, or shout ‘/8 ~~saverez’~~		# Use the “saverez” menu button as described in step 3a, or shout ‘/8 saverez YourPropName’
	Find the ~~“REZME”~~ line in your nearby chat window that has the name of the prop you are moving. Copy this single line into your clipboard.		# Find the printed line in your nearby chat window that has the name of the prop you are moving. Copy this single line into your clipboard.
	Derez your props.		# Derez your props.
	Finally, open up the ~PACKLIST notecard and ~~paste this new line overwriting~~ the ~~previous “REZME”~~ line for this ~~one specific~~ prop ~~and~~ save the notecard.		# Finally, open up the ~PACKLIST notecard in the PE and replace the old line for this prop with the new line from your clipboard, thend save the notecard.
	Rez your props again, and verify the position you changed has updated as you expect.		# Rez your props again, and verify the position you changed has updated as you expect.

	~~4.c Adding new props~~		== How to Add New Props ==

	If you wish to add a new prop object to a MST performance engine:		If you wish to add a new prop object to a MST performance engine:

	Place your new prop in the desired location on your stage and add a “~MST reztracker” script inside it as usual.		# Place your new prop in the desired location on your stage and add a “~MST reztracker” script inside it as usual.
	Click the MST performance engine and select “saverez” button or use the “/8 saverez” shouted chat command, as described ~~in step 3a~~. You can save time by just copy-pasting the single new ~~“REZME=”~~ line that includes the name of your new prop, and pasting that single line to the end of the ~PACKLIST notecard.		# Click the MST performance engine and select “saverez” button or use the “/8 saverez” shouted chat command, as described earlier. You can save time by just copy-pasting the single new line that includes the name of your new prop, and pasting that single line to the end of the ~PACKLIST notecard.
	Pick up your new prop ~~and~~ drag it into the contents of the performance engine.		# Pick up a copy of your new prop to inventoryu, remove the original, then drag the new copy from your inventory window into the contents of the performance engine.

	~~4.d~~ Removing ~~props~~		== Removing Props ==

	It is easy to remove an object from your MST performance engine.		It is easy to remove an object from your MST performance engine.