Proton Proton 10.0-2 Release Candidate testing

Hey all!

We've put together a new Proton 10.0 Release Candidate build for you to test.

In the Steam client the Proton 10.0 app should have a release-candidate beta branch (look for Proton 10.0 in your Steam Library, right click -> Properties... -> BETAS) which you can choose to start testing the 10.0-2 Release Candidates (note that the name of the build in the Steam Settings dialog will not be updated). I will post changes here when we push new builds. The source for the latest RC build is available on the proton_10.0-rc branch in this repository. This branch may be force pushed.

We are interested only in issues that are new to the 10.0-2 RC builds. If you believe that something broke please confirm that the problem does not occur with 10.0-1 (the "none" beta branch) before reporting it here.

The changelog is tentative - it has not yet been verified by our QA staff, and can change before the final release as we add or remove features during RC testing.

Most if not all of the fixes listed below were deployed previously via Proton Experimental or Proton Hotfix. Appropriate Proton version was used automatically on a game basis on the Steam Decks. This release stabilizes those changes after extensive testing.

Now playable: Stardust Skate, STAR OCEAN THE DIVINE FORCE, Champions of Anteria, IL-2 Sturmovik Cliffs of Dover, Click&Fight, Tunnet, WRC Generations, Post Mortem.
Fixed Proton 10 regressions:
- Warframe launcher should no longer have issues displaying titlebar elements.
- Enshrouded no longer crashes when refreshing server list.
- VRChat video playback issue that affected some instances is fixed.
- The Sims 2 Legacy Collection is playable again.
- Atelier Yumia: The Alchemist of Memories & the Envisioned Land is playable again.
- Dishonored 2 window can be dragged around on Gnome again.
- Forza Horizon 4 and 5 no longer require focus change to not have black screen.
- Oddworld: Stranger's Wrath HD setting launcher renders correctly again.
- OpenVR is working with 32 bit games again.
Fixed The First Berserker: Khazan wrongly displaying a warning about the drive the game is installed on.
Fixed Cornerpond not rendering transparency correctly.
Fixed scaling in Imperiums: Greek Wars in fullscreen mode.
Fixed games not starting when upgrading from a removed Proton installation.
Fixed The Finals showing EOS EAC updater window twice on start.
Fixed boss intro videos playback in River City Girls.
Fixed Black Desert launcher rendering all black on Nvidia + Wayland setups.
Mitigated OpenSSL-related issues with many games including Claybook, Gravel, SMITE that happen on newer Intel CPUs.
Enabled nvapi for The Last Of Us 2.
Improved rendering of Alpha Protocol's launcher.
Improved situation with Once Human having bad stutter on certain setups.
Fixed Risk of Rain 2 and The Last of Us Part 2 Remastered not working on certains setups.
Fixed Monster Jam Showdown not being able to link Epic Games account.
Fixed Astroneer not being able to connect to an encrypted dedicated server.
Fixed transfer account option in The Eminence in Shadow: Master of Garden.
Fixed DLSS frame generation options being disabled in The Elder Scrolls IV: Oblivion Remastered.
Fixed radio not playing music in Fallout 3: GOTY.
Fixed game lag spikes in Mary Skelter Finale, Death end re;Quest, Death end re;Quest 2, Megadimension Neptunia VIIR and Dragon Star Varnir.
Fixed in-game screen capture in The Sims 2 Legacy Collection.
Fixed querying graphics settings in Marvel Rivals.
Fixed Tiny Troopers Global Ops having focus issues when using Steam Overlay on Steam Deck.
Fixed The First Berserker: Khazan showing a warning about outdated OS/GPU drivers version.
Fixed The Elder Scrolls V: Skyrim Special Edition having wrong scaling with high DPI.
Fixed Tower Unite crashing in VR mode.
Fixed built-in web browser in Banter.
Fixed The Witcher 3: Wild Hunt having issue with Nvidia HairWorks - hair should no longer disappear.
Fixed Ghostbusters: The Video Game Remastered showing green line at the bottom of video in the main menu.
Fixed beginning of the Planet of the Apes: Last Frontier being a black screen.
Fixed the new Final Fantasy XIV Online launcher not working.
Fixed Xalia not being able to fully progress through prerequisite installation in MultiVersus using only the controller.
Fixed a crash late in game in Crysis 2 Remastered.
Fixed Defiance failing to connect to the game.
Fixed touch input not working correctly in menus of No Man's Sky.
Fixed controller support in MySims Kingdom.
Fixed Space Engineers not registering trigger input with controllers.
Fixed Grand Theft Auto V Enhanced showing driver version warning with AMD GPUs.
Fixed screen darkening in e-Racer.
Fixed some games using DirectStorage not working with Intel GPUs.
Improved force feedback support in Assetto Corsa EVO.
Fixed Dead Island 2 not detecting Epic Online Services and not allowing cross-play.
Fixed controller detection issues with devices that do not have axes, only buttons.
Fixed DOOM (2016) having issues with window decorations on certain setups.
Fixed VRChat not being able to Alt+F4 out of game after playing some videos using Unity Player.
Fixed VRChat crashing on some setups when h264 playback is attempted.
Fixed Dune: Awakening DLSS support.
Enabled Xalia by default instead of only for selected titles. It should work with most launchers using builtin Win32 controls.
Updated Wine-Mono to 10.0.0.
Updated Xalia to 0.4.6.
Updated vkd3d to vkd3d-1.16-194-g7c0da1747a89
Updated vkd3d-proton to v2.14.1-286-g2b766f7639cf
Updated dxvk to v2.6.2-1-g08870ab62b36
Updated dxvk-nvapi to v0.9.0-8-g5fa4b3c7cddc

