I recently spent some time with the Framework 13 laptop, evaluating it with the new Intel Core Ultra 7 processor and the AMD Ryzen 7 7480U. It felt like the perfect opportunity to test how a handful of games ran on Windows 11 and Fedora 40. I was genuinely surprised by the results!

...

The Framework 13 is perfectly capable of gaming even with its integrated graphics, provided you’re willing to compromise by lowering the resolution and quality presets for more demanding games. (It’s also a testament to how far AMD’s APUs have come in the past decade.)

Summary of results:

• Shadow of the Tomb Raider: Linux wins
• Total War: Warhammer III: Windows wins
• Cyberpunk 2077: Linux wins
• Forza Horizon 5: Windows wins

These results are an interesting slice of the Linux vs Windows gaming picture, but certainly not representative of the entire landscape. A few shorts years ago, however, I never would have dreamed I’d be writing an article where even two games on Linux are outperforming their Windows counterparts.

Archived Link

So i have a problem plsying the Finals on linux. They are clearly garbage graphics. The walls dont even look how they are supposed to and the permanent fog makes it unplayable. The shadowing is too dark. Forget fps, when play on windows and linux it is night and day. Its as if the game isnt using its correct shaders or textures.

Has anyone dealt with this? Im thinking that the finals is not utilizing my nvidia graphics card so if anyone has advice i would greatly appreciate.

I tried letting vulkan load the shaders, ive tried skipping vulkan shaders and there is no difference. Im using proton glorious egg and i have no idea what to do or what the problem is.

EDIT: putting “ PROTON_ENABLE_NVAPI=1 %command% -dx11” in launch options fixed the bad graphics but now i have fps issues unfortunately.

I did it. For a few years now I've wanted to make the jump but lazyness and a bit of worry that my main game wouldn't work very well kept me from it.

Then some effing windows update caused ridiculous stuttering on games (or maybe it was a auto-update of some other hidden thing, I couldn't figure it out) so I decided that if I needed a system wipe, might as well as try gaming on linux.

Honestly? Much easier than I expected. Install Steam, turn two options on and 90% of your library is ready to go. I had to tinker with getting freesync to work (ended up just switching to wayland, which just worked) but other than the plugins I use for my main game requiring a bit of more work, smooth as butter really.

So yeah, if you are a lazy gamer like I am, next time you do a system wipe or get a new computer, try installing linux first. Don't even bother Dual booting it, if you don't like it just reinstall (setup your usb drive with ventoy and the images you want to try out.)

cross-posted from: https://lemmy.nowsci.com/post/9782732

cross-posted from: https://lemmy.nowsci.com/post/9782596

Hi all,

I've finally gotten around to releasing these formally after much testing of prints and usage.

The Twystlock system is a set of 100% 3D printable gaming accessories that require no printed supports or additional parts. This means no springs to buy and no metal elements to melt in, just access to a 3D printer and a bit of super glue. Originally designed for the Steam Deck, these accessories can be applied to the case of any mobile gaming device.

The Twystlock connector itself is designed as a quick-connect that secures parts together with a simple twist motion, can be fully recreated with affordable home-based 3D printers, and doesn't require complicated supports to print. The first use of this connector has been for the Steam Deck, specifically to supply an alternative accessory platform that is more accessible to the everyday 3D printing hobbyist, however it could be utilized as a connector in almost any environment.

Feel free to download what you like, and if you would like to request a new accessory design, or vote on the next accessory to be created, please visit our Lemmy community at https://lemmy.world/c/[email protected].

cross-posted from: https://lemmy.zip/post/20949510

SOLUTION: Apparently there’s some sort of bug in xwayland that causes Steam games to flicker, so “downgrading” to X11 solved it (for now). Now all I need to know is how to file a bug report for this.

I'm trying to set up a Linux install for my mom (Ultramarine KDE on Wayland), and all her (2) Steam games are flickering. I thought it was from fractional scaling, but that doesn't seem to be the case.

Her games don't flicker on Windows, and I've already tried multiple versions of Proton. I'm not quite sure what's happening, and any help would be appreciated.

Specs

• OS: Ultramarine Linux KDE Edition
• Host: Dell Inspiron 15 3511
• CPU: Intel Core i5-1035G1
• GPU: ~~pretty sure it uses integrated graphics~~ ~~apparently it uses Nvidia? First time I've seen that, gonna have to remember that in the future.~~ Both Linux and Windows are using integrated graphics with no sign of Nvidia anywhere??

If you need any more information, please ask me

Edit: other than the flickering, her games run perfectly fine.

Edit 2: Just learned my mom's laptop model has a discrete Nvidia GPU, gonna troubleshoot that in a bit.

Edit 3: Her laptop doesn't seem to have anything Nvidia inside, despite the fact that the Dell website says her laptop should, weird...

cross-posted from: https://lemmy.ml/post/19176020

Compressed using ImageMagick and oxipng as cosmic-screenshot produces huge sizes that Lemmy doesn't want to handle.

Desktop

Wallpaper

• wall.alphacoders.com

Appearance (based on Factorio.com)

• Dark: true
• Accent color: #FF9F1C
• Application or window background: #242324
• Container background: #313031
• Interface text tint: #FFE6C0
• Control component tint: #242324
• Use theme accent color as active window hint: true
• Style: Square
• Active window hint size: 6
• Gaps around tiled windows: 12
• Experimental settings > Apply this theme to GNOME apps: true

Other configuration should be visible, just a matter of taste and Factorio UI.

Factorio.ron

(
    palette: Dark((
        name: "cosmic-dark",
        blue: (
            red: 0.5803922,
            green: 0.92156863,
            blue: 0.92156863,
            alpha: 1.0,
        ),
        red: (
            red: 1.0,
            green: 0.70980394,
            blue: 0.70980394,
            alpha: 1.0,
        ),
        green: (
            red: 0.6745098,
            green: 0.96862745,
            blue: 0.8235294,
            alpha: 1.0,
        ),
        yellow: (
            red: 1.0,
            green: 0.94509804,
            blue: 0.61960787,
            alpha: 1.0,
        ),
        gray_1: (
            red: 0.105882354,
            green: 0.105882354,
            blue: 0.105882354,
            alpha: 1.0,
        ),
        gray_2: (
            red: 0.14901961,
            green: 0.14901961,
            blue: 0.14901961,
            alpha: 1.0,
        ),
        gray_3: (
            red: 0.1882353,
            green: 0.1882353,
            blue: 0.1882353,
            alpha: 1.0,
        ),
        neutral_0: (
            red: 0.0,
            green: 0.0,
            blue: 0.0,
            alpha: 1.0,
        ),
        neutral_1: (
            red: 0.105882354,
            green: 0.105882354,
            blue: 0.105882354,
            alpha: 1.0,
        ),
        neutral_2: (
            red: 0.1882353,
            green: 0.1882353,
            blue: 0.1882353,
            alpha: 1.0,
        ),
        neutral_3: (
            red: 0.2784314,
            green: 0.2784314,
            blue: 0.2784314,
            alpha: 1.0,
        ),
        neutral_4: (
            red: 0.36862746,
            green: 0.36862746,
            blue: 0.36862746,
            alpha: 1.0,
        ),
        neutral_5: (
            red: 0.46666667,
            green: 0.46666667,
            blue: 0.46666667,
            alpha: 1.0,
        ),
        neutral_6: (
            red: 0.5686275,
            green: 0.5686275,
            blue: 0.5686275,
            alpha: 1.0,
        ),
        neutral_7: (
            red: 0.67058825,
            green: 0.67058825,
            blue: 0.67058825,
            alpha: 1.0,
        ),
        neutral_8: (
            red: 0.7764706,
            green: 0.7764706,
            blue: 0.7764706,
            alpha: 1.0,
        ),
        neutral_9: (
            red: 0.8862745,
            green: 0.8862745,
            blue: 0.8862745,
            alpha: 1.0,
        ),
        neutral_10: (
            red: 1.0,
            green: 1.0,
            blue: 1.0,
            alpha: 1.0,
        ),
        bright_green: (
            red: 0.36862746,
            green: 0.85882354,
            blue: 0.54901963,
            alpha: 1.0,
        ),
        bright_red: (
            red: 1.0,
            green: 0.627451,
            blue: 0.5647059,
            alpha: 1.0,
        ),
        bright_orange: (
            red: 1.0,
            green: 0.6392157,
            blue: 0.49019608,
            alpha: 1.0,
        ),
        ext_warm_grey: (
            red: 0.60784316,
            green: 0.5568628,
            blue: 0.5411765,
            alpha: 1.0,
        ),
        ext_orange: (
            red: 1.0,
            green: 0.6784314,
            blue: 0.0,
            alpha: 1.0,
        ),
        ext_yellow: (
            red: 0.99607843,
            green: 0.85882354,
            blue: 0.2509804,
            alpha: 1.0,
        ),
        ext_blue: (
            red: 0.28235295,
            green: 0.7254902,
            blue: 0.78039217,
            alpha: 1.0,
        ),
        ext_purple: (
            red: 0.8117647,
            green: 0.49019608,
            blue: 1.0,
            alpha: 1.0,
        ),
        ext_pink: (
            red: 0.9764706,
            green: 0.22745098,
            blue: 0.5137255,
            alpha: 1.0,
        ),
        ext_indigo: (
            red: 0.24313726,
            green: 0.53333336,
            blue: 1.0,
            alpha: 1.0,
        ),
        accent_blue: (
            red: 0.3882353,
            green: 0.8156863,
            blue: 0.8745098,
            alpha: 1.0,
        ),
        accent_red: (
            red: 0.99215686,
            green: 0.6313726,
            blue: 0.627451,
            alpha: 1.0,
        ),
        accent_green: (
            red: 0.57254905,
            green: 0.8117647,
            blue: 0.6117647,
            alpha: 1.0,
        ),
        accent_warm_grey: (
            red: 0.7921569,
            green: 0.7294118,
            blue: 0.7058824,
            alpha: 1.0,
        ),
        accent_orange: (
            red: 1.0,
            green: 0.6784314,
            blue: 0.0,
            alpha: 1.0,
        ),
        accent_yellow: (
            red: 0.96862745,
            green: 0.8784314,
            blue: 0.38431373,
            alpha: 1.0,
        ),
        accent_purple: (
            red: 0.90588236,
            green: 0.6117647,
            blue: 0.99607843,
            alpha: 1.0,
        ),
        accent_pink: (
            red: 1.0,
            green: 0.6117647,
            blue: 0.69411767,
            alpha: 1.0,
        ),
        accent_indigo: (
            red: 0.6313726,
            green: 0.7529412,
            blue: 0.92156863,
            alpha: 1.0,
        ),
    )),
    spacing: (
        space_none: 0,
        space_xxxs: 4,
        space_xxs: 8,
        space_xs: 12,
        space_s: 16,
        space_m: 24,
        space_l: 32,
        space_xl: 48,
        space_xxl: 64,
        space_xxxl: 128,
    ),
    corner_radii: (
        radius_0: (0.0, 0.0, 0.0, 0.0),
        radius_xs: (2.0, 2.0, 2.0, 2.0),
        radius_s: (2.0, 2.0, 2.0, 2.0),
        radius_m: (2.0, 2.0, 2.0, 2.0),
        radius_l: (2.0, 2.0, 2.0, 2.0),
        radius_xl: (2.0, 2.0, 2.0, 2.0),
    ),
    neutral_tint: Some((
        red: 0.14117648,
        green: 0.13725491,
        blue: 0.14117648,
    )),
    bg_color: Some((
        red: 0.14117648,
        green: 0.13725491,
        blue: 0.14117648,
        alpha: 1.0,
    )),
    primary_container_bg: Some((
        red: 0.19215687,
        green: 0.1882353,
        blue: 0.19215687,
        alpha: 1.0,
    )),
    secondary_container_bg: None,
    text_tint: Some((
        red: 1.0,
        green: 0.9019608,
        blue: 0.7529412,
    )),
    accent: Some((
        red: 1.0,
        green: 0.62352943,
        blue: 0.109803915,
    )),
    success: None,
    warning: None,
    destructive: None,
    is_frosted: false,
    gaps: (0, 12),
    active_hint: 6,
    window_hint: None,
)

It’s only currently planned for PC, with no controller or console plans yet — and Mountaintop won’t necessarily allow Steam Deck to join. “Steam Deck is a concern as a cheating vector, and I think our anti-cheat systems may block it right now,” Mountaintop CEO and cofounder Nate Mitchell tells me.

https://store.steampowered.com/app/2641470/Spectre_Divide/

cross-posted from: https://lemm.ee/post/39456265

For those of you like me who are fed up with Microsoft’s BS but invested too heavily in hardware that Linux distros have yet to support well, I finally figured out a way to get HDR games to run well on my Nvidia GPU. This will be a brief description of more or less what I did to get this working. I’m very much a Linux noob so I don’t fully understand the way everything here works but I’m happy to try to answer questions if you have any.

OS: Bazzite –Desktop Nvidia KDE edition (BDNK) Bazzite was developed as a capable alternative to SteamOS on handhelds like the Steam Deck and ROG Ally, so the website is full of references to HDR, however from my attempts to get this working my understanding is that it’s easier to get that working in Gaming mode which is unsupported on Nvidia GPUs. Nevertheless, this version of Bazzite, while only for desktops, comes with KDE Plasma v6 installed by default meaning it technically supports HDR and you will likely see a difference if you install this version and flip the HDR switch from the display settings. I had tried installing Ubuntu on my desktop before and since it didn’t support HDR all the colors on my monitor were almost obnoxiously saturated; I see the same effect in BDNK when I disable HDR.

Drivers: I didn’t fiddle with my drivers. BDNK comes with up-to-date Nvidia drivers bundled and installs them when you install the OS.

Software: SteamTinkerLaunch (installed using ProtonUp-Qt) SteamTinkerLaunch (STL) is a user interface for making it easy to configure your launch options for any given game in your Steam library. If you don’t know what a compatibility tool is, it’s functionally a layer of software between the game you want to play and the OS you’re using which can tell the game to do certain things that your OS is not configured to do. STL can be added to the list of compatibility tools you have to use in your installation of Steam, though it is not technically a compatibility tool itself. STL is used to configure other compatibility tools that Steam already has at its disposal, like Proton which is the primary compatibility tool SteamOS uses to make Windows games run on Linux.

Follow the instructions in the SteamTinkerLaunch GitHub ReadMe to install the tool and add it as a compatibility tool in your installation of Steam. Once you’ve done that, I recommend rebooting. I have yet to get STL working as the * default * compatibility tool, so for the time being I have been manually editing the properties of each game I have installed (Steam Game Library > right click on a game > click properties > go to the compatibility tab) to set the compatibility tool to STL. From here, whenever you launch the game in Steam, it should bring up STL’s menu before launching the game.

Within STL, the key settings to mark are as follows: Gamescope: Use gamescope and mark HDR as enabled for gamescope. I also recommend setting gamescope to fullscreen with your desired resolution, and then also locking your cursor to the gamescope window so that you don’t end up with weird double mouse cursors that aren’t aligned on the screen. Proton: since you told Steam to use STL instead of Proton as the compatibility tool, you need to tell STL to tell Steam to launch the game with Proton.

And that’s pretty much it. Or at least, that’s all that I did. From there, you should be able to configure HDR settings within each game’s menus.

TL;DR – install Bazzite Desktop Nvidia KDE, then install and configure SteamTinkerLaunch for your games.

What games will this work with? No idea. So far I have tested it with Cyberpunk 2077, DOOM Eternal, and Elden Ring and HDR is looking to me as good as it does in my Windows installation.

Will the Gnome version of Bazzite work for HDR on an Nvidia GPU, or for that matter any other OS as long as I’m using gamescope to run the game with HDR enabled? Good question! I don’t know, please give it a try if you’re curious and respond back with your results.

I have another question that you didn’t list here, what’s your answer? Probably “I don’t know” since what I wrote here is more or less what I know, but by all means ask away and I’ll try to answer it!

This game plays like a top-down Terraria and is a lot of fun to play co-op. Great to see it's already sold a million copies on steam.

I'm looking for discussion and suggestions about the best way to play games from GOG on linux.

My current method is that I've got GOG Galaxy installed with bottles, and then I use GOG Galaxy to install and launch the Windows games. That's working alright so far. One downside is that won't install Iinux versions like that, so for games that have a native linux version I have to decide if I want to install it separately, or just run the windows version with the others. So that isn't perfect. Another minor thing I don't like is that since I'm installing games via GOG Galaxy via Bottles via Flatpak... I end up having very little idea of where stuff is being saved. It's difficult to find save game files for example; and if there is some junk installed or left over from something, there's very little chance that I'm going to notice and delete it. It just feels very opaque. (I guess that's mostly just about my personal lack of knowledge though.)

