obs-vkcapture VS tinywm

I can't speak for Chrome nor VMWare, but Firefox and OBS have received "Wayland native" screen capturing functionality, through XDG portals and Pipewire, as far as I'm aware.

As a side-note, I've recently discovered a really cool project[0] that enables incredibly fast screen capture for OpenGL and Vulkan applications, mostly tailored to games. Tried it with a bunch of stuff and it works much better than both X's and Pipewire's screen grabbing. I can actually capture videos at my monitor's native refresh rate (144Hz).

[0]: https://github.com/nowrep/obs-vkcapture

Just use this: https://github.com/nowrep/obs-vkcapture

Hello, so I use this OBS plugin obs-vkcapture. I use it as opposed to the built-in Window Capture, because with that option I would keep having to alt-tab back into OBS to select the game I want to record. This plugin is basically the "Game Capture" feature on OBS Windows brought to Linux. It makes it to where I can put a Steam launch option obs-gamecapture %command% and launching the game will make its executable show up in the Game Capture source, so I can just press record on move on, no more opening OBS to select the game's window and risk nuking it when alt-tabbing. It is much more performance efficient and it's a package/patch that is included in GloriousEggroll's Nobara distro's build of OBS as well. I however use it on Arch from the AUR, it's the only AUR package I use in fact.

I was using https://github.com/nowrep/obs-vkcapture but I also had Proton-GE 7-49

Back in december when I tried I had some success using this https://github.com/nowrep/obs-vkcapture

Additionally, I'd like to use Game Capture in OBS if possible via obs-vkcapture. If using this with gamescope, where do I actually put the variable or obs-gamecapture command? Does it wrap the entire gamescope command, or does it get wrapped by gamescope?

I think you mean obs-vkcapture-git. It lets you capture a window through Vulkan. Here is also its github repo for more informations.

I have spent a few hours trying all kinds of dependencies on Fedora 36 Workstation trying to get obs-vkcapture to compile. I have found the exact ones and hopefully it helps someone in the future: cmake gcc gcc-c++ obs-studio-devel mesa-libGL-devel vulkan-loader-devel Here is a convenient command to install all at once: sudo dnf install cmake gcc gcc-c++ obs-studio-devel mesa-libGL-devel vulkan-loader-devel

> Nobody's requiring Wayland.

Yet. Defaulting to it is one step on the path towards removing support for X and independent window managers forever.

I deeply, deeply care about running an independent window manager. A minimal X window manager is a page of code: https://github.com/mackstann/tinywm/blob/master/tinywm.c (yes, plus xlib); a minimal Wayland compositor is tens of thousands of lines of code.

> contrary to your statements, it's perfectly ready for prime time

These comments are full of folks mentioning issues. Wayland does not support my window manager; thus it is demonstrably not ready for prime time for me.

> Wayland is the way forward

It may actually be. I’m not as opposed to Wayland as I may sound! But do you understand how you and other Wayland advocates sound — like advocates? ‘Wayland is the way forward’; ‘there's no future for Xorg’; these things are arguably true, but they are also rather cruel to say (a bit like ‘inevitably you and everyone will die’: it really is true, but it’s also not at all a nice thing to say).

I do think that Wayland or something very like it may be the way forward, but it needs to be an evolution, not a revolution. I know that the party line is that that’s not possible, but I suspect that rather than not possible it is just very hard. It’s always easier to greenfield, and it is always hell to be 100% backwards compatible.

But that’s what it needs to be.

Hah. I didn't think this was quite HN worthy at this point - the code is still a mess, and has plenty of bugs. It was however the wm I actually use since I got frustrated with bspwm and did a very minimalist rewrite of TinyWM [1] in Ruby [2] and expanded it from there. It was painful the first few days until I'd had time to add multiple desktops and the start of a tiling mode. But at this point, it's "almost" pleasant for me.

The warnings are real, though, apart from the initial hyperbole - this is likely to break for you in all kinds of horrible ways still. I use very few applications beyond (my own) terminal, (my own) polybar replacement, (my own) file manager, and a browser, and so once Chrome and my own apps mostly started working ok I've had very little incentive to make sure it behaves nicely with anything else and I know the distinction between different EWMH window types is incomplete and broken - just not in ways that usually affect my own use.

[1] https://github.com/mackstann/tinywm/blob/master/tinywm.c

[2] https://gist.github.com/vidarh/1cdbfcdf3cfd8d25a247243963e55...

picking a random bare bones wm tinywm

Or Check out TinyWM. Its just a few lines of code.

TinyWM