Omega Add-Ons – RLV Outfit Kit

Omega RLV Outfit Kit

This kit is designed to allow you to create and save outfits that can be used with RLV.
With this Kit you’ll create huds that can store entire outfits and apply them to your Omega Enabled Mesh Body/Parts as soon as they are worn.  When placed in your RLV folders, RLV can be used to add them and change your outfit.

Important: These huds will attempt to apply multiple textures to your body in fairly rapid succession. As a result, it will not work if your mesh requires you to answer a prompt to apply, ie like Maitreya.  While we will try to note  which bodies it won’t work with, make sure your body is not one with a popup. For more details about each individual mesh, scroll to the bottom.

Part Zero: What is in the Box

Part Zero: What’s in the Box

  • RLV Outfit Applier: You will use these to arrange and store individual outfits to use later. Once created, these can be used on their own or in conjunction with various RLV products.
  • RLV Makeup Applier: These work the same way as Outfit Appliers, but are for Mesh Heads!
  • RLV Combined HUD: This is used when arranging RLV Outfits and for Stripping/Redressing if you don’t have a 3rd Party Product.
  • RLV Control Relay: This stores your outfit state and is what 3rd Party HUDs and Collars communicate with to be able to strip and redress you.

[collapse]
Part One: Prepping Your Body

Part One: Prepping Your Body

  1. Make sure your body has Omega Installed.
  2. Make sure your body has ALL it’s clothing layers turned on.
  3. If your body has a “prompt for layer” option, make sure you’ve turned it off.

[collapse]
Part Two: Creating Outfit Appliers

Step One: Rez the RLV Outfit and/or Makeup Applier.
They’ll look like this:
Step Two: Wear the RLV Combined HUD
It’ll look like this:

Step Three: Set up the Outfit Applier

Each RLV Outfit applier can apply up to 6 different clothing layers/zones. Each RLV Makeup Applier can store up to 9 different textures. The hover-text above the Outfit applier tells you what will happen to each one.

Each mesh is different. Not all will support ALL of these, and in some meshes, some layers will respond to multiple layers/zones (ie, a single layer mesh, will ussually respond to both bra and top layers). I suggest setting unneeded textures/zones to locked and ignore to avoid conflicts.

  • Loaded: Means a texture has been loaded into this slot and will be applied. To do this, simply wear and use an Omega applier. The Outift applier will hear and store the texure.
  • Clear: Means a transparent texture will be applied. Use this to clear layers that won’t be needed when using this outfit. To do this, use the Little Pink Eraser buttons on the RLV Combined HUD.
  • Ignore: Means nothing will be done with this slot. Use this for layers your body doesn’t have (ie tatts) and/or for outfits you want to be able to use with other  items. (Ie, if you want the applier to apply a dress on the pant/top layer without removing the bra/undies on the undies layer) To do this, use the X buttons on the RLV Combined HUD.
  • (Locked): This means that collars and other items using the API can’t accidentally remove this item. (good for tattoos! Also recommended for layers not supported by your mesh.) To Lock/Unlock, use the Red and Green Lock Buttons on the RLV Combined HUD

Important: You can only load the applier while it’s on the ground, it will not accept appliers while worn. This is to keep from accidentally overwriting it.

Step Four: Rename/Configure/pickup.
Once you’re happy with how it’s configured, rename it to reflect what is stored inside.
While you’re renaming it, check the Description Parameters.
  • If you’d prefer the applier to stay attached after applying, change the “on” to “off”.
  • If you find you have issues with lag, you can also change the delay. Default is 0.1 second between applications, but you can increase that by changing the number in the description to something higher.
  • If you’re not sure if you need a delay, I suggest setting the auto-detach to “off” until you’re sure you’ve got the right delay.
  • Once you’re happy with how it’s configured, pick it up.

Step Five:  Wear the applier.

The outfit should apply to your body automatically and, unless you changed the description, remove itself when it’s done.
If you’re wearing the Omega RLV Relay, the relay will also store the information so 3rd party huds can strip and redress you.

