Immerse Scenes (Legacy Feature)
Immerse Scenes are Unity applications which have integrated the Immerse SDK, been built, compressed and uploaded to the Immerse Platform. They are Zipped files containing a Windows executable, WebGL content and/or Android APK, along with a Manifest (metadata.json) file.
Once uploaded to the Immerse Platform, Immerse Scenes can be managed, shared and added to Immerse Sessions, allowing them to be accessed by VR and browser participants. Uploading an APK allows a 6-digit PIN to be generated which is then input into a standalone VR headset to join a Session.
All scenes available are listed in the Scenes tab. This includes My Scenes, which are scenes that have been uploaded personally by you and Shared Scenes which have been uploaded by other users in your organisation and shared.
Uploading a Scene
Log into the Immerse Platform and go to the Scenes tab at vr.immerse.io/scenes .
Click the [Upload scene] button. The Upload Scene window will appear.
Enter a scene name. The Immerse Platform supports PCVR, Web (browser) and Android scenes.
Upload file(s) (VR files must be .zip format, Web files can be .zip or .tar.gz.)
Note: The file size limit is 500 MB for Web and 1 GB for VR files.
Upload Thumbnail (recommended). Choose an image to represent the scene in the scene list. (.png or .jpg format supported).
Share scene (optional). If checked, any person in your organisation will be able to add this scene to a space.
Add custom messages (optional - see below)
- [Save] Scene
(1) displayed if the Scene has been successfully uploaded and processed on the Immerse Platform
(2) displays the number of Messages
(3) Shows supported devices
(4) Click to copy a URL, for downloading the APK
(5) Click to generate a URL for downloading the APK, to be used with services such as Oculus for Business self-hosted applications
Editing a Scene
After an Immerse Scene has been created, its VR and WebGL files can be updated by clicking on the scene's thumbnail and uploading new versions.
Custom Messages (advanced)
Custom Messages provide a way for objects, data and state to be synchronised across multiple users and persisted in an Immerse Session.
Before deploying an application to the Immerse Platform, contact its developer to determine whether Custom Messages have been used in its creation.
Custom Messages are defined directly in the Immerse SDK and are also configured when an Immerse Scene is uploaded to the Immerse Platform.
After uploading a zipped PCVR, WebGL or Android file, which has been built and compressed with the Immerse SDK, along with a "metadata.json" / Manifest file) Custom Messages will be automatically configured for the corresponding Immerse Scene:
How to manually configure Custom Messages
Take extra care when configuring Custom Messages
Any errors or typos could make the experience unstable, or even crash
Custom Messages are automatically configured when PCVR, WebGL or an Android file is uploaded, however it is possible to manually configure them too.
The example below defines an example 'XR Socket Service' message:
|Name||Type||Destination||Profile||Broadcast back to self?||Persist in session?|
|XR Socket Service||2900||Scene only||Participant||No||Yes|
Click Configure to edit the Scene's Custom Messages, as shown here:
Once in the Scene Message Configuration window, Messages can be added, deleted and modified. When all messages have been added correctly, hit [BACK], then [SAVE]
Updated 9 months ago