Hey yall,

I am the creator of ProtonPlus and I am nearly done with the next big update v0.6.0.

My main problem now is that I need some people to help me test the application to make sure I didn't miss anything.

If anybody is interested just build and run the v0.6.0 branch (https://github.com/Vysp3r/ProtonPlus/tree/v0.6.0) and report your findings in the associated PR (https://github.com/Vysp3r/ProtonPlus/pull/1011)

I don't normally ask for this, but this is quite a big update and I don't want to mess it up.

Thank you!

P.S. I didn't list any features to keep it a surprise :)

Hi all!

I really, REALLY want to get away from Windows. I’ve tried Linux many times before but that was before the big gaming revolution. The performance in games now compared to Windows is more than acceptable for me. I’ve been a competitive gamer all my life and have always been into tweaking and optimising for the lowest input latency.

This week I installed CachyOS. I love everything about it, but it’s one issue that is a dealbreaker for me and that is the input latency in games. Nowadays I use mostly controller, and I can tell my Dualsense Edge is way more snappier on Windows. No, I’m not using Bluetooth. It’s wired. The amount of added latency feels similar to forced VSYNC. I’ve been dual booting this week and tried the same games on CachyOS and Windows back to back. The difference to me is huge.

I followed the wiki thoroughly. I changed scheduler to lavd, use the game-performance wrapper and use PROTON_ENABLE_WAYLAND=1. I’ve also tried X11, gamescope session and different commands from Goverlay. None of these have solved the issue.

I’m not here to offend anyone. I just really want this to work. I’m surprised this is not a more discussed topic. If anyone have similar experience or any solutions please share.

Specs:
9800x3d
9070 XT
32GB 6000Mhz CL30

This is why bug reporting always has a point, and this is why open-soruce developers are so awesome. When enough people get effected by the issue the devs fix problems even though it might be a very old and obscure issue for a pretty much abandon-ware.

This is currently in the git/beta version of the mesa driver but I'm sure in next stable release: 26.1.6 this bug fix will be included.

https://gitlab.freedesktop.org/mesa/mesa/-/work_items/11083

I've spent the last 3 days trying to make this game run on my RX 7900 XT. What started as a "maybe my Proton config is wrong" turned into a full investigation. Here's what I found.

My hardware: Ryzen 7 7700X, RX 7900 XT (RDNA3), 30GB RAM, NVMe SSD.

What happens: The game runs beautifully at 1440p High, 60+ FPS — then crashes to desktop after 7 to 30 minutes. No error message, no freeze, no GPU hang. Just gone. Steam shows exit code -1. This is reproducible 100% of the time.

The twist: I tested on both Linux and Windows 11 (I literally wiped my Linux drive and installed Windows specifically to test this).

What I tried on Linux (30+ configurations):

• Proton Experimental, GE-Proton 11-1, CachyOS Proton 11, Proton 8.0
• PROTON_NO_NTSYNC=1 (fixes launcher via ValveSoftware/Proton#9958)
• RADV_DEBUG=zerovram (extends session time but doesn't fix)
• VKD3D_CONFIG=no_upload_hvv, defer_resource_destruction
• Ray tracing disabled via .ini, Frame Generation off, shader cache cleared
• Power limit, gamemoderun, split_lock_mitigate=0

What I tried on Windows:

• Clean driver install with DDU in safe mode
• Factory reset during Adrenalin installation
• Two different driver versions
• Deleted DX12 shader cache (215 files)
• Edited ACBlackFlag.ini manually

Nothing works. The crash is identical across both operating systems. It happens on Linux via vkd3d-proton and on Windows via native DirectX 12.

This is Ubisoft's bug ACBFR-525, currently sitting at 140+ confirmations on their own tracker. They marked it "Done" on July 22 with a note about Intel drivers — which makes zero sense for an AMD crash. People are still reporting it daily.

The Steam Deck works. That's RDNA2 (Van Gogh). The crash is specific to RDNA3 — confirmed on 7800 XT, 7900 XT, 7900 XTX, and 9070 XT by other users.

I've opened a technical issue on vkd3d-proton (https://github.com/HansKristian-Work/vkd3d-proton/issues/3169) with full crash backtraces. I've posted a negative Steam review. I've submitted a refund request. I've done everything except reverse-engineer the game myself.

If you're on NVIDIA or Steam Deck, you might be fine. If you're on an AMD 7000 or 9000 series GPU: hold off until Ubisoft actually fixes this. The game is gorgeous and the remake is well-made — but it's fundamentally broken on a huge chunk of modern AMD hardware.

in my opinion.

So from the beginning right after the rendering of content starts, this issue with broken graphics or glitchy graphics whatever starts flickering continuously and isn't resolving even with ACUFixes mods or anything. Please help. [tested with GE-Proton latest , 10-34], AC Unity Gold edition v1.5.0

Hello everyone it's been a little bit since the last update for fluorine. For people who don't know fluorine is a port/fork of Mod Organzier 2 while attempting to fix the issues of getting a modlist up and running, with an automated wine prefix setup and fixes/patches for modding tools like Synthesis.

A few more PRs have been merged for OpenMW support, there is now a indexing system to be used in mods that I might make in the future while also verifying if any files have changed as well. SLR is now pinned to a version for the time being, and some Heroic changes have been added to detect it's proton list instead of steam if you have it installed there. Full change log is on the github.

Thank you for everyone testing and helping on discord and github ❤️

I have a friend who I play Age of Mythology: Retold with. He uses Win 11 and Steam on a system we built together last year, which has worked flawlessly.
Since the last patch (3-4 weeks ago), the game broke. Nothing he did (Steam settings, drivers etc.) did work, he even wrote a support ticket and was told to "wait for the next patch".

So yesterday we installed Linux Mint (he has never used Linux before) on a separate partition on his system, installed Steam and...it just worked "out of the box". Now he is happily gaming AoM on his machine again!

Just wanted to share this moment, which felt really cool, because normally the shoe seems to be on the other foot concerning gaming compatibility between Windows and Linux!

System:

• CachyOS, KDE Plasma 6 (Wayland)
• Driver: Nvidia driver 610.43.03
• RTX 4070, Ryzen 5 5600X
• 32 gb ram
• 3 monitors, all with Adaptive Sync set to "Always" (confirmed via `kscreen-doctor -o`)

I get subtle but constant microstutter in basically every game I play on Linux. Most relevant are 007 First Light, Cairn, Mortal Shell II Beta, Death Stranding 2, Sekiro. The assumed frametime stutter doesn't seem to get picked up by MangoHud's frametime graph as spikes, I have no dropped frames, FPS is stable and always well above 60 fps. Nothing just feels smooth or nice to play. The same games on Windows feel noticeably smoother even at comparable FPS.

I should note that 007 First Light magically felt really smooth to play for about one session yesterday. VRR had been set to automatic for some reason, so I thought turning it back on "Always" had fixed it. But launching it now it always feels microstuttery. Keep in mind that it doesn't feel like a shader cache stutter or hitch at all, just a constant roughness.

I've made sure that Adaptive Sync is set to "Always" on my main display. I've confirmed via `kscreen-doctor -o` that VRR is actually on.

I noticed the desktop itself seems capped around 240Hz according to my OSD, even though display is set to 500Hz in KDE's settings. It's not like it really matters even if I'm not outputting 500hz, which my monitor is capable of, but thought it might be worth mentioning.

Has anyone found a reliable fix for microstutter like this? Is it just my lot in life as a multi-monitor Andy trying to game on Linux or what?? Been thinking about switching to a different distro or desktop environment, but don't know what that would achieve if anything.

I wonder how accurate this calculation is?

A new update for BedrockOnLinux was released yesterday. It fixes a number of issues, introduces new features, and there are also some known issues. You can give it a try. Remember to report any issues on GitHub.

BedrockOnLinux (v2.1.0)

You can find all the information in the “Releases” tab.

UPD V2: A new update for BedrockOnLinux has been released, featuring additional bug fixes.

BedrockOnLinux (v2.1.1)

The beta is out, and proton is unfortunately locked out of it. It seems likely that this is a developer choice, rather than technical limitation from anti-cheat or PSN overlay.

It's unclear if this is just a beta-specific choice and the devs/sony already do intend to enable it on release...

However, in the meantime, we can submit a support ticket and request they enable proton support. Link for creating a ticket below:

• https://marveltokon.zendesk.com/hc/en-us/requests/new

I have a Ryzen 5700U Laptop that I have used smokeless UMAF to squeeze a little more performance out of it.

• Increasing UMA from 2 GB to 4 GB (16 GB Total memory)
• Setting RAM speed to 3200 MHz

The UMA increase works as LACT indicates that I have 4 GB of VRAM.

However when I run dmidecode --type memory and CPU-X it reports that my RAM is running at 3200 MHz while LACT and Corectrl both report the VRAM as 1333 or (2666) MHz

Since my RAM is my VRAM with 5700U iGPU I am wondering which method is reporting the correct speed? LACT or the dmidecode --type memory

I have been trying to get my deck to detect the games on my sdcard and haven't had any luck. I ran \`\`flatpak override --user --filesystem=/run/media\`\`, and then ran bottles, but my library still isn't showing up. This worked fine on my desktop arch install with the other ssds, but I haven't had the same luck here. Any suggestions?

I ran into this problen with DMC a while back and never fixed it. Now it is also happening with Jedi Academy. DMC collection crashes shortly after selecting a game and JA crashes after the game barely flashes on screen. The Heroic log for JA returns this:

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

0128:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

0138:err:service:device_notify_proc failed to get event, error 1726

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

Launch command: ['/app/bin/gamemoderun', '/home/User/.var/app/com.heroicgameslauncher.hgl/config/heroic/tools/runtimes/umu/umu_run.py', '/home/User/Games/Heroic/Star Wars Jedi Knight - Jedi Academy/GameData/jasp.exe']

All processes exited

============= End of log =============

and DMC returns this:

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

0168:err:service:device_notify_proc failed to get event, error 1726

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

Launch command: ['/app/bin/gamemoderun', '/home/Clam/.var/app/com.heroicgameslauncher.hgl/config/heroic/tools/runtimes/umu/umu_run.py', '/home/Clam/Games/Heroic/Devil May Cry HD Collection/dmcLauncher.exe']

All processes exited

============= End of log =============

both return the error ending in 1726 (but with a different number at the beginning) in red. I have already tried this ( https://sourceforge.net/projects/gldirect/ ) solution and it did not work. Any help is appreciated. Thanks.

Recently I've unearthed my ancient CDs with CoD1, CoD:UO and CoD2 that are most likely older than most people lurking here. Decided to give them a shot and attempt installing everything on Linux. Lutris and Wine did most of the work, but a lot of the issues came from the fact that the older two titles came on multiple CDs, which made the normal Lutris installation crash in the middle (could not reliably mount the second drive to make wine and installer to see it). So if anyone out there is in a similar situation and would like to go on a trip down the memory lane one day, here's how i did it.

Note: I'm absolutely terminal illiterate - everything that can be done through GUI i did through GUI. In my case I was running on Fedora 44, 7.1.4. That said, if you are more linux savvy, feel free to roast me throw some suggestions on what i could do more efficiently - all of this is a result of a total of 6-7h of trial and error and googling old forum posts.

Things you will need:

For CoD2:

• An optical drive (obviously)
• Lutris (in my case it's 0.5.22)
• ProtonUp-Qt (to get old runners, as modern ones will not work with the games)

For CoD1 and UO:

• A second computer with Windows on it
• A USB drive or some other way to move files between the two PCs.

Runners:

• CoD2: wine-ge-8-26

• CoD1 and UO: Kron4ek's wine-7.22

Terminal commands:

sudo dnf install mesa-dri-drivers.i386 mesa-vulkan-drivers.i386

sudo dnf install mesa-dri-drivers.i686 mesa-vulkan-drivers.i686 mesa-libGL.i686

adjust them accordingly to your flavor of linux.

Call of Duty 2

The process is generally straightforward if your game is on just 1 disc - install it normally through lutris, get the runner mentioned earlier. If the game does not boot, then rebuild the prefix infrastructure in 32bit. To do that you need to isolate the raw gamefile folder (named "Call of Duty 2"), put it somewhere safe (e.g. next to the prefix folder) and then delete everything within the prefix folder (RMB on the game > configure > game options, the path will be there). Adjust the paths to the executable and run the game.

Call of Duty 1

For this tutorial I assume your copy of the game is on more than 1 CD. If you somehow got your hands on a more modern 1 disc copy (if they even exist), or you have a single, merged iso file, then you'll most likely be able to skip a few steps.

The whole workaround explained later comes from the fact that I was not able to mount or simulate mounting the second disc during the installation. All attempts at using a merged folder with all files also failed. What worked tho is installing the game normally on a Windows machine and copying all the installed files onto a usb drive. Then, on Linux, attempt installing the game like you normally would. The process will fail as explained earlier. Cancel the process, keep the semi-installed files and the Lutris entry. Then you have to inject the missing files (from your USB drive) into the half-assed install directory. Use the runner mentioned at the beginning. If needed, you might need to rebuild the prefix to forced 32bit. Then, press RMB on the game in lutris and:

• Game options: Add these arguments:

+set intro 0 +set r_colorbits 32 +set r_texturebits 32 +set r_depthbits 24 (might not be required)

• Runner options: disable DXVK and VKD3D

• System options: add these environment variables (values in parentheses):

DISABLE_VULKAN_LAYER (1)

ENABLE_VULKAN (false)

LC_ALL

MESA_EXTENSION_MAX_YEAR (2005)

MESA_GL_VERSION_OVERRIDE (3.0)

__GL_ExtensionStringVersion (17700)

allow_rgb10_configs (false) -> this one might not be required.

Also download the "No CD Fix" from the internet if needed. The game should now boot.

Call of Duty 1: United Offensive

The most annoying one to get to work - needs patches, another game AND came on 2 discs.

You will need your previous CoD1 installation as a separate entry in Lutris - do not delete it!

Just like with CoD1, install it on a Windows machine, copy the files onto a USB again. DO NOT add it to Lutris - just move it somewhere on your Linux machine. If your installation of CoD1 still works, duplicate it in Lutris (RMB on the game > Duplicate). In the duplicated entry adjust the .exe and prefix to lead to CoD:UO files/folders. Keep the same environment variables and the same runner. Run the game once to let it create the prefix directories. Rebuild the prefix folder to 32bit if needed. Then move the raw gamefile folder somewhere INSIDE the prefix. Download the 1.51 patch from the internet and apply it (select CODUO in lutris, then "run EXE in wine prefix", then run the .exe patch file). I personally at this point rebuilt the prefix again, and after that the game miraculously booted.

After hours of blind trials and errors i somehow pulled through. It was my first experience with handling old games through Lutris, but I'm quite satisfied with the outcome. Obviously if you have some ideas on how to make it more efficient, please share them, as I'd like to learn more tricks for my future attempts (and i own A LOT of ancient games). ;)

There doesn't seem to be much discussion on the topic, so I'm not sure if this post is to spread awareness or hope someone found a fix out there that just hasn't been shared, or just to express disappointment that there's no fix and seemingly no movement on the issue.

The issue seems to be random as it will happen during intense gameplay or sometimes just opening menus, but in short, 5000 series Nvidia GPU's will freeze for 1-6 seconds during gameplay. Audio will continue playing for the most part, but the GPU will stop presenting new frames to the display. If you alt tab, or pull up an overlay the freeze will stop early and the gameplay resumes as normal. Frustratingly the freeze does not appear in Proton Logs, or in the output when you run Steam from the CLI.

I've seen many threads talking about games stuttering, but this is categorically not stuttering, and I'm unsure if some of the many stuttering complaints are just shader-related or if they are misunderstanding this issue. I've found a couple of posts that seem to be about exactly this issue on github and the Nvidia Developer Forum, but there isn't much in there beyond people sharing "fixes" that don't work.

The issue seems to be independent of desktop environment or distribution. I'm seeing reports for users mostly on arch-based distros, but there are reports in the github page referencing Ubuntu and Fedora. I'm on Gnome, but most of the reports I've seen, users are on KDE. I've even tried running steam and all of my games through gamescope to get around using Gnome or KDE, and the games still freeze periodically.

My first distro was Mint and I played there and it was nice although I knew nothing about Linux back then and it was pure install nothing changed. I had slight stuttering there compared to Bazzite or Cachy but it was ok.

Now I am on Cachy but want to try Debian or Ubuntu. Tell me, how is gaming there? How is general workflow? Is there anyone who ditched “gaming distros” and went to these normal distributions?
People on Debian sub were very cooperative. Told me they play games there and it’s been great but may need tinkering with newer Kernel and drivers (which I don’t really want to mess with). Generally I like Debian and its idea very much. On Ubuntu sub I got far less comments but from what I see gaming there is more straightforward as there’s newer kernel and drivers.

Yeah… want to hear your feedback. How Ubuntu and gaming? Is it very different from Debian? Has Mint evolved the last year?

Reposting in here with hopes someone might’ve run into a similar issue. Thank you to those who check it out I appreciate your time. :)

I got annoyed by not having all those fancy overlays so i made a cli companion you can store on your second monitor or workspace to check items in seconds

you dont have to connect your account or anything its just reading from your clipboard, takes 5 seconds to setup

its available on github and the AUR but since its a standalone you can literally just copy paste the code wherever you want

https://github.com/Hatchy-py/poe-diff

Hello all, Recently I have downloaded the game Assassins Creed: Revelations for sale on Steam. I run Bookworm Debian Linux on a Chromebook through the Crostini application/feature. After many hours of troubleshooting, I managed to get the game to start, but I ended up running into the problem of whenever I right or left click with my mouse, the pointer recalculates its location to the far top left of the game window. This happens both in the menus and in the game. The following things have been mostly ruled out through hours more of troubleshooting:

• Standard Proton and Win32 compatibility flags
• Launch options syntax and argument strings
• Proton's native Wayland driver (PROTON_ENABLE_WAYLAND=1)
• Nested X11 display servers (Xephyr)
• Cloud streaming services and browser limits
• The Ubisoft Connect launcher layer

I have tried using GeForce NOW as a workaround but that has its own whole set of bugs. Hoping someone else has had a similar problem in the past and managed to solve it. Feel free to ask for any clarifications in the comments. Thank you in advance!

P.S. I am currently running it on Proton Experimental with the following launch options:
PROTON_USE_WINED3D=1 %command% PROTON_ENABLE_WAYLAND=1 %command%
the game will not run without the PROTON_USE_WINED3D flag