G General

Light Stage DEMO Version 1.0

Light Stage DEMO
Details
Features
Contents
Reviews

• This is a demo version. It's fully functional but will set the EEP environment only on the owner of the object. •

Thank you for your interest in Light Stage.

This tool lets you set an EEP windlight using an Experience. This way - once the experience has been accepted - it works seamlessly, setting and resetting the windlight by proximity. Windlights set by experiences override land windlights, but will not override the ones set by the user manually or the ones set through RLV.

An important note: this tools uses Experiences. For an experience to be used it must be enabled at the land level. If you don't have enough access to add an Experience to the land, this script will not work!

• Adding the 'Dreams' experience on your land •

One way to use the script right away is to add the experience called Dreams by Destiny (voluptiara Resident) to your land. In order to do so click on the land profile, got to the Experiences tab, click Add, search 'Dreams', make sure you are looking at the right experience and add it. If you then rezz the device it should work right away with the default settings.

• Using your own experience •

Something less common is to be able to use your own experience, but with this script you can. If you are advanced and you already have your experience (or you want to create one for your SIM), you can use that one instead of the 'Dreams' experience. This way if your visitors have already accepted the experience they will not be prompted to accept again.

To use your experience rezz Light Stage, edit it and go in the Contents pane. Edit the script named 'Light Stage Experience'. In the bottom of the window there will be a checkbox to check and a dropdown where you will select your own experience. Once your experience (remember you have to be an admin of the experience) is selected for the script save it. Still in the object edit the settings notecard and make sure to set to 1 the useCustomExperience parameter. It will read useCustomExperience::1 . Once done save. The script should use the default EEP right away.

• Adding new EEPs •

In order to use an EEP windlight, it must be added to the object. Go in the menu World > Environments > My environments and search the environment you want to use. Then drag it to the contents of the object. If you have environments created by others, you can use them also, provided they are copy.

• Editing the settings •

In the object you will find a notecard called 'settings'. It will let you customize the behaviour of the script. The format is parameter::value, so you will be required to edit the bit at the right of '::'. An explanation of the values is below.

delay: this is the number of seconds between proximity scans. If scans are too fast it might increase the lag. The default is 5 (that is it checks for new avatars every 5 seconds). You might want to edit it only if you run into issues.

environmentToSet: it's the name of the environment in the object's contents. It must be written exactly as in the EEP file.

cooldown: it's the number of seconds to wait after an avatar is not detected before resetting the EEP for that avatar. Likely you might want to leave it as is.

range: how many meters should the proximity sensor check? It will apply the EEP to AVs within that distance. This number you will likely want to edit.

transitionTime: how long does the transition to the EEP last from the current windlight. In seconds.

useCustomExperience: if you compiled the script with your custom experience then you will want to set this to 1. Otherwise leave to 0.

restoreEnvironment: if this is 1 then, when an avatar goes out of the range the script will remove the EEP that has been set, if it's 0 then it won't. Probably you will leave it at 1, but there are some conditions, like multiple zones close where you might want to set it to 0.

Finally if you click the object it will reapply the environment to all the avatars in range.