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.

Task for WebSocket communication ?


We have Perfomance issues.
Currently setting up a communication between a Hololens and a server, we are seeking to spread it through 4 different WebSockets

Up until now, We've been using 2 tasks for every WebSocket, one to send messages and an other which reads the buffer in a loop. It works so far, nevertheless it leads to lagging issues including a mediocre frame rate.

What could you suggest would be the best way to fragment the communication between a Hololens and a server?

Thank you!

Sign In or Register to comment.