Without Unity
You might encounter a situation where you want to run and test a GEM Unity Experience without wanting to install Unity. There are multiple methods to do so depending on the received build files.
Windows Client¶
Without GEM¶
You need the WindowsServer and WindowsClient build targets.
- In the WindowsServer folder, launch "{appname}_NoGEM.bat". This starts the windows-server with GEM Simulation.
- Input the amount of clients that you will be launching.
- In the WindowsClient folder, launch "{appname}_NoGEM.bat" for as many times as the amount of clients you have selected when launching the Server. This starts the windows-client with GEM Simulation.
You should be able to observe the client connecting to the server without GEM and the Experience starting.
With GEM¶
You need the WindowsServer and WindowsClient build targets and the gem_manifest.yaml
- Launch the GEM Siterunner
- install the show definition and site definition if not yet installed.
- install the gem_manifest.yaml
- Launch the GEM Showrunner for the show.
- In the WindowsClient folder, launch "{appname}_WithGEM.bat".
- Input an arbitrary device name.
- Input your operations area (by default with index 2).
- The client should launch and appear in "Unassigned" state.
- Repeat for as many clients you wish to launch.
- Open the GEM Dashboard and create a user for each device.
- Assign the Unassigned devices to the created users.
The windows clients should now register their height and proceed to the experience. You can now test the Experience in windows with GEM.
Android Client¶
Without GEM¶
You need the AndroidClient and WindowsServer or LinuxServer build targets.
- in the WindowsServer folder, launch "{appname}_NoGEM.bat".
- Input the amount of android clients you wish to launch.
- Follow instructions 7. to 17. in In Standalone VR (Android)/Without GEM
The android clients should now connect and proceed with the Experience.
With GEM¶
You need the AndroidClient and WindowsServer or LinuxServer build targets and the gem_manifest.yaml
Install and run the Experience like in a production environment. Refer to GEM Documentation for instructions.