We are currently working on a new package to reduce the possibility of the user being able to do something wrong as well as providing better options and instructions to trouble shoot or revers firmware to an older driver because this is were part of the issues happened for some here.
The driver download also includes PDF instructions explaining the process and also offering some trouble shooting steps in case something is not working right.
Download driver
unpack the installer
Have the base turned on and plugged into the PC (this help so that the correct USB drivers get already installed with the update and don't need to get installed later by the driver if the base is detected then).
Make sure everything is connected well, best directly to the PC with the original cable rather than longer cables or extensions.
Choose the correct installer based on your operating system (explained in detail in the instructions PDF). Most have 64bit by now but some older systems might have 32bit.
Install the new driver and follow the instructions
Do a windows restart after the update was completed, usually the driver suggests it anyway at the end and offers a button for it
Start the Fanatec Control Panel
It will show you the firmware update page
Click on Open Firmware Manager
Click on the green update button on the right side
The firmware update process is automated, it will guide you through with instructions on what to do next, things will automatically done in the correct order.
First it will automatically flash the motor firmware, then the fan of the base will run at 100% which is normal, it will go back to default speed after the base firmware update which is done right after.
After the base firmware update is completed it will offer you to do a center calibration (and shifter calibration of available).
After that you will be able to update your wheels or you can end the update process right away if there are no wheels you need to update.
The process is also shown in this video (timestamp):
thanks for the report, we'll investigate the issue, just to be sure: which base do you have?
to downgrade:
delete current driver 442
restart PC
install driver you want
restart PC
open Fanatec Control Panel
go to update page
start firmware manager
Important: Do the motor firmware first (second in the list), only after that do the base firmware (if you have a Podium DD, if its a CSL, then you can do it in any order)
We will take a look at the issue and try to reproduce it.
In case you want to go back to a previous driver, make sure to first flash the motor firmware which is second in the list, only after that flash the base firmware.
In case anyone is having issues with a not detected/working Podium DD base (fan running at 100%), I've created a PDF with some more detailed instructions on how most should be able to recover their base to a working state.
I,ve almost the exact experience with my gt dd pro so maybe my answer would be helpful as well.
I play GT7 and ACC on PS5 so I use the recommended settings for those two games. The scratchyness and vibrations are not related to a specific game. You can feel it everywhere. It mixes into the FFb effects and is still present when you close the game or disconnect usb.
I am already in touch with your tech support and they also suggested to try the test motor firmware 1.0.2.3 wich I did.
Its calming the vibrations but they are still present.
This is actually independent of being connected with usb or not. However I must say that after some more testing the new new wheelbase is vastly improved and only after it starts getting warm do I notice this scratchy feeling sometimes it’s very slight and so far only tested on ACC with the recommended settings for PS5. I haven’t been playing much in general though the last few weeks.
I don’t think that with the new wheelbase I would be able to duplicate the scratchy feeling if the base is not connected whereas the previous two bases would get scratchy even when not connected to any device by USB. Playing around with settings didn’t help at all. The only thing that made a difference is Motor Firmware 1.0.2.3 which was sent to me by support.
Can you explain the kind of situation in which the jolts happened?
Did you notice a weird jump of the steering input/animation in-game? Next time it happens you could have a look in the replay, slow motion might be needed, to see if you see the in-game wheel going shorty into a wrong direction to then come back to the correct position. This still seems to happen for some and we want to further investigate it, would be interesting if the remaining jolts are caused by this or something else.
Are you using an analysis or ITM screen on the Podium DD or are you on the default screen with the Fanatec logo?
Theoretically it could also be a jolt created by the game/road mesh, you could try to driver over the same spot some additional times to see if it happens again.
If not, please provide the log files as explained in my comment above.
There were slight "ghost" inputs reported with this firmware, we are currently working on to fix them for the next driver upload. Right now it can happen that you see a slight input on clutch and throttle when pressing the brake for example. This can be worked around with manual pedal calibration.
Did updates work fine in the past with other drivers and now they suddenly don't work anymore with this driver? If yes, which was the last driver updates worked fine with?
Would be helpful if you can provide log files from the Settings page of the Fanatec Control Panel
Please follow the instructions of this PDF, let me know if it helped. If it didn't and the base seems permanently bricked, you will need to contact support but until then I'll try to help.
This one is for all kinds of wheels, let me know if it helps with the McLaren because the issue might be different and I don't know how effective the tool for the wheels is yet.
No, I'm not doing anything special with the G25 apart from enumerating the device and later polling it for input (I don't track connection events at all). Everything is pure DirectInput 8, no special handling of any device, and only set the FFB effect for the device that provides the steering input (Fanatec CSL DD). Maybe the fact that I also "open" the logitech device makes it somehow insert some FFB "middelware" even though I'm not sending FFB to the logitech device..?
I looked at the contact page you are referring to, but I'm just a hobbyist, so the requirement of providing a company name and e-mail etc. was enough to deter me from using it :D. But if you say that I should still use it even if I can only provide n/a to most fields then I will do so :)
Comments
Here is the Formula V2 firmware file included in 442
You can manually select it after starting a firmware update with the driver of your choice. Would be interesting if it then works.
Which steering wheel firmware do you have currently on the wheel?
Can't tell a time frame yet but it's one of the next things we are working on and high on the priority list
What are your tuning menu settings?
Does it happen already when the base is just sitting there in idle without a game running?
Or does it only happen during game-play and if yes, which game?
could be, I can't tell from here, best is to contact support by opening a ticket on the my products page in the shop
Hi Marcel I did this last Monday but your support is maybe very busy immo
Hi Marcos,
We are currently working on a new package to reduce the possibility of the user being able to do something wrong as well as providing better options and instructions to trouble shoot or revers firmware to an older driver because this is were part of the issues happened for some here.
The driver download also includes PDF instructions explaining the process and also offering some trouble shooting steps in case something is not working right.
The process is also shown in this video (timestamp):
If you encounter any issues or have questions, have a look in the instructions PDF or ask for help here
Below is a recovery tool for the Button Module, starting it will force a firmware update to hopefully bring it back to a functioning state.
thanks for the report, we'll investigate the issue, just to be sure: which base do you have?
to downgrade:
You can have the wheel on during the update. The process is done automatically and step by step with instructions.
Same here, running the recommended settings and in some rare corners I get the jolts, they are not so strong then before but they are there.
We will take a look at the issue and try to reproduce it.
In case you want to go back to a previous driver, make sure to first flash the motor firmware which is second in the list, only after that flash the base firmware.
Is your game handling the G25 in a special way which gets triggered by it being connected?
By the way there is a contact form for game developers on the Fanatec website: Software Developer | Fanatec
sorry, will add it now
Please post FanaLab related issues in the correct forum section.
In case anyone is having issues with a not detected/working Podium DD base (fan running at 100%), I've created a PDF with some more detailed instructions on how most should be able to recover their base to a working state.
Will also add this to the first post.
Any chance of offering such a bootloader for the MacLaren Wheels? 🙁
Wheel Base Model (product ID): CSW V2.5
Steering Wheel Model (product ID): CSW Formula V2
Driver Version: 442
Base FW Version: 691
Motor FW Version: 22
Wheel FW Version: 45
FanaLab Version: 1.64.5
Driver/FanaLab installed on C: drive
Hi, I noticed this probable anomaly, with the new Drivers or firmware,
after turning off the PC, the fans of the CSW 2.5 base continue to work even after waiting more than 1h and 40.
Previously they stopped after a while and then I turned off the base.
Now I turn off the base even if the fans are running.
It happens to you too?
It is safe and absolutely fine to power-off the Base when the Fan is running. There is no need to wait until the Fan stops..
Hi Marcel,
May i refer you to this thread?
https://forum.fanatec.com/discussion/23688/csl-dd-feels-scratchy/p1
I,ve almost the exact experience with my gt dd pro so maybe my answer would be helpful as well.
I play GT7 and ACC on PS5 so I use the recommended settings for those two games. The scratchyness and vibrations are not related to a specific game. You can feel it everywhere. It mixes into the FFb effects and is still present when you close the game or disconnect usb.
I am already in touch with your tech support and they also suggested to try the test motor firmware 1.0.2.3 wich I did.
Its calming the vibrations but they are still present.
This is actually independent of being connected with usb or not. However I must say that after some more testing the new new wheelbase is vastly improved and only after it starts getting warm do I notice this scratchy feeling sometimes it’s very slight and so far only tested on ACC with the recommended settings for PS5. I haven’t been playing much in general though the last few weeks.
I don’t think that with the new wheelbase I would be able to duplicate the scratchy feeling if the base is not connected whereas the previous two bases would get scratchy even when not connected to any device by USB. Playing around with settings didn’t help at all. The only thing that made a difference is Motor Firmware 1.0.2.3 which was sent to me by support.
Just realized Serkans post. Yes the thread is useful for debugging this issue I think.
Can you explain the kind of situation in which the jolts happened?
Did you notice a weird jump of the steering input/animation in-game? Next time it happens you could have a look in the replay, slow motion might be needed, to see if you see the in-game wheel going shorty into a wrong direction to then come back to the correct position. This still seems to happen for some and we want to further investigate it, would be interesting if the remaining jolts are caused by this or something else.
Are you using an analysis or ITM screen on the Podium DD or are you on the default screen with the Fanatec logo?
Theoretically it could also be a jolt created by the game/road mesh, you could try to driver over the same spot some additional times to see if it happens again.
Do you get an error message?
Please provide the driver log files, you can export them on the Settings page of the Fanatec Control Panel
Here is the firmware file of the ClubSport V3 pedals, let me know if it worked with manually selecting it.
If not, please provide the log files as explained in my comment above.
There were slight "ghost" inputs reported with this firmware, we are currently working on to fix them for the next driver upload. Right now it can happen that you see a slight input on clutch and throttle when pressing the brake for example. This can be worked around with manual pedal calibration.
Here are two tools, one for recovering the BME and the other one for wheels.
Did updates work fine in the past with other drivers and now they suddenly don't work anymore with this driver? If yes, which was the last driver updates worked fine with?
Would be helpful if you can provide log files from the Settings page of the Fanatec Control Panel
Yes, in case you haven't seen the other post with them yet, here is the PDF:
Give this recovery tool for the BME a try and let me know if it helped.
Please follow the instructions of this PDF, let me know if it helped. If it didn't and the base seems permanently bricked, you will need to contact support but until then I'll try to help.
This one is for all kinds of wheels, let me know if it helps with the McLaren because the issue might be different and I don't know how effective the tool for the wheels is yet.
Hi, thanks for the response :)
No, I'm not doing anything special with the G25 apart from enumerating the device and later polling it for input (I don't track connection events at all). Everything is pure DirectInput 8, no special handling of any device, and only set the FFB effect for the device that provides the steering input (Fanatec CSL DD). Maybe the fact that I also "open" the logitech device makes it somehow insert some FFB "middelware" even though I'm not sending FFB to the logitech device..?
I looked at the contact page you are referring to, but I'm just a hobbyist, so the requirement of providing a company name and e-mail etc. was enough to deter me from using it :D. But if you say that I should still use it even if I can only provide n/a to most fields then I will do so :)