If "Disable low latency update" is set to false for vive controllers a line trace appears to lag behind

If "Disable low latency update" is set to false for vive controllers a line trace appears to lag behind the mesh of the vive controller. This makes it so that the line trace appears to bound and lag. The difference in position appears to be more than expected for something that is updated on tick (in this example).

1. Make sure that the vive is hooked up and turned on
2. Download the attached project
3. Open the project
4. Make sure that "Disable low latency update" is set to false for VR_Pawn
5. Play In VR preview
6. Move the left controller around
7. Notice that the line trace appears to have a bouncy laggy look

Expected: The line trace would only be about one frame behind (because it is updated on tick)
Result: The Line trace appears to bound and lag heavily

UPDATE: Alternate Repro: VIVE ONLY (No repro with Rift)

Download TestLateUpdate project and open MotionControllerMap

Project contains the VR interactable cube with 2 children

One child cube is set to "Use Attach Parent Bound"

Make sweeping motions with Cube (Video example: [Link Removed] )

Use console command 'showflag.bounds 1' to visualize bounding box lagging similarly to laser in other project.

Result: The bounding box will enter the cube, causing it to be culled for occlusion

Fix UE-51650

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

When I open UE4 4.24.3 it appears that. Does anyone know how to solve?

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

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

Launcher Black Screen

How to achieve HLSL Multiple Render Target in Material blueprints?

How can i modify the param name in EQS node

What method is used to fill polygonal regions when drawing spline mesh at run time?

How does UMG set overlapping layouts?