bigmclargehuge @ bigmclargehuge @lemmy.world

Posts

6

Comments

333

Joined

2 yr. ago

I'd be willing to use flatpak if all else fails. I've had lots of wierd issues with flatpak that overall have me leaning away from using them if at all possible. I generally prefer using native programs unless there is literally no other option.

I use jstest-gtk. Really light handy tool for testing and calibration. Antimicrox also works great for rebinding controllers.

Yeah im not sure about audio. I'm using pipewire and it seems to work fine OOTB with both the built in Quest 2 speakers, and my sound card audio

Adding a little update. Recently reinstalled my system as things were getting cluttered. For some reason, I was unable to install ALVR (or the git version) from the AUR. When building the AUR package manually, I'd get to 99% and the terminal would just close, yay resulted in the same error.

However, the portable .tar release of the latest version works perfectly. Performance is even better, I've had fewer bugs/connectivity issues, and once I followed the official Settings Tutorial and this article on how to disable SteamVR Async Reprojection things have been working 99% as well as they were on Windows. I have noticed occasional quality degradation, but it was never detrimental to the experience overall. And, it's worth noting that ALVR can function over USB with a link cable, so that should eliminate any issues caused by wireless streaming.

Just thought I'd report my experience and hopefully give some folks a push to try it out. This is a huge step for the overall Linux experience IMO, as it's very quickly opening up an entire aspect of gaming/computing in general really that, until a few months ago, was effectively not viable outside of Windows.

As a few others have said, most distributions are good for gaming. Arch, being a distribution that requires lots of manual configuration, requires some setup for the best performance.

Read these two articles throughly and use the tweaks that apply to your system/needs.

Straight from the Arch Wiki:

Improving Performance

Gaming (section 7 and section 9 are especially useful).

There was never really "a burning" that destroyed it in one go. Over many years, there were numerous factors that caused many of the works to be lost. Some were lost to smaller fires, some were stolen, some just disintegrated due to age. If no one bothered to copy them by hand to have more than one copy, that was that.

If you reset all theming options to default (icons, window decorations, colors, etc), and backup your config files, there should be no issues upgrading to KDE6. Keep in mind though, most themes for KDE5 don't work for 6 unless the author updated, or you're willing to manually modify a couple files. Most icon packs should be available though.

I'm personally not a fan of any universal packaging solution. I've tried flatpaks, appimages, and snaps, and ran into weird, annoying issued that I just never have when I install via package manager, build from source or even just run a portable build of an app.

I see the appeal of a universal package, but imo a bigger emphasis on portable native builds would solve a lot of the issues these packaging solutions are aiming for, while not introducing many of the downsides

In an age where everyone rags on live service games that will inevitably lose support, a cheap, fun, well made, feature complete game (and was that way on release) that gets infrequent updates is "abandoned" and "insultingly barebones". Classic 2024 gamer moment right there

My biggest thing when switching to Linux was understanding why I didn't have permission to alter half of my file structure. I was trying to takeownership of my /usr directory as a user and had to have multiple people explain why that was a bad idea (and why simply making any changes as a super user via terminal was more than adequate for the results I wanted)

My mindset was a result of so many user files being spread across dozens of branches of the Windows file structure. Some very close to the root of the drive, some a few directories deeper.I didn't really understand the benefit of having all my stuff in /home

Yes I did a decent amount of research on their PSUs, I managed to get one with a pretty solid reputation.

And I'm on Linux and use a community made software suite called CKB-Next, so I haven't had to deal with iCue in a couple years thankfully

Have it on GOG and play via heroic. I get 80+ FPS at high settings @1440p (balanced FSR), AMD R7 5800x, RX 7600XT. This is on Arch.

I had to use winetricks to install some DLLs to the prefix in order for the game to work properly with mods, but beyond that I've had no issues.

Edit, I just reinstalled the game yesterday. Installed via heroic, set my wine version to Proton experimental. Set my launch executable to Cyberpunk2077.exe, rather than the launcher (launcher was just a black box for me). Opened winecfg from heroics settings for the game, went to the Libraries tab, and added version to my list of installed libraries. That can be typed in manually, or picked from the drop down. After that, the game works as expected, and most mods I tried work (unfortunately, a resource called Codeware that a lot of mods rely on seems to crash my game. However, I only have a handful of mods, and none of the ones I use need it).

I have to say i own a decent amount of Corsair hardware (kb+m, RAM, SSD and PSU), and none has ever given me an issue. Most of it I got a few years back so maybe that was before they declined?

