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.

Sharing CustomMessages Clarification

Hi I was looking at the CustomMessages Script in the HololensTookit > Sharing > Tests example and was wondering what this commented code meant:

/// <summary>
/// Message enum containing our information bytes to share.
/// The first message type has to start with UserMessageIDStart
/// so as not to conflict with HoloToolkit internal messages.
/// </summary>
public enum TestMessageID : byte
    HeadTransform = MessageID.UserMessageIDStart,

Does this mean that the first message sent has to be a byte? Do all messages have to be sent in bytes?



  • Jarrod1937Jarrod1937 ✭✭✭

    My guess is that the enums are defined by byte only values.

  • edited May 2016

    The messages are definitely sent as bytes. I was messing around with it to show the raycast of the remote players with a line renderer, and hand positions of remote player to put hand models.

    At the bottom of the custommessages.cs are 2 helper functions for appending vector3's and quaternions onto your message as bytes. And functions for reading out the bytes from a received message into Vector3's and quaternions that you call from the remoteheadmanager script that you then apply to your various objects' transforms.

Sign In or Register to comment.