Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
So, the academic answer should be Wayland has higher input lag compared to X11 when AllowTearing is not used, also Wayland use of libinput seems to be a tad different than X11's (not sure exactly how, though). Keep in mind also, that most games run on Wayland will be ran through XWayland (X11 being the back end), although Proton should pull the merge of Wayland support from upstream Wine, most native games will still use the X11 backend, although I'd expect CS2 to have native Wayland support alleviating the X11 on Wayland overhead.
However, in heterogenous refresh rate display setups does the synchronization affect higher refresh rate displays anyhow? What if only one display/refresh rate is in use so there is no need for this synchronization? (not my case though but assume it is) Would Wayland theoretically perform better in that case?
ps tip, try replacing libinput driver in xorg with evdev. I'm a bit fuzzy on the details, but as I recall, libinput sits on top of evdev as an added abstraction layer, and therefore will add some latency to input.
your xorg conf files will probably be found in one/both of these locations:
/etc/X11/xorg.conf.d/
/usr/share/X11/xorg.conf.d/
the conf files are loaded in priority order of numbering, 10 before 20 and so on, so make an early conf for keyboard and mouse, like 20-keyboard.conf and put this in:
Section "InputClass"
Identifier "My Keyboard"
MatchIsKeyboard "yes"
Driver "evdev"
Sorry that I can't remember where I got this from, I pour over too much stuff on a weekly basis to remember most of it when I'm done, but this gives you a start, hopefully, and with a bit of searching on arch forums etc. you should find some good further info.
My experience with it was that it lowered input latency. Snapping is fun, so hope it helps!
The situation has only gotten worse since, Wayland on Nobara now has higher input latency at the desktop aswell, beyond what is incurred by the V-sync, and the mouse cursor now stutters across the screen as though the polling and report rate have been greatly reduced.
When using X make sure to disable the compositor, to turn off V-sync.