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.
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.
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.
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.
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.
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 ;)
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.
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.
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.
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...
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.