Heroes of Might and Magic V no longer works with 7.0-2 RC. It seems to crash while playing an intro video (I can hear some audio ...). It used to work for me with 7.0.

steam-15170.log

I have a question

Does the fix for Forza Horizon 5 also fix the stuttering issue?

Does it fix crash in game on fall guys ?

The issue is for testing of regressions compared to previous released stable and reporting of those. 👀
If it wasn't fixed on experimental then it likely isn't fixed here is my guess. People in the games own issue might be able to help you :)

UNO multiplayer isn’t working for me. Tried on Proton 7.0-1, Experimental, and the 7.0-2-rc, always get a crash when joining a game.

I’m not using the Steam version, I installed Ubisoft Connect via non-Steam game and then pointed it at the Ubisoft Connect launcher, then launch UNO from there. This might be causing the problem, if someone with the proper Steam version could test that would be great, however I doubt it is causing the issue as I have other official Ubisoft games on Steam and they essentially use the exact same method to launch.

@shinratdr if the issue isn't specific to this release candidate it's better if you post it in the games own proton issue. I can see online play is an issue for others aswell

Derp i missed the fix part of the changelog. My bad.

Guys, would be nice if you could include the following commits from DXVK's master branch for this release:

• https://github.com/doitsujin/dxvk/commit/b0ed9e30ceeb8ef16d242ea189f53e717ab37201
• https://github.com/doitsujin/dxvk/commit/957a305ca822c90a358a9771194cfdacb3bc7f47

They fix a regression in Metal Gear Rising introduced with Proton 7.0-1 (DXVK >= 1.9.3) that freezes your whole system. This issue has been reported and discussed by other users as well:

• https://github.com/doitsujin/dxvk/issues/2569
• https://www.protondb.com/app/235460

Also fix #4913 for me

@cypx You are saying in that post it has been fixed in this RC
Or are you not saying that it needs fixing?

@Blisto91 it has been fixed in this RC

Hi, I am sorry if this is the wrong place. But I seem to have encountered a usb device regression between 7.0-1 and proton experimental (I assume that it is the 7.0-2 that this thread is all about.. )

[#4134 (comment)](https://github.com/ValveSoftware/Proton/issues/4134#issuecomment-1102758990)

The usb rudder pedals are present when I have forced proton 7.0-1, but when I force proton - experimental I only get the flight stick and the throttle.

7.0-2 RC is not the same as Experimental. Some changes stay Experimental only due to known problems. That includes a lot of controller changes, especially around windows.gaming.input implementation.

Can you check if you see the issue with Proton 7.0-2 RC specifically? You can switch to it by searching for Proton 7.0 in your library, right clicking on it, going to Properties... and then selecting proton-7.0-2-rc in the BETAS tab. You can undo it later by selecting None beta.

Replying to https://github.com/ValveSoftware/Proton/issues/5749#issuecomment-1102791487

Ah sorry. Thank you for the instructions. I get the same behaviour with the 7.0-2 RC as with the experimental branch. If I launch the game with Proton 7 with beta set to none, I get rudders but if I launch it with the beta set to 7.0-2 RC i get only my stick and throttle.

With no beta:

With beta set to the RC:

I can post the logs as well for both cases, but they are around 25 MB each and maybe don't contain anything useful for this.

( Also sorry for accidentally deleting my original post )

Thanks for checking @hefax. I suspect that it may be caused by https://github.com/ValveSoftware/wine/commit/7c8b30bbe89619fb219657982e92472ac9ae2665. Sadly I don't have access to the same controller. Can you try this build which reverts the mentioned commit and tell me if it makes any difference? We may want to add your device to the hidraw accept list.

https://www.codeweavers.com/xfer/ahiler/hidraw-for-all/ (password: hidraw)

You can just drop the directory contained in the archive into $HOME/.steam/root/compatibilitytools.d/ and it should appear on the compatibility tools list after you restart Steam.

That build showed the rudder pedals ok.

Just to confirm that the correct build was indeed loaded here is the head of the log.

If you want to add the device into a separate accept list here should be the necessary info:
lsusb:
Bus 007 Device 010: ID 044f:b679 ThrustMaster, Inc. T-Rudder

As an additional info (not sure if this is relevant in any way) I had to make a custom udev rule for the device. Because it has no buttons and 3 axis the system assumed that it was an accelerometer. This rule corrects that assumption
udev rule:
KERNEL=="*", ATTRS{idVendor}=="044f", ATTRS{idProduct}=="b679", MODE="0666", TAG+="uaccess", ENV{ID_INPUT_JOYSTICK}="1", ENV{ID_INPUT_ACCELEROMETER}=""

@hefax that was helpful, thanks!

https://www.codeweavers.com/xfer/ahiler/hidraw-for-all/ (password: hidraw)

can you take a look at a hidraw-for-tfrp.tar.zst available in the same location? Instead of a revert it now has the following change:

diff --git a/dlls/winebus.sys/bus_udev.c b/dlls/winebus.sys/bus_udev.c
index 90878e229bb..eeb0b6ff712 100644
--- a/dlls/winebus.sys/bus_udev.c
+++ b/dlls/winebus.sys/bus_udev.c
@@ -1695,7 +1695,7 @@ static void udev_add_device(struct udev_device *dev, int fd)
         memcpy(desc.serialnumber, zeros, sizeof(zeros));
     }
 