Update 4+: You can now mass update many outfit configurations at once.

  1. Rez all the appliers that need changing
  2. Type /99 and the new description. Ie: /99 auto-detach;off;delay:0.5
  3. The scripts will automatically round to .1
  4. Once you’re happy with how they are configured, pick them up!
    Careful to not touch them while rezed, or they will overwrite each other!

[collapse]
Part Three: Third Party Controls


Part Three: Third Party Controls

  1. Find and wear the “RLV Clickable Control”
  2. It’ll appear in the lower left as a Heart and Omega Sign.
  3. Click the Heart to toggle hover text between info about your current state of dress, your makeup and nothing.
  4. Click the On or Off Button to turn the relay on or off. While On, the Relay will be RLV Locked to your person. While Off, It will continue to listen and remember appliers while turned off, but will not respond to any commands from items trying to dress or undress you.

<p?This lets you know what textures have been saved.
This is important if you’re using 3rd party products to strip and dress you,
It’ll also turn red when processing appliers. They can only reapply what has been saved to this little relay.

Update 4+:

The script can now be removed and placed into any collar or other accessory you’d like to use as a relay. Doing so will remove the hovertext completely, the on/off button and it will not RLV lock to you. To get a report of your current dress state you can type /1 report and it will spit it out to local.

[collapse]
Part Four: Using with RLV

Part Four: Using with RLV

Strictly speaking.. very little in this product uses RLV. Rather it’s designed to be used by other products that have RLV.. primarily collars and other things that your partner can use to force you to wear the various RLV folders you’ve set up. I will not go into detail about how to set up RLV folders, there are plenty of guides for that. (If anyone has a favorite guide, feel free to leave in the comments).  What is important however, is when you set it up that:

  • Your body and Control Relay needs to be worn first.
  • Place the The Outfit Applier into a folder along with any accessories and other bits you wish to wear.
  • Use RLV to wear that folder. The Outfit Applier will apply to your body as soon as it’s worn.
  • To strip, use the included RLV Combined HUD or any 3rd party product that has been set up to support this product.

[collapse]
Part Five: Individual Body Notes

Part Five: Individual Body Notes

We will do our best to note any special actions that need to be taken in order to work with popular bodies. If we leave something out, please, let us know so we can keep this up to date. 
(Srsly… 50 + bodys…)

  • Maitreya:  Not Usable.  Because of the prompt, appliers need to be done one at a time, disabling the function of this product. If we come up with a solution, we will update the product.
  • Sking + any part with a relay:  Make sure your relay is being worn before attaching the Outfit.
  • Fussion + other bodys that call the inner layer a “tattoo” layer: Remember with Omega, the outtermost layer is always the Top/Pant Layer, the next inner layer is the Bra/Undies layer, and then ONLY if there is three layers is the innermost layer referred to as a Tattoo Layer, regardless of what the mesh maker calls them.

[collapse]
Part Six: Developer Infomation

Part Six: Developer Information

You can communicate with the Relay via a Channel that is available on request.
(If we’ve spoken about RLV before, that Channel should be in a NC in the bundle I sent out 12/30/2015)
Update 4+: The Same commands can also be sent via Linked Messages with a Integer 788 if the Relay Script is placed in an object with your own scripts.
For the moment, the Relay Script is no-trans while I work out how to avoid the possible conflicts of someone wearing multiple products with the script included
The Entire API for you is this:
  • Redress:all
  • Redress:top
  • Redress:bra
  • Redress:upTatt
  • Redress:pants
  • Redress:undies
  • Redress:lowTatt
  • Strip:all
  • Strip:top
  • Strip:bra
  • Strip:upTatt
  • Strip:pants
  • Strip:undies
  • Strip:lowTatt
  • Redress:head
  • Redress:hTatt
  • Redress:makeup
  • Redress:hairbase
  • Redress:forehead
  • Redress:eyebrows
  • Redress:eyelid
  • Redress:cheeks
  • Redress:lips
  • Redress:chin
  • Strip:head
  • Strip:hTatt
  • Strip:makeup
  • Strip:hairbase
  • Strip:forehead
  • Strip:eyebrows
  • Strip:eyelid
  • Strip:cheeks
  • Strip:lips
  • Strip:chin

