"SceneUnderstanding" prefab encapsulates all necessary components for Scene Understanding to work, most of this prefab is copied from SceneUnderstanding Unity example provided by Microsoft.

https://github.com/sceneunderstanding-microsoft/unitysample

Prefab Structure

• SceneUnderstandingManager: Main component of SceneUnderstanding prefab, scene object is detected by "Scene Understanding Data Provider" script and rendered by "Scene Understanding Display Manager" script
• InputManager: A script that allows user to navigate in the game and adjust some scene understanding settings on the run. This might interfere with your existing controls. Disabling this script wouldn't affect scene understanding's functionality, feel free to disable this script if controls are interfered.
• Root: Detected scene object would be attached to this game object.
• HelpText: A UI text box with instructions on what you can do with InputManager enabled.
• StatusText: A text box that displays current status.
• CRASHSceneUnderstandingUtil: A util that contains all scene understanding related functions written for CRASH project. New scene understanding related functions for CRASH project should be added in this script.

SceneUnderstandingManager

When "Run On Device" is checked, this prefab would access Hololens 2's related sensor and generate scene understanding results using those sensors. If sensor's unavailable, an error message would be logged in Unity console.

When "Run On Device" is unchecked, this prefab would load saved scene understanding result located at "SU Serialized Scene Path". "SU_Ktichen" provided here is a saved scene understanding result file offered by Microsoft.

We normally uncheck "Run On Device" and use a saved scene understanding result whenever we're testing our game in Unity.

Detected Scene Objects

All detected scene objects would be attached as a children of "Root" object in "SceneUnderstanding "