Just wanted to open a topic about it, I'm on the Valve Index and have the exact same problem.

Thank you for pointing this out, and apologies for the issues! I've heard other reports on this, but haven't been able to reproduce it locally, but I do have a hunch as to what might be going on.

Could either of you try a beta branch with a new build to see if it resolved the issue? To access the code, you can use the code "SolidDissection" in the settings for the game in the Steam Library.

@rrrl.kf just had another Quest 2 user say the beta branch I mentioned above helped solve the issue when playing with Airlink (they still had issues with Virtual Desktop, but afaik that was never a supported way to play).
Let me know in case it also works for you!

(btw, those previous posts were from my personal account - forgot to switch to my dev account)

Hey folks, just wanted to update you that I've pushed the fix to the main branch. Let me know if you have any further issues with the controls!

unfortunately, still not working.
i have tried the beta and also reinstalled the game, but still having the same issue

FYI, i am using oculus Link (Via Oculus Cable ) not AirLink, not sure if this makes a difference.

I'm on the htc vive controller and i have a same problem

Hey folks, thank you to everyone reporting this issue. I've pushed a new build to the beta branch (code 'SolidDissection' to unlock) - if any of you have a moment, could you switch to this branch, make sure the game updates (uninstall and re-install if needed), and let me know if it works?

Apologies for the ongoing issues - it's been hard to nail down exactly what is happening since I still haven't been able to reproduce these issues locally. If this new build doesn't work, I might just switch to OpenXR input instead as a next step.

I think I was just able to reproduce the issue.
By any chance, are any of you using SteamVR as the OpenXR runtime?

You can check this under SteamVR settings, enable advanced settings, then under developer settings check whether Current OpenXR runtime is set to SteamVR. I just enabled this, and the issue propped up for me too.

So after more experimentation, it very much seems like the SteamVR OpenXR runtime is the culprit here, as it's breaking some of the methods which the game uses to detect which headset is playing, and whether the controllers are present.

If you also have Oculus home on you computer, this issue can be temporarily fixed by switching to the Oculus OpenXR runtime in the Oculus home settings under general.

For a permanent fix, there doesn't seem to be a way around me switching the game to OpenXR input, since there doesn't seem to be a clear way around turning SteamVR's OpenXR runtime off if you can't switch to the Oculus one. Switching to OpenXR input will likely take a few days, but hopefully I can get a build out soon!

I am not sure why but i cant set my Oculus to be OpenXr runtime on my oculus home, and yes on my SteamVR settings i have the current OpenXR Runtime as SteamVR.

Hmm odd - it should be under settings > general > OpenXr Runtime. Maybe there's an update for Oculus home you need to install first?

In any case, I think I'm getting pretty close to a proper OpenXR build of Cubism for Steam, I'll let you all know as soon as I have a beta branch up for it. (hopefully by tomorrow!)

Ok, I have an OpenXR build which should resolve the problem!

Could you guys switch to the OpenXR branch (code "cubismopenxr") and let me know if this version works for you? Thanks in advance for the help!

I just bought the game and ended up here because I have the same problem - Index controllers. I saw your comment and installed the OpenXR build - worked great for me! Thanks!