This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
I had to uninstall iRacing and reinstall it on the day of the update. (Don't get me started on that debacle....its 2023 and we are we are still going deep in to the C drive files to individually delate ALL files associated with iRacing??) Sorry, i digress, anyway, after I did that, I updated everything and go back to racing. I was racing the Cup series so I was in sequential mode for the shifter. Then I decide to test the H-Shifter. I calibrated inside of iRacing, no go, then I went to Fanatec control software and calibrated it and still....no go. Did this several times. I tried going back to the previous drivers....no go.
Is there a reset option on the shifter? Is this a new driver bug? I'm currently rebuilding my rig because I got a new frame but I will be done tonight so I'd like to have a fix for this sooner than later.
What do you mean with deleting something iRacing related in the C drive? This is not necessary at all, at least not Fanatec related even if it would be necessary - but it isnt.
What do you mean with "no go" for the Shifter? What is not working? Which Shifter port on the back of the Base is the Shifter plugged into?
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
the 442 drivers have seen the complete rewriting of the DD firmware considerably improve the FFB rendering of our wheelbases.That said, I still get random peaks and coggling, even if it's less prevalent than before (DD2, even in 451).
Are there any more big surprises in the pipeline to further improve the rendering of our podium wheelbases? Can they still be improved from a software point of view? Or do you think you've reached the level that the hardware allows?
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
the 442 drivers have seen the complete rewriting of the DD firmware considerably improve the FFB rendering of our wheelbases.That said, I still get random peaks and coggling, even if it's less prevalent than before (DD2, even in 451).
Are there any more big surprises in the pipeline to further improve the rendering of our podium wheelbases? Can they still be improved from a software point of view? Or do you think you've reached the level that the hardware allows?
Thank you for your reply 😉
Those are most likely the steering input jumps which was improved but not fully fixed yet, which mostly appear to happen in iRacing.
Its planned to fully fix this issue sometime in the future, yes.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Hi wen I’m in the fanatec tuning menu it says 15nm and not 20nm anymore and I can’t not change that can you look into this .thk
You can hover over the value with your mouse to get an explanation which settings have an influence on the Nm value.
The Nm depends on the used FFB, FOR and FFS setting. Most likely you use the base in FFS LINEAR Mode instead of PEAK Mode. In LINEAR Mode the max torque of the DD1 is 15 Nm with FFB and FOR set to 100 - so the value is correct.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
You can hover over the value with your mouse to get an explanation which settings have an influence on the Nm value.
The Nm depends on the used FFB, FOR and FFS setting. Most likely you use the base in FFS LINEAR Mode instead of PEAK Mode. In LINEAR Mode the max torque of the DD1 is 15 Nm with FFB and FOR set to 100 - so the value is correct.
Thanks for the info Maurice I go look in to that .
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is not related to driver 451, but threads for older drivers are already closed.
With driver 444 the old legacy control panel was removed and nobody probably misses it.
However, if enabled it had a really useful feature showing the corresponding button numbers and the values of the levers for a mounted wheel.
And to answer any response regarding button numbers in the manual: No they don't match and manual doesn't even list all buttons. Numbers shown in old control panel are the ones that get passed over to a game.
Could we at least get the button numbers back in one of the following driver versions?
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is not related to driver 451, but threads for older drivers are already closed.
With driver 444 the old legacy control panel was removed and nobody probably misses it.
However, if enabled it had a really useful feature showing the corresponding button numbers and the values of the levers for a mounted wheel.
And to answer any response regarding button numbers in the manual: No they don't match and manual doesn't even list all buttons. Numbers shown in old control panel are the ones that get passed over to a game.
Could we at least get the button numbers back in one of the following driver versions?
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Same wrong numbers that are in the manual, and only buttons 1 to 32. Nice try though.
The buttons you see in the Gamecontroller Menu are the button numbers which gets send to the game.
Xbox button is supposed to be button 25 and not 24 on a McLaren wheel so the old driver is wrong. Maybe was mapped to 24 in an old Firmware and was changed to 25 in the meantime, but 25 is definitely correct. So even if this would be implemented into the UI it would also show 25.
For the "regular" buttons 32 buttons from Gamecontroller menu is also enough, above 32 are only "special" buttons like the 12-positions of each MPS etc.
Can suggest to re-implement a button number indicator somehwere in the UI, however I dont know how to implement so that it looks "good", so might have very low prio and something not coming in one of the next drivers but maybe in the (far) future at some point.
it would be nice in general if such values are displayed, it could also help with the calibration of the pedals, if you get raw values displayed. Something doesn't have to be "pretty", as it can be seen on the screenshot, that is completely fine.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
If you report a driver or firmware issue, please make cross checks:
Update driver and FW separately to isolate an issue and find out if caused by driver OR firmware.
Which driver OR firmware shows the issue
Which driver OR firmware does not show the issue
Check if you can reproduce the issue again if you go back to the version which seems to have caused the issue
Check if the issue is related to specific settings of for example the tuning menu. Is it happening more or less with a specific setting raised or lowered?
Post the answers gathered from the questions above + a short description of the issue including the following info:
Wheel Base Model (product ID): ...
Steering Wheel Model (product ID): ....
Driver Version: ....
Base FW Version: ....
Motor FW Version: ....
Wheel FW Version: ....
FanaLab Version: ....
Tuning Menu settings
Driver/FanaLab installed on C: drive or else?
With driver related issues collect log files and zip them from C:\Users\Public\Fanatec Logs
Changelog of driver 451 (since 450)
Firmware versions included
Podium DD1 / DD2 Base: 3.0.1.4
Podium DD1 / DD2 Motor: 3.0.0.2
CSL DD / GT DD PRO Base: 1.1.8.5
CSL DD / GT DD PRO Motor: 1.0.3.2
CSW V1 Base: 692
CSW V2 Base: 692
CSW V2.5 Base: 692
CSL E Base: 692
CSL E Base PS4: 692
CSL / CSW Motor: 22
Podium BMW M4 GT3: 8
Podium HUB: 6
Podium BME: 22
CS SW Formula V2(X), V2.5(X): 46
CS SW RS: 4
CS SW BMW V2: 3
CS UH V2 / UHX V2: 2
CS SW F1 Esports V2: 5
GT DD PRO SW: 8
CSL SW McLaren GT3 V2: 46
CSL SW McLaren GT3: 36
CSL SW WRC: 4
CSL UH: 8
CS P V3: 1.35
CSL EP V2: 1.6
CSL EP LCK: 1.13
CSL P LCK: 1.8
USB Adapter Handbrake mode: 1.10 (NEW)
Control Panel
Fixed UI freeze/crash with pedals connected and when going to the pedals page.
Fixed issue of incorrect steering angle shown (-1080°) when opening the driver with wheel turned completely to the left.
UI now shows current maximum torque in Nm depending on the FFB strength settings set in the Tuning Menu. On the Podium DD it's also dependent on the connected wheel and the torque key, therefore the torque value is only shown with a steering wheel connected.
Wheel Base page is now always shown for easier access to trouble shooting tips if needed which was more difficult to find when other devices were still connected.
Included additional hint info for Standard/Advanced Tuning Menu toggle to explain that Setup 1 will be reset when going back to Standard mode.
Increased the timer to show hint texts until mouse is moved away.
Other minor improvements.
USB Adapter Handbrake Mode
Added manual min/max calibration for the handbrake connected to the USB Adapter. Firmware update of USB Adapter required.
Tray App (optional installation)
Latest version of FanatecApp on Android/iOS required as well, more info about the app on: https://fanatec.com/eu-en/app
Fixed Tray App icon not shown in the Tray since Windows 11 "Moment 2" update.
Fixed several issues with the SEN slider, including a crash which could happen while switching between Standard and Advanced Tuning Menu mode.
Fixed default values resetting to wrong values while switching between Standard and Advanced Tuning Menu mode.
Fixed an issue where only Green FlagLEDs were working in the Dashboard, now all FlagLED colors are working.
Fixed non-working ACP radio buttons. Now the radio button is reflecting the actual status of the chosen ACP setting and it's now also possible to change the ACP setting in the App which previously had no effect at all.
Now possible to switch between Standard and Advanced Tuning Menu through Mobile App.
Now possible to reset Tuning Menu settings through Mobile App.
Known Issues
If you had issues with the Control Panel UI crashing: Re-download the driver below (it got updated) -> uninstall the current version -> Install the new driver 451.
When entering a game menu while driving it can happen in some games that the FFB effect doesn't get canceled which results in the wheel turning to one side. (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)
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)
The steering input jump issue was greatly improved so the issue happens a lot less than before. Full fix expected for one of the next versions.
I have a CSL Elite PS4 WB, is this driver compatible ? Because I thought firmware updates for this base had discontinued as with the availability of this product ! I don't have any issues with my wheel even though it's nearly 5 years old so are there any benefits to this update ? Not sure which firmware I have only that 684 22 displays on the wheel, last update May 2021 and I do recall ABS was changed to BLI last time, many thanks.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
I have a CSL Elite PS4 WB, is this driver compatible ? Because I thought firmware updates for this base had discontinued as with the availability of this product ! I don't have any issues with my wheel even though it's nearly 5 years old so are there any benefits to this update ? Not sure which firmware I have only that 684 22 displays on the wheel, last update May 2021 and I do recall ABS was changed to BLI last time, many thanks.
The CSL Elite PS4 Base is still fully supported and not EOL yet.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
bei mir wird nach dem Treiber update am Podium Button Modul Endurance die Bremsbalance, die in ACC eingestellt ist, nicht richtig angezeigt.
Der Wert ist am Modul grundsätzlich falsch
Das kann nichts mit einem Treiber Update zu tun haben. Die Werte kommen über FanaLab und nicht dem Treiber.
Welche FanaLab Version ist im Einsatz? Es sollte nur 1.99.05 mit Treiber 451 genutzt werden, keine 1.69.x Version. Die 1.69.x Versionen sind uralt und haben bspw die 2023er ACC Autos noch gar nicht drin, entsprechend wird mit dieser alten Lab Version natürlich immer ein falscher BB Wert angezeigt.
Notfalls die mal deinstallieren, den xml Ordner bei AppData/Local/Fanatec/FanaLab löschen und das Lab neu installieren, damit sich die Liste mit den BB offsets neu generiert.
PS: next time please post in English according to the forum rules.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Turn on the base (in PC mode) and wait for the PC to recognize it?
download the latest drivers from the site and install them with the base turned on?
restart when the program says so with full access and wait for it to return to the desktop?
all correct?
I can't find an official guide on the matter, each player has his own opinion and you can never figure out which one is correct. I hope someone can help me and also future players who read this post.
I haven't seen it mentioned (forgive me if it was), that the brake force factor loading is very unreliable in the CSL DD firmware. I use the Clubsport V2 pedals and different brake force factors for different profiles on the CSL DD. When starting up, I have to check if these brake force factors are the correct value, because ~1 out of 3 times one of the brake factors gets copied to all or multiple profiles. I didn't notice any definite pattern as to which value is repeated, but it's definitely not as simple as "the factor of the first profile is used for every other profile". As far as I can tell, all other profile values are handled correctly, but the brake force factor is rather erratic.
I haven't checked whether the wrong profile values are persisted or upon next restart it loads the correct (previously) saved value.
I'm encountering the issue of the Firmware updater continuously populate itself and my wheel Clubsport Formula V2.5x restarts itself after the firmware update and the Firmware updater windows keeps popping up and keeps making to update. Is my wheel bricked or something else is wrong with it?
Comments
What do you mean with deleting something iRacing related in the C drive? This is not necessary at all, at least not Fanatec related even if it would be necessary - but it isnt.
What do you mean with "no go" for the Shifter? What is not working? Which Shifter port on the back of the Base is the Shifter plugged into?
Yo everyone!
I also have weak ffb on my CSLDD and this is only 1 month old!
I contacted with support, i got RMA, sending back the base, and today i got my base, with the same weak ffb.
Only changed the shaft clamp that's it! Why wasn't it replaced my base???
I need to set my ffb to 100% in Fanatec driver, and 100% ffb ingame, and can turn the car with one hand, with 8nm!!!
In good condition with this settings, would be break my thin arm...
When i got this CSLDD, then the ffb enough with 60-65%, then 2-3 week later, became weaker, and now, the 100% ffb not enough.
What i did already:
- Uninstalled the whole Fanatec driver
- Uninstalled Fanatec devices in Device Manager
- Resetting my Fanatec device
- Tried few older fanatec driver
Nothing change, still the same weak ffb, and Fanatec not replaced my base, THANK YOU!!!!
You obviously need to contact the support again and ask for an exchange of the whole base.
Nobody here can help you as it's no driver or firmware related issue.
I asked it already, but they didn't replace it...😤
I am contacting consumer protection, cuz it's a joke what Fanatec did with me...
Maybe you have already done it, but I'd test the base on another pc or laptop, just in case.
Same result. The base sadly wrong. I don't know why Fanatec not want to replace.
Hello @Marcel Pfister,
the 442 drivers have seen the complete rewriting of the DD firmware considerably improve the FFB rendering of our wheelbases.That said, I still get random peaks and coggling, even if it's less prevalent than before (DD2, even in 451).
Are there any more big surprises in the pipeline to further improve the rendering of our podium wheelbases? Can they still be improved from a software point of view? Or do you think you've reached the level that the hardware allows?
Thank you for your reply 😉
Those are most likely the steering input jumps which was improved but not fully fixed yet, which mostly appear to happen in iRacing.
Its planned to fully fix this issue sometime in the future, yes.
Hi wen I’m in the fanatec tuning menu it says 15nm and not 20nm anymore and I can’t not change that can you look into this .thk
You can hover over the value with your mouse to get an explanation which settings have an influence on the Nm value.
The Nm depends on the used FFB, FOR and FFS setting. Most likely you use the base in FFS LINEAR Mode instead of PEAK Mode. In LINEAR Mode the max torque of the DD1 is 15 Nm with FFB and FOR set to 100 - so the value is correct.
Thanks for the info Maurice I go look in to that .
Guys just a little help...
I have a F1 podium DD for PS5... Does the F1 wheel works on other bases of Fanatec?? Or only on the podium base???
Every wheel works on any Fanatec Base.
Feature request:
This is not related to driver 451, but threads for older drivers are already closed.
With driver 444 the old legacy control panel was removed and nobody probably misses it.
However, if enabled it had a really useful feature showing the corresponding button numbers and the values of the levers for a mounted wheel.
And to answer any response regarding button numbers in the manual: No they don't match and manual doesn't even list all buttons. Numbers shown in old control panel are the ones that get passed over to a game.
Could we at least get the button numbers back in one of the following driver versions?
Thanks
Matthias
You can still see the button numbers when you open the entry of your base in the Windows Gamecontroller Menu.
Maurice,
I knew you would come up with something but didn't expect you to suggest this ;-)
Same wrong numbers that are in the manual, and only buttons 1 to 32. Nice try though.
The buttons you see in the Gamecontroller Menu are the button numbers which gets send to the game.
Xbox button is supposed to be button 25 and not 24 on a McLaren wheel so the old driver is wrong. Maybe was mapped to 24 in an old Firmware and was changed to 25 in the meantime, but 25 is definitely correct. So even if this would be implemented into the UI it would also show 25.
For the "regular" buttons 32 buttons from Gamecontroller menu is also enough, above 32 are only "special" buttons like the 12-positions of each MPS etc.
Can suggest to re-implement a button number indicator somehwere in the UI, however I dont know how to implement so that it looks "good", so might have very low prio and something not coming in one of the next drivers but maybe in the (far) future at some point.
it would be nice in general if such values are displayed, it could also help with the calibration of the pedals, if you get raw values displayed. Something doesn't have to be "pretty", as it can be seen on the screenshot, that is completely fine.
Fix drivers Fanatec (Fallatec in spanish)
?
Fanatec Driver 451 (Current Official Release) for CSL, CSW and Podium WB (all wheels)
I have a CSL Elite PS4 WB, is this driver compatible ? Because I thought firmware updates for this base had discontinued as with the availability of this product ! I don't have any issues with my wheel even though it's nearly 5 years old so are there any benefits to this update ? Not sure which firmware I have only that 684 22 displays on the wheel, last update May 2021 and I do recall ABS was changed to BLI last time, many thanks.
The CSL Elite PS4 Base is still fully supported and not EOL yet.
bei mir wird nach dem Treiber update am Podium Button Modul Endurance die Bremsbalance, die in ACC eingestellt ist, nicht richtig angezeigt.
Der Wert ist am Modul grundsätzlich falsch
Das kann nichts mit einem Treiber Update zu tun haben. Die Werte kommen über FanaLab und nicht dem Treiber.
Welche FanaLab Version ist im Einsatz? Es sollte nur 1.99.05 mit Treiber 451 genutzt werden, keine 1.69.x Version. Die 1.69.x Versionen sind uralt und haben bspw die 2023er ACC Autos noch gar nicht drin, entsprechend wird mit dieser alten Lab Version natürlich immer ein falscher BB Wert angezeigt.
Notfalls die mal deinstallieren, den xml Ordner bei AppData/Local/Fanatec/FanaLab löschen und das Lab neu installieren, damit sich die Liste mit den BB offsets neu generiert.
PS: next time please post in English according to the forum rules.
I’ve got an issue with the CSL DD and ACC. The framerate goes from 40 (locked) to 1 fps when I turn on the CSL DD.
so when the 452 update available any information on this
Next month.
Hi!
Installation procedure:
all correct?
I can't find an official guide on the matter, each player has his own opinion and you can never figure out which one is correct. I hope someone can help me and also future players who read this post.
Hi,
I haven't seen it mentioned (forgive me if it was), that the brake force factor loading is very unreliable in the CSL DD firmware. I use the Clubsport V2 pedals and different brake force factors for different profiles on the CSL DD. When starting up, I have to check if these brake force factors are the correct value, because ~1 out of 3 times one of the brake factors gets copied to all or multiple profiles. I didn't notice any definite pattern as to which value is repeated, but it's definitely not as simple as "the factor of the first profile is used for every other profile". As far as I can tell, all other profile values are handled correctly, but the brake force factor is rather erratic.
I haven't checked whether the wrong profile values are persisted or upon next restart it loads the correct (previously) saved value.
Hi,
I'm encountering the issue of the Firmware updater continuously populate itself and my wheel Clubsport Formula V2.5x restarts itself after the firmware update and the Firmware updater windows keeps popping up and keeps making to update. Is my wheel bricked or something else is wrong with it?