Hello. Silly question perhaps... but by updating to the v454 driver should I update the base again? In the control panel everything appears green as if everything is updated. Thank you
Am i the only one who has problems with driver 453 and WRC, when you play suddenly it looses all FBB and the game chrashes, and before you say update to driver 454 have you seen how many have problems with that driver, it can´t just be bad luck
One question can i go back to driver 452, will it work with the updated firmware and will i have to go back to the previous fanalab
I am unable to install these drivers. Coming from 451, and I did upgrade to Win11 yesterday. Was able to uninstall 451 and thought I was starting clean, however, the install gets seemingly halfway, then hangs here. Sound on my PC starts cutting out, the lights on fans and what not start getting choppy which is what I used to see in Win10 before a bluescreen.
I can't cancel, either. I click cancel and it acts like nothing happened. Task Manager is showing no activity.
Well, the answer to the issue, even though you dont want to get this as an answer, is to update to driver 454.
Also there are not that many people who have issues with 454. It's a LOT less than how many had issues with 453 and 454 is much better than 452 which is even worse.
So in case you want the issue fixed then you should update to 454.
Based from the trace, it says the Wheel Base is still in use, meaning some application is still using the Base, e.g. games or any softwares with DirectInput feature, therefore the installer cannot completely finish the installation.
For these issues, the workaround is to:
Unplugged Wheel Base USB from PC or simply power OFF the Wheel Base.
Uninstall the current driver.
Restart PC.
Install Driver.
Connect Wheel Base or Power ON Wheel Base.
Can you please try if the driver now finishes the installation with this workaround?
This issue looks like a side effect of a fix we needed to implement to prevent an issue where the Uninstallation is blocked by COM Surrogate pop-up, that issue is harmless though simply annoying.
We will discuss if we revert that specific fix as the uninstallation continues when you would click "OK", the installation however seems to stop which is of course worse... However by far not everyone, but only a very few people, seem to be affected by the installation issue, therefore further investigations are ongoing what exactly causes the issue for those few affected people.
To draw attention to mistakes so that you can fix them, nothing comes from you fanboys, you talk to you everything is nice and let yourself be sold for stupid ...
Thank you. I didn't follow your instructions exactly because if the wheelbase is in use, it means i can just turn it off and install the driver, and restart.
Had to restart again upon opening Fanatec Control Panel because the DD1 isn't detected and it had to do something.
My suggestion to your software team: if you are resource constrained (sounds like you are, because QA would've caught this otherwise), just tell the users to turn off the wheelbase when installing the driver in the instructions using big bold text or something. This is far easier than fixing a bug caused by a fix of another bug.
I'd highly recommend management at Fanatec consider allocating resources from marketing to engineering AND software team (including QA.) This stuff seriously makes the company look bad/incompetent (not the developer, Maurice, or any individual, the company as a a whole/brand.)
The above is not at knock on you at all Maurice, really appreciate your patience and replies. Thank you again.
I made the mistake of updating my V3 pedals firmware, due to choppy input. That issue was fixed, but now I'm screwed lol.
in one of the older drivers, I was able to adjust the "Max" on the brake pedal, and apparently someone thought it was a brilliant idea to remove that option in the newer drivers. So now, even on min brake force setting on the wheel, I can't reach max brake point without pain (car accident injury).
So am I supposed to go through and change the in game settings of every game I own now to try and find that sweet spot? Who's bright idea was it to remove that option? WHY would you remove it? its just silly. As is, I'll never be able to get my pedals back to where I want them, because of this. An already annoying situation (car accident) now made worse by stupid decisions like this.
And if I come off as angry, its because I am. I cannot stand when companies remove existing options for literally no reason.
The max Brake adjustment should never be there in the first place. It was an issue that it was available in the past, therefore it was removed quite a long time ago, I think last year with driver 447.
You can control the Brake Force through the BRF setting in the Tuning Menu when you attach the pedals to the base. So if you cant reach full Brake input then you should lower the BRF value.
Well as I already said, that wasn't enough. My knee is too messed up now to even get full brake on the most sensitive setting without pain every time. Fortunately after I had time to cool down a bit, I remembered I still had my old driver install file on my PC, so I removed the newest driver and went back to the old one long enough to change the max pressure. And fortunately those settings stick across driver updates.
Its an option that needs to be either be re added, or the brake force option needs to be adjusted further. I never liked the original full force needed, but now I just can't use it due to injury.
I’ve seen this pop up probably 3 times randomly since the WQR update. Just when the DD1 is initially switched on. Not sure if my DD1 is starting to fail or if this is from an update issue…
i got the window event logs uploaded did you get a chance to look at this? ive tried evry troubleshoot you guys reccomend already. still cant get the control panel to open. appreciate the help
Hello, this is the first time that I am posting something on here so please have mercy if I am doing... anything wrong. Maybe it's the wrong thread Idk. But, is there any way for me to get rid of that BRF setting and just set the max brake pressure manually again? I feel like it's completely undriveable like that.
Comments
I have no access to the CRM but thanks for the report, that's something I can work with.
Forwarded it to our Dev who will now investigate.
Hello. Silly question perhaps... but by updating to the v454 driver should I update the base again? In the control panel everything appears green as if everything is updated. Thank you
driver and firmware are two different thing, if you already todo that firmware update with 453 before, you to not need todo again with 454
That's what I wanted to know. Thank you very much for your prompt response!! ;)
Am i the only one who has problems with driver 453 and WRC, when you play suddenly it looses all FBB and the game chrashes, and before you say update to driver 454 have you seen how many have problems with that driver, it can´t just be bad luck
One question can i go back to driver 452, will it work with the updated firmware and will i have to go back to the previous fanalab
Regards JMP
I am unable to install these drivers. Coming from 451, and I did upgrade to Win11 yesterday. Was able to uninstall 451 and thought I was starting clean, however, the install gets seemingly halfway, then hangs here. Sound on my PC starts cutting out, the lights on fans and what not start getting choppy which is what I used to see in Win10 before a bluescreen.
I can't cancel, either. I click cancel and it acts like nothing happened. Task Manager is showing no activity.
i just made sure im all updated in windows.
how do i upload the window log files?
The Windows Log files are evtx files which need to be zipped into an archive to then be able to upload them here.
Well, the answer to the issue, even though you dont want to get this as an answer, is to update to driver 454.
Also there are not that many people who have issues with 454. It's a LOT less than how many had issues with 453 and 454 is much better than 452 which is even worse.
So in case you want the issue fixed then you should update to 454.
Why you on here if you don't like Fanatec lmaoooooo
The dev had a look at your issue now.
Based from the trace, it says the Wheel Base is still in use, meaning some application is still using the Base, e.g. games or any softwares with DirectInput feature, therefore the installer cannot completely finish the installation.
For these issues, the workaround is to:
Can you please try if the driver now finishes the installation with this workaround?
This issue looks like a side effect of a fix we needed to implement to prevent an issue where the Uninstallation is blocked by COM Surrogate pop-up, that issue is harmless though simply annoying.
We will discuss if we revert that specific fix as the uninstallation continues when you would click "OK", the installation however seems to stop which is of course worse... However by far not everyone, but only a very few people, seem to be affected by the installation issue, therefore further investigations are ongoing what exactly causes the issue for those few affected people.
To draw attention to mistakes so that you can fix them, nothing comes from you fanboys, you talk to you everything is nice and let yourself be sold for stupid ...
So you meen i can´t go back to a driver that acually works ( 452 or 451 )
452 does not work, it's one of, if not THE, worst driver we have ever released.
You can of course downgrade back to driver 451 as that is a super stable driver. Note that you would need to downgrade FanaLab as well.
But it would be best to upgrade to 454.
you should not use 453, that was a bugy as hell, there is also 454 released
Thank you. I didn't follow your instructions exactly because if the wheelbase is in use, it means i can just turn it off and install the driver, and restart.
Had to restart again upon opening Fanatec Control Panel because the DD1 isn't detected and it had to do something.
My suggestion to your software team: if you are resource constrained (sounds like you are, because QA would've caught this otherwise), just tell the users to turn off the wheelbase when installing the driver in the instructions using big bold text or something. This is far easier than fixing a bug caused by a fix of another bug.
I'd highly recommend management at Fanatec consider allocating resources from marketing to engineering AND software team (including QA.) This stuff seriously makes the company look bad/incompetent (not the developer, Maurice, or any individual, the company as a a whole/brand.)
The above is not at knock on you at all Maurice, really appreciate your patience and replies. Thank you again.
Hi to all, i started with my new PC and had to install the software new. Downloaded
PC driver 454 and did all updates. now the fanalab displays a max toruqe of 6Nm.
Im using a CSL DD (8Nm) / CSL Pedale LC / Wheel Clubsport Formula V2.5 X
sadly i cant say what PC driver was running on the old PC.
I detectd the issues by seting up my games and the force feedback was not same as usualy.
Is there a hardware or software issues ongoing?
thx for any suggestions or solutions
You're in Linear mode, which limits maximum torque output to 6Nm. Switch to Peak and you should see it then read 8Nm.
I made the mistake of updating my V3 pedals firmware, due to choppy input. That issue was fixed, but now I'm screwed lol.
in one of the older drivers, I was able to adjust the "Max" on the brake pedal, and apparently someone thought it was a brilliant idea to remove that option in the newer drivers. So now, even on min brake force setting on the wheel, I can't reach max brake point without pain (car accident injury).
So am I supposed to go through and change the in game settings of every game I own now to try and find that sweet spot? Who's bright idea was it to remove that option? WHY would you remove it? its just silly. As is, I'll never be able to get my pedals back to where I want them, because of this. An already annoying situation (car accident) now made worse by stupid decisions like this.
And if I come off as angry, its because I am. I cannot stand when companies remove existing options for literally no reason.
The max Brake adjustment should never be there in the first place. It was an issue that it was available in the past, therefore it was removed quite a long time ago, I think last year with driver 447.
You can control the Brake Force through the BRF setting in the Tuning Menu when you attach the pedals to the base. So if you cant reach full Brake input then you should lower the BRF value.
Well as I already said, that wasn't enough. My knee is too messed up now to even get full brake on the most sensitive setting without pain every time. Fortunately after I had time to cool down a bit, I remembered I still had my old driver install file on my PC, so I removed the newest driver and went back to the old one long enough to change the max pressure. And fortunately those settings stick across driver updates.
Its an option that needs to be either be re added, or the brake force option needs to be adjusted further. I never liked the original full force needed, but now I just can't use it due to injury.
I’ve seen this pop up probably 3 times randomly since the WQR update. Just when the DD1 is initially switched on. Not sure if my DD1 is starting to fail or if this is from an update issue…
Ditto, anybody know how to fix this?
i got the window event logs uploaded did you get a chance to look at this? ive tried evry troubleshoot you guys reccomend already. still cant get the control panel to open. appreciate the help
Hello, this is the first time that I am posting something on here so please have mercy if I am doing... anything wrong. Maybe it's the wrong thread Idk. But, is there any way for me to get rid of that BRF setting and just set the max brake pressure manually again? I feel like it's completely undriveable like that.
Is there anyone else who has problems with Asetto Corsa crasching after update to driver 454
Regards JMP
After update to 454 I have problems to calibrate the H-pattern shifter. 1 = reverse, 5 = 7
Any solution?
Great... worked... THX for your eagle eyes...😉