You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2024. It is now read-only.
If I follow Chapter 1: Scanning and Chapter 2: Visualization the project doesn't show anything in my HoloLens. The problem seems that StartObserver doesn't get called in the SpatialMappingManager. So no data is acquired and nothing will be displayed.
In Chapter 3: Processing there will be visual output once the PlaySpaceManager has been updated, because it will enter scanning mode if not enough surfaces have been found.
The text was updated successfully, but these errors were encountered:
Specifically I added the autoStartObserver property and Start method back into the SpatialMappingManager address this issue according to the implementation in the Toolkit.
[Tooltip("Determines if the surface observer should be automatically started.")]publicboolautoStartObserver= true;
// Use for initialization.privatevoidStart(){if(autoStartObserver){StartObserver();}}
Adds the Start() method back to SpatialMappingManager, which was
accidentally removed during the last update. This method is repsonsible
for starting the SurfaceObserver.
Also fixed: the RecalculateNormals was no longer present in
SpatialMappingObserver.cs. This call is required when using shaders
(like 'BlueLinesOnWalls') that rely on surface mesh normals being
correct.
If I follow Chapter 1: Scanning and Chapter 2: Visualization the project doesn't show anything in my HoloLens. The problem seems that
StartObserver
doesn't get called in theSpatialMappingManager
. So no data is acquired and nothing will be displayed.In Chapter 3: Processing there will be visual output once the
PlaySpaceManager
has been updated, because it will enter scanning mode if not enough surfaces have been found.The text was updated successfully, but these errors were encountered: