Hell Nirvana.9045
-
Posts
145 -
Joined
-
Last visited
Content Type
Forums
Blogs
Events
Articles
Downloads
Gallery
Store
Posts posted by Hell Nirvana.9045
-
-
On 5/26/2024 at 10:19 AM, CETheLucid.3964 said:
But it's been happening for a while.
It's been like that for maybe 3 months for me. And definitely became more intense since they split up the post-processing effects.
On 5/26/2024 at 10:19 AM, CETheLucid.3964 said:Recently got a new GPU.
Nvidia? AMD? Did you switch from one to another or stick with the same chip manufacturer?
-
On 1/16/2024 at 11:24 PM, Nemecyst.5437 said:
My guess is that pixman got handed over to a different maintainer who wasn't aware of the versioning scheme either.
The person who made the version bump doesn't have a lot of commits on the project, but the oldest ones are from 2021. Perhaps this was just a slip-up.
Edit: And an oopsie it was.
-
1
-
-
Or Arch could bump to the latest commit, which is 0.43.1, considered stable by the versioning.
https://gitlab.archlinux.org/archlinux/packaging/packages/pixman/-/issues/1-
1
-
-
In the end, it's just Arch packaging a debug build of pixman.
An interesting way to define your stable and development versions.
-
1
-
-
1 hour ago, zistenz.1945 said:
So the answer for everything is not 42 but 43? Those mices miscalculated something or it is a floating point rounding error...
Yes. Just because the meson.build file is at version "0.43.0", somehow causes these freezes.
This might go all the way to compiler, which would be GCC in this case.
-
14 hours ago, PzTnT.7198 said:
I'm hoping this will be fixed with plasma 6 if nothing else.
Pixman is a central library for pixel manipulation on Linux; it's not limited to Plasma.
4 hours ago, Sina.9208 said:It's easy to reproduce this crash on virtually any DE or WM config.
Yup! My money is on an obscure xorg bug that doesn't like the number 0.43.0 😂
-
Yup, that's what happens on X11. Proper hang in Wayland.
-
So... Arch still has the old version of pixman for 32-bit 😑
I've posted my current findings to the pixman issue tracker, after trying to build and load pixman myself.
Please, ArenaNet, stop relying on 32-bit in your game.
Edit: While I still maintain abolishing 32-bit, the actual problem seems to be quite weird. Having "0.43.0" as the version of pixman causes hangs, but changing the number (even arbitrarily!) makes all the hangs go away! I smell an xorg bug...
-
1
-
2
-
1
-
-
9 minutes ago, garpu.6210 said:
Something changed with the launcher, and something in proton needs to change to adjust for it.
But then the launcher would be broken no matter what, yes? Like I said, I can get the game working just fine with Proton builds I've used before. Since the issue gets fixed when I revert my last system update (which doesn't contain any Proton packages), it seems more like an issue with Arch. Or Proton team needing to catch up with whatever Arch did?
-
Shouldn't be a Proton issue, since it occurs with previously working versions, but breaks after system update?
I should've mentioned that I use Wayland. On X11, I can enter my password and enter the game, since only the launcher is frozen, and not the GPU. 👍 -
6 hours ago, PzTnT.7198 said:
Out of curiosity, what distros/DEs are you on if you got the freezing issue?
Manjaro and Plasma.
It's something in a recent package update that seems to cause it for me. If I revert the last update via Timeshift, the launcher works again.
17 hours ago, PzTnT.7198 said:i managed to start the game by clicking where the buttons should be to log in.
Didn't work for me and neither did pressing Enter. Can't even switch to another TTY. Seems me and @Catory.3954 have the same issue. Seems like the GPU hangs when the launcher is supposed to appear. Mine is 7800 XT.
-
Looks like I can't get the game to work after today's update.
My whole desktop environment freezes when the launcher is supposed to appear. I've tried different clean Proton prefixes, and even tried dropping from kernel 6.7 to 6.6 🤔
-
1
-
-
I've upgraded from Nvidia's 1080 Ti to AMD's 7800 XT, and running the system pretty much exclusively on Wayland at the moment.
One quirk I have at the moment is that if I switch away from the virtual desktop GW2 is running on, it starts to render slower. Not just lowering the frame rate, but literally slows the game down. When I switch back to the game, it fast-forwards to catch up to what state the game is supposed to be at...
Apparently an upstream bug that's hopefully fixed in Plasma 6 🤞
Edit: I managed to find out how to fix my forced 12-hour clock, by setting HOST_LC_ALL=<your locale here> in my launch parameters for the game on Steam. Proton prefixes default the locale to en_US.utf8
Edit2:
It seems the slowed down rendering when in another virtual desktop seems to be fixed now.It's in fact caused by the in-game vsync 😐 -
Having separate preferences for Dailies and Weeklies would be perfect. I don't want to dabble in WvW on a daily basis, but do with my guild once or twice a week.
-
1
-
-
21 hours ago, Sina.9208 said:
Run 'qdbus org.kde.KWin /Compositor suspend' to temporarily turn off the compositor. See if that helps, if it does not, then experiment with fps limits. (the sweetspot for my 60hz monitor is 47-48)
I've experimented with allowing applications to block compositing for a few days. Seems to work (even let's me utilise Adaptive Sync), but the blocking doesn't seem consistent. Sometimes compositing stays on when the game is launched, other times it re-enables itself (inconsistently...) if I switch between virtual desktops.
-
44 minutes ago, DemiurgChaos.8643 said:
Why don't work WvW weekly achivment Tower Guardian, my balist destroy enemis catapult, and I didn't got achivment? 😡
That is because qualifying for defence means you have to kill another player in the area 😞
-
On 7/2/2023 at 1:33 AM, Hell Nirvana.9045 said:
I'm now often getting screen tearing in the middle of the screen. Goes away for some time if I open and close the Steam overlay or switch back and forth between virtual desktops. Goes away on its own sometimes, even. Probably another Plasma oddity...
Even opening the world map seems to eliminate the tearing 🤔
-
I'm now often getting screen tearing in the middle of the screen. Goes away for some time if I open and close the Steam overlay or switch back and forth between virtual desktops. Goes away on its own sometimes, even. Probably another Plasma oddity...
-
On 3/14/2023 at 1:49 AM, Veprovina.4876 said:
KDE seems to have some messed up locale settings lately. Some other programs are also giving me "unable to set locale" warnings or something like that (they work fine though).
Eh, they'll fix it i guess...
Did this ever get fixed for you? Mine's still in 12-hour mode :C
-
Interesting. I'm also in the client beta, but for me, /wiki opens up the Wiki in my default browser, Firefox.
-
For me, the transition to CEF has been quite painless.
I only have some wrong fonts being used in the Trading Post. A font called Menomonia isn't rendered, and replaced with a fallback, it seems. Looks similar to New Times Roman. -
There's gonna be take three.
Back to CoherentUI:-
1
-
-
On 3/5/2023 at 3:00 PM, Veprovina.4876 said:
I'm on 5.27.2...
Same here.
-
Seems some KDE Plasma update today has made it so that GW2 shows the 12-hour clock for me, no matter what my system locale settings are.
Playing Guild Wars 2 on Linux - Performance optimizations and more.
in Account & Technical Support
Posted
Ok, so the bug being tied to a GPU is very unlikely.