bino icon indicating copy to clipboard operation
bino copied to clipboard

Flatpak does not work with VR

Open yaomtc opened this issue 1 year ago • 3 comments

/home/chris/.var/app/org.bino3d.bino/config/

This folder does not exist when the Flatpak is installed, so there's no path registry. Building/installing QVR and then Bino on Arch Linux from AUR might give VR functionality with my Index - I'm not sure as testing that has other issues, such as:

Hardware does not support image size 4320x2160 (constraints: width 0-4096 height 0-4096)

The native resolution of the Index display(s) shouldn't matter, should it? Isn't it a virtual screen?

yaomtc avatar Aug 01 '23 00:08 yaomtc

Using Wayland at least I can get pixels from the video to appear on the headset, but... does it need to be scaled down with another tool to get it to actually display, and not get jumbled up?

yaomtc avatar Aug 01 '23 02:08 yaomtc

Regarding the folder you mentioned: I'm not sure what the significance of this is, or what you mean with "path registry".

Regarding the resolution: All VR applications must first render the scene into textures, which are then passed on to OpenVR which postprocesses them in a way suitable for your headset. That means the GPU must be able to render into large textures so that you can use the full resolution of your head set. That should never be a problem however because all GPUs that can handle VR can also handle large textures. Is yours an exception to this?

Regarding Wayland: I have only tested with SteamVR on Linux X11 so far. What do you mean with "jumbled up"? Can you describe the problem in more detail?

marlam avatar Aug 07 '23 05:08 marlam

Regarding the folder you mentioned: I'm not sure what the significance of this is, or what you mean with "path registry".

When I execute the current binoFlatpak with flatpak run org.bino3d.bino --vr I get Unable to read VR Path Registry from /home/max/.var/app/org.bino3d.bino/config/openvr/openvrpaths.vrpath as a response and only a black window opens.

1Maxnet1 avatar Feb 01 '24 08:02 1Maxnet1

OK, I now have a Wayland setup to test with. This message appears for me too, but not on X11. As far as I can see, it can simply be ignored. Steam with Wayland does not work well for me, I did not even try Wayland+SteamVR. I would say that for now, X11 is still recommended for SteamVR. I will regularly test with Wayland in the future of course.

marlam avatar May 31 '24 18:05 marlam