ValveSoftware / VR-Community-Bugs

Repository for VR Bugs reported through tickets and community outreach
10 stars 0 forks source link

Oculus Rift: Several titles prioritize Oculus Controls over SteamVR Controls. #136

Open KWS-Compat opened 5 years ago

KWS-Compat commented 5 years ago

On certain titles, The title will prioritize Oculus Settings and Controls over SteamVR Settings and Controls, even when launched through SteamVR or the Steam Library. This prioritization blocks the title from interacting with several SteamVR Elements:

•Titles are unable to open the SteamVR Overlay •User is unable to set custom Control Maps for the Controllers •User fails to return to SteamVR Home in the HMD after the title is closed

Repro Steps:

  1. Launch an affected title in SteamVR.
  2. Wait for the title to fully load and attempt to open the SteamVR Overlay. Observe that nothing occurs and the title proceeds as normal.

Expected Result: Title interacts with SteamVR Functions, such as SteamVR Overlay, Custom Control Maps, etc. Encountered Result: Titles prioritize Oculus Rift settings and fail to interact with SteamVR Features.

Notes: This issue appear to be related to Github #53, as both issues affect many of the same titles.

Several of the affected titles prompt the user upon launch with the choice to launch in Oculus Mode or SteamVR Mode. This issue still occurs if the user chooses to launch the titles in SteamVR Mode.

Issue has been observed to affect the following titles in all cases: •Blind •Zero Caliber VR •Karnage Chronicles •Audica •Creed: Rise to Glory •Moss •Loco Dojo •Summer Funland •Crisis VRigade •Accounting+

Repro Rate: 5/5

Config Details: Observed HMD: Oculus Rift Observed on CPU: Ryzen 7 1700 Observed on GPU: Radeon RX 580

Build: •SteamVR Build ID: 1.3.16

KWS-Compat commented 5 years ago

Issue has been observed to still occur as of SteamVR Beta Version 1.5.4 and Oculus Software Version 1.37.1.

KWS-Compat commented 4 years ago

The issue has been observed to still occur on several titles as of SteamVR Version 1.7.15 and Oculus Software Version 1.40. However, serval titles are no longer observing the issue. The main ticket has been updated with the currently observed list of affected titles.