Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Immersed feature comparison #82

Open
Victor239 opened this issue Oct 15, 2024 · 5 comments
Open

Immersed feature comparison #82

Victor239 opened this issue Oct 15, 2024 · 5 comments

Comments

@Victor239
Copy link

I got interested in getting a VR headset after seeing Immersed but unfortunately learned it has poor Linux support for important features like virtual monitors. I was wondering if this app is a good alternative, and if any of these features are present or planned:

  • Virtual monitors (i.e. arbitrary amount of screens regardless of how many are physically present)
  • Passthrough portals (e.g. being able to make cutouts to see keyboard, doorway, etc)
  • Custom environment (e.g. 360 photo support)
@galister
Copy link
Owner

Virtual monitors right now depend on the desktop environment in use. Gnome and wlroots virtual displays usually work, while KDE ones don't. There's an ongoing effort to add WayVR support, allowing users to spawn windows directly in VR, without having to mirror a screen.

Passthru is generally out of scope for the project, since it's primarily an overlay app.

Custom photos are supported on Monado, as long as there is no scene application running (there is nothing to overlay on top of).

You might also want to check out StardustXR!

@Victor239
Copy link
Author

Thanks for the response.

How come KDE ones don't? Is there a KDE bug I can follow to check the status of the issue?

I found VKMS through some further research, sounds like a distro-agnostic solution. WayVR sounds very cool too.

Cheers, I'll check it that that out too.

@galister
Copy link
Owner

There's isn't a standard or protocol for virtual monitors, and so the fact that it's not compatible with how Wlx handles virtual monitors cannot be considered a bug.

@Victor239
Copy link
Author

I meant KDE bug as in their issue tracking platform, tickets can be raised for bugs, feature requests, etc.

VKMS looks like a protocol for virtual monitors from what I understand.

@galister
Copy link
Owner

I believe it would work with VKMS or anything that makes the display show up as if it were a physical display. What doesn't on KDE is creating a temporary virtual screen by selecting "virtual" on the PipeWire screen share prompt.

Wlx works on any virtual or other display that implements wl_output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants