lukypie
New Member
I don't know if that's has something to do with my setup, here it is:
Ubuntu 19.04
Linux 5.0.0-8
GPU Nvidia GTX 1060 3GB, NVIDIA Proprietary drivers, 418.56
OBS Versions: Tried a bunch, the one from the 19.04 repository, the one from the snapcraft.ioedge repository, both have the same problem
- The OBS preview was disabled
Basically, when OBS is set to record the with the fullscreen option (XSHM), even before starting to record, the input in games becomes laggy, and the fps drops dramatically from 180 to 130.
The game in question was using the Vulkan API and is called Serious Sam fusion 2017.
Everything works fine when OBS is set to record that game via Window (Xcomposite)
Some notes:
- The input lag is the same even if start recording
- When the "eye" on the right is active in the "sources" section, the issue is present, when the eye is greyed out, it's not (Makes sense)
I think the same happens with SimpleScreenRecorder, so in case this couldn't be solved because is a technical X.org limitation, I may suggest to add warning message people about using this method that could lead to this problem and recommend recording the Window instead when games are involved
Thanks for the attention...
Ubuntu 19.04
Linux 5.0.0-8
GPU Nvidia GTX 1060 3GB, NVIDIA Proprietary drivers, 418.56
OBS Versions: Tried a bunch, the one from the 19.04 repository, the one from the snapcraft.ioedge repository, both have the same problem
- The OBS preview was disabled
Basically, when OBS is set to record the with the fullscreen option (XSHM), even before starting to record, the input in games becomes laggy, and the fps drops dramatically from 180 to 130.
The game in question was using the Vulkan API and is called Serious Sam fusion 2017.
Everything works fine when OBS is set to record that game via Window (Xcomposite)
Some notes:
- The input lag is the same even if start recording
- When the "eye" on the right is active in the "sources" section, the issue is present, when the eye is greyed out, it's not (Makes sense)
I think the same happens with SimpleScreenRecorder, so in case this couldn't be solved because is a technical X.org limitation, I may suggest to add warning message people about using this method that could lead to this problem and recommend recording the Window instead when games are involved
Thanks for the attention...