Happy testing :-)

Jun 19 '25 19:06 ivyl

Warframe launcher should no longer have issues displaying titlebar elements.

The launcher now is unable to find the Warframe.x64.exe executable. I reported it when Proton 10 beta came out on the Warframe issue.

Jun 20 '25 21:06 braiam

New Release Candidate is now live. The changes:

Disabled Xalia for Rockstar Launcher - aftar a recent update it got native contoller support which resulted in registering events twice.
Fixed windowing regression introduced in 10.0-2 builds that made RiME not behave correctly when alt-tabbing.

Jul 03 '25 18:07 ivyl

Hi, I might have found something:

In Dungeons and Dragons Online, when I go into TPS mode (which makes the camera move with mouse movements), sometimes the camera will rotate towards a random direction at a random yet constant speed while my mouse is at rest, and when I do move my mouse it feels like the game is fighting for the control.

My native resolution is 1920x1080, and this only happens when in-game resolution is below that, and becomes very noticeable at 1280x720 which is what I always play with (I do so due to UI issues specific to the game).

I did a quick test; this behavior doesn't exist in 10.0-1, and curiously it doesn't happen with gamescope + 10.0-2 RC, nor does it happen when the game is set to "windowed".

Summary Camera spins towards random direction at random yet constant speed when

fullscreen, below native resolution, 10.0-2 RC

but not when

windowed, 10.0-2 RC
fullscreen, native resolution, 10.0-2 RC
10.0-2 RC, gamescope -H 720 -f -- %command%
10.0-1, regardless of fullscreen / windowed / resolution

Jul 09 '25 06:07 Recipient4626

@Recipient4626 I took a quick look at 1280x720p as a non-native resolution and couldn't replicate this on my current setup. What Linux distro do you use currently, what desktop environment do you use, and is it X11 or Wayland?

Additionally, could you grab a log for me of the failure please? You can do that by opening the games Properties in Steam, and typingPROTON_LOG=+event,+x11drv,+x11settings,+win,+system,+xrandr,+fshack %command% into the launch options. This will create a log file in your home directory. If you would be able to upload it here, I would appreciate it. If it's a large file, you can try compressing it. Proton log files compress really well.

