0x0

Oh, okay.

I’d say around half of the games I play on Linux require some kind of special launch script, specific Wine version, or even different versions of Steam to run properly. It’s nowhere near as simple as people make it out to be.

Hmm, good question. I’d imagine they’re very similar (if not identical.) Don’t know, however. Mine is self-compiled from source, but when I tried Arch’s LTS package it didn’t crash either.

I believe 6.6 is the current LTS version. A similar crash to the one you describe in the OP started happening to me in the 6.7 kernel. If you check my posts, I have a writeup on it.

Try the LTS kernel. Fixed a similar crash for me.

Warframe at 28 is nice. The devs acknowledge Proton and even accept bug reports for those using it. Very cool chart overall.

Unlikely to help, but while you’re experimenting: PROTON_LOG=1 PROTON_LOG_DIR="/tmp/" WINEDEBUG="-all" fixed some extremely annoying hangs during loading screens for me. Probably a 1 in a million chance it helps in your case, but who knows.

The biggest red flag here is that someone is trying to derive meaning from Eva, an anime whose religious/philosophical imagery and themes were used “just because they looked and sounded cool” (not a direct quote.) I mean I like it too, but it’s gibberish.

I’ll say this about OSS and the community around it: It’s painfully obvious at times that while the individuals working on these projects (often thanklessly) are brilliant people, they often lack the communication and project leadership skills necessary to make a project thrive. The last few posts I’ve seen on this particular issue have been extremely vague and for whatever reason just won’t come out and say what they mean. They’re verbose, go off on tangents, and beat around the bush. We must first have explained to us the plots of TV shows, movies, and other ancillary things in order to understand what likely boils down to “people with differing viewpoints cannot find common ground.” I see the linked blog post as nothing more than someone trying to work out relatively complex feelings about the time/effort they contributed to a project they no longer have faith in more than an “expose-eh.” Given that people in the comments of previous threads have boiled the issue with NixOS down to a sentence or two, I think this is an accurate view.

See: Soft skills.

deleted by creator

Check out :set url.default_page and :set url.start_pages.

As I understand it, Wayland offloads a ton of stuff that was core to X11 (like input device handling) directly to the compositor. The end result is every compositor handling things differently. Compare something like i3 to Sway. Sway has to handle input, displays, keyboard layouts, etc directly in its config. If I switch to Hyprland I then have to learn Hyprland’s configuration options for doing the same. Meanwhile, switching from i3 to dwm requires only setting up the WM to behave how I want - no setting up keyboards, mice, etc. It just feels clunky to work with Wayland compositors, frankly.

Also when something breaks in Wayland the fix is almost always hard to find or incredibly obscure because the fix isn’t for Wayland- it’s for the compositor. If your compositor isn’t popular then good luck!

Both of them have issues depending on the setup. X11 has worked flawlessly in my experience. Wayland has worked the same for most.

Personally, Wayland still has some growing pains, especially in regards to Input handling (mouse, keyboard, etc). In X11 it was “trivial” to edit one file and have the settings stick across different WMs (switching from DWM to i3, etc.) There’s no standard for this with Wayland since it’s up to the compositor to handle these things, meaning you’re relearning how to do something as basic as setting pointer speed each time you try a new compositor. This is my only real fair gripe about it currently, as the rest of my complaints are just due to how young a lot of the Wayland-specific tools are - this will improve with time.

Yup, remove the installed drivers. Good luck!

X11 is, to put it simply, not at all fit for any modern system. Full stop. Everything to make it work on modern systems are just hacks. Don’t even try to get away with “well, it just works for me” or “but Wayland no worky”.

I really don’t know if there could be a more obnoxious opening than this. I guess Wayland fanatics have taken a page from the Rust playbook of trying to shame people into using it when technical merits aren’t enough (“But your code is UNSAFE!”)

Interesting read. I prefer C over any other language for game development. It’s cool to see people work with it and realize it’s still viable.

I’ve put a few hundred edits through this and it’s solid. I do deal with a persistent crash on clip import with medium/large projects, so I import clips -> save -> relaunch and it seems to work fine afterwards.