Anyway, I'm mostly just wondering how others are choosing to handle their games from GOG.

cross-posted from: https://lemmy.dbzer0.com/post/25475442

Dear fellow enthusiasts,

my wife and I finally got stable enough in our living situation, that we can buy some new hardware (ours is 7+ years, while hers is a laptop). So I went out into the wild wild web to catch up with 7years of hardware progress (I am technological affine, but not following the trends in any way) and wanted to run by my first iteration of a setup with the infinite wisdom of this community.

For the background: both of us only use Linux at home and at work and do not plan to change this. We do not play AAA games, the most demanding game we play as of late is probably Dota2, ARK and GTNH (a Minecraft mod pack, that eats your ram for breakfast). Hence we won't need cutting edge hardware, more like an upper end budget setup. Anyway, with my last PC I had tons of troubles with the mainboard, the GPU (nvidia) and other stuff, even though I thought I checked stuff in advance, so I wanted to have an outside opinion.

TL;DR: here my draft, with prices from an online store:

• Mainboard: ASRock B650M-H/M.2+ 97.90€
• CPU: AMD Ryzen 7™ 7700, 8 core, 3.800 MHz base, AM5, 32 MB L3 cache 227.90€
• GPU: XFX Radeon RX 6650 XT Speedster SWFT 210 Core Gaming, RDNA 2, GDDR6, 3x DisplayPort, 1x HDMI 2.1 249.90€
• RAM: ADATA DIMM 32 GB DDR5-4800 (2x 16 GB) Dual-Kit, 84.90€
• PSU: be quiet! System Power 10 650W 61.90€
• Storage: Crucial P3 Plus 1 TB, SSD PCIe 4.0 x4, NVMe, M.2 2280, Reading: 5.000 MB/s, Writing: 3.600 MB/s 69.99€
• CPU cooler: be quiet! Pure Rock 2 Black 39.89€
• case: generic 50.00€

sum: ~880.00€

we don't mind to pay a little bit more here and there, but I do not see any real benefit to it. Even storage should be fine for our purpose and can be easily expended (the MB has two M.2 slots, and even Sata3 should be fine for raw storage).

ah, and we would buy two of those... My first idea was to buy one PC with two GPUs with passthrough of GPU and USB input (sitting anyway close), but I got the impression, that is at this moment more something to tinker, then to run "in production".

Best wishes, me

PS: if this community is not correct, I apologize and would kindly ask for the better fit.

Hey all. I'm heading to Quakecon 2024 tomorrow and will be repping the penguin. I've got all my games set up and ready, but was now wondering, are there any extra steps I should take as far as network security goes?

I'm sure I'm not as vulnerable to random badness as the flock of Windows machines that will be on the network, but you never know. The only thing on my list so far is to disable sshd. I thought about installing Portmaster but it has always messed up my DNS in the past...

I'll probably run Wireshark just to see if I can capture anything interesting there. Do you all have any other suggestions for prepping my PC?

I'm on Kubuntu 24.04, rocking a build that was pretty darn high end in 2021 with an AMD 6800 XT, and of course, Wolfenstein: The New Order was already old news by then. Proton does miracles, but this game freezes my entire machine. The last time I saw something like this happen was with Monster Hunter World in 2018, on a much older version of Proton. I can reliably get the game to freeze my machine in the opening level of The New Order, even across multiple versions of Proton, even with the renderapi launch parameter that should switch it back to OpenGL. Of course, even if I report this to Steam support, they'll tell me that they only support Steam Deck and not bespoke Linux desktops, and the game works fine on my Steam Deck, but would they be interested in some logs and a bug reported against the GitHub project? This is assuming no one here has an easy fix, of course. But if not, how would I get the logs? I wouldn't know what I'm looking at in those logs, personally. I'm also not sure if they'll write out correctly. Because it freezes the entire machine, I end up having to hard shut down the computer by the power button, and once or twice during my experiments, it failed to mount my game SSD (a separate drive from where my OS is installed) at boot, and I had to set up the automatic mount in the partition manager again. So assuming that doesn't impact the ability to write out the logs, I can collect them with some instructions, if you kind strangers in the know wouldn't mind providing them, please. And if Valve is interested in looking at them.

Hello everybody! My brother plays Insurgency Sandstorm a lot and I wanted us to be able to play together, so I got it and after some messing about got it working on my system. One of the things I read in forum posts to do to get it to work on an Arch based system is to install glibc-eac-bin which has some patches to make certain games work (I hope I understood that correctly).

Today when I try to update my system I get the following message and it will not allow me to continue:

:: Starting full system upgrade...

resolving dependencies...

looking for conflicting packages...

:: glibc-2.40+r16+gaa533d58ff-1 and glibc-eac-bin-2.40-1 are in conflict. Remove glibc-eac-bin? [y/N]

I dont want to remove glibc, but i want the message to go away and to be able to proceed with my updates. Any suggestions on what I should do?

Thanks in advance

cross-posted from: https://lemm.ee/post/38676431

A while back I ended up getting tired of making hacks to get custom binaries to launch in Steam for Windows titles. Primarily for modding, I would find a way to simply launch custom EXE files through Steam to ensure the modding tools and the game were contained neatly in the same prefix. My first ventures with this were Skyrim and Fallout: New Vegas. With these titles, I overrode the gamebryo/creation engine launcher EXE with Mod Organizer 2 (renamed to be the launcher). While this worked, the solution doesn't work for other games without a secondary launcher that is targeted through Steam.

I eventually came to the conclusion that one can override launch targets entirely in Steam, and that tools like SteamTinkerLaunch could take advantage of this. However, STL certainly does a lot and honestly, that is way more than I really desired just to launch games with a custom EXE. Thus I made a shell script that essentially allows for the user to write in their own custom target and have it launch right through Steam.

The usage for this is simple. Just copy the 'shim' file into the game directory, override the Steam launch arguments to include "./shim %command%", and all is good. Furthermore, environment variables (such as DRI_PRIME=1), additional launch wrappers (gamemoderun), and game launch arguments (-novid for Source Engine titles) all work. If one needed a combination of all of this, it would look something like "DRI_PRIME=1 gamemoderun ./shim %command% -novid".

The way target editing currently works is on first launch the shim file grabs the default game target and writes it as the contents of 'target', another file in the game directory. From there, one can simply edit the target location in the file and shim will launch the custom executable.

So far, I have used this to get things like RaftModLoader and BeamMP working (mod loader for Raft and multiplayer for BeamNG.Drive respectively). I see no issue with this being able to also work for Bethesda titles and others that need custom executables. As I understand as well, the actual game install directories on a Steam Deck with SteamOS are mutable, and with a bit of tinkering through desktop mode should help get a seamless experience for launching modded Steam games for Deck users as well.

I hope someone finds as much use and utility that I have for getting a lot of modding tools for Windows games working without needing to mangle the prefix using protontricks in some cases or install the absolute multi-tool that is SteamTinkerLaunch.

About a week late to post this but someone could probably use this info.

This is a community made patch to fix serious issues playing Black Ops 3 online everything from stuttering in menus to RCEs, it's basically a requirement even if you're just playing zombies with friends.

The latest version no longer requires you to run an exe along side the game and is officially supported on Linux now.

The beautiful games I own are Snake Pass and Sonic Racing Transformed, both of which have sound issues (muffled audio) when played through a cheap soundbar via bluetooth, audio for all other games with this soundbar works perfectly.

I'm on EndeavourOS (Arch Linux) using repository Steam, KDE Plasma and Pipewire. I've tried all the different proton versions (experimental, 9, 8, 7, 3, etc) without success. Maybe I could solve it by removing pipewire but I don't think it's worth worsening the entire OS, since it's only about these two titles.

Q:

• The problem seems to not appear on other distros, like Debian (maybe due to different packages / pulseaudio?).
• Coincidentally it only happens with these two SumoDigital games, could proton be missing some component commonly used in these games?
• Since I can't find any relevant solutions online, I assume that the problem only exists with this type of Bluetooth audio device.

[edit] AtM I "solved" it by connecting the speaker via cable.

I have been using GNU for so long now and what always annoyed me, was the fact that the last proprietary components of my OSs were always some kernel firmware blobs that are packaged with the official Linux kernel. Now I'd like to know if anyone has already tried the Linux-libre kernel on a modern system.

Update wine to latest bleeding edge

Update dxvk to latest git

Update vkd3d-proton to latest git

Import upstream proton changes

Rebase staging

Add xinput patch for Dragon Age: Inquisition ( thanks cammoore1 )

Protonfixes:

Add protonfix and steamgameid envvar to trigger Dragon Age: Inquisition xinput patch (allows to work with EA version in umu)

Add protonfix for Flowers - Le Volume series (thanks R1kaB3rN)

Add protonfix for The Last Blade (thanks ranplayer)

Add protonfix for GOG Beyond Good and Evil (thanks ImLinguin)

Add protonfix for WRC4 (thanks ToRRen1812)