There's not many ways this can happen I guess. I've followed this thread because I find interesting that Windows drivers can have an influence on the hardware under Wine/Proton. From my understanding the windows driver loads the registry keys I mentioned above.īut perhaps installing the driver is not doing very much inside the prefix, aside from installing some registry Keys so that some games can detect the wheel. I thought, perhaps installing the driver in the prefix would allow the original thrustmaster driver to be loaded for the game.īut I now doubt that that is the behavior. This device on the host system is passed through to wine/proton so the game can see it. Oversteer is a utility on the Linux host itself, which can modify the device settings. However, I am not sure if it would be even able to talk to wheel hardware. So I assume to get registry values to wheel TM control panel would need to be run in wine prefix. I assume those value are set only "once" - when oversteer/control panel is running. Same as TM control panel is doing in windows - from registry values in this case. Hi do you use oversteer? my understanding is oversteer will set those values when run. Switching the wheel to PS4 mode it's not detected by oversteer or Linux in general but when I start the game it detects it as a Xbox controller. UPDATE: It loads both the libraries every time the game is started. Trace:loaddll:build_module Loaded L"C:\Program Files\Thrustmaster\FFB Racing wheel\drivers\amd64\tmInstall.EXE" at 0000000100000000: native Seems like it's directly loading tm_api_lib_圆4.dll Can’t really say if it’s for better or worse but the pedals do provide more depth or range of motion for sure.Ĭould you shed some light on this perhaps? I honestly feel like this should not have done anything yet it made a big difference. I race daily and I have very fine settings I always keep, but this changed it quite significantly. What really surprised me is that the feel of the wheel and especially the pedals changed a lot after installing the drivers. With both titles the games did not recognize my previous configuration and I had to recalibrate everything. I then decided to test other titles such as ams2 and acc. The wheel is detected and works perfectly. I was pretty sure it won’t do anything, knowing wine has massive limitation when it comes to driver support, but it did. Eventually I gave up assuming it was a game issue.Ī few days later I noticed a post on vales proton bug tracker about someone who installed the windows drivers inside the prefix and then the wheel was detected and mapped correctly on startup. I recently acquired F1 22 and it did not recognize my wheel no matter what I did. I know this will sounds a bit strange but I have been able to reproduce this on multiple occasions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |