Controller issue

Homepage Forums Technical Support Controller issue

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #218145
    Waz999
    Participant

    Hi guys.

    I’m trying to play Titalfall 2 and I’ve managed to get it up and running and looking pretty good. Problem however is that I use an Xbox controller and the key bindings are all messed up. For example, in game, it tells be that the B button is for crouching but when I press it, I melee attack.

    I’m using a Quest 3 via Virtual Desktop and Steam on Windows 11. I have switched my Quest controllers off completely in the vorpX menu. If I play the game flatscreen, the controls do as intended. It only gets screwy once I play it through vorpX. I haven’t encountered this issue before with other games I have played with vorpX so I was wondering how I could go about fixing this.

    #218154
    Ralf
    Keymaster

    Please reset the profile to default. This is not supposed to happen at default settings. You shouldn’t really have to tinker with any settings in the vorpX menu aside from the ‘Resolution Quality’ option anyway. This is a profile where vorpX automatically adjusts game settings for the best possible experience.

    On a sidenote: Unrelated to your issue, but in general it’s better to use native Oculus mode and Quest Link with vorpX. That’s how things are supposed be done for Quest. SteamVR mode is intended for native SteamVR headsets like Valve Index. When you use SteamVR with a Meta/Oculus headset you add an unnecessary translation layer, SteamVR in the end uses the Oculus runtime anyway.

    #218171
    Waz999
    Participant

    Thanks for the reply Ralf, I’ll definitely try that. Now that you mention it – I played Hitman in VR in the past, using both VD and Airlink and I remember that the controls were different in each one, even though I never changed anything, so I think that using Airlink may resolve the issue.

    #218184
    Waz999
    Participant

    Hi everyone. I can confirm that playing through Link / Airlink instead of Virtual Desktop did solve the problem in case anyone else is having this issue.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Spread the word. Share this post!