This section lists some common problems when using the CAVE, and some steps to hopefully solve them.
In general, please don't restart the CAVE computers. It will mostly likely cause more problems than it will solve. 1)
Commands have changed in the year 2011. Here are some useful one:
cave-psvrui: Show all Vrui processes running on all nodes.
cave-killvrui: Kill all Vrui processes running on all nodes. Use this if you are having a hard time starting Vrui applications, and
cave-psvruiis showing another (probably dead) Vrui application still running.
cave-framelock: This will reset the framelock between all the render nodes. Try this if stereo doesn't seem to be working.
See caves status to make sure that there isn't a known problem.
Right Wall Shows Unexpected Colors: see caves status
Application run via icons in the Demo directory should output any error messages on a console that pops up after they fail. Applications run from the command line should output messages to the command line window from which they were run.
Here are some error messages to look for, and how to respond to them.
MulticastPipeMultiplexer: Unable to bind socket to port number <some number> while initializing cluster communication
Cause: Another application is already running, or remnants from another application are still blocking some of the CAVE cluster nodes.
Ignoring input device adapter CAVEAdapter due to exception TCPSocket: Unable to connect to host caveman on port 8555
Cause: The VR device daemon, which receives tracking data from the tracking system, is not running.
This really shouldn't happen anymore, so if you find this you should e-mail KeckCAVES help via email@example.com. Yet here you are, so give the following a try:
sudo service VRDeviceDaemon stop
cave-killVRdevicedaemonto end any lingering process.
sudo service VRDeviceDaemon start
terminate called after throwing an instance of 'Comm::TCPSocket::PipeError' what(): TCPSocket: Connection terminated by peer during read
Cause: The InterSense tracking system is no longer communicating with the head node.
Solution: The InterSense tracking system needs to be restarted. Unfortunately, this requires stepping behind the CAVE, and it would be preferable if people didn't make a habit of this.
You're doing what now? You may be kinda on your own here, pal.
However, if you get an error with the InputDeviceManager, it's probably a configuration file problem. Please see Configuration Files in the CAVES
Here are some possible causes and solutions:
Your glasses batteries may be low on power.
Please try another pair of glasses. If that works, let firstname.lastname@example.org know and set the glasses aside.
Frame lock may have been lost between the render nodes. This can happen if the render nodes have been restarted, e.g. due to a power outage.
To try fixing this:
Sometimes the monitor graphics get jumbled and the log-off menu doesn't show up. To log off type this command in a terminal:
killall -9 gnome-session
This will log you off and show the main login screen.
On any other error messages that do not come from the application itself (missing input data, wrong data formats, etc.), please email email@example.com.
Since most CAVE applications are prototypes and still under development, any of them might crash at any given time. Due to the CAVE computer system's cluster nature, the operating system can not always automatically clean up after a misbehaving application. Crashes come in three flavors:
In all cases, the first thing to do is to remove all remnants of the misbehaving application. Each application runs as a separate process on the console computer and the render nodes, and if only some of those processes crash, the others are stuck, but still running. The following steps will remove all “hung” application processes:
cave-psvrui. This shows all VR application processes, running on the console computer (caveman) and the render nodes (render-1 to render-5).
cave-killvrui. This will kill all VR application processes on all CAVE computers.
DeviceTest localhost:8555command first, and then the other steps if it fails.
If the image on the screen appears “warped” or does not change when a user moves her/his head, the head tracker might not be able to communicate with the tracking rails (above the CAVE, with the blue “blinkenlights”). The head tracker has two tiny microphones on the top front corners. The tracker will not work properly if the microphones are obstructed, for example by a visor. (Although not recommended as a fashion statement, it is advisable to wear baseball caps backwards, or not at all.)
If the image on the screen appears “double” and there is no depth perception, the stereo glasses might not be able to communicate with the projectors. The stereo glasses are controlled via an infrared signal; the infrared receiver is located between the eye glasses. The line of sight between the receiver and the projectors (behind the screens) must not be obstructed (headgear advisories apply as above). Sometimes the glasses do not turn on properly; in that case, taking them off, folding, and unfolding them again usually fixes the problem.
In case you don't trust running the automatic
cave-framelock, or it doesn't seem to be working for you:
cave-framelock --guifrom the command line.
For experts only!
sudo service VRDeviceDaemon restartin terminal.
cave-psvruilists (no) processes on all five nodes.
cave-framelockor manually as described above.