@GooseCreature Interesting, do you have an idea of which rogue devices are causing the issues? And as such which do you remove? I didn't see any active usb devices obvious for me to remove. You say you need to do this before each session. I guess you mean every time you boot your pc? Thx
I did ranked today, F4 tatuus. I'd put the flatspot wave type to sine (0) and the magnitude back to 0.25, and I still had mayor issues. The f4 tatuus seems to be the car to choose when it comes to reproducing this problem. I've disabled flatspots for now, until there's something new to test.
FFB problems: yes Wheelbase: TS-PC Rim: Ferrari 488 Challenge Driver version: 2.10.10.0 Firmware version: 11.00-R7.00 Windows version: 1909 Comments and other relevant info: Pulls to the left after a flatspot, but feels like a flat tire. Only happens below about 100 km/h. No problems if I turn off Collision effect. Me switching between Collision on/off
I find either an extra TM wheel or unnamed devices, I don't get them every time, probably 1 in 5 times. Rogue devices will have either a pink or white pseudo LED rather than the preferred green. I check with USBDview every time I fire up RR. The devices won't be active, just right click, uninstall any device that hasn't a green LED, works every time on my system, get the weird wheel shenanigans, check USBDview and new devices will have been produced, get rid and all is returned to normal.
@GooseCreature Thanks for the info! I found those inactive thrustmaster devices as well, I'm going to try to remove just those to see if that helps. Would be nice if we can pinpoint to a single device.
Uninstalling the inactive thrustmaster devices did not do it for me. I have collision effect always disabled.
That's unfortunate, works every time for myself. You do right click uninstall them? It makes no difference whether collision effects are at 0 to 200. What is bugging me is the total randomness of it, put a fair few laps in this week and only had one rogue device appear in a 7 day period, what I have noticed is it makes absolutely no difference what I set kerb effects and min forces, I get exactly the same feeling no matter what I set the parameters to, even if this is zero on both.
Yes, right click uninstall. I hope you find out some additional info. I'm always using VR. Don't know if that matters. If having a flat spot, it feels like the wheel is clipping near the center, but the graph doesn't show any clipping. Would it be possible that the wheel receives so much data it can't handle it?
FFB problems: yes Wheelbase: T150 Rim: Stock Driver version: 2.10.10.0 Firmware version: 22 Windows version: Windows 10 pro 64bit Comments and other relevant info: It has been appeared after the 2020. november big windows 10 update. And It appears when I use the kerbs or the green artificial grass, but not immediately. For example I tried with wtcr cars in Shanghai, in the last corner I use the kerbs on the exit, and the wheel starts to oscillate just after the finish line. I've also tried with older firmware and older driver, but with the same (bad) result. Nothing helped. A clean windows install will be the next... Video:
FFB problems: no Wheelbase: t300RS Rim: Stock rim Driver version: 2.10.10.0 Firmware version: 29.0 Windows version: Win10Pro 10.0.19041 build 19041 Comments and other relevant info: Every works perfectly including flatspots, no adverse effects when taking tyre damage. Fine with custom RCS and default.
Btw I was able to reproduce my issue with a fresh, vanilla T300 profile The problem started after going slightly wide in T1, only hit record after that.
Can you post the RCS file from that one please, flatspots should be turned off in the default now so I need to check that one over. Thanks
@Balrog You can try installing the previous driver package (Know to work perfectly on my wheel, firmware v29) and see if that fixes your issue. https://www.driverscloud.com/en/ser...river/72630-85841/thrustmaster-2019-ttrs-1exe
Btw is it possible to downgrade the firmware? My googling skills have failed me before, but I haven't found anything useful this time either.
I've seen some say it can be done by installing a previous package as linked above, but some say not. Worth a go. Worst case scenario you just have what you have now
FFB problems: YES Wheelbase: TMX PRO Rim: Stock Driver version: 2.10.10.0 Firmware version: 15 Windows version: Windows 10 PRO (64) V: 2004 Comments and other relevant info: Since September I have been the same problems with FFB. Normally, the problems start when I block brakes and make flat spots on the wheels. It's specilly hard with the WTCR. I've tried similar actions that you describe. I contacted with Thrustmaster Technical Sevice and I sent the wheel. They have said that the wheel has no problems. Does anybody know what is the reason of the problem?. And the solution?.
FFB problems: YES Wheelbase: T300RS Rim: Thrustmaster F599XX EVO 30 Alcantara Edition Driver version: 2.10.10.0 Firmware version: 25 Windows version: 10.0.19042 Build 19042 (Win 10 Home - 64 bit) Comments and other relevant info: Flat spots causing FFB and wheel effects to be delayed vs input. Corrects itself in some time, but will return again. New install on new PC with a freshly created wheel profile. Will try removing the flat spots lines of code in the meantime.
From another thread- not sure if you've done this yet or not: You can edit your *.rcs inside the folder \Documents\My Games\SimBin\RaceRoom Racing Experiecnce\UserData\ControlSet And change to FFB flatspot magnitude="0.0" Use the windows notepad app to open the file to make the change and save. I've just made the change and have not had time to test.