Issues on many games, how to debug and contrib #70
Comments
|
Hello, thanks for the report. Quite a lot to chew through, apologies if I miss anything. First of all, could you just confirm that you have working FFB in some games?
What does WRC 8 do without
I don't own the game, do you mean there's a setting in the game for this and with input set to
General thoughts: Some input/FFB issues could be attributed to stuff similar to #38, i.e. games having an internal database of wheels, and Linux for some reason or other not fulfilling the requirements the game sets to recognise a wheel. Some games use Still, each game might have its own issues, so the approach unfortunately might have to differ from game to game.
Man in the middle works pretty well for monitoring FFB, could maybe also work for monitoring input though I'm not entirely sure how that would be useful. The thing is that this driver doesn't actually handle input, that job is delegated to the HID subsystem in Linux. Frankly I'm fairly confident the input is handled correctly by the Linux kernel, and I would suspect these issues exists outside of it, either in Wine/Proton or the games themselves (or any combination of both). Wine tracing might also give some insight into what a game is doing, or at least what services its requesting from Wine, which might be helpful, though very context sensitive.
Entirely possible that some subsystem steps in and tweaks inputs between the kernel and whatever game you're trying to play, always something to keep in mind. Also note that there are at least two subsystems for joysticks,
Dinput for me as well, couldn't get FFB effects to work in the control panel but they work in games so not sure what that's about. Maybe something worth looking into.
I'm guessing the handbrake shows up as a separate controller with one axis. If you know which axis the handbrake shows up as, you should be able to remap it on a system level to some other axis to avoid games interpreting the handbrake as a 'normal' input. Alternatively, maybe calibrate the device to a range so that the axis doesn't register left input when not being touched. |
Hi
I had issues with the wheel on many games (all with thrustmaster driver installed on prefix) with T300RS:
Game: WRC 8
Proton: 8-11
Status: Works all except force feedback
Game: Dirt5
Proton: 7-55, 8-11
Status: Crashes at start (only when wheel is plugged)
I noticed it has a tm_api_lib_x64.dll
Game: VRally 4
Proton: 8-11
Status: Seems it's miss mapped and:
I added
WINEDLLOVERRIDES="xinput1_3=n,b"steam launch option for some games to work, like wrc generationsI wonder where i should look at to debug it
I'm a programmer however not a super hardcore nerd but i would try my best
Should i monitor like man in the middle ? Would virtualbox serve for this ? or some wine tracing ? or rebuild the module with some debug info added ?
I had other input issues unrelated to this driver too that somehow i think they may be related to elogind and seats
Should i see the ts300 as an xinput device on wine control ?
I see it as a dinput device
I also turned off the thrustmaster api in flavour to dinput on wrc generations and everything went fine
(unrelated too) I also have the always left issue when i plug a custom handbrake
Thanks for any help in advance
dmesg:
The text was updated successfully, but these errors were encountered: