Describe the bug

A clear and concise description of what the bug is.

To reproduce

Steps to reproduce the behavior:

1. While tethered to a PC running an Oculus Link in Unity's Editor
2. Seems to happen when going between transitioning the headset up on my head and back down while simultaneously having controllers/hands being tracked

Expected behavior

Line 475 of BaseControllerPointer.cs throws a null reference exception error. This is occurring because at that moment in time the InputSourceParent reference hasn't been fully established yet and/or is cleared when the headset goes into an idle state?

Screenshots

Your setup (please complete the following information)

• Unity Version 2019.4.8LTS
• MRTK Version 2.4

Target platform (please complete the following information)

• Oculus Quest

Additional context

I originally posted this bug with the MRTK Quest extension and realized that this is actually more or so related to the BaseControllerPointer script which the quest extension is referencing. My workaround is just to check if the InputSourceParent exists. Included a photo for that here as well and the previous bug I filed with MRTK-Quest.

MRTK-Quest Closed Bug