Proton 5.0-6 RC testing

[aeikum]

Proton users,

In an effort to get more testing of upcoming Proton builds, we are going to start sharing Release Candidate (RC) builds of new Proton versions before we set them live on Steam. These builds have not yet been through our full QA process, so we encourage you to stick to the default branch if you prefer a stable experience. We hope enthusiastic users will enjoy testing these pre-release builds and sharing their findings with us to help make the final release a better product.

The RC builds will be available in the Steam client on a branch of the Proton 5.0 app called "next". You may need to restart the Steam client for this branch to appear. We will be updating this branch periodically to fix issues found during the RC process. When the RC process is completed and the release graduates to the default branch, we will retire the "next" branch and your Steam client will move you back to the default branch. The source code for this branch is available in the usual repositories on the proton_5.0-next branch. This branch is not stable and may be rewritten.

If you find an issue on the "next" branch, please post about it here. We prefer to get reports here on this issue, and not on individual game issues. We are interested only in new issues that are present in the "next" branch and that are not present on the default branch. If you believe you have found a new issue, please verify that the issue does not occur on the default Proton branch before reporting it here.

This is an experiment. If it goes well, we'll keep doing this. So please, keep your feedback focused and on topic. :)

Here is what's new in 5.0-6 RC1. This is not the final changelog for 5.0-6. Features may be added or removed during the RC process.

-Fix DOOM Eternal DRM failures. This game requires the very latest video drivers.

-Update DXVK to v1.6, plus some fixes for Half-Life: Alyx and Grand Theft Auto 4.

-Performance and graphical improvements for Resident Evil 2 and 3 in both Direct3D 11 and 12 modes.

-Fix VR regression when users have a custom XDG_CONFIG_HOME setting.

-Fix external web browser links in some games.

-Fix 5.0 regressions in Rock of Ages, Dead Space, and Elder Scrolls Online.

-Ignore Wacom tablets that present as joysticks.

-Fix incorrect resolution scaling in Titan Souls. (Removed in RC2.)

-Fix DmC Devil May Cry crashing with rumble controllers.

-Fix Fallout 3, Panzer Corps hanging on launch.

-Improve Rockstar Launcher appearance.

[XakepSDK]

Can we have something like Proton Next tool with branches for different versions instead of branch for 5.0? Because i want to complete some games before testing and test other games and switching every time may be annoying or you may forget to switch back and break your prefix accidentally. Thanks

[DadSchoorse]

This also fixed the 5.0 regression in Victoria 2.

[libcg]

Hi, I can't figure out how to make this work. Only Proton 5.0-5 is showing in Settings -> Steam Play. Proton 5.0 is not showing in the Tools view of the Library, but I see 4.2, 3.7 and 3.16. Finally I can't find Proton when searching the Store. I did restart Steam a couple times.

EDIT: turns out Proton 5.0 was present in my library but hidden. in the Tools sections, search for "Proton", deselect "Sort by recent activity", a "Hidden" section will show with Proton 5.0 in it. right click it, Manage, Remove from Hidden will fix it.

[rstrube]

Hi, I can't figure out how to make this work. Only Proton 5.0-5 is showing in Settings -> Steam Play. Proton 5.0 is not showing in the Tools view of the Library, but I see 4.2, 3.7 and 3.16. Finally I can't find Proton when searching the Store. I did restart Steam a couple times.

I also couldn't find it in the steam settings screen, but I did find it on BETAS tab for Proton itself:

[ghost]

That's great to see the evolution of Proton. But I still miss some games, especially those that use EAC. Do you have any position on this? It would be a very big victory for us in the Linux community. I tested Resident Evil 2 REMAKE and GTA 4 and I didn't feel much of a difference in performance. GTA 4 in this version came back to work more (GTA 4) as RE 2 prevents me from changing the ALT + TAB window and that sucks. Is that a bug or do I have to activate something? In other games they work well and the Rockstar Launcher just got a lot better.

[kisak-valve]

Hello @XakepSDK, splitting the work-in-progress Proton build into a separate release instead of a beta branch blocks Steam from moving all the pre-release testers back to the mainline, supported build of Proton. This was tried early on with the Proton 3.7-beta releases and my understanding is that wasn't the workflow we were looking for.

Friendly reminder that we only want new regressions from between Proton 5.0-5 and Proton 5.0-6 RC to be discussed here. Everything else is considered off-topic for this issue report and should be discussed separately.

