ah that could explain it, if the main firmware was not communicating correctly with the motor firmware it didn't show the motor related settings and didn't show the correct version number.
@Stephen Frith try to re-flash the firmware by using the manual update function of the firmware manager to see if the problem gets fixed. If it stays you probably need to open a support ticket.
I just saw that my WheelBase HUB is not fully aligned with the guide ! I think this is the root cause, finally something that give me hope, will reattach it and tried
I recently bought a new PC with a Ryzen 9 7900x and RTX 4090. I've had to fresh install everything with the latest drivers, and my DD2 was no different. Currently on Driver 447 FWWB 3.0.0.6 FWM 3.0.0.2 FWWHEEL 6 FWRELEASE6 FWPEDALS 1.35. After updating and installing everything ran smooth for the first few hours. I drive a lot of winged sprint cars on iRacing and I have run into an issue on multiple different occasions that on corner entry wheel input is freezing for a quarter second (causing spin outs). I have also been able to replicate this "input freeze" in AC and Dirt 2.0, so it's not a game issue. I have checked my Windows USB devices to ensure that the wheelbase isn't on any power save options. I have also tried plugging in my wheelbase into the different types of USB options available on the back of my PC. The issue showed up only since updating to this and it persists. I am at a complete loss other than starting a support ticket, any ideas?
I have a video clip of the telemetry from iRacing where you can see the wheel freeze and then return back to normal state, if that helps describe.
Define "many". I saw a hand full of reports, if not even less. Compared to the 67k Views this thread has with let's say around 30k people who then also actually loaded the driver, that's not really "many" for me. If it would be a widespread driver issue then it would be reported by a LOT more people.
So yes, for me this totally sounds like a hardware issue.
I bought WRC Generations, and to test it, I had to use my old clubsport V1 😀
To update it, I downloaded driver package n°447 including the firmware 691. This firmware doesn't works with CSW V1, it erased the possibility to choose beetween differents settings on my BMW Wheel (S_1 / S_2...). The entire menu of my wheel was made of only two options : SEN & FF.
After many tests I had to came back to the driver package 423 and so firmware 687 to recover the choice beetwen five settings menus. So I think you a yet aware of this issue, I post here in case of you didn't already know... 🤷
Does CSW V1 firmware won't be update anymore ? And does CSW v1 is compatible with Fanlab (all tuning menus are unavailable on my soft) ?
No, the Firmware did not erased the possibility to choose between different settings on your BMW Wheel (S_1 / S_2 ...).
You are just using the (not so new anymore) Standard Tuning Menu which was introduced over a year ago.
This was shown to you in the attached very big fat popup during the update process which you seem to have just clicked away without reading it.
That new Standard Tuning Menu on old Belt Bases only consists of SEN and FFB settings, so thats actually correct and intended.
To get back into the "old" Advanced Tuning Menu with the 5 Setups and more Tuning Menu settings, you need to press and hold the Tuning Menu Button for 3 seconds while being in the Tuning Menu.
So the CSW v1 is still fully supported at the moment as there is a new Firmware included for it in driver 447 which would not be the case if the base wouldnt be supported anymore. However, as the base is now 10 years old and its electronics are quite outdated, there might be a point where support will end in the future, but for now, its still fully supported by driver 447 and firmware 691.
I am not so convinced being an affected user. My DD2 has been flawless other than a loose USB port that was repaired under warranty. This issue only showed up for me personally when my new CPU came in. Not sure if I am a casualty of being on the bleeding edge of technology (probably 1% of all users currently) with the Ryzen 9 7900x and the motherboards they require or if it has something to do with the USB ports being the latest generation. Either way I have seen multiple other people experiencing the same issue here that I am. Could it be a coincidence, possibly? Maybe... but I would rather see if this is a driver issue before I go open a support ticket, get spun around in circles for days (Looking at you tech support), end up having to mail in my base, have my wallet crushed again after just upgrading my CPU. I guess all i'm really trying to ask for here is some clarity on whats going on? In this thread this issue seems to have popped up for multiple users since this drivers release, is Fanatec aware that this is an issue?
I seriously can't trust my wheel in official races right now :(
If its only happening in one game and not in others you've already answered the question what is likely causing the issue. Why would you know think its a driver issue? Maybe its more due to how this specific game implemented the wheel and feature support, maybe being inefficient in comparison to the other games not showing the issue.
Feel free to share the mentioned telemetry clip, might be interesting.
Can you use the downgrade function of the firmware manager to go back to a previous version and try if the issue is then gone?
If it started after updating the firmware and is not happening anymore after downgrading the firmware then there is no need to open a support ticket, as there is no hardware defect. If it's caused by the firmware, we need to look into it and fix it there, but to know for sure it would be great if people having the issue could double check and let us know.
Ok so do I understand correctly that the issue of a freezing steering angle for a brief moment is not because of a firmware update but rather since a motherboard update. Meaning this might be a motherboard compatibility issue?
I've come across some general USB issues with AMD and found the following suggestions which might help or might not:
Try a different USB port. For example, front USB instead of back. Or located lower/higher on the mainboard. USB ports close together are likely using the same USB controller but if they are spaced further apart, they are probably using different controllers.
Updating BIOS if available
Switch from PCI Gen 4 to Gen 3 in the BIOS settings
Turning off Global C-State setting in the BIOS settings
I'm unsure of what is causing but the issue has only shown up since plugging everything into my new CPU which required a fresh install of everything. I did go back into my old computer and checked out what driver that was on and it was 439. When my wheel was on my old machine it worked fine. I had heard someone else say in they thought it had to do with the latest gen motherboards or USB ports. I also posted that clip above, watch the telemetry at the 5-7 second mark.
Thanks for looking into this Marcel, I will try the steps you've listed and report back.
Exact same thing happen, and I do a wrong update / downgrade, my base go to repair . But the problem start freezing wheel input and lost the car on iracing .
thank you for explain all this
My setup it’s not a amd , but new intel z690 and i9 12900kf
Comments
ah that could explain it, if the main firmware was not communicating correctly with the motor firmware it didn't show the motor related settings and didn't show the correct version number.
@Stephen Frith try to re-flash the firmware by using the manual update function of the firmware manager to see if the problem gets fixed. If it stays you probably need to open a support ticket.
Lol.....
You should read carefully in order to help others. Otherwise you just confuse people.
😁
I just saw that my WheelBase HUB is not fully aligned with the guide ! I think this is the root cause, finally something that give me hope, will reattach it and tried
When using dirt 4 with DD2, frame drops occur.
1% LOW 10 It is inconvenient to use because the screen is cut off when the game is running in the early frame.
If you turn off the DD2 power and use it as a pad or keyboard, there is no problem.
There is no problem in other games such as dirt rally 2.0 dirt 5 and assetto corsa among the games currently used.
I think it's a driver problem, but I'd like to know how to fix it.
Wheel Base Model (product ID): ...DD2
Steering Wheel Model (product ID): ....Podium Steering Wheel Porsche 911 GT3
Driver Version: ....447
Base FW Version: ....3.0.0.6
Motor FW Version: ....3.0.0.2
Wheel FW Version: ....HUB 6, BUTTON MODULE 21, QR 6
FanaLab Version: ....1.66
I recently bought a new PC with a Ryzen 9 7900x and RTX 4090. I've had to fresh install everything with the latest drivers, and my DD2 was no different. Currently on Driver 447 FWWB 3.0.0.6 FWM 3.0.0.2 FWWHEEL 6 FWRELEASE6 FWPEDALS 1.35. After updating and installing everything ran smooth for the first few hours. I drive a lot of winged sprint cars on iRacing and I have run into an issue on multiple different occasions that on corner entry wheel input is freezing for a quarter second (causing spin outs). I have also been able to replicate this "input freeze" in AC and Dirt 2.0, so it's not a game issue. I have checked my Windows USB devices to ensure that the wheelbase isn't on any power save options. I have also tried plugging in my wheelbase into the different types of USB options available on the back of my PC. The issue showed up only since updating to this and it persists. I am at a complete loss other than starting a support ticket, any ideas?
I have a video clip of the telemetry from iRacing where you can see the wheel freeze and then return back to normal state, if that helps describe.
Exact same thing happen with me
Yes i did everything, unfortunately it didn't help
Today the loss of ffb has happened again
Base shaft seems normal
Then you should contact the support as its very likely a hardware issue.
Is it a coincidence that many other people report the same problem? I think it may be a driver problem rather than a hardware problem
Define "many". I saw a hand full of reports, if not even less. Compared to the 67k Views this thread has with let's say around 30k people who then also actually loaded the driver, that's not really "many" for me. If it would be a widespread driver issue then it would be reported by a LOT more people.
So yes, for me this totally sounds like a hardware issue.
Hello Fanatec team & fans !
I bought WRC Generations, and to test it, I had to use my old clubsport V1 😀
To update it, I downloaded driver package n°447 including the firmware 691. This firmware doesn't works with CSW V1, it erased the possibility to choose beetween differents settings on my BMW Wheel (S_1 / S_2...). The entire menu of my wheel was made of only two options : SEN & FF.
After many tests I had to came back to the driver package 423 and so firmware 687 to recover the choice beetwen five settings menus. So I think you a yet aware of this issue, I post here in case of you didn't already know... 🤷
Does CSW V1 firmware won't be update anymore ? And does CSW v1 is compatible with Fanlab (all tuning menus are unavailable on my soft) ?
Thanks.
No, the Firmware did not erased the possibility to choose between different settings on your BMW Wheel (S_1 / S_2 ...).
You are just using the (not so new anymore) Standard Tuning Menu which was introduced over a year ago.
This was shown to you in the attached very big fat popup during the update process which you seem to have just clicked away without reading it.
That new Standard Tuning Menu on old Belt Bases only consists of SEN and FFB settings, so thats actually correct and intended.
To get back into the "old" Advanced Tuning Menu with the 5 Setups and more Tuning Menu settings, you need to press and hold the Tuning Menu Button for 3 seconds while being in the Tuning Menu.
So the CSW v1 is still fully supported at the moment as there is a new Firmware included for it in driver 447 which would not be the case if the base wouldnt be supported anymore. However, as the base is now 10 years old and its electronics are quite outdated, there might be a point where support will end in the future, but for now, its still fully supported by driver 447 and firmware 691.
Thanks a lot for you reply and my appologies for the wrong shortcut !
Is there any update on whether or not this is a driver issue or a hardware issue? My DD2 is bricked until a solution is found.
Steering input jumps are a FW issue and they get improved with the next FW.
I am not so convinced being an affected user. My DD2 has been flawless other than a loose USB port that was repaired under warranty. This issue only showed up for me personally when my new CPU came in. Not sure if I am a casualty of being on the bleeding edge of technology (probably 1% of all users currently) with the Ryzen 9 7900x and the motherboards they require or if it has something to do with the USB ports being the latest generation. Either way I have seen multiple other people experiencing the same issue here that I am. Could it be a coincidence, possibly? Maybe... but I would rather see if this is a driver issue before I go open a support ticket, get spun around in circles for days (Looking at you tech support), end up having to mail in my base, have my wallet crushed again after just upgrading my CPU. I guess all i'm really trying to ask for here is some clarity on whats going on? In this thread this issue seems to have popped up for multiple users since this drivers release, is Fanatec aware that this is an issue?
I seriously can't trust my wheel in official races right now :(
Thanks for the clarity, anything I can do until the next FW drops?
No, but your issue does not sound like the steering input jump issue anyway but, again, more like a hardware issue.
What specifically makes you think this is a hardware issue? You will have to pardon my ignorance, I am a boomer.
If its only happening in one game and not in others you've already answered the question what is likely causing the issue. Why would you know think its a driver issue? Maybe its more due to how this specific game implemented the wheel and feature support, maybe being inefficient in comparison to the other games not showing the issue.
Feel free to share the mentioned telemetry clip, might be interesting.
Can you use the downgrade function of the firmware manager to go back to a previous version and try if the issue is then gone?
If it started after updating the firmware and is not happening anymore after downgrading the firmware then there is no need to open a support ticket, as there is no hardware defect. If it's caused by the firmware, we need to look into it and fix it there, but to know for sure it would be great if people having the issue could double check and let us know.
For you it was also since updating the firmware?
Can you do the things suggested in the comment above and let me know of the result?
There is one way to find out if its a hardware or a firmware issue.
Go back to the driver an older driver/firmware and see if the issue is happening there or not.
Ok so do I understand correctly that the issue of a freezing steering angle for a brief moment is not because of a firmware update but rather since a motherboard update. Meaning this might be a motherboard compatibility issue?
I've come across some general USB issues with AMD and found the following suggestions which might help or might not:
Source: AMD Suggests Possible Fixes for Ryzen USB Connectivity Issues | Tom's Hardware (tomshardware.com)
Here is the clip of what is happening. Pay attention to the telemetry wheel in the bottom left corner at the 5-7 second mark.
Fanatec Freeze.mkv - Google Drive
I'm unsure of what is causing but the issue has only shown up since plugging everything into my new CPU which required a fresh install of everything. I did go back into my old computer and checked out what driver that was on and it was 439. When my wheel was on my old machine it worked fine. I had heard someone else say in they thought it had to do with the latest gen motherboards or USB ports. I also posted that clip above, watch the telemetry at the 5-7 second mark.
Thanks for looking into this Marcel, I will try the steps you've listed and report back.
Thanks for the video
Exact same thing happen, and I do a wrong update / downgrade, my base go to repair . But the problem start freezing wheel input and lost the car on iracing .
thank you for explain all this
My setup it’s not a amd , but new intel z690 and i9 12900kf
Should I hold off on that downgrade? Don't want to do the wrong thing here and make it worse.