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.

Import anchor fails [Unity3D]

sebseb
edited September 2017 in Questions And Answers

I've setup my own sharing solution and now I'm at the last step importing the anchor after transferring it. However I get the message in console:

ImportAsync_Internal can only be called from the main thread.
Constructors and field initializers will be executed from the loading thread when loading a scene.
Don't use this function in the constructor or field initializers, instead move initialization code to the Awake or Start function.

I've tried calling it from Unity main thread which is basically any non-threaded MonoBehaviour but I get the same message. So how do I do this correctly?

Best Answer

  • sebseb
    Accepted Answer

    Apparently I was in a another thread. The solution was to implement a Producer-Consumer pattern Queue on main thread (e.g. gets consumed in Update()).

Answers

  • Just a hunch but could it be that ImportAsync_Internal is getting called in a different SynchronizationContext than the UI's context?

  • sebseb
    Accepted Answer

    Apparently I was in a another thread. The solution was to implement a Producer-Consumer pattern Queue on main thread (e.g. gets consumed in Update()).

Sign In or Register to comment.