Update, 2020-04-29: Since upgrading to kernel 5.6.6 and Mesa 20.0.4 I haven’t had any GPU resets anymore even without this workaround. It seems the reclocking issue is fixed. Keeping the article for reference:
If you have an AMD Vega 56 or 64 you may have had some issues using the amdgpu driver, namely random GPU resets leaving you with a blank or colored screen and freezing the computer after a few minutes. It seems that too aggressive memory reclocking is the culprit, but I found a solution in the Freedesktop issue list on their GitLab instance:
Stick this in your systemd, e.g. to /etc/systemd/system/amdgpu-pp.service:
[Unit]Description=AMD PP adjust service
When I got all fancy and moved to the 5.x kernel and Pulseaudio 12.2, I had one big new problem: My sound card would make an ugly popping noise every time it started playing sound again. Very, very 90s.
Fortunately, this can be fixed. Thanks to hateball for this solution. Stick this in your ~/.config/pulse/default.pa:
I’ve been trying SUSE as my main distribution and that’s something that hasn’t happened in my life since 1996. Even worse, this distro impressed me, a hardcore Debian nerd, quite a lot.
The reason for distro-hopping is Canonical’s bold decision to drop support for using 32-bit executables (and libraries) in Ubuntu starting as early as October 2019. That means that potentially thousands of games will no longer work, and it prompted Valve to drop support for Ubuntu in Steam. Valve is arguably the most important contributor to Linux gaming, so this is a big deal and a good enough reason to look at distros other than Ubuntu.
None of the systems that Final Fantasy XV throws at you really work on their own. The fast travel system is not fast at all. The combat can be anything from confusing to floaty, from frustrating to disappointingly easy. The world that’s presented, a melange of present-day hyperrealism, sci-fi and fantasy, shouldn’t work at all. Leveling up can only be done while resting, magic spells need to be constructed from scratch before use and the controls and camera are sometimes terrible, sometimes passable. You’d think this game would be a huge disappointment, but strangely, it develops a rough charm that’s impossible to pin on any one thing.
TLDR: 7/10. Problematic but weirdly enthralling. Read on for the details. Minimal spoilers (character names and backstory) ahead.
A few kernel versions (or Steam versions) ago, my Dual Shock 4 controller spontaneously stopped working in Steam. Big Picture mode said “no controller detected” and only games that had their own native DS4 support managed to still use it.
Looks like you need some udev rules to make sure all things are good. For my wired DS4v2 I stuck this:
I can’t remember where I found this, I’m pretty sure I didn’t figure this out for myself. If you need a DolphinBar, Aliexpress should have you covered. It could be that the vendor code differs for yours, so make sure to watch dmesg when you plug it in.
So the proprietary Nvidia driver is a large, steaming, smelly pile of shit. At least that’s the impression you get when you read what developers say about it. There’s a bug here and a workaround there, and we haven’t even started talking about the messy situation that is EGLstreams yet. So why do people use Nvidia cards on Linux? Because so far, they give good bang for the buck, use relatively little energy for what they do and work with all commercial games. I’m pretty sure those are the reasons, anyway.
But Nvidia at least on Plasma/KDE has some serious problems with tearing and stutter — I have three Nvidia setups and they all are unsatisfying out of the box. If you use ForceCompositionPipeline like I recommended earlier, you will probably run into stutter issues. But I think I found the perfect setup now, stutter-free and tearing-free for desktop use as well as perfect for gaming.
There are two alternatives:
Method 1: Solve it by switching the GL yield mechanism to USLEEP
Add the following to ~/.config/plasma-workspace/env/kwin.sh:
Thank mahenou on Steam for suggesting I try this again. The first time I did, it was probably too late in the environment for Kwin to pick it up. It’s important that the var is set when Kwin initializes.
Method 2: Solve it by forcing triple buffering
Add the following to ~/.config/plasma-workspace/env/kwin.sh:
And chmod +x the file. Then add the following to an Xorg config snippet, for example /etc/X11/xorg.conf.d/20-nvidia.conf:
Then make sure you have compositing enabled in System Settings -> Display and Monitor -> Compositor. If you are very doubtful, do a restart. After that you should have a perfect, tear-free and stutter-free desktop experience. I had to disable compositing manually with Alt-Shift-F12 before starting games with the triple buffering method. This was unnecessary with the __GL_YIELD method.
I can’t truthfully explain why this works, but I know it works around a bunch of bugs and unexpected default settings in the Nvidia driver. Also, Kwin is now able to compute the right timings and handle triple buffering instead of rendering half-finished frames like a fucking moron when it still believed Nvidia was doing triple buffering by default.
For me this has been wonderful. The desktop is smooth as if I were using a proper graphics card like an AMD RX 580 with Mesa. Games run exceedingly well, and there is no stutter or delay like with ForceCompositionPipeline. Not even in videos. It’s all just perfect.
This is a mix of hints received from several people on Reddit and Steam that I unfortunately forgot the names of, as well as info from the Arch Linux wiki. I’d like to thank all these people for their knowledge.
Update: There are now easier ways to manage this, for example through Lutris. If you manage your WINEs in Lutris, you simply have a checkbox whether to include dumbxinputemu or not.
If you need to use WINE to play some Windows games, the lack of Xinput support might get on your nerves. WINE maps joystick devices to Dinput. That works for some older games, but buttons need to be mapped manually, and many newer games don’t detect the controllers at all because they expect Xinput.
I tried to get by this issue using x360ce, but this is a fickle beast already when run natively on Windows; even more so in WINE. What worked really well for me was dumbxinputemu. Sometimes dumb things are the best.
To use it, determine if you’re running a 64-bit or a 32-bit game, then copy at least the matching xinput1_3.dll from the latest release to the same directory as the game’s binaries. In the case of Steam, that’s probably somewhere inside Steam/steamapps/common. Then make sure your WINE is set to prefer the native version of the DLL via winecfg:
In the “New override for library” dropdown select “xinput1_3”, then “Edit…” that entry to set it to “native” only. If you have a very new game, you might need to do repeat all these steps for xinput9_1_0.dll. This worked surprisingly reliably for me, no more double-detection of joysticks, no more wrong labels for buttons inside games, no more fiddly x360ce that works sometimes but then mysteriously breaks. Everything behaves as it shoud. Thank you, kozec.
Oh, the PS3. A problematic console from the start, with its strange Cell processor and its status somewhere between home entertainment system and games console. I suspect it only succeeded because of Sony’s muscle at the time, having emerged from the last console wars as a winner.
But this isn’t about the PS3, or only insofar as inFamous 2 is one of the titles that really, really taxes the system, and is a PS3 exclusive. Here’s inFamous 2 in a few paragraphs, maybe enough of them stick for you that you’ll give this game a chance:
The synopsis is this: You’re a freak who gets electricity-based superpowers, but now you can’t drive a car anymore and water kills you. Make sense so far? But you gotta save the world from the The Beast that approaches the Floridaesque or New Orleansy coastal city of New Marais.
Writing, characters, story
There is excellent writing (for an action game) with solid characterization and great voice work. The lead character, Cole, is interesting because the voice actor (Eric Ladin) does this gruff-sexy-action-hero type of gravely monotone, but he puts just the right amount of emotional nuance into it to make it interesting. The lines he gets are often surprisingly human. These people talk just like people! The game won’t bore you with ages of exposition, each dialog is just the minimal amount of information to move the story forward, delivered in short well-written bursts.
Graphics and sound
You’ll find breathtaking environments. Think Zelda: Breath of the Wild invented the scenic third-person game? Think again. inFamous 2 has beautiful vistas by the truckload. Particularly the skyboxes are astonishing — depending on the mood they want to create, they either look like something from a comic book or something from an apocalyptic classical painting.
Lighting is carefully chosen in general, with the whole scene bathed in a bluish twilight here or a dark orange sunset glow there. The architecture also deserves to be mentioned. It’s as if the developers had worked with an architect and a city planner to lay out the areas. Wood shacks and half-collapsed brick houses in Flood Town, colonial redbrick and a huge cathedral in the main part of town, an industrial wasteland full of gas tanks, train tracks and repair warehouses in the, err, industrial part. It all looks believable and organic.
Textures deserve to be mentioned as well, as I haven’t seen many PS3 games with such varied and careful texture work. Bricks and rocks have a palpable rough feel to them, colors in the main part of town are chosen carefully to be muted so that the many neon signs and lights pop out. Scenes with water feel glistening and wet.
This sequel has much more accessible gameplay than inFamous 1. That alone sets it apart enough for me. You unlock superpowers at just the right rate, and you feel like a badass as you climb through the cityscape or grind on a powerline. There aren’t any of those annoying tutorial levels like in inFamous 1, so in case you’re worrying about that, worry not.
You’ll be facing hundreds of normal, smaller enemies that each use different tactics, and usually the AI is good enough to make things interesting. You rarely feel totally overpowered, so you can rarely just stop thinking. Sometimes the AI gets stuck in corners, especially if you are very far away, but that’s fine. Most of your powers don’t have enough range to hit then anyway, and when you move closer the AI wakes from its daze and joins the fight again.
The few battles with extremely large enemies are all the better for it. Usually you fight enemies roughly your size or twice that. But there are occasions where you need to take on much larger beasts. Those truly shine because they are the exception. You’ll remember these enemies and fights precisely because you didn’t get inundated with sixty bosses already.
The only major criticism I could lob at the game is the framerate. It’s uneven, staring at the sky might get you around 60 fps, but actually playing in the streets hovers around 25 to 30, and battles can go down to the low 20s. They did a fantastic job adapting the controls so that you can win the fights anyway, even when the framerate tanks. But it’s just not beautiful anymore in the age of rock-solid 60 fps like the Nintendo Switch delivers for many games. This game needs a remake. Anyone listening? Screw The Last of Us, inFamous 2 is a fantastic action romp and it needs to be 1080p60 for fuck’s sake.
Festival of Blood: Electric Vampires
If you haven’t had enough of inFamous 2, there is a standalone side-game in the form of inFamous: Festival of Blood that uses the same locations but that lets you be an electrified vampire during a Mardi Gras-ish festival, hunting Bloody Mary, a vampire that terrorizes town. Yes, the cocktail was named after her in this universe, not the other way round.
The writing is once again spot-on, especially Bloody Mary’s diary segments. They’re delivered in her lofty English sing-song and written in the style of Gothic horror novels, always with a fun twist at the end.
Technically the game isn’t different from inFamous 2, but the colors are all changed (much more red) and the atmosphere in the street is very different with hundreds of festivalgoers wearing neon glow-in-the-dark bracelets.
Gameplay is changed from the base inFamous 2 by the addition of vampire powers (vampire sense lets you see into people and whether they are hidden vampires, bat flight turns you into a flock of bat, biting people and sucking their blood refills your bat flight energy, etc.).
The only criticism here is that environments are reused quite often, with one section of catacombs underneath the cathedral serving as location for at least three quests. But this is forgivable.
Oh, the PS3. It’s getting old now. This is an advantage for you, in case no remake is coming. If you don’t have a PS3, you can get one now for 50 bucks of whatever currency, and inFamous 2 in a digital sale often dips below 10 and includes Festival of Blood. Physical, you might be able to score a used copy for 5.
Also, if you have a beefy PC, keep an eye out for RPCS3. This PS3 emulator has been making great strides, and you can rip games yourself quite easily. It doesn’t really run the inFamous games yet, though. Maybe if RPCS3 becomes optimized enough, we won’t need a remake anymore. A very, very fast PC can potentially play this game at a solid 30 or 60 fps, as there is no frame limiter in the engine.
Here’s a full playthrough with major spoilers if you want to see what the game is like: