This driver not solved the grainy feeling on EA WRC. Does not matter i use the NFR, or not, or in game the Wheel / Tyre friction, the grainy issue still here on DD1. Very noticable on tarmac stages. Please fix this! Thank you!
As you say its only an issue in this one game, you are sure its not just the game which has not so good FFB (which I have heard from some)? Why do you think its a Firmware issue which Fanatec needs to fix instead of a game issue which Codemasters needs to fix?
Natural friction can start to feel weird after some time of driving. In case you experience issues with NFR, we suggest to turn it OFF for now. (this got now fixed for the Podium DD but can still happen on the CSL DD. We will now apply the fix for the CSL DD as well)
This weird feel a lot of people they saying "grainy".
It's like sand is stuck in the base. It's interesting you never heard of this, when this problem has been present for 4-5 years.
Sometimes help, if i turn off the base, and turn on again. But i only feel this issue on this game, so probably the game need some fix.
It's very likely a completely different issue when it's happening also with NFR OFF.
And when it only and exclusively happens in WRC then the Chance is extremely high that's it's an issue with the FFB of this one game.
If you have grainy FFB in all games also with NFR set to OFF then it would be a hardware issue where the base starts to feel grainy when it gets warm but apparently that's also not your issue as you say it's only happening in this one game so my best guess is that its a game related FFB issue (or creators intend that they actually want the FFB to feel like that).
I always use NFR and NIN on ACC like 10%, and everything it's fine, so the base i guess not have any problem. I just thought this weird feeling with the NFR was fixed in this game. Probably this is a road effect, but in WRC, no options to turn off, or something.
I received my new CS DD and wheel QR2s and everything set up fine except this firmware below.
ClubSport DD(+) WQR: 1.0.0.3 (NEW)
The base and my two wheels are all updated and seems to be working well so far. I ran the new base and both my wheels in iRacing and everything seems normal. What should I do next to have all firmware updated, specifically this WQR version?
I did remove the wheel each time I tried that FW. I have not tried removing all the usb connections and will give that a try next should I remove everything except the DD wheelbase USB?
thanks for the quick response. BTW what happens if this won’t update trying this next step, can I continue using it?
You can continue using it but you should then contact the support as that would indicate that something with the QR might be wrong.
QR update is quite important as that is responsible for communication to the wheel so when you cant update the QR and you are stuck on the one which was pre-installed then you will encounter a lot of weird steering wheel issues, some wheels wont even work at all for example etc. So to get the QR to update is essential.
Maurice it worked! Thanks so much for the very quick response and the tip of the other USBs. I removed all but the mouse and keyboard (yes I know why not wireless!) and changed spots and retried and it worked the first time.
why would the UI come back as incompatible? I've tried installing the correct 64 bit driver multiple times now. no matter what I try the ui will not open for me. i had it on this system before then only thing that's changed would be the fact that I've done a clean windows install recently. every other program/app I had before has installed fine. some help would be much appreciated.
Then it's a game issue as all freezing related firmware issues are definitely fixed and there is no room for more improvements and it only happens in AMS2.
I fail to see how the PBME freezing in AMS2 is a Reiza issue and not a Fanatec issue. There is no issue with the AMS2 telemetry as other software, like Simhub which displays exactly the same telemetry feed as the PBME, works absolutely perfectly.
The fact that it is only the PBME that seems to have issues with the data feed points to it being Fanatec issue and not a game issue - otherwise all hardware displaying this data would have issues.
I'm using a BMW M4 wheel on a DD2 base and have the same problem with the driver 454 (inci. firmware) like in driver 452 (incl. firmware) with the green rotary swtch (constant Mode). Position 1 to 4 is working normal (costant) but from position 5 to 12 I have just pulsing outputs with round 1 Hz. The driver 451 works normal without pulsing. All firmwares from my base and wheel are up to date (454).
Hello, I have had the problem that the UI doesn't open for a while, it started all of a sudden, not when I installed the driver but from one day to the next. I still had driver 451. But there were some Windows 11 updates. However, I couldn't solve the problem even by reinstalling the driver and the subsequent drivers 452, 453, 454. If I don't have my DD1 base connected to the PC, I can open the UI. So I first start the UI, then switch on my base and only then connect it to the PC and so the UI works and I can use it perfectly.
Applying that same logic, if it was purely an AMS2 data feed issue, it would happen in all software that utilises that data feed. :-)
The issue is obviously down to how the PBME is reacting to the AMS2 data feed - until you work with Reiza to track down what the trigger is for the issue it's a bit too soon †o categorically say there is no room for improvement on Fanatec's side.
These kind of absolute statements in situations where there are still unknowns have a habit of coming back to bite.
Adopting a mindset of all is good in our house, our software isn't the problem, is not great for a dev team. Until the unknowns become known you have no idea of what changes might be needed in the future. These are basic development principles - not rocket science.
The grainy issue in rF2 is an issue of the game. It's indeed known for years that the game spams the DPR channel the more often you you back to the garage. They did not fixed it yet, obviously.
You can workaround this by changing some settings in the ini files of the game and by setting DPR to OFF.
It's under investigation why it pops-up more often now but no, it most likely will not be fixed directly in the next driver as the next driver is going to be released quite soon already.
Comments
This driver not solved the grainy feeling on EA WRC. Does not matter i use the NFR, or not, or in game the Wheel / Tyre friction, the grainy issue still here on DD1. Very noticable on tarmac stages. Please fix this! Thank you!
Never heard of this.
What do you mean exactly with "grainy issue"?
As you say its only an issue in this one game, you are sure its not just the game which has not so good FFB (which I have heard from some)? Why do you think its a Firmware issue which Fanatec needs to fix instead of a game issue which Codemasters needs to fix?
This weird feel a lot of people they saying "grainy".
It's like sand is stuck in the base. It's interesting you never heard of this, when this problem has been present for 4-5 years.
Sometimes help, if i turn off the base, and turn on again. But i only feel this issue on this game, so probably the game need some fix.
Maybe EA fix this, idk, but annoying.
It's very likely a completely different issue when it's happening also with NFR OFF.
And when it only and exclusively happens in WRC then the Chance is extremely high that's it's an issue with the FFB of this one game.
If you have grainy FFB in all games also with NFR set to OFF then it would be a hardware issue where the base starts to feel grainy when it gets warm but apparently that's also not your issue as you say it's only happening in this one game so my best guess is that its a game related FFB issue (or creators intend that they actually want the FFB to feel like that).
I always use NFR and NIN on ACC like 10%, and everything it's fine, so the base i guess not have any problem. I just thought this weird feeling with the NFR was fixed in this game. Probably this is a road effect, but in WRC, no options to turn off, or something.
Thanks Maurice, have a nice weekend!
I received my new CS DD and wheel QR2s and everything set up fine except this firmware below.
The base and my two wheels are all updated and seems to be working well so far. I ran the new base and both my wheels in iRacing and everything seems normal. What should I do next to have all firmware updated, specifically this WQR version?
Thanks for any assistance you can give.
Ed
In order to get the WQR updated you need to remove the wheel from the base and its also best to disconnect all other USB devices you have.
Hi Maurice,
I did remove the wheel each time I tried that FW. I have not tried removing all the usb connections and will give that a try next should I remove everything except the DD wheelbase USB?
thanks for the quick response. BTW what happens if this won’t update trying this next step, can I continue using it?
You can continue using it but you should then contact the support as that would indicate that something with the QR might be wrong.
QR update is quite important as that is responsible for communication to the wheel so when you cant update the QR and you are stuck on the one which was pre-installed then you will encounter a lot of weird steering wheel issues, some wheels wont even work at all for example etc. So to get the QR to update is essential.
Maurice it worked! Thanks so much for the very quick response and the tip of the other USBs. I removed all but the mouse and keyboard (yes I know why not wireless!) and changed spots and retried and it worked the first time.
have a great weekend.
why would the UI come back as incompatible? I've tried installing the correct 64 bit driver multiple times now. no matter what I try the ui will not open for me. i had it on this system before then only thing that's changed would be the fact that I've done a clean windows install recently. every other program/app I had before has installed fine. some help would be much appreciated.
should we worry about this Maurice? or could it just be a side effect of the new QR firmware?
:) Thanks
Nothing to worry about.
It's an annoying pop-up but it doesn't harm the hardware.
Just click it away and restart the base when it happens.
Thank you.🙏
Sadly the PBME still has freezing issues with the latest firmware in AMS2
Then it's a game issue as all freezing related firmware issues are definitely fixed and there is no room for more improvements and it only happens in AMS2.
Will forward it to Reiza.
I fail to see how the PBME freezing in AMS2 is a Reiza issue and not a Fanatec issue. There is no issue with the AMS2 telemetry as other software, like Simhub which displays exactly the same telemetry feed as the PBME, works absolutely perfectly.
The fact that it is only the PBME that seems to have issues with the data feed points to it being Fanatec issue and not a game issue - otherwise all hardware displaying this data would have issues.
If it would be a BME issue then it would happen in more games but apparently it's only happening in AMS2.
The Reiza Devs already confirmed that it's only happening in their game and that they might need to apply some fix on their side.
From a firmware side every possible root cause for Freezes are fixed and there is just no more room for improvements here.
I'm using a BMW M4 wheel on a DD2 base and have the same problem with the driver 454 (inci. firmware) like in driver 452 (incl. firmware) with the green rotary swtch (constant Mode). Position 1 to 4 is working normal (costant) but from position 5 to 12 I have just pulsing outputs with round 1 Hz. The driver 451 works normal without pulsing. All firmwares from my base and wheel are up to date (454).
Hello, EA WRC's FFB is unfortunately bad. I was able to fix the grainy feeling on my DD1 by reducing FEI to 80.
Hello, I have had the problem that the UI doesn't open for a while, it started all of a sudden, not when I installed the driver but from one day to the next. I still had driver 451. But there were some Windows 11 updates. However, I couldn't solve the problem even by reinstalling the driver and the subsequent drivers 452, 453, 454. If I don't have my DD1 base connected to the PC, I can open the UI. So I first start the UI, then switch on my base and only then connect it to the PC and so the UI works and I can use it perfectly.
Can confirm this and have forwarded it to the FW dev.
Hopefully fixed with the next firmware in the next driver.
Is there a manual or a clear description somewhere to guide you on how best to update the drivers?
Now you will see many different ways of updating and problems.
Keep Base on...base off
Unistall, overwright...ect...
Applying that same logic, if it was purely an AMS2 data feed issue, it would happen in all software that utilises that data feed. :-)
The issue is obviously down to how the PBME is reacting to the AMS2 data feed - until you work with Reiza to track down what the trigger is for the issue it's a bit too soon †o categorically say there is no room for improvement on Fanatec's side.
These kind of absolute statements in situations where there are still unknowns have a habit of coming back to bite.
Adopting a mindset of all is good in our house, our software isn't the problem, is not great for a dev team. Until the unknowns become known you have no idea of what changes might be needed in the future. These are basic development principles - not rocket science.
i been doing like this.
Download the driver
turn off the base
uninstall driver if needed
install driver
restart the pc ( if not todo that then i seen weird stuff like firmware failure install )
turn on the base
open the fanatec control panel
start the Firmware update protsess
I got this error message after i updated my DD1 with the 454 driver. Will it probably be fixed in the next drivers?
I thought my base was dying.😅
Thank you, i will try it! 😉
Never heard of this ... really? this grainy feeling also happens since years in Rfactor2 ... a little research and you will find it.
Easy reproduce by driving and go back to pits. I cant really drive a complete session without this issue.
Many Fanatec users have this problem. But the buck was apparently passed back and forth for years
The grainy issue in rF2 is an issue of the game. It's indeed known for years that the game spams the DPR channel the more often you you back to the garage. They did not fixed it yet, obviously.
You can workaround this by changing some settings in the ini files of the game and by setting DPR to OFF.
It's under investigation why it pops-up more often now but no, it most likely will not be fixed directly in the next driver as the next driver is going to be released quite soon already.