Notes:
-You will be able to redress all layers, but only able to strip those layers that have not been locked.
-“All” Commands only affect the body. To strip the face, use “head” commands.
-The user must be wearing the Control Relay.
-I really want feedback on this.

Creator Questions
Thank you, those of you that have already given me feedback and asked some questions! I’m going to try and answer them here for everyone’s benefit!
1. How do you plan on distributing the kit, in particular the RLV Control Relay/the Control Relay script? My wish would be that the script was copy&trans so that creators and users could add it to their own RLV relays. For this purpose, I’d welcome that the floating text isn’t shown by default but could be turned on via an API (message on a channel / linked message).

The Control Relay… I’m torn on.. for two issues.

  1. I just cause I HATE bugging designers to update scripts…..it’s really hit or miss weither they do it.
  2. I worry about people wearing more then one. What weird things might occur if someone is wearing say a collar… and a wardrobe manager?  And should those things need to be worn for the system to continue to work?

I think it may just come no-trans at first. and after I’ve finished adding in the makeup portion and it seems to have all the bugs worked out, then..change it to transfer…I’ll need to add a “kill” command though to make sure they can delete the script out of extra no-mod items.

That being said, they can move the script themselves….As for the floating text toggle.. that is a splendid idea and I’ll make sure that gets added if we move to transfer.

2. Additionally to the chat channel API, I’d welcome a linked message API version of the Control Relay script for integration into RLV relays (of course, llSay isn’t hard to use, but llMessageLinked seems a bit securer).

No,  but I do recommend llRegionSayTo. It’s faster and more secure.

3. In an ideal world (just thinking out loud; this would be the ultimate feature for me), the Control Relay script had an API to retrieve the currently active state (the currently applied textures) so that the state could be restored later by passing in the data. Obviously, the data would need to be encrypted so the texture UUIDs couldn’t be extracted, and the encryption would also have to be a function of the owner’s UUID so that the data couldn’t be passed on to someone else.

This…is an interesting idea…but doing this in a properly secure manner might be beyond my current abilities and knowledge. Maybe sometime in the future.

[collapse]
Part Seven: Early Release and Planned Updates

Part Seven: Early Release and Planned Updates

Normally I dislike releasing things as “beta”. But in this instance I think it’s warranted. The basic needed functionality is there for 3rd party designers who have been wanting me to get this done. So while there is work to be done, I really don’t want to make you folks wait and wonder when I’m going to have something ready for you to use.

The Plan:   I like plans… they keep my rear in gear…so here is the plan…
  • Version 2.2:
    • Release done (1/14/2016)
    • Updates will follow every two weeks.
  • Version 3.0 : (2/3/2016) 
    • The addition of Makeup Appliers
    • The ability to adjust the applicator timing.
    • A slimmer stripping HUD for customers
    • A Toggle for “auto un-equip” for those who would rather keep the applier on screen
  • Version 4.0: (Current Version 3/4/2016)
    • Ability to Mass update the Delay/Auto detach settings
    • Use of Linked Messages.
    • Ability to toggle hover text on Relay.
    • Ability to turn relays on and off.
    • Relay Now Locks itself to you when turned on
    • Hover Text and Texture changes are now turned off when relay script is inserted into other attachements.
    • /1 report will now spit out the information shown in the hovertext to local
  • Version 5.0: (eta 3/18/2016)
    • The ability for multiple relays to co-exist.
    • A Copy/Trans Version of the script for designers to include in products.
      (may need applying for? -undecided-)
    • Speed Optimization (Switch from llSay to llRegionSay)
    • Put Affiliate Vendor in Dev Kit

[collapse]