Hello everyone.

We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.

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.

The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.

On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.

So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. 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.