04-28-2017 07:21 AM
05-28-2017 01:53 AM
05-28-2017 02:50 AM
Kirshaw said:
I noticed it by end of april, don´t know if there was a change of the touch codes programming after that period... best course of action would be a march oculus home version rollback to test it
05-28-2017 02:59 AM
05-28-2017 08:48 PM
06-03-2017 09:31 AM
06-05-2017 07:04 AM
06-06-2017 06:31 AM
cybereality said:
Best thing to speak with us on the support ticket and see if replacement is an option. You can also post your LogGatherer logs here so I can take a look to.
https://forums.oculus.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-ri...
06-06-2017 02:19 PM
06-07-2017 06:09 AM
cybereality said:
I'm not sure if that's related to the controller issue, but it seems you have Rift connected to the wrong HDMI port. Be sure Rift is plugged into the primary dedicated GPU, and not the motherboard or any secondary cards. You should also update your video driver to latest. It probably wouldn't hurt to update USB drivers for your motherboard and/or try using different USB ports for Rift (USB 3.0 and 2.0 should both work).
06-07-2017 06:23 AM
whatisusername said:
cybereality said:
I'm not sure if that's related to the controller issue, but it seems you have Rift connected to the wrong HDMI port. Be sure Rift is plugged into the primary dedicated GPU, and not the motherboard or any secondary cards. You should also update your video driver to latest. It probably wouldn't hurt to update USB drivers for your motherboard and/or try using different USB ports for Rift (USB 3.0 and 2.0 should both work).
I'm sure Rift is plugged into the primary dedicated GPU, and the video driver was updated to latest version. Is it possible be an OS problem? I test touch on another computer today. It works fine in win 7, but becomes weird after upgrading to win 10.