I take my shitposts very seriously.
In general, you don’t need to install or update DirectX since it’s implemented outside Wine through dxvk or vkd3d. For other components (e.g. .NET or Visual C++), you should use Winetricks to automate the process:
List available components:
WINEPREFIX=/path/to/game/prefix winetricks dlls list
To install a component (e.g. Visual C++ 2015):
WINEPREFIX=/path/to/game/prefix winetricks vcrun2015
Do not delete the thread if this answers your question.
This is my method for GOG and other offline installers.
To run the installer, I use GE-Proton9-27. Something happened with Wine 10 and some installers completely freeze after a few seconds. Wine 9 still works well enough.
Create a directory for the game’s prefix:
mkdir -p /path/to/game/prefix
Then run the installer with Proton (assuming you’ve installed GE-Proton into Steam’s compatibilitytools.d directory):
WINEPREFIX=/path/to/game/prefix ~/.local/share/Steam/compatibilitytools.d/GE-Proton9-27/files/bin/wine /path/to/setup.exe
Then install the games to the C: drive.
I like having my games installed outside the prefix (e.g. another directory mounted as the G: drive, or an absolute path in Z:), but for some reason, lettered drives other than C: are mounted as some kind of union filesystem where changes are only written into memory. If you want to have a game outside the prefix, you’ll still have to install it to C: and move the directory afterwards.
You’ll then have to set up a launcher to manage and launch the actual game. I recommend Faugus Launcher, but Heroic and Lutris are also options. The two most important fields to set are the prefix and the executable path. In Faugus and Lutris, you can set those paths when you add the game. Heroic creates a separate prefix by default, but you can set the prefix math manually in some sub-menu.
You can select the latest Proton (or GE-Proton) to run the games, downgrading to Wine 9 was only necessary for the installer.
This worked perfectly, thanks a lot! I’ll update the main post.
I’ll try it as soon as I get home.
It makes sense, since Wine uses SDL2 to emulate XInput.
(edit) I’m cautiously optimistic. I’ve just tried this on my work PC (without SISR):
SDL_GAMECONTROLLER_IGNORE_DEVICES='0x28de/0x1304' wine control joy.cpl
…and XInput doesn’t detect the SC. It should still receive inputs from the emulated device since it uses different a different PID/VID.
Are there any good indie games on the world’s largest video game store? I dunno, are there any leafy trees in the Amazon?
From what I’ve been playing: Stardew Valley, Factorio, Vampire Survivors, Derail Valley, A Hat In Time, Project Wingman, Frostpunk 1 and 2, Portal 2 (technically self-published), Signalis. Voices Of The Void will eventually have a Steam release. All of those games work well on Linux.
Yes, it’s recognised as a controller both in non-Steam games and in other applications like KDE Settings. It works just like any other controller with the usual, quasi-standard inputs (analog sticks, face buttons, etc). Steam support regarding non-Steam games:
Everything should work as intended if you have purchased and launched your game directly through Steam, but in many cases you will also be able to use the Controller with non-Steam games that run independently.
I’ve heard the argument that it is recognized as a KBM if you’re not on Steam.
If Steam isn’t running and there are no other games that capture the controller input, the SC enters “lizard mode” where it emulates mouse and certain keyboard inputs. The right touchpad becomes a mouse, the left touchpad becomes a scroll wheel, R2 is left click, L2 is right click, A is Enter, B is Escape; wev displays the correct input events. Lizard mode is disabled when you launch a game.
(edit) It sounds like this only works in Linux. Windows needs a separate utility to use the SC with non-Steam games.
(edit 2) This is what KDE reports:
It can detect the back buttons (Paddle 1-4) and the quick access menu (Miscellaneous). hid-recorder also shows that all other inputs are also available through the /dev/hidraw* device. I wouldn’t be surprised at all if someone released a standalone Steam Input emulator app within a few weeks.
That’s not true. If you don’t use Steam Input, you only lose the Steam-specific inputs, like the touchpads, gyro, grip sense, and back buttons. Otherwise it is pretty much equivalent to a modern Xbox controller:
I’ve played a lot of Project Wingman with it, and the TMR inputs are actually a massive improvement.
Is that before or after Emperor Palpatine’s cameo in Rugrats?
LLMs are not a vital resource like food or electricity. Refusing to participate will at worst be an inconvenience.
Software can coexist. One application won’t kill another just because its developers can put out more code per hour. If it were otherwise, Linux wouldn’t exist.
I can’t fix the problem, therefore I’ll be part of the problem.
Rolling release doesn’t mean that no testing is done. All updated packages are tested by maintainers before being released into the official repository. A rolling release simply means that there are no individually marked OS versions and you always get the latest packages.
In contrast, take Debian for example. It uses a point release system with major named versions (e.g. Debian 13 “Trixie”), minor point releases (e.g. 13.1), and security and bugfix patches between those. New feature updates are released only between point releases, and breaking changes are only introduced between major versions. This allows the maintainers to practice a greater amount of care in testing that the packages work well together, but also means that new features are always held back to some extent. This does not happen in a rolling release system. All upstream changes are pulled, tested, and released, regardless of whether a breaking change is introduced.
By its nature, a rolling release distribution will require a greater amount of maintenance. If a package update requires manual intervention, it will be published on archlinux.org. For as long as I’ve been a Linux user, I’ve only seen one package update that made systems temporarily unbootable, and I was saved from that by being a Manjaro user at the time.
But, to answer the question, I usually update my home and work PCs (both Arch) about once every week or two, or as required by a new software or important security update.
It’s less about the concept of a game-centric headset and more about the brands that sell themselves as “We Are Gamers” with angular shapes and RGB out the ass. Steelseries, Razer, Alienware, Aorus, ROG… I’ve had many bad experiences both personally and professionally. The only one I didn’t end up regretting was Logitech G. The G502 mouse is a beast.
I used to own a HyperX Cloud Flight. It’s the best wireless headset I’ve ever tried. It comes with a USB dongle, no Bluetooth. Worked out of the box on Arch. I bought mine before HP infested HyperX, but my sister uses a post-buyout one and she says it’s perfect.
Pros:
Cons:
In general, avoid anything “Gamer”. You’re paying for the brand, not the quality. Even the cheapest “audiophile” headphones are better.
Wireless headsets will always be limited by their internal DAC. Another option is to get a decent wired headset and a dedicated wireless DAC. I currently use a modded Beyerdynamic DT770 and an AKG K-240, and if I need them to be wireless, I clip a Fiio BTR5 to the headstrap and connect it with a short cable.
That’s why you shouldn’t drive a 1969 Mustang project car immediately after getting your licence. You figure it out on a 2003 Honda Civic, then move on to bigger things when you have both the basic knowledge and the willingness and ability to advance your knowledge.
You claim that installing with btrfs failed. Did you look into what the error messages meant? You claim to not know what Flatpak is. Did you look it up?
RTFM is not just a thought-terminating cliché used by elitist wankers. It’s a philosophy you have to live by if you want to play with powerful toys. Look at manuals, the Arch Wiki, Stackoverflow, or ask a clanker. If that’s beyond your abilities at this time, you’ll either have to improve yourself, or surrender for the time and try a more beginner-friendly OS.
The 10.0 is Wine’s version that the Proton release is based on, the -4 is the version of Valve’s patches on top of Wine. Steam doesn’t keep individual patch versions around, only the latest available patch for each major version.
I know. I was responding to the comment, not the video.
it’s still hard to set up Nvidia GPUs on Linux, even on Bazzite
No it isn’t. Wade specifically admitted that he didn’t do any “setup” beyond installing and updating the system. If he had done a minimum amount of superficial research, like googling “how do I install driver”, the numbers wouldn’t have been held back by NVK or llvmpipe. The video is not representative of Linux gaming, or Bazzite even. He half-assed his way to some kind of result.
I know, I was talking about the state of Vortex as of today.
My experience says: don’t. Vortex uses some weird-ass GUI toolkit that doesn’t like running on Wine. Mouse-related events (hover, click, drag) sometimes don’t fire. If MO works for you, Vortex is probably not worth the effort.
Use Wine 9 or a fork of Wine 9, and install to the C: drive. Works every time.