Compared to Razer, where I've owned 3 mice and all of them failed one way or another. Decent keyboards though.

Some Android phones can already be dual booted with (in theory) any other UEFI compatible OS. There's a whole guide on the PostmarketOS about setting up a dual boot environment.

I briefly tested PostmarketOS on a OnePlus 6T. The core functions seemed fine but overall it lacked functionality, so my plan was to dual boot with LineageOS (a degoogled android project) for the bits that really just want a true android environment to function properly, and PmOS for everything else I could manage. In the end I just wasn't up for the process of setting up a dual boot, and went with just LineageOS. Been really happy with it so far, and will probably revisit dual booting when PmOS is more feature complete.

Edit, I suppose this doesn't touch on the idea of running two separate OS's on separate chips, and it does require a reboot to get the functionality of one OS or another, but besides that hiccup you'd get mostly the same functionality out of less complex hardware.

Well I'll be, I humbly stand corrected. I will don the dunce cap for this one

How to actually get games running:

Download steam, make an account, log in. Go to the settings, find "Steam Play" and enable for unsupported titles. This enables Proton, which is a customized version of Wine, a Windows-Linux translation layer, plus some extra tweaks specifically for gaming. This lets you play the vast majority of all Windows games on Steam on your Linux machine.

Check out protondb to find out how compatible your chosen game is. You'll see a rating, as well as user experiences on how well it worked, what issues they experienced, and the tweaks they made to mitigate them (take note that there is a section on each games page that is specific to the Steamdeck, Valves handheld. Not all info in this section is relevant to general PC users, so make sure you follow the more generic section).

If you look around and find a specific game that isn't on Steam, Heroic Launcher and Lutris are your friends.

Heroic is a very nicely polished launcher for Epic Games, Amazon and GOG. It allows you to pool all three into a single library. You can use tools like winetweaks directly in the launcher, pick different Wine/proton versions per-game, etc. I'd use this as a secondary option to Steam.

Lutris also allows you to pool your games from multiple storefronts into one (Steam, Epic, EA, Ubisoft, GOG, and manually installed). Lutris can be a little complex compared to Steam and Heroic. It's very powerful, but somewhat spartan and can also be a bit buggy in some specific instances. It's very well suited for older games that aren't on major storefronts, emulators, or old CD games, mainly thanks to its option to set games up via standard windows installers or add existing games by pointing lutris to their installation path.

TL;DR, Start with steam, try some cheaper/free games. A great starting point would be Valves own games, as they're cheap and heaps of fun (Portal, Half-Life, etc). They also usually have a Linux native version so you don't need proton (although, counterintuitively, I find Linux Native games often don't work as well as Windows games+proton). After you get your toes wet, go for some other storefronts and library apps. Have fun and good luck, don't be afraid to ask for help.

Well thats the thing, generally if I see an acronym and have to ask myself how it would be pronounced as a word, by my rule I just spell it out.

For a great example of this (unrelated to FOSS), look at LGBTQIA+. Even though it's a mouthful to say each letter individually, no one wrestles it into "Leguhbuht'kwia plus", it just doesn't make sense and saying it that way would probably ellicit a dead stare from whoever heard it. Unless it's painfully simple to morph into a word or single syllable, I don't bother.

I'm not trying to say this is the right way, mind you. It's just the way that makes the most sense to me.

No. I've never seen an english word resembling this type of spelling, so I just say each letter.

To each their own, imo my way reduces the risk of confusion. There's no way to misinterpret what I mean when I say G-N-U rather than g'nue

I have a rule about acronyms: if the spelling makes sense to be said as a word, I follow the English grammatical rules. A word that's spelled s-u-s-e would be pronounced "soos", so that's what I say.

This is why I don't pronounce GNU as "ga-noo", it doesn't make sense as a word. In those cases, I just spell them out.

Find the .desktop file for the desired program (should be in /usr/share/applications) Right click, properties, then somewhere in that window, it should show the exact command that the .desktop file invokes when launched. In that command should be the actual program name (ie, /usr/bin/firefox-esr, firefox-esr is your program name).

Alternatively, right click, "Open With", choose a text editor, then you'll see a couple lines of information. One of those lines of info should be that command as well.

Edit, to be fair, I'm also not a fan of Gnome's obfuscation of program names. It may make sense for very new users, but I also found it counterproductive in certain use cases