Hello everyone.

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.
Options

Locatable Camera sample code bug?

I was using the UnProjectVector sample code from https://developer.microsoft.com/en-us/windows/holographic/locatable_camera and noticed a potential bug.

It appears that the camera position information is lost during matrix multiplication for the WorldSpaceRayPoint2 calculation.

** float3 WorldSpaceRayPoint2 = mul( CameraToWorld, CameraSpacePos ); // ray point in world space**
should be
float3 WorldSpaceRayPoint2 = mul( CameraToWorld, float4(CameraSpacePos, 1) ); // ray point in world space

This discussion has been closed.