search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.67k stars 1.07k forks source link

Proton 9.0-3 Release Candidate testing #8006

Closed ivyl closed 2 months ago

ivyl commented 3 months ago

Hey all!

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

In the Steam client the Proton 9.0 app should have a release-candidate beta branch (look for Proton 9.0 in your Steam Library, right click -> Properties... -> BETAS) which you can choose to start testing the 9.0-3 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_9.0-rc branch in this repository. This branch may be force pushed.

We are interested only in issues that are new to the 9.0-3 RC builds. If you believe that something broke please confirm that the problem does not occur with 9.0-2 (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.

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.

ranplayer commented 3 months ago

is D8VK available for this RC ?

ivyl commented 3 months ago

D8VK is no more. It's a part of DXVK nowadays. Yes, included DXVK contains D8VK work. Also see PROTON_DXVK_D3D8 in README on the RC branch.

ranplayer commented 3 months ago

Thanks for the explanation. I'm going to test some D3D8 games with this variable.

ghost commented 3 months ago

cool, new proton 😃

Tiagoquix commented 3 months ago

@ivyl The default is to use D3D8 from DXVK in this Proton version?

alasky17 commented 3 months ago

@Tiagoquix No - the default has not been switched for D3D8 to using DXVK - it is currently available as a launch option to enable manually.

ranplayer commented 3 months ago

I've found a minor regression for Split/Second (297860): it's not recognizing my DualShock4 controller (working with 9.0-2 and 8.0-5).

Logs: steam-297860-split-second.tar.gz

Specs:

alasky17 commented 3 months ago

@ranplayer Thank you for the report!! I can repro this, and it is clearly a regression between 9.0-2 and 9.0-3. It looks like a side-effect of enabling the evdev controller work by default. We will look into this and resolve things so that the regression doesn't ship with 9.0-3 stable.

ranplayer commented 3 months ago

Great @alasky17 . I'm still retesting everything I can on my end to help you guys with this release.

minuteworld1 commented 3 months ago

for king of fighters, it plays flawlessly except that it starts in windowed mode and when you alt-enter, it only shows the bottom right corner of the screen zoomed way in and when you go into setting and change the resolution to fullscreen/4k and hit accept, it will keep switching to the wrong resolution and sometimes have black bars on the top and bottom of the screen. you have to continually switch your resolution back and forth for it to actually display right in 4k. and once you get it to display right in 4k and save the changes, when you exit and re-enter the game, it completley forgets what you set it too and the game is at the bottom right, zoomed in again.

maybe this is a nvidia issue since I'm on nvidia but I thought i should bring this to your attention.

kisak-valve commented 3 months ago

Hello @minuteworld1, friendly reminder that on release candidate issue reports, we are specifically looking for very recent regressions. In this case, any regressions between Proton 9.0-2 and Proton 9.0-3 rc. If this isn't the case for your findings, then please add a note to the compatibility report for the game instead of discussing it here.

matte-schwartz commented 3 months ago

I am seeing the same issue with a DualSense controller (connected via USB) and STAR WARS Jedi: Survivor (1774580). Input stops working with Proton 9.0-3 rc while it works as expected with Proton 9.0-2.

alasky17 commented 3 months ago

@matte-schwartz Thank you for the report! This should be fixed with Proton 9.0-3-rc2. This breakage came from an unexpected place - we yanked the commit from 9.0-3 to give it more time to stew in experimental. Experimental-9.0 still has the commit, along with a new commit to fix the regression. If you wouldn't mind also testing the bleeding-edge-9.0 branch of Proton - Experimental to confirm this is fixed for you (it was fixed in my testing) that would be greatly appreciated :) The new fix will also be in the next experimental release.

alasky17 commented 3 months ago

@ranplayer We pulled the evdev backend change from Proton 9.0-3 for now -- this should be "fixed" with Proton 9.0-3-rc2.

Unfortunately, after further testing, it looks like this might actually be Windows behavior. We tested the game on Windows, and found that the behavior with 9.0-3 actually matches Windows better than 9.0-2. Both the Xbox1 and PS4 controllers were broken on Windows, both with and without steam input enabled :/

I found a bunch of user reports complaining of this, and we found that the xbox360 controller is the only one actually supported by the game (which works without steam input enabled on both Windows and Proton, even with the new changes), and on Windows, none of the controllers work with Steam input enabled. We are still going to take a look to see if there is a way that we can be better than Windows for this game :D

matte-schwartz commented 3 months ago

@alasky17 thanks for the quick fix! unfortunately I am unable to re-test at this time, as my EA App has decided it no longer wants to launch under any Proton version whatsoever... this seems to be an unrelated issue, judging by other comments on the existing Jedi Survivor issue. I'll add my own Proton logs onto the existing compatibility report as even Proton 9-02 stable, which was working last night, no longer works. I will comment again here if I manage to sort that issue and confirm that the changes solve the controller regression.

ranplayer commented 3 months ago

@alasky17 thank you for the explanation and keeping the old behavior for now (I didn't know this was the expected Window behavior )

matte-schwartz commented 3 months ago

@alasky17 one total game reinstall later, and proton experimental bleeding-edge does indeed fix my controller issue :tada:

zelburg commented 2 months ago

Is there any hope the issue with multiple monitors will be addressed with this release of Proton 9?

It makes little sense for many of to use Proton 9, let along test 9-beta while this is still a problem.

At least maybe an acknowledgment that it IS a known issue and perhaps ONE of the following:

A) We're aware of this issue and are working on a fix. B) We're aware of this issue and have plans to work on a fix. C) We're aware of this issue and have no intention of fixing it.

hajosattila commented 2 months ago

The EA app isn't working link

tgurr commented 2 months ago

Possible regression in Shadow of the Tomb Raider (750920)

ivyl commented 2 months ago

The issue with multiple monitors is not a 9.0-3 regression and is being troubleshooted in the dedicated issue.

As of Shadow of the Tomb Rider we'll have a look into it. Thanks for reporting.

Closing this issue as RC phase is over.