Open whizse opened 3 years ago
ivyl
commented
3 years ago The game should be playable out of the box with today's experimental.
Steering wheels should work, but some other controllers may not, as they requires as of yet unimplemented windows.gaming.input.dll. This can be worked around by setting the game's prefix to win7 and overriding xinput1_3.dll with the builtin.
xpander69
commented
3 years ago Works great with Logitech G920.. FFB works fine also. Thank you for the proton-experimental update! i'm playing with DX11 mode on my 1080Ti cause DX12 performance is half of the DX11 for me.
Gameplay video with G920 Cam: https://youtu.be/8c8y61dN9w8
xpander69
commented
2 years ago There was a game update (3GB) recently and it seems i lost some of the ingame sounds for some reason. Co-driver is quiet, road effects like gravel stones hitting the car are missing and the car engine volume is changing weirdly depending on the RPM. Feels like 5.1 or 7.1 is turned on on a 2 speakers or on headset.
log: steam-1462810.log
could be problem on my system also though, but haven't noticed that issue on any other game as of yet.
weird parts in the log:
57112.961:0140:0144:warn:debugstr:OutputDebugStringA "D:\\Dev\\PlayAll\\Code\\Runtime\\Common\\PlayAll\\Common\\Core\\MountTool.cpp(121) : warning : Mount failed : Path = <COMMON/SOUNDS/VOICES/EN> Virtual Drive = <VOICES:/>\n"
57112.961:0140:0144:trace:seh:dispatch_exception code=40010006 flags=0 addr=000000007B01236E ip=000000007B01236E tid=0144
57112.961:0140:0144:trace:seh:dispatch_exception info[0]=00000000000000a3
57112.961:0140:0144:trace:seh:dispatch_exception info[1]=000000000063a5e0
57112.961:0140:0144:warn:seh:dispatch_exception "D:\\Dev\\PlayAll\\Code\\Runtime\\Common\\PlayAll\\Common\\Core\\MountTool.cpp(121) : warning : Mount failed : Path = <COMMON/SOUNDS/VOICES/EN> Virtual Drive = <VOICES:/>\n"edit: seems there are people on windows also having this issue: https://steamcommunity.com/app/1462810/discussions/0/3085520348624868994/
xpander69
commented
2 years ago Ok fixed the audio issue by editing:
~/SteamLibrary/steamapps/compatdata/1462810/pfx/drive_c/users/steamuser/Documents/My Games/WRC10/UserSettings.cfg
and setting spatial audio to false
Engine.Audio.SpatialMix = false;
seems to affect windows users also, so probably not a proton bug
xpander69
commented
2 years ago Ok one more weird issue i noticed. Im not sure if its the game itself (i don't have windows to try) or something in proton. Basically i have G920 and a cheap chinese Arduino based Handbreak. Everything is nicely detected in the game, including handbreak axis. But the problem is that when i hit the handbreak i will lose the output from my wheel when 1 of the axis is active on my wheel. so i have to release lets say acceleration for a sec and then i can use it again. Its like both of those devices aren't used simultaneously. its either one or other. Not sure how to debug this or if anyone on windows can try this. Same thing seems to happen when i map the handbreak to my keyboard button for example. Might be a game bug also ofc.
TheAquabat
commented
2 years ago the fix proposed doesn't solve the issue with my controller I have a GameSir T4 pro, it can work as a Xbox One controller or an Xbox 360 controller none of them work. (I tried the bleeding edge branch of proton experimental.)
here's a log with Proton experimental
https://drive.google.com/file/d/1jbKIZKA6BlS2ZaKLQbd6K34IBqDDVj8D/view?usp=sharing
but also I must mention that a previous steam beta broke controller support on all games for me, it was fixed with another beta update, but maybe it wasn't completely fixed. and also it's strange because the start button will work on the start screen, but if I go to the configuration menu there is no controller to select.
EDIT: it works but setting on big picture to use the controller to control the desktop, like a virtual mouse and keyboard... so to speak in "emulation mode" then I have to configure the key bindings one by one, which is not ideal.
EDIT2: I made it work but with Proton 6.15-GE-2, I first updated vk3d, then ran protontricks 1462810 winecfg set windows to windows 7, and then added this to the command launch options WINEDLLOVERRIDES=”xinput1_3=b” %command%. (also remember to delete/recreate the pfx prefix, first) Seems to me that something has regressed on proton experimental (and other proton version like proton ge 6.20) that makes the controller not work even using basically the same workarounds.
ivyl
commented
2 years ago We had to switch to STEAM_COMPAT_CONFIG, so instead of the override it may be necessary to STEAM_COMPAT_CONFIG="" %command% in addition to using win7 prefix.
TheAquabat
commented
2 years ago yes can confirm that command works in WRC8, which esentially has the same issue. (I refunded WRC10 tho) thanks
Samsagax
commented
2 years ago We had to switch to
STEAM_COMPAT_CONFIG, so instead of the override it may be necessary toSTEAM_COMPAT_CONFIG="" %command%in addition to using win7 prefix.
I'm using Big Picture Mode with controller support for a PS4, I've installed WRC 10 yesterday and worked out of the box with proton 6.3-8 (current one). But the controller I'm using is not recognized, only mouse and keyboard (not very playable).
Tried the suggested fix (setting STEAM_COMPAT_CONFIG="" %command% as launch option) but didn't work, the game showed a crash report utility.
Tested other proton versions (GE-6.20, GE-7.1) with and without the launch option and had the same result except this time the crash report utility didn't show up.
Does setting the prefix to win7 made any difference in this? I'm not sure how to configure it.
Samsagax
commented
2 years ago New tests I made:
Proton 7 as is won't recognize the PS4 controller.
I tested proton 6.3-8 with the Windows version set to "win7" and the PS4 controller works without any launch option configuration. But the buttons are scrambled: Y axis on sticks are reversed, A and B buttons are Circle and Square. Triggers are scrambled too, mapping to "right stick left".
Then setting WINEDLLOVERRIDES=”xinput1_3=b” %command% as command line option yielded the same result. The controller is recognized, but the mappings are scrambled.
After the fix @ivyl suggested (setting STEAM_COMPAT_CONFIG="" %command% as launch option) The game did not start at all showing an error report window under proton 6.3-8. Under proton 7.0-1 after setting the windows version (via registry editing or winecfg) the game starts and the PS controller is recognized with it's own correct mapping.
So maybe it is worth removing this change for this title and also override the Windows version as "win7" in the user registry.
BruebachL
commented
2 years ago I'm unable to either join or create a lobby in any kind of multiplayer menu. Anyone experiencing a similar issue?
polluxau
commented
1 month ago in 2024 this game works perfectly under proton 9, no audio issues, played a public multiplayer match, my 8bitdo controller is working properly, no fps problems on my amd card either, works better under dxvk tho
would like to see if this game can be changed to playable as i dont see any major problems anymore
Compatibility Report
System Information
I confirm:
Symptoms
The game starts and seem to work but have similar issues to WRC 8 (tracked in bug #4567), it needs Proton Experimental to run. It will also need xinput1_3 set to native, or Windows version to 7.
The game still crashes because of problems with the DX12 renderer. Bug report with trace here.
As a workaround, the game can be configured to use the DX11 renderer. This needs be set in a configuration file, but the game crashes before the file is created. I have saved a working copy (set to DX11) here.
Place UserSettings.cfg in
<Steam-folder>/steamapps/compatdata/1462810/pfx/drive_c/users/steamuser/My Documents/My Games/WRC10My racing wheel (Logitech G29) is detected and works with force feedback, but only if Steam Input is disabled. I've seen reports of this happening on Windows too so it's probably not an issue unique to Proton.
Extended gameplay have not been tried, network play have not been tested. There might be other issues. I noticed some intermittent problems loading the leaderboards but it might not at all be related to Proton.