Linux gamer, retired aviator, profanity enthusiast

  • 20 Posts
  • 1.12K Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle


  • For new users, if it doesn’t exist in the repos, you’ve gone too far.

    I don’t think this holds up under scrutiny. Theoretically sure, installing using your distro’s package manager is the beginner skill, compiling from source is the advanced skill.

    The reality is, people transplanting from Windows often own hardware they want to continue to use, that require software that isn’t in a distro’s package manager. For me, this included a DisplayLink docking station, an Epson printer and a SpaceMouse. For some, it will include gaming keyboards or mice, stream decks, who knows what else. A lot of times, there are folks making open source software for these things, but they don’t package them. So you end up on Github as a beginner looking for the thing to make your thing work.

    As you migrate into the ecosystem, you start buying hardware that is well supported by the Linux ecosystem, that problem starts to fade away.

    by rpm vs deb, I wasn’t meaning downloading individual files…though I’ve done that. DisplayLink offered their driver as a .deb. At first, that Epson printer only issued a .rpm, and I had to use Alien to install a .rpm on a Linux Mint computer. With time, they offered a .deb, and eventually the printer was just natively supported by CUPS. I meant, I find that the Debian/Ubuntu repos (the dpkg/APT system that uses .deb files) have more stuff in them than Fedora’s repos (the DNF package manager that uses .rpm files) do.

    Does Mint still not use Wayland?

    When I built my current PC, Wayland support in Mint Cinnamon was “We’ve just now added it, it doesn’t work worth a damn but you can try it.” They’re coming along, but they’re behind.

    Is an older codebase generally good for new users? The first distro I installed on an x86 PC was Mint Cinnamon 17. Quiana. On a then brand new Dell Inspiron laptop. For about 6 months, the kernel that shipped with the OS didn’t support the laptop’s built-in trackpad. I had to manually update the kernel through Mint Update for the trackpad to work. There’s problems at the bleeding edge, but there’s problems at the trailing edge as well.



  • At least some of the problems I reported about Bazzite are inherited from Fedora. Bazzite didn’t create Anaconda.

    Fedora has the problem of being generally fine, but most of the world for the last decade has been targeting Ubuntu as THE Linux distro, so there’s a lot if Git repos out there that don’t include instructions for Fedora. Way fewer things are packaged in rpm rather than deb. I’ve never seen Linux Mint kernel panic unless I was fucking around with the video drivers, I’ve seen Fedora kernel panic.

    The main reason I’m using Fedora right now rather than Mint is Mint tends to have an older codebase, and we’re at a point in PC technology where things like wayland offer support for video and graphics stuff that don’t work well under X11. like my 1440p ultrawide 144Hz monitor sitting next to a 1080p 60hz side monitor. Fedora KDE has it ready to go, Mint Cinnamon does not.


  • Bazzite offers KDE or GNOME, and in the menu mentions KDE is what is used in SteamOS.

    I installed Bazzite on my HTPC recently. It was the worst install process I’ve seen in over ten years of using Linux. I shall enumerate the problems I had:

    1. The image is weirdly large, it’s like 9GB in size. It takes awhile to download and a weirdly long time to write to a USB stick.
    2. Once written, you boot the image, and GRUB has the options to Install Bazzite or Test Media And Install Bazzite. By default, Test Media is selected. It always fails this test.
    3. If you use the typical non-live environment image, the scaling is tiny on a 4k monitor, and there’s no way to adjust this.
    4. If you use the live environment image (in beta at time of writing), it might just lock up. I had that happen twice just while clicking through the Anaconda installer.
    5. The Anaconda installer, which I think they inherited from Fedora, was I think designed by one of the contrarian idiots who work for Gnome. There’s a DONE button up in the far upper left hand corner of the screen that sometimes acts as a back button, sometimes acts as a forward button. You have to move the mouse from the top corner of the screen to the center of the screen a lot, for no reason. The top-left corner of the screen is a dumb place to put a DONE button because most languages read top to bottom, left to right, the DONE button is where a START button should go.
    6. There isn’t a simple way to tell it “put / on this drive, put /home on that drive.” There’s an automatic installer which will do god knows what…fail, most likely. There’s a “custom” partition dialog which I couldn’t make heads or tails of, and then there’s a “custom advanced” one that lets you set the size and position of each partition to the byte. Doing it this way apparently REQUIRES you to not only set up a /boot/efi partition, but also a /boot partition separate from /root.
    7. If you’re in the habit of putting /, you know, operating system and software, on one drive, and /home on another drive, you have to learn from osmosis that part of Bazzite’s immutableness means that there is no /home, there’s a /var/home symlinked to /home.

    And if it doesn’t randomly lock up, you’ve got Bazzite installed!

    Bazzite markets itself as a newbie friendly Linux. They’ve got that configurator on their website that gives you a little Cosmo quiz about what system you have, what desktop you want etc. which is good! That is good user friendly design. But the actual software you get rattles like a Chrysler. How many noobs are going to bounce right off that?







  • I don’t think that’s true. Take Little Rocket Man, that achievement is a special challenge run that encourages people to replay through the game, probably after they’ve beaten it naturally, and then they see that achievement in the list and they get some more fun playing through it doing this weird thing.

    Subnautica’s achievements are pretty much all on the critical path, only two (launching a time capsule during the end game sequence and hatching a cuddlefish) are reasonable for a first timer to not do. These serve more as useful metadata for both players and the developer. For example, the achievement “Get your feet wet” stands at 88.7% of players have gotten that achievement. 11.3% of players have played Subnautica but haven’t gotten into the water? You can look at the achievements in the order a player would probably do them, and you can see where players tend to fall off, and in fact it makes 100% sense to me why it does where it does. If a lot of players start the game and get early achievements, but there’s a sharp drop in the mid-game where players fall off, maybe you need to look at the mid-game, especially if it’s an early access title like Subnautica was, or you can learn from how players interact with this game and apply that knowledge to your next one.


  • Breath of the Wild does it both wrong and right.

    Weapons in BotW are almost like ammunition. A given sword or club or whatever does so much damage per swing, and will last a certain number of swings, so it represents an amount of damage you can do to an enemy. This system is at its best when you break a sword over an enemy’s head, pick up his weapon, and then keep beating him with that. Problem is, there’s only so cool weapons can get. Players that want to work hard to get a really cool weapon don’t really have a way to both play with it and keep it around. Hell, the Master Sword breaks and grows back.

    BotW does it right with shields. Shields have a use case, and an abuse case. If you do a perfect parry, your shield takes no damage. Same thing happened in Skyward Sword, if you abused your shield too much, it broke. But if you used it correctly, it wouldn’t break. If you built use cases and abuse cases for weapons, for example, bashing a sword against an enemy’s shield would wear it out, but striking soft flesh wouldn’t, that would reward players for learning the combat system by giving them a way to keep their coolest swords around.

    TotK…Youtuber Skittybitty did a 3-hour takedown of that game and I could add at least two hours of my own criticism.


  • Eh, these can be implemented well or badly.

    Look at Subnautica’s achievements. There are seventeen total, seven of them are triggered by events required to beat the game, 5 are triggered by non-required but main path “players will do this” story beats, and 3 are “engage in a major advertised featuer that are technically possible to skip.” The last two are “play with this little bonus feature we included.”

    I’m quite fond of a couple achievements for Half-Life 2 Episode 1 and 2, which are basically challenge runs. “The One Free Bullet” which challenges the player to beat the game having fired only one round from a gun (the crowbar, grenades, rocket launcher, crossbow I think, and gravity gun don’t count as “bullets”) and Little Rocket Man, an achievement for carrying a garden gnome from the beginning of the game all the way to the end and placing him in the rocket.

    Possibly my favorite achievement in all of gaming history has to be in Portal 2. At the beginning of a chapter, PotatOS says “Well, this is the part where he kills us.” And you land on a platform surrounded by spikes and Wheatley says “Hello! This is the part where I kill you!” And then the chapter heading reading “Chapter 9: The Part Where He Kills You” flashes on screen. And then you get an achievement for “The Part Where He Kills You: This is that part.”


  • I’ve been looking into robotic lawnmowers, and they’re basically the same. The more primitive ones have a hall effect sensor under their snout feeling for a wire you bury around the edge of your yard, and do the “go until you hit something, turn a random amount, repeat until low battery, follow perimeter to dock” or they require phoning home in some way, shape or form.

    Meanwhile, some guy’s got an open source system that runs on a Raspberry Pi on the mower itself.

    I guess I’m willing to believe that some of the LIDAR or camera-only guided mowers need some serious processing power to create the maps they use for guidance around the yard, and that’s more practical to do on the company’s servers than on the device itself…except not really; we’ve got decently powerful ARM SoCs that don’t cost much, don’t take a lot of power to run, and can do that job. The reality is, you can’t get a pedometer app for a smart phone that doesn’t broadcast sensor telemetry to two continents these days.