-
Notifications
You must be signed in to change notification settings - Fork 26
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
Severe degradation using obs-vkcapture together with gamescope on Steam games #209
Comments
Try |
Here is the odd thing, the artifacts are completely gone on Persona 4 Golden using that launch parameter. But I cannot make OBS see Portal 2 as an available source if I put obs-vkcapture after the two lines. Keeping same settings and everything obviously. If you have a spare second would you mind explaining what those two lines do? Is it some sort of piping? Btw, thank you for the quick reply! (here is the launch parameters I have used to test both Person 4 Golden and Portal 2 just now)
Logs
|
You're using old obs-vkcapture version (1.4.3), current is 1.5.0.
Do you have 32bit obs-vkcapture installed?
https://unix.stackexchange.com/questions/11376/what-does-double-dash-double-hyphen-mean |
I actually have the latest flatpak versions installed of both these packages:
As far as I know a --version switch doesn't exist so I unfortunately cannot tell you for certain which version it is and I do not even know if a 32 bit flatpak version exists I am going to be honest, I pretty much just followed the instructions on this README file. If I did something wrong please let me know and I will try to fix it. Thanks again! |
@SuNNjek perhaps you can help me solving this problem, I see you are the main maintainer of the flatpaks. I would be really glad if you could give me your feedback too. Thank you in advance! |
@Plarpoon To answer the question about a 32-bit flatpak: There's no separate flatpak for the 32-bit libraries, both the 64-bit and 32-bit libraries are included in the flatpak. If you are getting an output (albeit corrupted) I doubt that flatpak is the problem here honestly. Unfortunately, I currently don't have a gaming capable Linux-machine ready to reproduce this on. Maybe Portal 2 will run on my underpowered ThinkPad. If it does, I'll try and look into it 😅 |
I mean.. it's a 2011 game so perhaps it could (wish you luck 😃). Anyway, I think nowrep might have nailed the other issue with the question raised before. I just tested Half-Life (the 1998 one) which should also be at 32 bit and it's not detected at all by Game Capture. If this issue gets also solved together with the corruption issue already being mitigated thanks to the usage of the end of options delimiter we are nearing the closure of this GitHub issue. Btw, let me know if you would prefer for me to close this issue right now and open a new one in @SuNNjek's repos instead. |
@Plarpoon It seems to work fine on my system (ThinkPad T480s, Arch Linux, using the same command you used). For some reason my mouse input is broken, that's why I'm spinning uncontrollably, but that has nothing to do with the recording, so ignore that 😅 test2.mp4Does the output look corrupted in the stream preview in OBS as well or is it only an output issue? Have you tried different encoder settings? |
I think there was a miscommunication sorry for my poor English, the issue of video corruption was resolved when I modified the launch parameters. Initially, I was using:
However, I switched to the following format based on a suggestion from nowrep here, which resolved the video degradation issue:
Despite this, a new problem arose. Even though I have installed both of these flatpak packages:
I’m unable to record any 32-bit video game if I place the obs-vkcapture string after the --. It works when it’s placed before the --, but not after. For example: This command makes video capturing be recognized by OBS, but it results in video corruption:
This command doesn’t cause video corruption, but OBS doesn’t make the video source appear if the game is in 32-bit:
|
I have updated my previous comment after realizing how much badly it was written in English, please let me know if you have doubts on what I am meaning, sorry again |
I think LD_PRELOAD (which is used for OpenGL capture) may not be correct in flatpak, there were other issues about this too. |
If I can help testing something or you need any more feedback I am available for anything, from providing logs, testing things to straight up join one of you in a VC with screen-sharing. I am at your complete availability as this is a problem I would like to see solved as-well. Thank you all! |
@SuNNjek if you think you can confirm nowrep's suspicion about LD_PRELOAD being incorrect in the FlatPaks I will close the issues on Valve's GitHub and RedHat's BugZilla. Take all the time you need, relax and enjoy your first of May both of you! 😃 |
The reason why capturing gamescope results in partially corrupted image is because gamescope presents without wait semaphore which works for compositors but not for capture. Probably it would be best to just blacklist gamescope, same as what mangohud does. |
Is there anything that I can do to make it work with the 32 bit game scope apps? Because unfortunately this is a hit or miss issue, I recorded the entire first half of Portal 2 and it worked perfectly fine, the day after booting the PC as usual and couldn't make it work without corruption. My understanding as of now is that the best option is to just wait for an update where gamescope is blacklisted as you suggested but of-course that means waiting for it to be approved and imported into the flatpaks distribution system too. |
You can check EDIT: I just checked and this seems to be correct. No idea why it doesn't work for you, maybe something with Steam sandboxing again. |
If there is anything I can do to test it with sandboxing and relying you the results let me know, I am more than available to test it |
Describe the bug
Hello, my name is Alex,
I have been having this bug for almost a week now, I have opened issues at Valve's gamescope, RedHat BugZilla and even talked with the OBS support on their Discord. This is the last place I have left then I don't know how to solve this issue anymore, so please if you have any idea on how I could better identify the problem help me out.
Here is the issue!
Since the day after I updated to Fedora 40 KDE (from Fedora 39 KDE) whenever I record a video that is taken from gamescope with the Game Capture function on OBS, using obs-vkcapture the video in the preview and the recorded (or streamed) format will look like the video embedded below.
Here is the list of the odd things:
The solutions I have tried as of now are as follows:
Screenshots or video
https://youtu.be/7svRzATLp_0
System (please complete the following information):
OBS log:
Game log:
steam-1113000.log
The text was updated successfully, but these errors were encountered: