-
Notifications
You must be signed in to change notification settings - Fork 68
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
Unstable rendering with libX11 1.8.3 #3105
Comments
I got the same problem, for me the game hangs when I'm not sending inputs: |
Same Issue here |
Same issue. The game is like SUPERHOT. Time only moves while you're sending inputs... |
the following solved the problem for me:
|
@UnlegitSenpaii |
This worked. Thank you! |
That worked! |
Same here on Gentoo. |
I did a system update couple days ago. CSGO went from playing fine, to lagging. I had upgraded mesa and libx11, so after some troubleshooting it was clear it was libx11. As someone said, inputs makes the game render properly. It seems that if the cursor is visible on the screen, as in any menu, console or chat, the game renders properly. If you are playing, the game will be frozen if you give no inputs. Continuous movement of mouse makes the game render properly, for example by making a circle movement with the mouse. Keyboard inputs also unfreezes the game but only on the key down event. If you hold the key down, it seems to unfreeze momentarily, making the game seem very laggy. |
I'll add this bit of potentially useful information. The issue stops when the game is paused. |
can confirm having this bug, thanks for the fix @UnlegitSenpaii !! |
Bisected and found likely cause, see #174 on libx11's gitlab |
can u help me downgrade i'm new to all these stuffs |
You have to install package called "downgrade" then use the package to
reverse libX11 to version 1.8.3
На нд, 18.12.2022 г., 13:17 ч. Ankit Shrestha ***@***.***>
написа:
… the following solved the problem for me:
- downgrading libx11 to version 1.8.1-3
can u help me downgrade i'm new to all these stuffs
—
Reply to this email directly, view it on GitHub
<#3105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWIPNBDLKANXXXC2SHX5DFLWN3XFJANCNFSM6AAAAAATB3I63U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Using |
because it just relates CS:GO I did it this way: build libX11 1.8.2 (works too) by sources:
and than preload the lib(s) just for CS:GO in steam start options:
|
The package maintainer for libx11 on Arch Linux bumped the package with some patches. The |
On gentoo i fixed it by downgrading to 1.8.2, ubuntu is not a measurment for any distro. Installed versions: 1.8.2-r1^t(18:49:16 17.12.2022)(-doc -test ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="32 64 -x32") |
@Brottweiler Can confirm that on 1.8.3-3 issue has been resolved. |
it's fixed as I'm on the 1.8.3 -3 version |
I updated to 1.8.3-3 and it has been resolved |
I guess it is not really fixed with 1.8.3-3. i have many (at least every 3rd game) random crashes especially on DZ. |
Seconded, 1.8.3-3 does not seem to fix things for me either ( on Arch) |
This issue is a regression in the distro-managed libX11 library. If Arch is maintaining an early merge of https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/176 and https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/177 in attempt to mitigate that regression, and that is insufficient to resolve the regression, then that feedback needs to go to the upstream libX11 dev(s) to ponder. |
If
Version 1.8.3-3 regression fix seems to be only for 64-bit libraries at the moment. Try downgrading the 32-bit library as well to <= 1.8.2-2 on your distro since many older games use x86 architecture. This worked for me on Arch Linux: Games tested: CS:Source, TF2, HL2DM. Hopefully upstream libX11 dev(s) will regress 32-bit as well. |
libx11 1.8.3-4 is in the repos. Is that version helping? |
For me libx11 1.8.3-3 totally ruins Steam playing (my OS is Manjaro Linux). Actually none of Steam games were able to start after upgrade to 1.8.3-3. So I fixed it by rolling back to 1.8.2-2 and freezing libx11 on that version. In case of Manjaro, the package name is "libx11" and I don't know if it contains 64bit or 32bit binaries. |
I am using Arch Linux with the |
It's 64 bit package, 32 bit is lib32-libx11 from multilib repository. |
Since there are 2 versions of libX11 (32 & 64 bit), it seems 64-bit is currently the only one being updated. 32-bit hasn't had any updates thus far and is still suffering from the same problems. I am currently using As I use Arch Linux I'll reference it here, but this likely holds true irregardless of which Linux distro is used.
Per Latest Arch-Linux Repos:
|
The problem still remains. high frequently random crashes especially in danger zone with libx11 1.8.4-1. |
Hello @daxcore, the upstream libX11 regressions in 1.8.3 that I'm aware of have been resolved upstream with 1.8.4. If the game is still stable with libX11 1.8.2 and unstable with 1.8.4, then it would be a good idea to report your findings to the upstream libX11 issue tracker (https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues). |
I still have this issue that manifests exactly as described in the OP. The game starts running fine but becomes unplayable after a few rounds with heavy 2-5 seconds long freezes. It's as if there's some buffer that runs full. No matter if I use opengl or vulkan. I had no problems playing CS:GO a few months ago. I'm on latest rolling Arch, currently libX11 1.8.6-1, kernel 6.4.1zen2-1, nvidia-dkms 535.54.03-1 I'm playing on a ultra-wide screen 3840x1600. What mitigates the issue is lowering the various details and graphics performance settings and resolution to 1920x1080 (window mode), then in most cases (not every time though, rebooting helps then) I can play indefinitely. (And even then, it seems it's still happening very often in the Danger Zone mode likely because of the large maps and many graphical objects.) I'm guessing because not everyone plays with such a high resolution, the core issue may still be prevalent and is just not reported so often. |
Hello @scr0llbaer9000, as previously noted, the issue reported here was root caused to an upstream regression that was also resolved upstream. Please open a new issue report so that your issue can be tracked properly. |
For completion, the reason for the problem I had was my HDMI cable, which was baffling (for me). https://bbs.archlinux.org/viewtopic.php?id=287313 |
System information
Please describe your issue in as much detail as possible:
After last update CS:GO is not playable. The game is constantly stuttering and starting very very slow. Its just hangs from like every 2-5-10 seconds. Loading a map takes like 5 minutes. I've tryied so far = -vulkan and opengl.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: