-
Notifications
You must be signed in to change notification settings - Fork 5
Deployment
The deployment scripts can be used manually by running them with the correct parameters (help shows up if you don't give parameters) or by simply using our GUI that does the work for you. Just enter your CAVE configuration and project and hit deploy/start (see paragraph "ConfigTool").
- Visual Basic GUI
- Batch Scripts
- Perl Scripts
Since the possibilities in our CAVE (made by IMSYS) are very limited we had to rely on a relatively complicated method for the deployment to the CAVE-Clients:
- Deploy:
- Enter parameters
- Add command to IMSYS' JVM config file (on client)
- Restart JVM (on client)
- Copy files to destination folder (xcopy)
- Start
- give parameter (project name) to batch script
- batch script uses perl sockets to speak to JVM on clients which execute the command specified in Deploy Step 2.
Because of these limitations porting the deployment scripts to a different CAVE setup likely requires modification.
If you have unrestricted possibilities in your CAVE however I recommend the following:
- Forget about the JVM/Perl/socket mess
- Copy the files with xcopy to the client PCs
- Use PsExec to execute the applications on all client PCs
General
Our Team
Quick start
The CAVE
Synchronization
Concept
Input
Time
Physics
Collision & Trigger
Particles
GUI
Animations
ConfigTool
Import Config-File
Add/remove Computers
Deploy/Update/Start project
Configuration
Deployment process
The Configuration-File
Projection
Interpupillary distance
Jenga VR in Unity
Sounds & Music
Game-Logic
Main Menu
Radial Menu
Flystick
Flystick Simulator
Info-Screen
Driving Simulation
Steering Wheel Integration
Source Collection
Stereoscopy
Unity Cluster Package
Networking