I’m new here and new to linux. I need some help with obs studio. Here are my laptop specs:
CPU: 11th Gen Intel i5-11400H
GPU: Intel TigerLake-H GT1 [UHD Graphics]
GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q
Model: MSI GF63 Thin 11SC (muxless)
Currently, I’m running the following system
OS: EndeavourOS Linux x86_64
Kernel: 6.11.3-arch1-1
Shell: bash 5.2.37
DE: Plasma 6.2.0
WM: kwin 6.1.2-1
Wayland
The issue I’m experiencing is that when I use OBS Studio to record using “Screen Capture (PipeWire)” as the resource and then choose windows for screen sharing and then choose fullscreen app that run on prime-run as the media I want to show on the canvas (in this case I choose game) then fullscreen app that i choose will freeze. However, everything works fine when I use the integrated graphics (not run the app or game using prime-run) or using Laptop Screen for the recording.
Screen Capture (PipeWire) > Open Selector > Windows > fullscreen app (prime-run) = Error.
Screen Capture (PipeWire) > Open Selector > Windows > fullscreen app (Integrated graphic) = Fine.
Screen Capture (PipeWire) > Open Selector > Screens > Laptop screen = Fine.
I’ve found a couple of potential solutions:
Downgrading the kwin package to version 6.1.2-1 or earlier.
Creating a window rule for the app, though this sometimes leads to other issues.
For now I just downgrade my kwin package and everything works fine. I post this here just to ask if anyone know what cause the kwin after version 6.1.2-1 having this error and if anyone have similar problem or anyone have another way to fix it.
Bellow is provided video of what I just said since I believe my explanations are bad.
I have the same issue (also on dGPU laptop setup) and wanted to inform you I have opened a KDE bug.
Interestingly, even for single GPU case like on a Desktop, there was freezing like this but it was dependent on if the target Window was hiding or showing the mouse cursor. Maybe when this was addressed, it broke for our dGPU case.
I confirmed from your findings 6.1.2-1 works for me. I had been using it prior to 6.1.3+ and this interrupted my workflow. Many thanks for finding which version it started.
Thanks for your testing.
Can you please edit post 3 to remove the incorrect test you later confirmed was on kwin 6.1.2-1?
This way if KDE member reviews this post directly it won’t cause confusion.
I will do my own tests from your new scenarios you listed and report on KDE bugtracker once confirming I can reproduce.
First of all, I made this reply because in the previous reply that I probably already deleted, I’ve made a few mistake and with this, I’ll trying to rewrite it as detail and correct as possible. I apologize for that.
Second, I want to thank you for creating the KDE Bug post since I don’t know if I can do that.
From what i saw on the KDE Bug post, there’s few version on how the freezing can happen.
At the previous reply, I’m trying to do some test with dual monitor setup because from what I saw on KDE Bug post’s reply and since I’m able to have access to external monitor at the time.
I’m trying to do the test on two version of kwin (6.1.2-1 and 6.2.2-1). The fullscreen app I’m using on this test is steam game (Inscryption) running on prime-run.
This is what I got from the test: 1. On kwin 6.2.2-1 1.1. If both OBS and the app (running on prime-run) in the same monitor (either external or internal) it will freeze the app. 1.2. If the OBS and the app not on the same monitor (OBS on external and app on main monitor or vice versa) it will not freeze the app.
2. On kwin 6.1.2-1 2.1. If both OBS and the app (running on prime-run) in the same monitor it will only freeze when I put both on my main monitor (laptop monitor). 2.2. If the OBS and the app not on the same monitor (OBS on external and app on main monitor or vice versa) it will not freeze the app.
3. Other thing I want to mention 3.1. I try to change the color profile to Built-in when using only one monitor and it fixed the problem (the app not freeze anymore). 3.2. Changing color profile on the monitor where both app running to Build-in solve the problem on 1.1. 3.3. Changing color profile on main monitor to Build-in solve the problem on 2.1.
At the moment I write this reply I don’t have access to external monitor anymore so I can’t do another test. So, that is all what I got from the test.
Below is the Screenshot of the Display Configuration.
Note:
I only change the color profile on this test, I’m not changing anything other than that. Just plug the monitor and do the test.
Testing was done on a laptop without mux switch and the HDMI port is connected directly to iGPU (no way to bypass nvidia optimus).
For now that’s what I got. Sorry for the confusion and inconvenience. I hope this help.
Thank you.
I got another freezing and don’t know what happen.
As I write this November 3rd 2024 (1:45PM UTC), I just update my system (pacman -Syu) but still not update the kwin version (it stay at 6.1.2-1). After that I’m trying to do live stream for game called Insrcyption and the game now freezing when I trying to window capture it on OBS.
I try another games, osu! and osu! lazer and both game are not freezing.
Also few days ago before I write this, I trying install osu! lazer and trying to stream it and got the same freezing. The solution I got for the osu! lazer is change the settings on the game to windowed and back to fullscreen and everything works fine now.
The solution above wont work for this, but the solution I got for this Inscryption game is change the Display Configuration to Switch to Laptop Screen or other by using shortcut Meta+P. Now when I relauch the game, its now freezing anymore
I don’t know what happen really, I just add this if somehow this can help.
Note:
Since I forget to add the dual monitor test date, I do the test on October 30th 2024.
I just doing small test on one game osu!.
On the game there’s options to use compatibility mode, which based on this forum it will translate OpenGL to DirectX.
The small test I was doing was like this.
Open the game using prime-run.
I tried to use the compatibility mode and then game got restarted.
Open OBS and choose the game (now running on compatibility mode).
Back to the game and the game is not freezing.
Quit the game and relaunch it and choose the game again on OBS and still got the same result (not freezing).
Turn off the compatibility mode and the do the same with OBS, but now the game is freezing.
Another things I got from this is when I looked at nvtop I got this two different result on the game.
The first one was when the game not using the compatibility mode and second one is when the game using it.
This test was running on kwin 6.2.3-1.
I don’t know anything about OpenGL or DirectX and I also don’t know if the compatibility mode really translate OpenGL to DirectX. I post this if somehow this will help something.
In the end I’m not using the compatibility mode since it hurt performance.
12/22/2024. Kwin version 6.2.4-4 still has the same problem too.
I also notice on single GPU (my desktop) I am running into similar issues when capturing a Window directly if the app hides the mouse cursor.
Seems for now staying on 6.1.2 until a KDE member figures out the issue is required even for non-prime/dGPU situations. Unfortunately this type of code is out of my understanding, but perhaps I can bisect and help find the bug cause.
Kwin version 6.2.5-1 still has the same problem. Also I’ve been trying using flatpak version of OBS and the result is still the same.
Before this, my work around of this either using old version (6.1.2-1) or change color profile on display settings. But as I write this, I also using obs-vkcapture because from my experience using this plugin, the performance is way better than using window screen capture.
The obs-vkcapture is good but still need a bit of work since I need to launch the program using command obs-gamecapture and environment variable (/etc/environment) “OBS_VKCAPTURE=1” is not working for me. Also I need to lauch the OBS using prime-run if I also launch the game with prime-run or it will not capture (and vice versa if I use the iGPU).
Thank you for giving me an update and letting me know about this. I’m glad that this hopefully will fixed soon. I think I will wait for the merge and if it’s really fix, I’ll give an update and then maybe close this forum.
As such kwin 6.3.0 is also available as stable release.
Is the issue now resolved for you?
I confirmed on my hardware that both Single GPU scenario with multi monitor and laptop scenario (iGPU and dGPU) the issue no longer occurs.
Thanks again for your in depth report of the issue, it helped prioritize this bug.
I want to confirm that on my system (after update to Plasma 6.3.0 and using kwin 6.3.0-3), the issue is resolved for me. I only test it on a single monitor setup on my laptop. Launch OBS with or without prime-run is the same (both working), but I haven’t tested the performance yet (and compared to obs-vkcapture).
Other thing I noticed after the update is when I choose a game for OBS to be captured and then close the OBS and even the game, after relaunch the OBS and the game, I don’t have to choose the game again. I don’t know this because I update my OBS or because I update my system, I’m just thinking this worth to mention.
Also, I want to thank you for opening the KDE bug, at the time I don’t know that exist and if I can do that.
