• SatyrSack@quokk.au
    link
    fedilink
    English
    arrow-up
    0
    ·
    13 days ago

    Mainly Beat Saber. I tried out a couple flat rougelikes (I think Brotato and Deep Rock Galactic Survivor), and they worked fine.

    I also tried PolyCube, but it did not work in VR mode. It would launch and I could see my controllers, but pressing buttons did nothing. I could not even navigate the in-game menu to start playing a session. Perhaps if I connected a standard Xbox controller or something, that would work. I know that a standard controller is recommended for that game, and from my own experience years back with older generation VR controllers that lacked traditional face buttons, that surely was preferable. But I was expecting that the Frame controllers would suffice. Unfortunately, this game was abandoned by its developer, so I doubt it will ever be patched to make the Frame controllers work properly. Perhaps an update to the Frame itself will fix whatever the issue is. Everything works fine if you launch the game not in VR mode, though. The VR controllers work just as well as an Xbox controller or something thanks to the fact that they actually have face buttons unlike most VR controllers when the game was originally made.

    Lastly, I keep trying to figure out how to make the mouse pointer appear. It seems like Valve disabled it because they want to just use the laser pointer thing that appears when you point your VR controller. But that means that when you connect a literal mouse to use in desktop mode, you can’t tell where you’re pointing. I am sure there is some way to revert whatever Valve had disabled, but I am not finding anything relevant in the KDE settings.

    All of this is standalone. I have not tried streaming.

      • SatyrSack@quokk.au
        link
        fedilink
        English
        arrow-up
        0
        ·
        11 days ago

        Thanks! This seems like something that Valve had intentionally disabled, so once they become aware that some people actually want it, I assume they will add an easy setting to re-enable it.

        But in the mean time, so people don’t have to visit Reddit, here is the relevant bit from that post:

        The Actual Fix via Konsole:

        Once you know the mouse is paired correctly, and see that it works (just the pointer is not visible) open Konsole and run this single command to force KWin to render the pointer icon over the Gamescope layer:

        mkdir -p ~/.config/environment.d && echo "KWIN_FORCE_SW_CURSOR=1" >> ~/.config/environment.d/kwin_cursor.conf

        Make sure to restart Desktop Mode (or reboot the headset) after running this for the changes to take effect.