More or less yeah. My PS5 controller has stopped working via bluetooth (on basically all my machines) until I applied a firmware patch using a Windows only tool. Other than that, it's been my preferred controller, and the PS4 controller was before that. I don't like the internal lithium ion batteries in them though. I've had to replace 3 of them between the 2 controllers in the ~8 years I've had them. Xbox controllers just take regular batteries with is pretty handy. Though I've had the same suddenly-stopped-working-on-bluetooth-until-you-update-the-firmware issue on those as well. -_-
slembcke
joined 1 year ago
OBS Studio mostly. It's not the most convenient for a quick screencap, but I can record 720p@60 fps video downscaled and resampled from my 1080p@144hz monitor and it just kinda works fine. The other nice feature of OBS is that you can have it recording all the time and then press a button to dump the last few seconds when something interesting happens. Handy when trying to get interesting clips of my game. For quick recording I usually just use Kooha or the built in Gnome one.
I've been using Wayland daily for a few years (2020 at least?) on intel and AMD graphics and have had few complaints:
- Some games didn't work right a few years ago. (Under Proton or otherwise. Haven't had issues for a while)
- RenderDoc, a vital bit of graphics debugging software, works poorly on Wayland. (Easy fix is to force X11 for QT via QT_QPA_PLATFORM=xcb)
- Had some issues with mixed integrated/NVidia graphics on a laptop I was using for a demo once.
- Covering or otherwise hiding a Wayland window blocks a program's graphics thread. This is sometimes problematic.
- VR development had issues a while ago? (This was for work. It just... stopped working at some point. Dunno if it was a Linux, SteamVR, or Unity3D issue. My work machine mostly runs Windows 10 now as a result. Oh well.)
- Screen recording didn't work well a while ago... (continued)
Overall, it's just worked great though!
My anti-complaints:
- Mixed refresh rates on monitors "just works" now. (I have a 1080@144 for gaming, and a 4k@60 for work)
- Video frames don't have half drawn content. (ex: when resizing windows), except on XWayland stuff
- Video tearing has basically disappeared.
- Video timing issues seem to be improved.
- Input handling for keyboard layouts has improved.
- Screen recording in Wayland is way better than it ever was on X11 now. I do this a lot to share gamedev stuff I'm working on.
I was certainly behind the curve here, but Horizon Zero Dawn! I was expecting some vagely Zelda like adventure RPG (and it was), but the story was so much more compelling than I expected. What a memorable game! I even got a second hand PS4 to play the sequel on... which I haven't for like 6 months now. >_< (Too many other things to do!)
Ooh. This one looks great. I'd parrot an excuse about how I "don't have the time", but that will always be true until I make the time.
A bit of a zombie thread, but I'm not making anything up here. The blocking issue gets discussed a lot in gamedev circles, and there are issue threads that have been locked by folks with the power to do so because they just said "no". One of them (Maybe Sebastian Wick? I don't remember... doesn't really matter) gave verbatim that use case where a video service they use would stop playing videos when the browser was in the background, and that is why they won't report . Maybe they weren't a "core" developer, but they had the ability to say "no" and end the discussion thread.
As for it being not a problem anymore, it still occurs even on Fedora 39. The 1 second present timeout still only works for XWayland, and that's... not a great solution. Also, realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don't have the time to worry about what GTK, Qt, or XDG shell does. We are already supporting multiple rendering APIs, and combining that with multiple UI libraries just to get a window to draw a triangle into is a combinatorial explosion. Last I remember reading from the SDL folks, they were waiting for the functionality to appear in Wayland before they could implement it, and they weren't expecting anything to change soon either. Speaking personally, my current game project is single player so I can just pave over the timing issues when they come up:
Long frame detected: 6463.731931 ms. Skipping ahead!
The most frustrating part to me is much more meta. You get discussions with other game devs that have heard about this stuff and they continue to think that supporting Linux is just way too much work. Sometimes they are right, but rarely for the right reasons it seems. I believe in the glorious Wayland future... I just wish it would get here a bit faster. ;) On the other hand, if we rushed it and botched it then it would never arrive at all I suppose. (sigh)
As for how window activation works, you got me there. I just heard other people discussing that one, but it did explain why on Wayland I would just get "Firefox is ready" notifications when opening links instead of just showing me the page like X did. Though I'm quite happy that it's gone now in Fedora 39. Progress is good!
Yup, don't. People already covered why. I will add that I tried learning dvorak for quite a while and it didn't stick until I went cold turkey. It was very frustrating hunting and pecking for a couple days, but I made pretty quick progress. IIRC I was back up to 20-30 wpm after a week which was "usable" at least, and back to 60-70 wpm after a month. I had regular wrist pain before switching, and it was basically gone after. I don't think it helped my typing speed. Like I can do 90 in bursts for a bit longer, but generally I "cruise" much slower than that. ;)
People keep saying this, but X forwarding seems to work just fine with XWayland. I just tried a handfull of X programs between my machines, and neither are running X11. I don't use it everyday to know the gotchas, but there you go. Programs that use shared memory pixel buffers (everything that isn't xeyes realistically) even run better than I remember now that I have gigabit. >_< It's still a way worse experience than VNC or RDP though.
Wayland is great! Except for all list of not-a-bugs that I'd like to see fixed. Still, I'm not going back to X, so take that how you will.
What are the not-a-bugs? Things like covering up a Wayland window will block it's rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don't want applications to know if their window is visible or not because it's mild information about a user's attention that should be private. Every game dev on the other hand is asking "WTF!?" as it causes their games to break randomly.
Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can't pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can't open and focus URL in your web or file browser. Instead they have to give you a notification telling you "Firefox is Ready" and make you do it manually.
A lot of this is slowly (painfully?) changing, and the adversarial nature is a bit frustrating. Wayland fixes so many little things that I find it well worth it though, and I say that as a game developer frustrated by many of the core design decisions.
Both the PS5 and Xbox Series X controllers are very good. I've had some incompatibilities on my computers with older bluetooth hardware though. Speaking practically, I'd recommend the Xbox one as it's slightly cheaper, takes regular replaceable batteries. Subjectively, I prefer the PS5 controller (I like the feel, and the trackpad is really handy), but I've already had to replace the lithium ion battery in mine. (Had to do the same with my older PS4 controller too)
I really like plain "boring" vanilla Gnome. It's straightforward, I like it's workflow, it does everything I need it too, and looks nice too. I'm not a fan of "power user" UIs as I feel like they have too many features I'll never use filling them up. You can always get more programs to do more things anyway. Like I use compilers and disassemblers all the time, but I'm not upset that Gnome doesn't ship with those features built in when I'm in some weird 1% of users that need them. On the other hand, I think KDE is important to the ecosystem too, and I donate $100 a year to both the Gnome and KDE projects.
I had a 10th gen S76 Lemur. The hardware was a mixed bag. Chassis was nice and light (compared to Apple), but enameled so the edges eventually chipped. Keyboard/trackpad were average. Speakers were awful... Battery life was excellent like usually got around 20 hours on a charge (and often more with a little effort!). I also had a number of hardware failures and dealing with their support was pretty terrible... Broken control key out of the box, Wifi died twice, second time they replaced the motherboard (and that took like... 9 weeks), then it completely died a year later when it was finally out of warranty. A real mixed bag of Pop OS being nice, and having great software/firmware support, but also multiple hardware failures coupled with terrible warranty support.