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).
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
Head over to the existing AnswerHub thread and let us know what's up.