Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DR
Posts
0
Comments
106
Joined
2 yr. ago

  • A gallon glass carboy is $20-25 and that's going to be your biggest up front expense. That's reusable, however so once you've got that you're not going to need another for simple small batches. Champagne yeast is like $10-20 for 10-20 packs (figure a dollar per pack) and each pack can easily make 2 gallons if you're smart enough to split it in half. 3lbs of raw honey from Costco will run $12-15 and a gallon of boiled water rounds out your list. Yeast nutrient is probably a good idea since it almost guarantees good results (1lb is like $10-15 and you only use 1/4 tsp or so per gallon batch). One-way air locks for brewing with stoppers are $2-10 depending on how many you buy (also reusable). So your first batch is your most expensive at $85 absolute worst case with today's prices. From there on out subsequent batches cost only the honey, water, and any fruit or spices you want to try adding. As far as hobbies go, that's not bad considering how much variety there is in it. I can't comment on beer, but mead is dead simple as long as you keep everything sanitized before and after brewing.

  • As someone who makes meads/wines in a closet and has done so while renting, I don't particularly see the relevance as long as your batches are small and contained... Typically, the tools and ingredients aren't wildly expensive either if you're keeping things simple (in the US, anyways). Honestly, I don't see how more demographics don't get into the basics of homebrewing. It's dead simple to make something "passable" and with time and effort you can even make something good/great!

  • I have personal experience with BTRFS and Windows. And that experience is that it's roughly as stable/complete as NTFS is for Linux. 6 of one and a half dozen the other. I can't recommend either situation for guaranteed stability long term between systems if one really needs to swap between the OS's frequently while accessing all the same files.

  • Tribes 3 was missing all the secondary objectives stuff that made T2 so much more accessible. Even if you weren't snapping crazy midair shots or cruising through fast flag caps you could still contribute via base attack or defense, vehicle support, etc. It felt like a crazy mix of arena shooter and early Battlefield games.

  • They actually had a neat solution to that in the form of some basic bots to help fill in for under-queued matches. Not too different from what Splitgate had going on (man, I miss that one too!) It gave beginners something to chew on a little bit. Would have been nice to have custom server options to tune bots and matches, like in Tribes 2. Apparently that kind of thing is simply too much to ask for.

  • To say that EVERYONE saw this coming may be an understatement. The moment the devs teased taking out the Honorball game mode and spinning it off into a completely separate game, the writing was on the wall. Possibly my favorite shooter series and it seems to be stuck in development purgatory. Even the unofficial Tribes-likes and other FPS-Z games can't ever seem to find their footing.

  • Weird! I'm running Bazzite kde (so fedora based, like Nobara but with different tweaks and it's atomic), and gamescope gives me zero problems. Might be some weird combination of software versions between gamescope and kde in your system. Or just a general kde config problem. I love kde, but all that customization can absolutely come at the price of stability at times.

  • Interesting. I haven't had any issues with gamescope for a long time... Back when it was new I definitely had issues running things with it... But it's been a long time since that's been the case. I can recommend running steam from a terminal and viewing the output after trying to run the game with gamescope. It might point you in the right direction.

  • Should be something like - "gamescope -W 1920 -H 1080 -f %command%" I will also note that mine tends to crash/not launch if I don't put Mangohud arguments BEFORE gamescope. The w and h arguments are just width and height resolution, so set those to match your monitor. The "-f" is for full screen.

  • In my experience this is almost always the compositor not properly syncing display frames with the game render frames. The best solution I've personally found is to run the offending game through game scope. It worked for Fallout 4 on my rx 7600xt gpu when I went to lock the fps to 60 (to avoid physics bugs, stupid Bethesda). Without game scope locking the frame rate caused horrendous stuttering despite solid fps.