FAQ

SightLab VR Pro FAQ

      Sightlab VR Pro works with the following headsets:

For eye tracking:

For non-eye tracked headsets you can use head position with these headsets: 

For additional hardware supported, see the Vizard Supported Devices page


The first thing to try that can get past a lot of error is to go into the "sightlab_configs" folder and delete the "recent_config" file. If this doesn't work can run the main SightLab file in the Vizard python editor and refer to the error message.

SightLab VR Pro requires WorldViz Vizard software for its full functionality as SightLab VR Pro is an add-on software to our Vizard software engine. You can although still us a software like Shadowplay to stream via the cloud to a device running in stand alone mode. 


You can import 3D models in the usual formats, so .glTF, .obj and .fbx and other common formats will work. There may be mixed results depending on how the textures are packed (the most consistent format would be .glTF). For more information see this page

 

Currently, SightLab only runs on the Vizard platform, but you can import assets from Unity by using their FBX exporter. Here's an article on doing that. 

 

Yes, the data files are in .csv and .txt

 

Number of fixations, time to first fixation, average fixation time, total fixation time, fixation timeline, gaze intersect position, individual eye rotation, saccade amplitude and velocity, fixation spheres to show amount of fixation time, time stamps, head position, pupil diameter, as well as the ability to add custom flags such as interactions. Additional data is available with custom code and varies per eye tracked headset (such as “eye openness” for the Vive Pro Eye). To add more data points see the data logger example. 

The multi-user version has all the same functionality as the single user, but with the ability to have multiple participants in a session interacting together. 

See this document on how the process of updating your SRAnipal driver works. 

See the Example Script - Large List of Items or the code attributes page to see ways you can add a large list of objects if the GUI doesn't allow to select all of them. 

See this page on all the places in which to get assets

 This usually happens if you have your participant ID either left blank or the same name as an earlier one, but that  earlier one is still open in a spreadsheet editor program. 

    This is most likely that you put an underscore the participant ID name. You can remove that underscore to see the file,  but underscores will cause this issue.  

     You can use various optimization methods (see this page). This is a simple couple of lines that could be tried:
    env = sightlab.objects[0] #If using the GUI, add this after the experiment starts in the sightLabExperiment function


env.optimize(viz.OPT_REMOVE_REDUNDANT_NODES)

env.hint(viz.VBO_HINT)
Additionally, you can open the model in Inspector and choose the textures tab on the bottom right, then shift click to select all textures, right click and compress them. 

     Search for the python library version using the Package Manager:     https://docs.worldviz.com/vizard/latest/#Package_Manager.htm 

You may need to play the sound directly in SightLab/Vizard using audio = viz.addAudio('someFile.wav') 

#Add this code to offset the texture in the z axis

z_offset_value = -1.1  # Adjust as needed

youTexture.zoffset(z_offset_value)

Add this code to the top of your script to find the path

import sys

sys.path.append(r'C:\Program Files\WorldViz\Vizard7\bin\lib\site-packages')

or for Vizard 8

import sys

sys.path.append(r'C:\Program Files\WorldViz\Vizard8\bin\lib\site-packages')


For answers to all technical Vizard questions, please go to the Vizard 7 Documentation FAQ of the additional Vizard FAQ page here