Additionally, if you find a regression, please make it clear how it's regressed, which game(s) are involved, that you confirmed the healthier behavior with Proton 5.0-5, and attach a Proton log of the regression.

[clintar]

So how I test this? I have Proton 5.0 set to the -next- and the version file says 5.0.6 RC whatever when looking under browse local files, but I see no way to use it

[folknor]

So how I test this? I have Proton 5.0 set to the -next- and the version file says 5.0.6 RC whatever when looking under browse local files, but I see no way to use it

1. Right click a game in the library
2. Open Properties
3. Check the bottom checkbox that says Force the use of a specific Steam Play compatibility tool
4. Select any version

Of course, a 3-second cursory web search would have told you the same thing.

[clintar]

And that version isn't there for me. Is it for you? Edit: sorry for my rude outburst, @folknor. Thanks for the info. So I just keep 5.0-5, got it

[folknor]

And that version isn't there for me. Is it for you smart ass?

This replaces Proton 5.0-5.

[soredake]

Double cursor bug in dead space is fixed, but 640x480 don't work anymore, logs: steam-47780.log steam-17470.log steam-38400.log https://github.com/ValveSoftware/wine/commit/ed7fc966ba6531f20096b7d7a2ad91870e086c5e

[pingubot]

Hi,

with the 5.0.6 rc, wolfenstein 2 doesn't open on my main monitor anymore, instead it opens in a tiny window on my second monitor.

Opting out of the beta fixes the issue.

Christian

[kisak-valve]

Hello @pingubot, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression and attach the generated $HOME/steam-$APPID.log.

[pingubot]

Hello @pingubot, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression and attach the generated $HOME/steam-$APPID.log.

@kisak-valve attached find the logfile. steam-650500.log

[Kaned1as]

@clintar @libcg to test this you have to follow different procedure.

• Enable "Tools" in library tab

  

• Select Proton 5.0 properties

  

• Opt-in to - next beta

  

Wait till it is downloaded.

@folknor please don't post misleading guides.

[rezzafr33]

Weird, there is no next on my dropdown list, any advice?

[SuperMatt]

I cannot say if this is a bug with Proton or not, but in Doom Eternal, if I alt+tab out of the game and go back in again, the tab key is no longer recognised by the game. I tested the same steps in Quake Champions under the next version of proton , but the tab key continued to function after this, suggesting the problem only exists in Doom Eternal.

The same thing does happen with GloriousEggroll 5.4-GE3, but it does not rule out that Proton 5.6 doesn't have the same bug.

I am running Ubuntu 20.04 beta, with an AMD RX590, Mesa driver version 20.0.2, and AMDVLK installed.

[kisak-valve]

Hello @SuperMatt, please add your feedback to Doom Eternal's compatibility report. Because that game does not work at all with Proton 5.0-5, it can't be investigated as a regression.

[Xinayder]

Seems like there is a regression in Elder Scrolls Online. I switched to the RC branch and tried playing the game. My FPS would sit at around 100-130 depending on the zone I'm in (I tested it at Mournhold's Undaunted Enclave), but with the RC version it dropped to 60-70, with ESYNC disabled and FSYNC enabled.

[libcg]

@Adonai in my case Proton 5.0 isn't showing up at all in the Tools sections even though it's installed.

EDIT: fixed, it was hidden from my library for some reason. I managed to set it up.

[lllsondowlll]

"-Performance and graphical improvements for Resident Evil 2 and 3 in both Direct3D 11 and 12 modes."

Resident Evil 3 doesn't even launch, even with a fresh prefix generated by 5.0.6, not sure how these "improvements" were established. Log file generated is almost 500MBs. Had to compress it to upload. steam-952060.zip

Distro: Manjaro Linux Kernel: 5.4.28-1-MANJARO RAM: 32 GB GPU Driver: NVIDIA 440.64 GPU: NVIDIA GeForce RTX 2080 CPU: Intel Core i7-8700K @ 3.70GHz

[aeikum]

Double cursor bug in dead space is fixed, but 640x480 don't work anymore, logs: steam-47780.log steam-17470.log steam-38400.log ValveSoftware/wine@ed7fc96

@soredake Thanks. Is 640x480 an important resolution for you? We intentionally disabled resolutions smaller than 600 vertical pixels because they don't seem to be reported on most Windows machines, and they were causing an issue in some other game.

[aeikum]

