If you are planning on expanding ExPresS XR, using external materials or only using some parts of the project, you might want to take a look at the following information.

Note: Cursive layers/tags/... are built in.

0. Default
1. TransparentFx
2. Ignore Raycast
3. Player: Layer for the Player. All components of the XR Rig (except the HUD) should be set to this layer.
4. Water
5. UI
6. UI Always On Top: Will be rendered by the HUD Camera but not the Main Camera. The HUD of the XR Rig should be set to this layer.
7. Ignore Camera: Will not be rendered by the Camera.
8. Ignore Mirror Camera: Will not be rendered by the MirrorCamera of ExPresS XR's Mirrors, thus being invisible in the reflection.
9. AreasOfInterest: Layer for Areas of Interest. Will not be rendered by any camera.
10. AreasOfInterestBouncer: Layer for Areas of Interest Bouncers. Will be rendered by the camera.
11. Bow: Layer for the bow of BaAM VR.
12. ArrowShot: Layer for the arrows of BaAM VR so that they do not collide with the player or the bow.

Be aware: Adding new Layers might result in them not being visible in VR as they are not added to the MainCameras Culling Layer. This must be done manually!

Only some of the built-in tags are required. The "Player"-tag should be set to all objects of the rig, to prevent self collisions being detected by with the HeadCollider. One exception is the MainCamera-GameObject which needs the 'MainCamera'-tag.

For the example scenes and some prefabs two custom tags were created:

• Test: Used in the Interaction Area to show the functionality of a TagCheckSocket.
• PictureData: Used by the TagCheckSocket of the PictureScroller. This is not required but recommended to easily filter which objects are accepted and which are not.

Make sure to use the InteractionLayerSettings from "Assets/Settings/Resources/InteractionLayerSettings.asset" or adjust your own to contain the following values.

0. Default  

    ...

31. Teleport: As per recommendation by XRI. It is used for teleporting.

The Input Action at Assets/Settings/Input Mappings/ExPresS XR Default Input Actions.inputactions is used and is based on the one from the XR ITK with the following additions:

• XRI Head/Head Gaze Prevent Interaction of type Value(Vector3) with a binding to deviceAngularVelocity [XR HMD] and a Press-Interaction with Trigger Behavior Press Only and Press Point set to 0.3.
• XRI Head/Head Gaze Perform Interaction of Type Button with Bindings to the Forward-Button on the Mouse and the Enter-Key on the Keyboard. The first one is generated during runtime to perform the Head Gaze Select Action. The second one is for debugging.
• XRI Head/Test of Type Button with a Binding to the T-Key of the Keyboard. It is not used for anything but can be used for debugging.
• XRI LeftHand Interaction/Hand Menu of Type Button with a Binding to the Left Controllers Primary and Secondary-Button. Used for opening and closing the HandMenu of the rig at the left hand.
• XRI RightHand Interaction/Hand Menu of Type Button with a Binding to the Right Controllers Primary and Secondary-Button. Used for opening and closing the HandMenu of the rig at the right hand.

Make sure to delete the Default Input Action that gets imported via the XR Interaction Toolkit-Package!