Difference between revisions of "RLV SMARTSTRIP FOLDERS"
(→Arrange outfits to work with Smart Strip) |
(→Arrange outfits to work with Smart Strip) |
||
Line 60: | Line 60: | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
*NOTE avoid placing multiple copies of the same dummy layer in a single outfit, since sl will not allow you to wear two copies of an identical item. | *NOTE avoid placing multiple copies of the same dummy layer in a single outfit, since sl will not allow you to wear two copies of an identical item. | ||
*NOTE* Smart Strip can work with linked items, only if the links are to an original copy that is also in #RLV shared folders. Remember that the strip function by itself does not use folders, it identifies the actual worn item. But smart strip requires that item to be in an RLV folder for the next operation, which is "detach with this everything in the same folder". Therefore, the target of the link, the original worn item, must be in an RLV folder, and that folder must already be organized into groups that will be stripped with the item, since that is the folder the command will "see" when it strips the clothing layer. Too confusing? don't use links then. | *NOTE* Smart Strip can work with linked items, only if the links are to an original copy that is also in #RLV shared folders. Remember that the strip function by itself does not use folders, it identifies the actual worn item. But smart strip requires that item to be in an RLV folder for the next operation, which is "detach with this everything in the same folder". Therefore, the target of the link, the original worn item, must be in an RLV folder, and that folder must already be organized into groups that will be stripped with the item, since that is the folder the command will "see" when it strips the clothing layer. Too confusing? don't use links then. | ||
− | Once the #RLV folder is built, a user can just browse the menu and select particular objects and outfits to wear or remove. | + | *Once the #RLV folder is built, a user can just browse the menu and select particular objects and outfits to wear or remove. |
− | NOTE: If you place a + sign at the start of a folder name in your inventory, this also means "add"--it will add when the command issued RLV, is actually "wear". | + | *NOTE: If you place a + sign at the start of a folder name in your inventory, this also means "add"--it will add when the command issued RLV, is actually "wear". |
− | .Hidden folders | + | ===.Hidden folders=== |
Any folder with a dot in front of the name will not appear in the collar menu, nor will any of its subfolders. For instance, keep a folder named [.hidden] in your RLV folders. Use it when sorting outfits you don't want to show in the collar menu. | Any folder with a dot in front of the name will not appear in the collar menu, nor will any of its subfolders. For instance, keep a folder named [.hidden] in your RLV folders. Use it when sorting outfits you don't want to show in the collar menu. | ||
Do not place a dot in front of a subfolder that contains items to be worn; when you issue an rlv command to wear the outfit, the subfolders will not be found. For Firestorm and other viewers with RLVa, only a chat command with that exact folder name will still find a hidden folder. | Do not place a dot in front of a subfolder that contains items to be worn; when you issue an rlv command to wear the outfit, the subfolders will not be found. For Firestorm and other viewers with RLVa, only a chat command with that exact folder name will still find a hidden folder. | ||
− | (nostrip) | + | ===(nostrip)=== |
Add (nostrip) to the end of any item or folder containing an item that you do not ever want stripped by rlv. For instance, a folder contains a hair named blondie. If the folder is named blondie (nostrip) it cannot be stripped. Or if the hair item can be named blondie (nostrip) it cannot be stripped. This does not work for subfolders if only the top folder has (nostrip) at the end of the name. | Add (nostrip) to the end of any item or folder containing an item that you do not ever want stripped by rlv. For instance, a folder contains a hair named blondie. If the folder is named blondie (nostrip) it cannot be stripped. Or if the hair item can be named blondie (nostrip) it cannot be stripped. This does not work for subfolders if only the top folder has (nostrip) at the end of the name. | ||
− | |||
− | |||
− | |||
===Make sure your RLV Folders are setup=== | ===Make sure your RLV Folders are setup=== |
Revision as of 15:53, 5 March 2019
__NO EDITSECTION__
Basic Viewer Setup | Basic Folder Setup | Basic Relay Setup |
About RLV | SmartStrip Folders | SmartStrip Relay Setup |
AutoAttach | AutoAttach Folders | Quick Start |
Smart Strip
Smart Strip solves the problem of clothing items not being actual clothing layers.
- For instance, "boots" might include a shoe base, ankle attachments, and alpha.
- Or in the case of Mesh Avatars, where none of your clothes are actual clothing layers.
It provides a method to use 'fake clothing' to build folders of items to be attached and removed.
Setting Up Smart Strip
Arrange outfits to work with Smart Strip
Start with a default blank outfit in your RLV folder. | |
If you do not have one you can get it here: | |
Copy and rename it to something useful, like Outfit-1
|
|
- NOTE avoid placing multiple copies of the same dummy layer in a single outfit, since sl will not allow you to wear two copies of an identical item.
- NOTE* Smart Strip can work with linked items, only if the links are to an original copy that is also in #RLV shared folders. Remember that the strip function by itself does not use folders, it identifies the actual worn item. But smart strip requires that item to be in an RLV folder for the next operation, which is "detach with this everything in the same folder". Therefore, the target of the link, the original worn item, must be in an RLV folder, and that folder must already be organized into groups that will be stripped with the item, since that is the folder the command will "see" when it strips the clothing layer. Too confusing? don't use links then.
- Once the #RLV folder is built, a user can just browse the menu and select particular objects and outfits to wear or remove.
- NOTE: If you place a + sign at the start of a folder name in your inventory, this also means "add"--it will add when the command issued RLV, is actually "wear".
.Hidden folders
Any folder with a dot in front of the name will not appear in the collar menu, nor will any of its subfolders. For instance, keep a folder named [.hidden] in your RLV folders. Use it when sorting outfits you don't want to show in the collar menu.
Do not place a dot in front of a subfolder that contains items to be worn; when you issue an rlv command to wear the outfit, the subfolders will not be found. For Firestorm and other viewers with RLVa, only a chat command with that exact folder name will still find a hidden folder.
(nostrip)
Add (nostrip) to the end of any item or folder containing an item that you do not ever want stripped by rlv. For instance, a folder contains a hair named blondie. If the folder is named blondie (nostrip) it cannot be stripped. Or if the hair item can be named blondie (nostrip) it cannot be stripped. This does not work for subfolders if only the top folder has (nostrip) at the end of the name.
Make sure your RLV Folders are setup
- Put outfits and restraints that you want others to use on you in folders of their own, inside your #RLV folder.
- Name the folders something short, unique and clear as to what they contain. For instance: #RLV>Restraints>Gag would be a sample folder set, with Gag inside Restraints, inside #RLV.
- Every item, such as a gag, needs its own folder even if it is only one piece. Similarly, every item put in the same folder as something else will go on at the same time as everything else in the folder.
For more on shared folders see Marine Kelley's tutorial at http://realrestraint.blogspot.com/2008/08/objects-sharing-tutorial.html.