03-10-2019 02:10 PM - edited 04-02-2022 06:04 PM
Close your Oculus software
Open your explorer and travel to C:\Users\[username]\AppData\Local\Oculus\TouchCalibration
Copy the files in this folder as backup.
Open the .LTouch(left) or .RTouch(right) file with notepad, which ever touch controller you have the issue with.
To search hit the hotkey: Ctrl+F and enter either JoyYDeadMax or JoyXDeadMax or JoyYDeadMin or JoyXDeadMin
6. Y = Forward and backward dead zone issues
X = Left and Right dead zone issues
7. Increase or decrease the number by 50 each time until it stops (you may need to do this multiple times depending on how bad it is, restart software after each attempt)
Save + Close, restart your Oculus software. You may have to restart your computer.
Here are some examples of what to do when one of these is happening to your controller:
Eg.. JoyXDeadMin = -X value, JoyXDeadMax = +X value and so on
i7 8700k; 5ghz (water cooled), Asus Rog Strix Z370-E Gaming, Corsair 270R case, EVGA 3090 FTW3 Ultra, 32 GB Corsair Veng DDR4 2666 Ghz, Adata SX900 SSD, 1TB M.2 SSD, Adata Su800 SSD, Adata SU650 SSD, BarraCuda 2TB HD, Toshiba 3tB HD, Rift (dead), Rift S, Win 10 Pro 2004, Inateck KT4006 USB3.0
08-16-2022 05:28 PM
I haven't been able to find anything, but I don't really know the internals of android that well.
It's possible all of the calibration stuff was moved onto the controllers themselves for the Rift-S, Quest and Quest 2 and they just return the normalized results.