Jul 09 '25 15:07 AJuujarvi

@Recipient4626 I have some additional questions ... First off - any tips for us to reproduce this? Does it happen after standing around for a while without moving the mouse/camera, or immediately after moving the mouse/camera actively, or after a certain amount of time, etc etc? Any tips would be very useful since you said it only happens "sometimes" :)

Also - what directx version are you using?

in addition to providing the details @AJuujarvi mentioned and a log, could you also please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in your reply?

Jul 09 '25 18:07 alasky17

Replying to https://github.com/ValveSoftware/Proton/issues/8830#issuecomment-3053089558 Replying to https://github.com/ValveSoftware/Proton/issues/8830#issuecomment-3053692162

Here's the log: steam-206480.log.tar.gz

and here's the system information: https://gist.github.com/Recipient4626/112dddcbbc7ecfd82e04bc8783060b74

I am running Arch Linux, KDE Plasma 6.4.2 (Wayland). Every package is up-to-date, and my Steam is from Arch official repository. In-game "OPTIONS" menu shows that "Graphics Hardware Level" is set to "DirectX11".

How I reproduce it: After logging into the game world, press T to enter TPS mode. Sometimes this is enough to trigger it immediately.

If it doesn't then I try:

while in TPS mode, move the mouse erratically
press T to leave TPS mode, T again to enter TPS mode, repeatedly, possibly placing the cursor at different locations before re-entering TPS mode

On my system, it happens within a minute by spamming T and random mouse movements.

Jul 10 '25 07:07 Recipient4626

@Recipient4626 Thank you for all the details! We were finally able to reproduce the bug (which is the first step towards a fix in these cases - WM bugs like this can be extremely tricky). Interestingly, I'm also seeing this behavior on 10.0-1f. Could you please retest 10.0-1f and if you still cannot repro the bug there, could I see a log? I'm fairly confident that I'm seeing the same bug as you, so the difference between 10.0-1f and 10.0-2-rc is baffling.

Jul 11 '25 15:07 alasky17

Replying to https://github.com/ValveSoftware/Proton/issues/8830#issuecomment-3062793490

Yes you are right; I reproduced that on 10.0-1f this time. Maybe I was extremely lucky (or unlucky) last time.