Seems like there is a regression in Elder Scrolls Online. I switched to the RC branch and tried playing the game. My FPS would sit at around 100-130 depending on the zone I'm in (I tested it at Mournhold's Undaunted Enclave), but with the RC version it dropped to 60-70, with ESYNC disabled and FSYNC enabled.

@RockyTV Thank you. We'll look into this. Do you notice a performance drop if you test between 5.0-5+esync and 5.0-6+esync? (E.g. is this performance regression only present when you have fsync enabled?)

[alasky17]

@RockyTV Also, could you provide the specs for your PC?

[aeikum]

Hello. I've just pushed RC2 live. This removes the 600-pixel restriction, which I think should fix the issues that @soredake and @pingubot reported in RC1.

[soredake]

Double cursor bug in dead space is fixed, but 640x480 don't work anymore, logs: steam-47780.log steam-17470.log steam-38400.log ValveSoftware/wine@ed7fc96

@soredake Thanks. Is 640x480 an important resolution for you? We intentionally disabled resolutions smaller than 600 vertical pixels because they don't seem to be reported on most Windows machines, and they were causing an issue in some other game.

I usually play fallout 1/2 at these resolution, so yes, kinda important.

[Xinayder]

@RockyTV Thank you. We'll look into this. Do you notice a performance drop if you test between 5.0-5+esync and 5.0-6+esync? (E.g. is this performance regression only present when you have fsync enabled?)

@RockyTV Also, could you provide the specs for your PC?

I've tested it today and noticed that after a few minutes in game, my FPS will drop from about 110 FPS to 60, with ESYNC disabled and FSYNC enabled. If I enable ESYNC, the average FPS after logging in is about 90-100, then it drops to 50-60.

On the RC version, without ESYNC, the average FPS after logging in is about 70-80, then it drops to 50. And with ESYNC enabled, it had the same results as enabling ESYNC and using the stable version.

My PC specs are the following:

• Ryzen 5 3600
• NVIDIA GTX 970
• 16 GB RAM DDR4
• Arch Linux, kernel linux-zen 5.5.13
• NVIDIA driver 440.64-10

EDIT: these tests were made by running around near the Undaunted Enclave in Mournhold. I noticed that, with the RC version, when I ran inside the Undaunted tent my FPS would drop considerably, and wouldn't go back even after I left the tent.

[pingubot]

@aeikum thx a lot, rc2 indeed fixed the issue with Wolfenstein 2 !

[aeikum]

I've tested it today and noticed that after a few minutes in game, my FPS will drop from about 110 FPS to 60, with ESYNC disabled and FSYNC enabled. If I enable ESYNC, the average FPS after logging in is about 90-100, then it drops to 50-60.

On the RC version, without ESYNC, the average FPS after logging in is about 70-80, then it drops to 50. And with ESYNC enabled, it had the same results as enabling ESYNC and using the stable version.

Just to be clear, if your kernel supports fsync, then you have to also disable FSYNC in order to test with ESYNC. For example, PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=0 will test with esync.

So far our QA hasn't been able to reproduce your problem. I'm not sure I'm reading your findings correctly. Just to simplify, can you fill in your results like this:

Proton 5.0-5 with fsync: Proton 5.0-6-rc with fsync:

Proton 5.0-5 with esync: Proton 5.0-6-rc with esync:

[BlueGoliath]

