Assert error every frame demanding "Near plane must be zero for raycast distances to be correct"

[provencher]

XRTK - Mixed Reality Toolkit Bug Report

Describe the bug

Focus provider expects near plane to be zero on UIRaycastCamera, when that makes no sense.
It pops an assert every frame because of this.

To Reproduce

Open up and configure a blank scene with Lumin setup. Hit play

Debug.Assert(UIRaycastCamera.nearClipPlane.Equals(0f), "Near plane must be zero for raycast distances to be correct"); will pop from method private void RaycastGraphics(IMixedRealityPointer pointer, PointerEventData graphicEventData, LayerMask[] prioritizedLayerMasks, PointerHitResult hitResult) in the FocusProvider.

Expected behavior

No assert error every frame.

Actual behavior

Assert error every frame

Your Setup (please complete the following information)

• Unity Version 2019.1.0f2
• XRTK Version 0.1.8
• XRTK Lumin configured

Target Platform (please complete the following information)

• WMR immersive
• OpenVR
• HoloLens
• Lumin

[StephenHodgson]

Should be fixed in 0.1.9

[provencher]

When's that coming?

[StephenHodgson]

Pretty sure that's the latest release, let me double check.

[StephenHodgson]

Yup, it's already out, please update and let me know if it still persists.

Fixed in #153

[provencher]

I just pulled this evening lol! I'll update and give it a try this week sometime.

Thanks!

[wassx]

I tried 0.1.9 on an existing project where same issue ocurrs. When I try to set the near clipping plane of the uiRaycastCamera to 0 it jumps back to 0.01 in the editor.

Comparing upm branch to development the RaycastGraphics in FocusProvider.cs is different

[wassx]

it seems this commit hasn't made it into 0.1.9 3985a85

https://github.com/XRTK/XRTK-Core/commits/development

[dumitrusisianu]

Near clip plane can be set to zero only if UIRaycastCamera is ortographic (instead of perspective). With ortographic camera, the input seems to be working fine on the Leap, but is not working correctly in the Editor.

[StephenHodgson]

My apologies guys. I'll reopen this until it hits release 0.1.10

[StephenHodgson]

Closing now that 0.1.10 is released