search

LocalJoost / BlogComments

This repo is solely used for comments on https://localjoost.github.io/
4 stars 0 forks source link

Comments on "Using ARPlaneManager as an alternative to Scene Understanding with MRTK3 on HoloLens 2" #445

Open LocalJoost opened 1 year ago

LocalJoost commented 1 year ago

Original article: https://localjoost.github.io/Using-ARPlaneManager-as-an-alternative-to-Scene-Understanding-with-MRTK3-on-HoloLens-2/

ArnaudBBRI commented 1 month ago

Hello, Thanks for this post!

An additional question, if I may ;) How would you get a raycast hit (and its world position) on such ARPlanes ? I have a MRTK Ray Interactor on one of my hands, for which I enable AR Configuration > Enable AR Raycasting.

I hoped then the m_ARRaycastHitsCount inside the UpdateRaycastHits method of XRRayInteractor (base class for MRTKRayInteractor) would get updated, but it remains desperately at 0. In particular, I see XRRayInteractor automatically adds a ARRaycastManager onto the first XROrigin found, and it then performs the Raycast inside the CheckCollidersBetweenPoints method. When debugging, the ray origin/direction seem plausible, and trackableType is PlaneWithinPolygon, which I guess should work with the ARPlanes created. But like I said, somehow the hit count remain to 0.

Would you have any ideas on how to solve this ?

Thanks a lot!

ArnaudBBRI commented 1 month ago

Well, I guess I can also follow the methodology you provided in https://localjoost.github.io/Getting-the-hand-ray-end-position-with-MRTK3/ !