"Physics.ClosestPoint can only be used with a BoxCollider" - Continiously printed in the Log File

[arunrajselvaraj]

This issue has been migrated a new MRTK repository, and the status of this issue will now be tracked at the following location:

• "Physics.ClosestPoint can only be used with a BoxCollider" - Continiously printed in the Log File MixedRealityToolkit/MixedRealityToolkit-Unity#424

---

Describe the bug

After starting the application, the below exception fills the log file continuously

To reproduce

Always reproducible

Expected behavior

Not to print this

Screenshots

``
Physics.ClosestPoint can only be used with a BoxCollider, SphereCollider, CapsuleCollider and a convex MeshCollider.
UnityEngine.Collider:ClosestPoint(Vector3)
Microsoft.MixedReality.Toolkit.Input.SpherePointerQueryInfo:TryUpdateQueryBufferForLayerMask(LayerMask, Vector3, Vector3, QueryTriggerInteraction, Boolean)
Microsoft.MixedReality.Toolkit.Input.SpherePointer:OnPreSceneQuery()
Microsoft.MixedReality.Toolkit.Input.FocusProvider:UpdatePointer(PointerData)
Microsoft.MixedReality.Toolkit.Input.FocusProvider:UpdatePointers()
Microsoft.MixedReality.Toolkit.Input.FocusProvider:Update()
Microsoft.MixedReality.Toolkit.<>c:b__67_0(IMixedRealityService)
System.Action1:Invoke(T) Microsoft.MixedReality.Toolkit.MixedRealityToolkit:ExecuteOnAllServicesInOrder(Action1)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:UpdateAllServices()
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:Update()

Your setup

• Unity Version - 2019.4.12f1
• MRTK Version - v2.5

Target platform

• HoloLens 2

Thanks

[JPhilC]

@arunrajselvaraj I have this problem. If you don't mind me asking, what was the internal problem with your project?

[arunrajselvaraj]

@JPhilC I closed this bug by mistake. Still we are facing this issue.

[JPhilC]

Funnily enough this started happening for me when I changed the Managed Stripping Level from Low to Medium. I changed it back and the problem went away.

[stale]

This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.

[derekdominoes]

This is occurring for me using the latest MKT3. It fills up my logs!
I have spline shaped meshes (road, wire, etc...) that need selecting thus have 'concave' Mesh Colliders.
The error is coming from the called to Physics.ClosestPoint inside "InteractorVisuals/ReticleMagnetism.cs:15"
Even though the error happens, everything seems to work fine (even the Reticle on the spline mesh seems correct).
Is there a way to turn off the Reticle Magnetism for certain Interactables?
Not sure how/where it gets enable?
As is, it makes my logs useless

Happens in the Unity Editor or on Oculus:
com.microsoft.mixedreality.openxr: 1.4.0
com.microsoft.mrtk.core: 3.0.0-development
com.microsoft.mrtk.extendedassets: 3.0.0-development
com.microsoft.mrtk.graphicstools.unity: 0.3.15
com.microsoft.mrtk.input: 3.0.0-development
com.microsoft.mrtk.spatialmanipulation: 3.0.0-development
com.microsoft.mrtk.standardassets: 3.0.0-development
com.microsoft.mrtk.uxcomponents: 3.0.0-development
com.microsoft.mrtk.uxcore: 3.0.0-development

[Zee2]

@derekdominoes thanks for bumping this. Sorry this fell in between the "couch cushions" so to speak. We'll take a look.

[Zee2]

This is almost certainly related to cursor magnetism.

[derekdominoes]

Not sure what it means to be added to a 6 week old milestone in your process?
The BUG still exists in the latest release so why mark as Closed?

com.microsoft.mixedreality.openxr: 1.5.1
com.microsoft.mrtk.core: 3.0.0-pre.11
com.microsoft.mrtk.extendedassets: 3.0.0-pre.11
com.microsoft.mrtk.graphicstools.unity: 0.4.0
com.microsoft.mrtk.input: 3.0.0-pre.11
com.microsoft.mrtk.spatialmanipulation: 3.0.0-pre.11
com.microsoft.mrtk.standardassets: 3.0.0-pre.11
com.microsoft.mrtk.uxcomponents: 3.0.0-pre.11
com.microsoft.mrtk.uxcore: 3.0.0-pre.11

[keveleigh]

@Zee2, is this the bug fixed by #11096?

[Zee2]

Yep, #11096 fixed this. @derekdominoes, we close issues when the fix is merged, not necessarily packaged as a release. Stay tuned for pre.12!

[derekdominoes]

Thank you. It does look like the same bug. I'll stay tuned :) Sent with [Proton Mail](https://proton.me/) secure email.

…

------- Original Message -------

On Friday, October 14th, 2022 at 1:06 PM, Finn Sinclair ***@***.***> wrote: Yep, [#11096](#11096) fixed this. ***@***.***(https://github.com/derekdominoes), we close issues when the fix is merged, not necessarily packaged as a release. Stay tuned for pre.12! — Reply to this email directly, [view it on GitHub](#8915 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEBLLD7QFQAC2XP7GHUGG43WDGOJPANCNFSM4TMN5TBQ). You are receiving this because you were mentioned.Message ID: ***@***.***>