Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.

If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.

Problems in Spatial Mapping. "SurfaceObserver" and "onDataReady" delegate.


In the title, I've written down the main problem which I have in SpatialMappingscript.

Can someone explain fo what we are using that onDataReady delegate? What is existing there?

It seems to me the answer is actually here, in the Update function:

if (surfaceWorkOutstanding == false && surfaceDataQueue.Count > 0)
SurfaceData smsd = surfaceDataQueue.Dequeue();
surfaceWorkOutstanding = Observer.RequestMeshAsync(smsd, Observer_OnDataReady);

But indeed that is not clear for me also. What the root cause why we have created smsd variable and used that in RequestMeshAsync() function.

Here's the link to see that script:


I wish, you helped me,
Thank you in advance!

Sign In or Register to comment.