The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
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.
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, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Broken mesh properties after delivered to a custom server
I built a Python server which mimics RemoteMeshTarget.cs. RemoteMeshTarget is supposed to run on a PC and runs on Unity which listens to your HoloLens and receive mesh properties(vertices and triangle indices). I also wrote Python mesh byte deserializer which mimics SimpleMeshSerializer. SimpleMeshSerializer converts the mesh properties into bytes.
According to my debugging, the communication works fine. I tested by printing out data being delivered on both HoloLens debugger and the server terminal and they print out the same.
However, the data doesn't look right. Here's a data collected from my room.
It looks like every mesh is pointing to the camera.
The mesh collected from HoloLens server looks like this.
I wonder why.
What I suspect: wrong coordinate system?
In RemoteMappingManager.cs, it transforms vertices into world coordinates. Do I need to transform it back to local on the server? I don't think I should.
for(int vertIndex=0; vertIndex < verts.Count; vertIndex++)
{
verts[vertIndex] = filter.transform.TransformPoint(verts[vertIndex]);
}
Any help will be appreciated.