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.
Did you manually flashed the McLaren Firmware to v44? In previous drivers there was a faulty v44 included with a broken right Clutch Paddle which was fixed in new drivers but the FW version is still the same with v44 so you need to manually update the Wheel Firmware again to get the right Clutch working normal again.
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.
BRF setting in Fanatec Control Panel workaround...
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.
what is the latest non-beta version of the drivers, 436 or 437? I still have version 429 because all the bugs I read about discourage me to install a higher version. I have the DD1 with Formula V2 steering wheel.
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.
what is the latest non-beta version of the drivers, 436 or 437? I still have version 429 because all the bugs I read about discourage me to install a higher version. I have the DD1 with Formula V2 steering wheel.
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.
what is the latest non-beta version of the drivers, 436 or 437? I still have version 429 because all the bugs I read about discourage me to install a higher version. I have the DD1 with Formula V2 steering wheel.
greetings...
If everything still works and you do not have any problems, no reason to update and risk finding out that something is not working right.
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.
Aha. And what makes you assuming that Fanatec is lying? What gives you reason to not believe them that the firmware re-write is still ongoing when they officially write this?!
Well I am sorry you think I think Fanatec is Lying. However I suspect that the problem has been put of the back burner. Anyway, I have said enough and will let more experienced people discuss this with you
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 tried to update the endurance button module on one of my wheels and it gave an error. Now the button module is not showing in control panel and buttons are not working. I have attached the logs.
Hi, after updating my CSL Elite v1.1 + WRC wheel from driver 3XX to 436 the only settings I can change are SEN and FF. How can I create presets and access the rest of settings this base/wheel combo support?
Going through threads on this forum hasn't helped.
Edit: After reading every changelog of every driver 4xx I found it:
Users can switch to "Advanced Mode" to access all settings like usual via the driver UI or by holding the tuning menu button for 3 seconds while being in the tuning menu.
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.
As you already try some drivers out you should maybe just try 437 now as well...
Maurice,
Too hard to explain, but discovered it was actually the physical end point setting inside the handbrake box that was causing problem. Small adjustment with a 3/8 inch wrench to adjust end point and now I have all the range. Thanks for getting back to me on the first post. I am new this this forum . so 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.
this wasn't an attempt to silence you, this was more a suggestion. I feel insulted by your post, so again, best to stay out of this "mess" as you call it if you cannot cope with my reply. Maybe Marcel should invite you as beta tester, then we will see if you can do a better job :)
Issues that are open for more than 2 years (basically since day one the DD1 and 2 where released) and after all that time those issues are still unresolved and there isn't a clear timeline or path when those will be resolved (customers are hearing the same message "we are investigating and working on it" over and over again and again and again), basic issues that could have been caught with a regression test etcetera etcetera... maybe @Gagaryn framed it a bit harsh but he's right in my opinion. Fanatec builds great hardware but it lacks proper software development and everything that comes with it!
Fanatec claims to have a pool of hundreds beta testers (and i only came across @maurice and you as "known" beta testers on all the forums and Facebook groups i visit once in a while... so maybe it's not hundreds of active beta testers) and if that's correct and there are hundreds of beta testers it only endorses what @Gagaryn said because last year basically every release was followed by a hotfix release (or 2) and none of the long outstanding issues were solved... new ones were introduced like the"max rotations" for example. And NO, beta testers aren't responsible for new introduced bugs and NO beta testers aren't responsible if anything slips through (shit happens) but it happens quite a lot at Fanatec so maybe the pool isn't diverse enough?
And the " you should become a beta tester to see if you could do a better job", although i applied multiple times as a beta tester i never got an answer back from Fanatec... maybe the form has the same magical behaviour as the forum sometimes has ;)
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.
in version 437 is the problem solved that the steering wheel could turn in one direction when you go into the game menu? i have a problem with my wrist and don't want to risk pain if the steering wheel does something i don't anticipate
Sadly this is not solved yet, we are still working on the issue.
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.
With 437, the right analog paddle on the McLaren GT3 v2 doesn't work, it's stuck on 100%, tried reflashing firmware and switching center dial modes but nothing changes. I didn't have this problem in 436 or earlier.
Can you please map two physical buttons to buttons 7 & 8. It's challenging missing such fundamental buttons that some games don't allow you to remap like the entire F1 series. The McLaren GT3 is the only wheel that's not compatible with F1 2021 (and I believe prior F1 versions don't work with this wheel either) If you have no plans to make this work, could you at least acknowledge that the firmware on this wheel is broken and you don't intent to fix? all the forum posts asking about this have been ignored since the wheel launched.
Weird normally reflashing should have helped
here the separate firmware you could try with
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.
With 437, the right analog paddle on the McLaren GT3 v2 doesn't work, it's stuck on 100%, tried reflashing firmware and switching center dial modes but nothing changes. I didn't have this problem in 436 or earlier.
Can you please map two physical buttons to buttons 7 & 8. It's challenging missing such fundamental buttons that some games don't allow you to remap like the entire F1 series. The McLaren GT3 is the only wheel that's not compatible with F1 2021 (and I believe prior F1 versions don't work with this wheel either) If you have no plans to make this work, could you at least acknowledge that the firmware on this wheel is broken and you don't intent to fix? all the forum posts asking about this have been ignored since the wheel launched.
Do you mean on PlayStation? The input is generally working, for example in ACC, the implementation of these inputs is up to the game developers. We can have a closer look and inform Codemasters about the not working input so they can fix it in their next game.
Sorry for the misunderstanding, the McLaren wheel has less buttons than the Formula V2 and most of our other wheels which is why its missing those. We can't just add buttons to the wheel, the others are already mapped and have functions, this would break support in other games. The F1 game should make the option you want to use them for adjustable so you could add any input. If they pre-map it to a button input number which not every wheel has and they don't make this adjustable, then its their "fault" in my opinion.
For example we also have a Podium Hub with button clusters which only features 6 buttons, it would theoretically be an issue on that as well. But not if the game offers to map everything you like to the button you like. Then its only an issue of the wheel having only 6 buttons which you know before buying.
We can ask Codemasters to make this game option mappable to any button. Because if we "fix" this on the wheel by making two buttons on it 7 and 8, who knows what other gamefunction in another game breaks or how many games already had functions working for this button and suddenly would not work anymore.
If you are on PC you could take a look at the program joy2key as a workaround. There you can assign any keyboard button to one on the wheel.
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.
Rfactor 2: driver 415, FFB in rFactor 2 felt a lot better around centre, you could feel tire grip through FFB, allowing you to feel the understeer and oversteer. Now the wheel is loose and then becomes notchy when the FFB builds up.
I have applied the recommended settings in the driver/fanalab and in game.
RF2 just undeliverable at the moment with the lastest drivers.
Other games like ACC, AMS2 and DIRT 2 feel fine, it's just RF2 FFB thats become worse.
Mates have other DD's from other brands and not experiencing these issues in RF2.
Please fix the RF2 FFB in the drivers, or provide new recommend settings to fix these issues.
Like Maurice said, try with DPR setting set to OFF.
We found out that rF2 spams the damper effect channel, constantly switching multiple effects on and off which increases the more often you go back to pits and click on drive. We've informed the developers of rF2, they are aware and its something they want to fix.
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.
For my GT DD PRO with V3 Pedals, 1.5 Shifter, Handbrake:
I had been running 434 with a "CSL_DD_Base_V1_1_5_2_testExport_reva059d384_app_S (1)" hex file I got from support that had worked pretty good for maybe 4 hours of driving. No miss shifts. No Flicker
So I saw here there was a new version and tried the Beta driver with the "V1_1_5_4_etc..." Hex file and I have had lots of miss shifts again.
Most common miss shifts are 2nd instead of 4th, 1st instead of 4th and 4th instead of 6th. So it seems to always be the bottom row of gears.
Thanks, the fix was regarding the calibration process failing, we are looking into the miss shifts to see if we can improve this as well.
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.
STILL?? I am sorry but I find that hard to belive that your still working on it, sorry
The firmware is incredibly complex with many features and compatibilites, It's done to some degree and tested on the way internally but there are still things which need to be re-written and added to make it complete and to feature the same as the current firmware.
The firmware evolved over 10+ years and countless of products until this point, it's not re-written in a better way quickly especially when turning around every stone to have a second thought of how it could be improved while already at it.
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.
3 - Attached the setup via the original Fanatec USB cable to the rear of the PC, plugged in the power and set the wheelbase to PC mode (red LED).
All items get recognized and the "New Firmware Available" notice is displayed.
4 - Open Firmware manager
5 - Select Update, pop up window with timer appears.
6 - Click OK on timer window
At this point I have tried several things, all to no avail
- wait, for an hour
- Click the Green "update" button
- close the application, repeat everything up to step 4, select "manual update"
None of these steps result in updated firmware.
I searched on Reddit, found people with similar issues, but most were pre-firmware manager, with the previous control panel. Tried some suggestions, like:
- Unplug everything from the wheelbase, including the steering wheel
- Use different USB cable
- Turn off windows defender, and/ or any other firewall blocking software.
- Turn off virus scanner
None of this worked, I even tried all of this on my laptop, just to rule out my PC, so I am hoping that you have any suggestions. The hardware works fine, I would just like to have the latest and greatest firmware on it.
Thank you for the detailed explanation and log files, I'll update our developer with this so we can hopefully get a better idea of whats going wrong here.
When you try to update like discribed and nothing happens, does the base seem to be in update mode indicated my flashing LED of the power button? Is the base in this situations working normally or do you need to re-boot?
With which driver did the update process work fine before? Can you please go back to that driver version to try the update process with that one again.
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 am getting the "exceeded maximum rotation" bug on my current DD1 podium wheelbase. This update shows this has been fixed, but then it is also crossed. What does this supposed to mean? You tried to fix it but got reports back that it didn't, or the fix didn't make into this beta, or it is not fixed properly yet but will be in the final release?
Thank you
Fixed error message of "exceeded maximum rotation" getting shown without reason
We tried to fix it and in first testing it looked like it was fixed, but later we found out and also others here reported that it's still happening. We have to work on this fix again.
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.
Wheel Base Model (product ID): Podium Wheel Base DD1 (P_WB_DD1_EU)
Steering Wheel Model (product ID): Clubsport Steering Wheel Universal Hub for Xbox One (CSW_RUHX)
Driver version: 437
Base FW version: 691
Engine FW version: 42
FanaLab Version: Not installed!
Driver/FanaLab installed on C: !
Windows 11 Pro, Ver. 21H2, Build: 22000.493
Raceroom feels good after the first round, then everything becomes a bit sluggish, the in-game FFB graph shows no change, although something has changed. At the beginning I had increased the FFB multiplier of the vehicle because it felt weaker at first, now it's just stiffer and without details, as if there was hardly any air left in the tires.
To try out the new feature of R3E, I selected Auto in the tuning menu, but nothing is changed by the game, it stays at the Fanatec defaults. I recognized this on the DD1 display, when I was scrolling through the last value, the DD1 freezes and I have to disconnect it from the power supply because the on/off button no longer works either.
SEN = Auto, FFB = 70%, FFS = Peak, NDP = Off, NFR = Off, NIN = Off, INT = 1, FEI = 100%, FOR = 100%, SPR = 100%, DPR = 100%
ACC feels good after a short test, no difference if I change NFR from 2 to 0.
SEN = 1080, FFB = 50%, FFS = Peak, NDP = Off, NFR = Off (or 2), NIN = 3, INT = 2, FEI = 100%, FOR = 100%, SPR = 100%, DPR = 100%
Dirt Rally with NFR on 3 after a short time again shows the problem that the steering becomes stiff. With NFR set to 0, I was able to drive about 3 stages without any problems, then the problem suddenly came here too, but it only lasted for a short time and disappeared by itself. I noticed this with different vehicles and routes. Thus, NFR appears to have a major impact, but is not the sole cause. In any case, the steering wheel is no longer turned to one side when I go to the menu.
SEN = 1080, FFB = 50%, FFS = Peak, NDP = 15, NFR = 3 or Off, NIN = Off, INT = 5, FEI = 100%, FOR = 100%, SPR = 100%, DPR = 100%
rFactor 2 feels very good at first and then becomes rough, it also feels choppy at times, as if interrupted, gas and brake then seem to respond with a time lag.
SEN = Auto, FFB = 45%, FFS = Peak, NDP = 8, NFR = Off, NIN = Off, INT = 6, FEI = 90%, FOR = 100%, SPR = 100%, DPR = 100%
All in all, the new driver and firmware is a step backwards for me and significantly worsens your product, and my confidence is also affected, because you don't know what's suddenly going to happen while driving and can no longer concentrate on the actual racing events.
This is very unfortunate as I love my DD1 and am very keen to keep it working properly. If something changes, it should be an improvement and reduce the list of known issues.
First I went back to version 415 with the base FW 686 and the motor FW 40, all games ran without problems, only with rFactor 2 I had to switch FFS from peak to linear.
But since I like the driver 429 with the base FW 689 and the motor FW 41 better, I have now installed it again and can set rFactor 2 FFS back to peak. I will stick with this driver.
Would it help to turn DPR OFF?
There is a game issue with rFactor 2 that it spams the damper channel more and more over time when going back on track. The rF2 developers are aware of it now and want to fix it.
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.
Maybe it's because it was announced that the firmware rewrite has been ongoing since the beginning of 2021, perhaps even earlier. In any case - it has been over a year since the first public announcement on that.
It doesn't take this long to write firmware for a simple device - especially so when you work for the company that designed the device. It is beyond belief that dev team has been working on this for such a length of time which is why users express their exasperation. It is more likely that this work has been planned but not given priority or resources.
It's no surprise that the dev team can't allocate resource to this - they have an endless battle fixing the new issues that are introduced with each update. If it is true that the dev team have been working on the rewrite for all this time, and still don't even have an internal beta version available then things are even worse - these issues will never be fixed.
I've said it before but it is unfathomable why the beta branch and the release branch are not separate. There should at all times be a proven stable error free "Official" release that users can rely on. New features should only release into the beta branch so that they are fully tested by official beta testers before any public beta release. The public beta should only exist to pick up the odd gremlin missed by the official test team. That way things get fixed - only error free releases make it Official Driver status.
As an example of the mess - there has never been a release for Podium DD that provides the functionality that was advertised - ITM on the wheelbase has NEVER worked reliably. Well over two years now since the product launched - this issue should have been fixed BEFORE launch!
At the moment every Fanatec user is a beta tester because the real beta testers do a terrible job of smoke testing the software before release. It's beyond a joke.
I can understand your frustration and I can understand your complaints but please don't direct it to specific people or a group of people, especially not in an insulting way.
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 guys are hilarious. You really think this development is going well? In the three years or so that I've used Fanatec products it's gone from bad to worse.
BTW - this is a user forum, sharing user's experience is what this is for - this isn't the first time you've attempted to silence me Sascha and I'd be grateful if you didn't do it again. Feel free to post if you have something useful to say but please don't try to silence valid criticism. Maybe concentrate on finding the bugs and not leaving that to the users. I'm sure you can do better than this mess.
Your criticism of the firmware/software might be valid, but your criticism towards specific or a group of people is not. Sascha didn't want to silence you regarding your opinion about the software, he was just offended by "Doing a terrible job..." and so on.
Comments
Did you manually flashed the McLaren Firmware to v44? In previous drivers there was a faulty v44 included with a broken right Clutch Paddle which was fixed in new drivers but the FW version is still the same with v44 so you need to manually update the Wheel Firmware again to get the right Clutch working normal again.
Go to Firmware Manager, check the Manual Update checkbox, click on Manual Steering wheel update, click flash, done.
BRF setting in Fanatec Control Panel workaround...
CSL pedals load cell kit. BRF resets to 30%, after turning CSL DD base off everytime.
pls refer my post today, 04/02... works for me
Hi.
After last firmware ( and beta drivers my DD1 start : https://youtu.be/ow28ErBeP7c
before it completed the full turn.
This is a problem?
That is a known problem of the NFR TestExport Firmware you have installed.
It does not harm but if it's annoying all you can do is downgrading back to the regular v42 Motor Firmware and not the NFR TestExport.
Thanks!. If it's a known "problem", it's not bothersome to me.
I wait for the next firmware.
Hello,
what is the latest non-beta version of the drivers, 436 or 437? I still have version 429 because all the bugs I read about discourage me to install a higher version. I have the DD1 with Formula V2 steering wheel.
greetings...
Stay at 429
If everything still works and you do not have any problems, no reason to update and risk finding out that something is not working right.
Well I am sorry you think I think Fanatec is Lying. However I suspect that the problem has been put of the back burner. Anyway, I have said enough and will let more experienced people discuss this with you
I tried to update the endurance button module on one of my wheels and it gave an error. Now the button module is not showing in control panel and buttons are not working. I have attached the logs.
What can I do?
Hi, after updating my CSL Elite v1.1 + WRC wheel from driver 3XX to 436 the only settings I can change are SEN and FF. How can I create presets and access the rest of settings this base/wheel combo support?
Going through threads on this forum hasn't helped.
Edit: After reading every changelog of every driver 4xx I found it:
Users can switch to "Advanced Mode" to access all settings like usual via the driver UI or by holding the tuning menu button for 3 seconds while being in the tuning menu.
I updated to PC driver 434 but wheel would not center with firmware version 688 so reverted to Wheel base FW 680, then able to calibrate center.
Everything worked fine except Handbrake 1.5. It now works like an on/off button.
Does the new driver and FW address this issue.
I use the Handbrake in Dirt Rally 2.0 . It worked great with PC driver 381 / Wheel base FW 680 and wheel fw 22. Now it is an on/off switch.
I tried to revert to 381 but again wheel would not center calibrate.
Can anybody help me here.
Thanks - Wayne
Here are details of system and hardware:
PC running Windows 10 - 64 bit - up to date
This is the Feedback thread for 437.
As you already try some drivers out you should maybe just try 437 now as well...
I guess I can give it a try. Thanks
Should I go to the 434 driver forum?
Hello,
I receive yesterday the GT DD PRO, and i have one question.
What driver should I install to play on PS4 without anomalies.
436 that is on the website or the 437 Beta?
Maurice,
Too hard to explain, but discovered it was actually the physical end point setting inside the handbrake box that was causing problem. Small adjustment with a 3/8 inch wrench to adjust end point and now I have all the range. Thanks for getting back to me on the first post. I am new this this forum . so thanks.
Wayne
Issues that are open for more than 2 years (basically since day one the DD1 and 2 where released) and after all that time those issues are still unresolved and there isn't a clear timeline or path when those will be resolved (customers are hearing the same message "we are investigating and working on it" over and over again and again and again), basic issues that could have been caught with a regression test etcetera etcetera... maybe @Gagaryn framed it a bit harsh but he's right in my opinion. Fanatec builds great hardware but it lacks proper software development and everything that comes with it!
Fanatec claims to have a pool of hundreds beta testers (and i only came across @maurice and you as "known" beta testers on all the forums and Facebook groups i visit once in a while... so maybe it's not hundreds of active beta testers) and if that's correct and there are hundreds of beta testers it only endorses what @Gagaryn said because last year basically every release was followed by a hotfix release (or 2) and none of the long outstanding issues were solved... new ones were introduced like the"max rotations" for example. And NO, beta testers aren't responsible for new introduced bugs and NO beta testers aren't responsible if anything slips through (shit happens) but it happens quite a lot at Fanatec so maybe the pool isn't diverse enough?
And the " you should become a beta tester to see if you could do a better job", although i applied multiple times as a beta tester i never got an answer back from Fanatec... maybe the form has the same magical behaviour as the forum sometimes has ;)
We are looking into it, if its an issue on our end, we'll fix it.
Sadly this is not solved yet, we are still working on the issue.
Weird normally reflashing should have helped
here the separate firmware you could try with
Do you mean on PlayStation? The input is generally working, for example in ACC, the implementation of these inputs is up to the game developers. We can have a closer look and inform Codemasters about the not working input so they can fix it in their next game.Sorry for the misunderstanding, the McLaren wheel has less buttons than the Formula V2 and most of our other wheels which is why its missing those. We can't just add buttons to the wheel, the others are already mapped and have functions, this would break support in other games. The F1 game should make the option you want to use them for adjustable so you could add any input. If they pre-map it to a button input number which not every wheel has and they don't make this adjustable, then its their "fault" in my opinion.
For example we also have a Podium Hub with button clusters which only features 6 buttons, it would theoretically be an issue on that as well. But not if the game offers to map everything you like to the button you like. Then its only an issue of the wheel having only 6 buttons which you know before buying.
We can ask Codemasters to make this game option mappable to any button. Because if we "fix" this on the wheel by making two buttons on it 7 and 8, who knows what other gamefunction in another game breaks or how many games already had functions working for this button and suddenly would not work anymore.
If you are on PC you could take a look at the program joy2key as a workaround. There you can assign any keyboard button to one on the wheel.
Like Maurice said, try with DPR setting set to OFF.
We found out that rF2 spams the damper effect channel, constantly switching multiple effects on and off which increases the more often you go back to pits and click on drive. We've informed the developers of rF2, they are aware and its something they want to fix.
Thanks, the fix was regarding the calibration process failing, we are looking into the miss shifts to see if we can improve this as well.
The firmware is incredibly complex with many features and compatibilites, It's done to some degree and tested on the way internally but there are still things which need to be re-written and added to make it complete and to feature the same as the current firmware.
The firmware evolved over 10+ years and countless of products until this point, it's not re-written in a better way quickly especially when turning around every stone to have a second thought of how it could be improved while already at it.
Thank you for the detailed explanation and log files, I'll update our developer with this so we can hopefully get a better idea of whats going wrong here.
When you try to update like discribed and nothing happens, does the base seem to be in update mode indicated my flashing LED of the power button? Is the base in this situations working normally or do you need to re-boot?
With which driver did the update process work fine before? Can you please go back to that driver version to try the update process with that one again.
We tried to fix it and in first testing it looked like it was fixed, but later we found out and also others here reported that it's still happening. We have to work on this fix again.
Would it help to turn DPR OFF?
There is a game issue with rFactor 2 that it spams the damper channel more and more over time when going back on track. The rF2 developers are aware of it now and want to fix it.
I can understand your frustration and I can understand your complaints but please don't direct it to specific people or a group of people, especially not in an insulting way.
Your criticism of the firmware/software might be valid, but your criticism towards specific or a group of people is not. Sascha didn't want to silence you regarding your opinion about the software, he was just offended by "Doing a terrible job..." and so on.