MaxWang-MS

@davidkline-ms Hi Dave any chance you have seen this before?

@davidkline-ms Do you feel like we should close this one as I believe you have fixed several issues causing a crash?

Hi @abhilashca, can you let us know what version of the Oculus Integration package you are using?

I am a bit confused about pointerPosition vs aimPosition in this PR... Are they the same? Also I thought we were done with `pointer`s in MRTK3, apparently that's not the...

After a discussion with @keveleigh we decided to not create a custom build processor for this and instead we are documenting this issue in MRTK3 docs.

This issue should have been fixed via #10871 and will ship in pre.11. Please feel free to reopen if you are still experiencing this issue.

I think this is a Unity bug/feature request as the TouchcreenKeyboard is a Unity API. If you are impacted I strongly recommend filing a bug report with Unity as that...

Hi @derekfreed, I have not heard any update on this issue and am not sure if a bug/feature request has been filed with Unity. Please go ahead and file a...

Hi @SimonDarksideJ, we just fixed an issue preventing the "select" keyword from being recognized on HoloLens 2 recently. The necessary changes on the MRTK3 side were made in pre.9, but...

No, the update should not change the behavior of the recognition of "non-select" keywords. In those cases, things should be working already. The Mixed Reality OpenXR plugin is 1.5 publicly...