Motion Controller Axis input values over scale in increments of 2

The Axis input values for SteamVR motion controllers will increase exponentially by 2 from the moment the editor starts and every time the user enters VR Mode or does a Launch On (eg. Entering VR Mode one will increase the input axis value -4 to 4, -6 to 6 etc.)

This does not occur with the Oculus Rift S

1. Setup SteamVR Device
2. Create a New Virtual Reality Template
3. Open the Entry level Level blueprint
4. Create a print string to print the motion controller Thumbstick X-axis to screen
   1. Add an Event Tick node
   2. Pull off of Event Tick and create a Print String node
   3. Pull off from "In Sting" in the Print String node, disable context sensitive and Search for MotionControllerThumbRight_X then select the Input Axis Value.
5. Enter VR Preview
6. With the right motion controller
   1. If using the Index move the joystick left to right
   2. If using the Vive wands slide your thumb across the track pad from left to right

Results: The values between the two axes will be -2 to 2 (Left to Right respectively).

Expected: The values between the two axes will be -1 to 1 (Left to Right respectively).

How does TextureRenderTarget2D get TArray<uint8> type data?

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

Why does the REMOVE method of map container remove elements have memory leaks?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

How to delete some elements correctly when deleting an array loop?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

What does the number (2152,1-34) in glsl error mean?

UMG RichText not appear image when packaged

How does TArray loop correctly remove elements in blueprints?

any help with here I am using a relativly highpoly model with 4k displacement and still get this wagy edges