Oculus CheckIfPointWithinPlayArea function returns incorrect results

Oculus CheckIfPointWithinPlayArea function returns incorrect results, always reporting true whether or not the hand is inside the play area or not.  The distance and closest point also seem incorrect.

1. Open the attached [Link Removed] project, and play in VR[
2. There is a widget attached to the controllers of the hand to report the values output from testing the current location of the MotionController component (as well as that location plus the HMD's location in tracking space).
   • [Image Removed]
3. Using that window, verify the following:
   1. IsTriggering is always true despite if the hand is inside or outside of the oculus boundary
   2. Closest distance is a very large negative number, but is not in normal unreal units as moving the hand all around does not change the number very much
   3. The closest point seems to not change much based on which part of the boundary the hand is close to
   4. The closest point changes based on the movement of the HMD.  Since it is supposed to be world space, this should not be the case.

Fix UE-51650

I am not able to find world outliner how to enable it?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

How does TextureRenderTarget2D get TArray<uint8> type data?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

How to achieve HLSL Multiple Render Target in Material blueprints?

How can i modify the param name in EQS node

An error occurred while trying to generate project files !?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?