-    if (!is_dualshock4_gamepad(desc.vid, desc.pid) && !is_dualsense_gamepad(desc.vid, desc.pid))
+    if (!is_dualshock4_gamepad(desc.vid, desc.pid) && !is_dualsense_gamepad(desc.vid, desc.pid) && !is_thrustmaster_rudder_pedals(desc.vid, desc.pid))
     {
         TRACE("hidraw %s: deferring %s to a different backend\n", debugstr_a(devnode), debugstr_device_desc(&desc));
         close(fd);
diff --git a/dlls/winebus.sys/unix_private.h b/dlls/winebus.sys/unix_private.h
index eff03dce3ce..c544c8207e6 100644
--- a/dlls/winebus.sys/unix_private.h
+++ b/dlls/winebus.sys/unix_private.h
@@ -284,5 +284,6 @@ BOOL is_xbox_gamepad(WORD vid, WORD pid) DECLSPEC_HIDDEN;
 BOOL is_dualshock4_gamepad(WORD vid, WORD pid) DECLSPEC_HIDDEN;
 BOOL is_dualsense_gamepad(WORD vid, WORD pid) DECLSPEC_HIDDEN;
 BOOL is_logitech_g920(WORD vid, WORD pid) DECLSPEC_HIDDEN;
+BOOL is_thrustmaster_rudder_pedals(WORD vid, WORD pid) DECLSPEC_HIDDEN;
 
 #endif /* __WINEBUS_UNIX_PRIVATE_H */
diff --git a/dlls/winebus.sys/unixlib.c b/dlls/winebus.sys/unixlib.c
index 636d4f1c557..3cf9ff4f1a5 100644
--- a/dlls/winebus.sys/unixlib.c
+++ b/dlls/winebus.sys/unixlib.c
@@ -105,6 +105,11 @@ BOOL is_logitech_g920(WORD vid, WORD pid)
     return vid == 0x046D && pid == 0xC262;
 }
 
+BOOL is_thrustmaster_rudder_pedals(WORD vid, WORD pid)
+{
+    return vid == 0x044F && pid == 0xB679;
+}
+
 struct mouse_device
 {
     struct unix_device unix_device;

If that works for you that's great and will be included in -2.

Also I've ordered T1600M combo with rudder and HOTAS so I should have easier way of debugging issues with similar setups in the future, but it will take some weeks to ship.

That patch was way simpler than what I expected. And yes it solved my issue perfectly.

Thanks for the effort :)

RC branch has been updated and your problem should be fixed there @hefax.

Also it the update fixes glitchy video playback in Monster Train, Hardspace: Shipbreaker, Car Mechanic Simulator 2021 and Nine Sols Demo.

@ranplayer cherry-picking changes is a bit problematic, so those will live in experimental for now.

7.0-2 is released, thanks all for testing and feedback :-)