Jump to:
Can I change the size of a zone trigger?
The trigger is not working even if I’m within the zone
Triggering events on enter/leave
Preventing access to a zone trigger
Zone triggers are special areas that can be added to a 3D environment to execute certain commands when a user enters or exits them, including “audio zones”. Zone triggers are available from version 2.14 onward.
FAQs
Can I change the size of a zone trigger?
Yes. Zone triggers are like other objects, and can be scaled either uniformly or only on one dimension (width, height, depth). For how to do so, see “Modifying items > Moving, rotating, and scaling objects” in the editing guide.
The trigger is not working even if I’m within the zone
For a trigger to fire, the avatar needs to be completely enveloped in it. Did you just add the zone, and it’s flush with the floor? If so, you might need to position it a bit lower – scaling up the zone vertically will also solve the issue. Since normally the floor acts as a barrier, Advanced Transform Controls are required, see “Modifying items > Moving, rotating, and scaling objects” in the editing guide.
“On Zone Enter” is not firing
When teleporting the user moves very fast but not instantaneously, so actions such as “teleportPlayerToSpotTag” might not work. In these cases, try adding a small delay to your action by using "delay":0.5 . This will start the action in the “On Zone Enter” field half a second after the user enters the zone, which is enough time for the teleport to complete.
How can I nest audio zones?
This feature is not supported, audio zones should not be nested within one another.
A nested setup is useful for booths that are intended to have a booth-wide call as well as private calls within smaller areas of the booth, but an equivalent solution can be reached by using the same Zone Conference ID in multiple audio zones (see image below: zones 4 and 5 will have the same conference call)
Creating a zone trigger
Zone triggers can be added from the edit menu
A yellow box will be created around your avatar: this is the area covered by the zone trigger. The box will not be visible outside of edit mode.
Triggering events on enter/leave
To trigger certain Actions when the user enters or leaves the area covered by the zone, two fields are available within the object’s options, On Zone Enter and On Zone Leave. To access these options, enter Edit mode, then hover over the object; a small panel will appear with a cog on it, among other icons; click on the cog.
Any of the actions within the Actions guide can be used. The required format is the one called onclick one (see “Triggering Actions from Scenario onclick”), which looks like this:
{"action":"completeTask", "shortcode":"my-task-name"} |
It is not required to fill both fields. Either (or both) can be empty.
Audio zones
“Audio zones” are trigger zones separated from the general call available within the 3D environment. This means that it’s possible, for example, to have an exhibitor’s booth contain its own voice call, or to have a private area with a voice call that is only accessible with a certain passcode, etc.
To set up an audio zone, a few fields can be useful:
Zone Conference ID: any string of lowercase characters. Special characters and numbers are not allowed. This is the identifier used when separating the audio zone from the other calls, so two audio zones with the same Conference ID will share the call.
For information about Zone Access Code, please refer to the following section.
Mute microphone on enter: automatically mute microphone of participant entering the audio zone.
Note that audio zones cannot be nested within one another. For an equivalent solution see “How can I nest audio zones?” |
Feedback for Enter/Leave (Confirmation) (3.0+)
This feature is only available in 3.0+
When entering or leaving an audio zone, the user is shown a confirmation popup by default. This can be changed using the “Enter/Leave feedback type” field. Options are:
- Confirmation popup (every time): User will always be presented with the confirmation popup.
- Confirmation popup (once): The user will see the popup only once as a tutorial.
- Notification: The user will see a non-intrusive notification on the top right corner.
- Nothing: No feedback.
Preventing access to a zone trigger
Zone Access Code is an option in the zone trigger settings: a “password” for the zone, which can be any text. When a user tries to enter a zone trigger protected by an Access Code they will be asked to provide it – they will only be able to enter the audio zone and trigger the enter/leave effects if they provide the correct code.
A user that enters a valid code will not be asked to enter it a second time (unless they reload the page).
Zone-based visibility
It is possible to make one or more objects visible only when a user is within a trigger zone. This can be useful for a variety of reasons, from performance in really big exhibition spaces (by only showing certain items when the user is within the same booth, for example), to sectioning breakout rooms within a bigger space.
This requires using the same tag on both the trigger zone and the objects.
Trigger zone setup
Write a keyword (only alphanumeric characters; spaces are not allowed) in the “Zone Visibility Tag” field.
Object setup
In the options of each of the objects that should be visible only when a user is within the trigger zone, add the same tag (myTag, in our example). If a tag is already present, include a comma and then your own tag.
Zone Avatar Instancing
Instancing is a feature that reduces the number of visible avatars to improve browser performance and avoid avatar overcrowding. By default when a user steps into a zone they will remain in the instance assigned to them when they entered the space. This may mean that when they step into a zone they do not see everyone who is in the zone, that is if people are entering the zone from different space instances.
You can override this and force people to see each other’s avatars when they step into a zone by assigning an Instance ID to the zone.
Be sure to choose a zone ID that is large enough to avoid the automatically created instance ID’s for the space (eg. 0,1,2,3,4 etc) . We recommend starting at 300, 320, 340, 360 etc for each zone.
The instance threshold of the space is respected by zone instances. So if the space instance threshold is 40, and the zone instance ID is set to 320 then the zone will also split users once the zone reaches 40 avatars. The next 40 entering the same zone will be in instance 321.