Frequently Asked Questions
To submit a new question, please use the discussion forum.
The list of data options that show up in the GUI are based on the *.json and *.csv files that are inside Assets/StreamingAssets/DxRData/ directory. To specify your custom url enter the url manually in the specs, e.g., via a text/code editor.
The list of mark options that show up in the GUI are based on the folders that are inside Assets/DxR/Resources/Marks directory. Each folder contains a game object prefab which is used as a prefab for visual marks. During deployment, DXR instead checks the list of marks in Assets/DxR/Resources/Marks/marks.json - this allows customizing the list of usable marks at deployment.
If the GUI buttons are not working during debugging, try reapplying the default mixed reality settings again: Mixed Reality Toolkit -> Configure -> Apply Mixed Reality Scene Settings. If you have this issue in a deployed version, try the following: 1) In InputManager object, set the UI Raycast Camera parameter to MixedRealityCamera, 2) Click DxRGUI component under DXRVis prefab and under Canvas in Inspector window, uncheck Receive Events, 3) set the Camera to MixedRealityCamera, 4) Recheck Receive Events option.
You can change the name of the DXRVis game object instance in your scene as you like. However, do not rename any of the game objects within the DXRVis hierarchy unless you know what you are doing because in most cases, scripts use the object names to search for them at runtime.
When specifying interactions, make sure there is only one interaction for each data field. Only the first one is created.
During prototyping, make sure your data file is not open in another application to avoid this error.