I think I can subtly feel it even without antiping? If I stack ontop of my dummy and then spam hook directly up, I still feel like I'm very lightly being hooked, depending on the bounce.
02:34
I feel my dummy hooking me from the weird copy thing going on ^
Even without copy being enabled(edited)
02:37
Ya, you can test this yourself, it's predicting that you're being hooked by your dummy even without antiping. If you stand to the left of your dummy, then hold hook while aiming left, you'll feel your dummy spam hooking you (your screen will vibrate)
02:40
I would avoid using latest nightly to play, even if you're not using antiping feels weird
Reported by @l-ouis on discord. It happens with a gore map when approaching some area in the map. Here's the crash report DDNet-Server_crash_log_101744_2022-05-31_18-09-30.txt I couldn&...
This is the third day. Every day, I break down and get stuck Now my game is normal I tried to repair some operations in the registry and restart the computer
This is the third day. Every day, I break down and get stuck Now my game is normal I tried to repair some operations in the registry and restart the computer
Until Git version 2.20, and unlike when pushing with git-push[1], any updates to refs/tags/* would be accepted without + in the refspec (or --force). When fetching, we promiscuously considered all tag updates from a remote to be forced fetches. Since Git version 2.20, fetching to update refs/tags/* works the same way as when pushing. I.e. any updates will be rejected without + in the refspec (or --force).
5 8 ms 7 ms 8 ms 81.253.184.178
6 7 ms 7 ms 7 ms 193.251.131.0
7 * * 7 ms 81.52.200.156
8 7 ms 7 ms 7 ms netzbetrieb-1.gw.opentransit.net [193.251.255.182]
9 20 ms 19 ms 21 ms ae1-2014.nbg40.core-backbone.com [81.95.15.206]
10 19 ms 19 ms 19 ms core-backbone.hetzner.com [80.255.9.22]
11 * 25 ms 22 ms core23.fsn1.hetzner.com [213.239.245.10]
12 21 ms 21 ms 21 ms ex9k2.dc6.fsn1.hetzner.com [213.239.229.82]
13 21 ms 22 ms 22 ms static.238.114.9.176.clients.your-server.de [176.9.114.238]
are there currently known issues with wayland (nvidia drivers)?
for example opengl is failing, while vulkan works but inputs in the UI and chat are buggy and take input hardly (also search input is showing [] as cursor for some reason), in-game movement works fine
I can open an issue with more details if it's not something unsupported
Xorg doesn't have this issue
the issue is with both nightly and the repo version for Fedora 36 (which is 15.9.1 and has no vulkan support so it doesn't start at all)
context: Fedora 36 added the ability to use wayland with nvidia graphics(edited)
feels weird
1
1
