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.
Our Unity App suddenly gone to the Background on RS4!
Hi, Holo developers,
Now, we have a BIG problem, updating to RS4 (Windows 10 April 2018 Update) !
Our application started from the Device Portal API had suddenly gone to the background on occasion. Once gone in the background and called again from the API, then the app came back foreground (the game was going well). So, we thought that our app was not crashed.
Our app was made by Unity 2017.4.5f1 (64-bit) with HoloToolkit-Unity-2017.2.1.4.
We tried two Task Manager's API ver. 10.0.17134.80 and 10.0.1734.111, but there were not the differences. Of course, no blooming nor the voice control.
So, does anyone have an idea? Please give us a clue!