nowrep
commented
1 year ago I'm wondering if there's a workaround/patch that can be made for this. It's not a huge problem, but it is a limitation.
Ideally you would be able to just import linear dmabuf on any GPU, but this doesn't seem to work on nvidia?
If for example the game is on the dgpu(sink providing) output, you would need to launch obs on the same gpu to capture it. However, this would mean that screen/window capture(pipewire) would instead be black as it follows a similar limitation. Obs needs to Be launched on the primary(sink source) gpu in order for screen/window capture(pipewire) to work.
Sure, but it shouldn't be much of an issue. Unless you want to show both screen AND game capture in one scene.
It would be ideal if we could capture the game with obs running on the primary(sink source) gpu regardless of what gpu the game is running on. This would allow us to use screen/window capture(pipewire) and game capture at the same time always. There's not many scenarios I can think of where that's needed, but it allows us the option if needed.
Sure, but I have no multi-gpu machine (let alone any nvidia hardware). Maybe you could make an extra GL context in OBS for the GPU that the game is running, import the game buffer there and then copy it to the OBS gpu. But for this, again, you would need to export dmabuf and import it on the other gpu - and this doesn't seem to work? Last option would be to do CPU copy, but that will most likely kill the perf.
Outside of that, it will also save a handful of people who are wondering why gamecapture isn't working & is just showing a black screen a headache since by default, obs launches on the primary(sink source) gpu. It might be worth noting this on the main page.
There's a FAQ for this = run on the same gpu in multi-gpu setups.
arazadaz
In prime system setups, where the system makes use of two graphics cards, an igpu(sink source) and dgpu(sink provider), vkcapture will only capture the game if obs is launched on the gpu the game is running on, otherwise it will only show a black screen.
I'm wondering if there's a workaround/patch that can be made for this. It's not a huge problem, but it is a limitation.
If for example the game is on the dgpu(sink providing) output, you would need to launch obs on the same gpu to capture it. However, this would mean that screen/window capture(pipewire) would instead be black as it follows a similar limitation. Obs needs to Be launched on the primary(sink source) gpu in order for screen/window capture(pipewire) to work.
It would be ideal if we could capture the game with obs running on the primary(sink source) gpu regardless of what gpu the game is running on. This would allow us to use screen/window capture(pipewire) and game capture at the same time always. There's not many scenarios I can think of where that's needed, but it allows us the option if needed.
Outside of that, it will also save a handful of people who are wondering why gamecapture isn't working & is just showing a black screen a headache since by default, obs launches on the primary(sink source) gpu & their game is likely on the dgpu(sink provider). It might be worth noting this on the main page.
I want to also say that in my experience, this behavior isn't always consistent. While trying to capture diablo 4 which was running on my dgpu, it did actually show on obs even when I ran it on my igpu, but would crash when trying to record/stream with a out of memory error with obs on the igpu. I think it tried allocating memory from the igpu which would explain that, but the point here is that this anomaly shows that it might be possible to get a proper workaround/patch for this. Other games that run on the dgpu show a black screen though in my testing.