ConfocalVR and ExMicroVR FAQ

Image Size:
The 3D image size limit depends on various factors, including available RAM/VRAM, the size and number of image channels, and how memory is allocated. GPU memory size is especially critical for 3D volumetric rendering, as larger datasets require more memory to store voxel data, textures, and rendering buffers. When the dataset exceeds available GPU memory, performance can degrade significantly or fail to load altogether. Additionally, modern GPUs dynamically allocate memory for rendering, so background processes or other GPU-using applications can reduce available memory. As a result, on some days, you may be able to load larger files, while on other days, system resources may be more constrained, limiting the channels or datasets you can load. We recommend using a tool like ImageJ to downsample your images for an overview in VR and then crop regions of interest for detailed study.

Collaboration:
Most collaboration issues stem from internet access problems. Ensure your computer is connected to an open or public internet connection. Restricted connections can prevent ConfocalVR from accessing the Collaboration Server. To check this, click the “Begin Collaboration” button in ConfocalVR. If your computer successfully connects to the server, your hand controllers will change, and pointer sticks will appear in front of them. Both computers involved in the collaboration must be able to connect. Additionally, ensure both computers are using the same Room Name (e.g., “DEMO”). If successful, you should see your own hands as well as the head and hands of your collaborators. For audio issues, confirm that your Windows audio device is set to your VR hardware.

Image Share:
While it’s possible for each collaborator to have a local copy of the image directory, it’s recommended to use a shared directory. This prevents discrepancies in slider settings or image data, which could lead to the two copies getting out of sync. If changes are made separately on each machine, it can break the collaboration session due to different image and configuration data being loaded. The typical workflow involves one collaborator creating and adjusting the image directory, saving any settings, and then sharing the directory with the second collaborator. After both users download the same folder, they can begin the collaboration session by opening their respective local copies of the image directory and proceeding with the interactive viewing and discussion.