Attempting to launch any game will delete the "bin" and "lib" folder now. I can no longer manually fix my previous issue(https://github.com/ValveSoftware/Proton/issues/3680) because of this. This didn't happen with the previous RC.

Edit: system updates & reboot and safety chdsk(which returned all good) later and it no longer deletes the files on launch. Some of the updates were Python related.

[aeikum]

Hello, I've pushed an RC3 update to the "next" branch. This update contains a fix for DOOM Eternal crackling sound on hardware with a sample rate other than 48kHz.

[soredake]

With rc3 sound is not crackling anymore in The Cat! Porfirio's Adventure and Kitty Play, but there is new graphical regression.

steam-492270.log steam-823800.log

[aeikum]

@soredake Thanks for reporting the graphics issue.

@Joshua-Ashton See above. Our QA confirmed the issue on AMD with driver 20.0.4 (I think?). Dropping the official DXVK 1.5.5 build into a 5.0-6-rc3 installation fixes the issue. Can you take a look?

[misyltoad]

@soredake @aeikum Would any of you, or the QA team be able to record an apitrace so I can look into that?

Cheers

[alasky17]

@Joshua-Ashton I tried to record an apitrace, but nothing showed up in the compatdata folder, and I got the following message in my terminal when running the 32-bit apitrace.exe: fsync: up and running. Setting breakpad minidump AppID = 492270 Steam_SetMinidumpSteamID: Caching Steam ID: 76561198012355273 [API loaded no]

Here is what I was running, perhaps I did something wrong?: /tmp/proton_alasky/run /home/alasky/Downloads/apitrace-msvc/x86/bin/apitrace.exe trace -a dxgi Game.exe

[alasky17]

@pingubot I've uploaded a build nearly identical to 5.0-6-rc1 here: https://www.codeweavers.com/xfer/alasky/proton-5.0-6-rc/ with the lock code "rc1". When you get a chance, could you get a log of Wolfenstein II working correctly with 5.0-6rc3 (or whatever is the newest release at the time) and launching in a tiny window with this build?

Please add the logging channels "+event,+x11drv,+x11settings,+win". The easiest way to do that is to copy and rename user_settings.sample.py to user_settings.py (in both of the Proton folders that you are logging) and edit that.

You can drop the tarball that I uploaded in ~/.steam/steam/compatibilitytools.d (you might have to create this folder). Then untar it and it will show up as another Proton version option in the drop-down menu in Steam.

Let me know if you need some more pointers to get the logs :) They will show up in your ~ folder, and you will need to rename the first one or it will be overwritten by the second one.

[Xinayder]

So far our QA hasn't been able to reproduce your problem. I'm not sure I'm reading your findings correctly. Just to simplify, can you fill in your results like this:

I just tried doing a round of tests and I think I was mistaken at first saying there was a regression in ESO. Maybe it could be due to my addons or ESO being silly with its performance, but when I login, I get around 120-130 FPS, then after idling for a while it drops down to 40-50, barely reaching 60, and at random times the FPS goes back up to about a hundred.

I have noticed similar performance just now, doing the tests. Same things happen, after idling for a while FPS drops from 110 to 40-50, it'll rarely reach 60 or above. Tried with ESYNC disabled first then FSYNC. Similar results.

[Vash63]

Hello, I've pushed an RC3 update to the "next" branch. This update contains a fix for DOOM Eternal crackling sound on hardware with a sample rate other than 48kHz.

This mostly fixed it for me. It's definitely good enough to be usable now (and maybe the same as Windows?) but it still was crackling intermittently. The main difference is that prior to this update, once the crackling started (usually about ~5 seconds into the music on the intro screen) it was constant and the audio never recovered. Now it seems to crackle for a split second and then recover, and I noticed a couple more recurrences over ~3 hours of play. It's very rare and not really that big of a deal anymore though (and might even happen on Windows). What is notable however is if I set to 48kHz first even prior to RC3, it would never crackle at all.

[misyltoad]

@soredake I can't repro the issue on latest master of DXVK. Interested to know if it works in master for you too... Not that anything changed in master that's related though :-/ :frog:

[misyltoad]

This should be fixed in latest master now, thanks.

[leillo1975]

Hello, I found a problem in 5.0-6. I just tested with Automobilista 2 and the force feedback in my Logitech G29 has gone. After Reinstalling 5.0-5, the problem fixes. Take a look, please.

[kisak-valve]

Hello @leillo1975, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[aeikum]

@leillo1975 Actually, please put WINEDEBUG=+dinput instead of PROTON_LOG.

[leillo1975]

This is the Automobilista 2 log with WINEDEBUG=+dinput steam-1066890.log

[leillo1975]

I have the same problem in rFactor 2: steam-365960.log

[leillo1975]

Seems that FFB are break with this version. Assetto Corsa Competizione has also the same problem: steam-805550.zip

[leillo1975]

I just to test Automoblista 2 with Proton-5.5-GE-1 (@GloriousEggroll ) and has the same problem.

[aeikum]

@leillo1975 I see the problem. I'll have this fixed in the next RC. Thanks again for testing.

[alasky17]

@Joshua-Ashton I tested the current dxvk master and the graphical issue does appear fixed. Thank you!

[Waistless]

@RockyTV You are describing a rather ancient problem with ESO that has existed natively in Windows for the longest time. If you reduce the view distance to around 0-25 you should find this happen a lot less. I suspect the game has some kind of resource leak that gets worse over time. Typically logging out to character select and back resets the state of the game back to normal fps.

It was most noticable IIRC in most of the trials, mid-trial it was helpful to do a re-log if you weren't speedrunning to fix the fps during the particle heavy fights.