Sorry about the confusion : (

I wasn't playing Dungeons & Dragons Online (until I logged in a few days ago), I don't remember exactly the Proton version on which this bug didn't exist.

I did a test on Proton 9.0-4 and it was fine. Here's the log if that helps: steam-206480.log.tar.gz

I'm having trouble building Proton from source, so sadly I can't dive into this further for now : (

Jul 12 '25 07:07 Recipient4626

@Recipient4626 Thank you for confirming! No worries at all - we can take it from here now that we can repro :D And thank you for the report! It is still a regression for us to attempt to fix :)

Jul 14 '25 20:07 alasky17

Steam controller input is intermittently not working for me on Hyperdimension Neptunia Re;Birth1 (282900) with the proton 10 release candidate. It works on another computer of mine (PC 2) but usually doesn't work on (PC 1). On PC 1, it wasn't working last night until a reboot, and today it only worked on the first launch of the game, and didn't on the 4 tries after. Neptunia Re;Birth1 requires a controller to be connected at launch or else the controller option won't be available in the settings so maybe that's related? To confirm, steam input is working on other games with Proton 10 as well as on Neptunia Re;Birth1 with Proton 9 and Experimental. I've tested PC 2 with kernel 6.8.0-62-generic which is still working

PC 1

GPU: NVIDIA GeForce RTX 2070
Video driver version: NVIDIA 575.64.03
Kernel version: 6.8.0-62-generic
Link to full system information: https://gist.github.com/ikaikahub/e4af5de5061679f361ebaed632c5c929

PC 2

GPU: Intel Mesa Intel (ADL GT2)
Video driver version: 4.6 Mesa 24.2.8-1ubuntu1~24.04.1
Kernel version: 6.14.0-24-generic
Link to full system information report: https://gist.github.com/ikaikahub/ae31af3d63dfca56f0b28a996205683d

Some logs I've collected steam-282900-proton 9.0-4 [working] (pc 1).log steam-282900-proton 10 release candidate [not working] (pc 1).log steam-282900-proton 10 release candidate [working] (pc 2).log steam-282900-proton experimental [working] (pc 1).log

Edit: I've tested proton 10.0-1 and the issue isn't there either steam-282900-proton 10.0-1 [working] (pc 1).log

Jul 27 '25 04:07 ikaikahub

Hi @ikaikahub. I wasn't able to reproduce it locally and I don't see anything suspicious in the logs.

Which controller are we talking about? Is it the Steam Controller?

Do you use the same controller between the two machines?

WRT PC1 I just want to make sure that I got you right - the controller for sure works 100% reliably with Proton 9, Proton Experimental and 10.0-1, but the intermittent issue is only present with 10.0-2 Release Candidate?

Few things to check:

PC1 runs Muffin, so that's Cinnamon? And PC2 runs xfwm4/XFCE? Can you check if using XFCE on PC1 helps?
Can you set command line for the game to PROTON_USE_XALIA=0 %command% and see if this helps with the situation on PC1? It's a long shot, but I don't see anything else on the commit list that could explain the behavior change when comparing Experimental vs 10.0-2 vs 10.0-1.
Can you provide me with log with PROTON_LOG=+hid,+xinput,+dinput,+rawinput,+plugplay,+setupapi,+joystick,+steamclient %command% from PC1 using Proton 10.0-2 RC for both scenarios - working and broken controller? Thanks in advance!

Jul 29 '25 14:07 ivyl

I use a Switch 1 Pro Controller connected via usb with this option enabled on both computers

The issue isn't present on Proton 9 and Experimental, after testing some more it is actually on both versions of Proton 10 which I realise isn't the purpose of this thread. This issue is so random sometimes that it's hard to be completely certain but I've never had it happen on Proton 9 or Experimental. Only on versions of Proton 10

It usually seems to work for a couple launches (if at all), then stop working for subsequent launches. Rebooting or switching desktop environments can make it work again for a launch or two

PROTON_USE_XALIA=0 %command% doesn't have an effect Switching to Xfce resolves the problem and the problem occurs on PC 2 as well when running Cinnamon

These logs are all from PC 1 Xfce: steam-282900 release candidate xfce working.log steam-282900 non release candidate xfce working.log Cinnamon: steam-282900 non release candidate working.log steam-282900 non release candidate not working.log steam-282900 release candidate working.log steam-282900 release candidate not working.log

Sorry this was the wrong place to report this after all but I hope this can still help

Jul 29 '25 17:07 ikaikahub

Thanks for the details and double checking your findings! We will continue looking into this as it's very unexpected behavior. It won't be blocking 10.0-2 release though as you've said it also happens with 10.0-1.

Jul 29 '25 19:07 ivyl

@ikaikahub I did take a small look at this, and I was able to confirm on my end the issue only happens on Cinnamon. It happens for me on Proton 9.0-4 as well however, so it looks like this is not a regressive issue in regards to this issue even happening. It happens 100% of the time for me on Proton 9.0-4, 10.0-1, and 10.0-2.

I checked on Windows and found that whenever I switched to the Switch Pro Controller, it caused the menu to freak out before leaving the menu. It unfortunately does not save the controller as turned on for me on Windows as well.

Jul 29 '25 20:07 AJuujarvi

I'm closing this issue as 10.0-2 just went live https://github.com/ValveSoftware/Proton/releases/tag/proton-10.0-2c

Huge thank you to everyone who contributed in here. I really do appreciate anyone posting in good faith and helping us to verify the initial findings and suspicions. We'll continue chasing the leads that turned out not to be -2 regressions as normal bugs.

Jul 29 '25 21:07 ivyl