Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DiRT Rally 2.0 (690790) Force Feedback doesn't work #2366

Open
xpander69 opened this issue Feb 26, 2019 · 16 comments

Comments

Projects
None yet
7 participants
@xpander69
Copy link

commented Feb 26, 2019

Compatibility Report

  • Game: DiRT Rally 2.0
  • App ID: 690790

System Information

  • GPU: GTX 1080 Ti

  • Driver version: nvidia 418.43

  • Kernel version: 4.20

  • System info: https://pastebin.com/wHH2qhNY

  • Proton version: 3.16-7 Beta

  • Proton log: <!-- steam-690790.log

  • Problem: Force Feedback doesn't work with the Logitech G920 Wheel
    With wine-staging 4.2 Force Feedback works fine.

@kisak-valve kisak-valve changed the title DiRT Rally 2.0 Force Feedback doesn't work DiRT Rally 2.0 (690790) Force Feedback doesn't work Feb 26, 2019

@kisak-valve kisak-valve added the XAudio2 label Feb 26, 2019

@nyanloutre

This comment has been minimized.

Copy link

commented Feb 27, 2019

Is there currently a way to use wine 4.2 with Proton ?

I found https://github.com/kakra/wine-proton but it doesn't seem to work with Dirt Rally 2.0

This issue aside, the game is working well for me with a GTX 1070

EDIT: I am running wine 4.2 staging and wine for Windows as a workaround. force feedback is working well.

@leillo1975

This comment has been minimized.

Copy link

commented Mar 5, 2019

In addition to the absence of feedback I notice that my G29 steering wheel has a delay in movement. I don't know if this can be configured in game. Is important to say that my wheel is not detected as predefined G29 and is necessary to assign the bottons and axis. Do you have the same problem?

@nyanloutre

This comment has been minimized.

Copy link

commented Mar 6, 2019

@leillo1975 how much of a delay do you have ?

@leillo1975

This comment has been minimized.

Copy link

commented Mar 6, 2019

split-second.... but enough to appreciate it on screen, and of course driving worse . Compared to DIRT Rally 1 it is very noticeable

@gotzl

This comment has been minimized.

Copy link

commented Mar 8, 2019

For me, the game runs fine with wine-4.2 and Windows-Steam, apart from occasional sound issues.
I've also build a local proton with this this version of wine, but FFB does not work with that.
Can it be that some patch included in proton breaks FFB?

@xpander69

This comment has been minimized.

Copy link
Author

commented Mar 9, 2019

Yeah i think some of the proton Contoller patches might do this... Not 100% sure but few unity (the Forest and Lacuna Passage for example) games also have issues with mouse dragging into bottom of the screen, while working perfectly fine with controller or using wine-staging they work fine with keyboard/mouse also. So i think there are some controller hacks in proton that might break other things

@gotzl

This comment has been minimized.

Copy link

commented Mar 9, 2019

I've dumped the dinput winedebug, maybe s.o. is able to find s.t. in there.
The log with proton-3.16-8 Beta where FFB is not working is here.
The log with wine-4.1 where FFB is working is here.

My input-setup is a Logitech Driving Force GT wheel and Fanatac CSL pedals (split from the wheel).
The dumps correspond to the early startup of the game. In case of wine-4.1, one recognizes a short application of force at some point, which indicates that the FFB of the wheel gets somehow initiated. This doesn't happen with proton.

@xpander69

This comment has been minimized.

Copy link
Author

commented Mar 27, 2019

No go with proton 4.2 for me either and no go with custom proton-tkg 4.4.r8 either. Something with native steam client killing the FFB? as the FFB works fine with regular wine 4.1 to 4.4

@nyanloutre

This comment has been minimized.

Copy link

commented Apr 30, 2019

Wine and steam-windows are causing frequent crash for me (full system freeze with audio looping). It never happens with Steam and Proton 4.2.

@nyanloutre

This comment has been minimized.

Copy link

commented May 21, 2019

I might have an idea by changing this file

In dlls/dinput/dinput_main.c there is a dinput_devices struct and each element is a type of device. The patch above is adding SDL support and a new type of device, but it is inserted at the top of the struct (and is used first when entering the EnumDevices loop). So if it's moved to the bottom, find_joydevs (the one working included in joystick_linuxinput_device) will be used instead of find_sdldevs (the one not working from the SDL Proton patch included in joystick_sdl_device)

Also this is a complete guess that I didn't test, but if someone want to give it a try here is my Proton fork with the patch applied

But this may be an ugly fix, the SDL/dinput compatibility layer is missing something (the force feedback should work), but my knowledge in the SDL library is limited so I wouldn't know what to look for in the patch.

@nyanloutre

This comment has been minimized.

Copy link

commented May 27, 2019

Even by disable the SDL patch completely Force Feedback is not working, but the wheel is detected more correctly (button pictures in menu are accurate)

@tipe84

This comment has been minimized.

Copy link

commented May 28, 2019

I was able to get Dirt 2.0 to recognize my G27 wheel correctly using proton-tkg 4.4.r9. Earlier builds that I tried didn’t work and after the next proton update (in early April) it stopped working. I have been using that build and updating only dxvk. If the game recognizes the wheel correctly all I had to do is replug my wheel in the game and force feedback works.

When the wheel is recognized as "Logitech® G27" force feedback will work. If it is recognized as "G27 Racing Wheel" it will not work.

@NekoNoor

This comment has been minimized.

Copy link

commented Jun 4, 2019

not sure if this is what the disable sdl patch does, but the /dev/input/event* device for wheels is the only one that supports force feedback, so if proton only detects the /dev/input/js* device somehow, force feedback won't work

@nyanloutre

This comment has been minimized.

Copy link

commented Jun 4, 2019

@NekoNoor no for this I still needed to disable the js device using the wine controller panel (also needed when using steam in wine without Proton)

@NekoNoor

This comment has been minimized.

Copy link

commented Jun 16, 2019

I saw this in the patch notes of a recent steam client update:

  • Added support for rumble pass-through for virtual controllers. This fixes missing rumble support for any controllers opted into Steam Input, and rumble emulation support for the Steam controller.

I was hoping this would fix this issue but it still seems to be present in proton 4.2-7 with the latest client

@NekoNoor

This comment has been minimized.

Copy link

commented Jun 29, 2019

I got it to work! using proton-tkg 4.11r6 with sdl support disabled in the config when compiling. then disabling the js joystick in wine control and when the wheel is recognized as "Logitech® G29" I replug in my wheel and force feedback fully works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.