Hm but all these games should work perfectly fine with what you have, not sure why you should not be able to play them. Can you go more in detail about what the exact issue is?
You should go back to the driver 429 and also flash the firmware from it, but you have to start this manually in the firmware manager.
I can only advise against the 69x firmware and do not understand why it is offered as part of the official driver 439, even if you select the DD1 only this is listed.
It doesn't continue to happen with driver 439, it occurs with wheel base firmware 690! I'm following the forum carefully and I'm not aware of any FW remedy, except for certain steering wheel problems. Since they're sticking with this 69x firmware despite these multiple issues, I suspect it's the long-awaited rewrite.
I can only say from my side, rather the "jolts"!
But they could help the user with a downgrade to driver 429, that's what this forum is for!
Not only can I, but I have to, clearly contradict them! I had already discussed the problem with Mr. Pfister and it is the Wheel Base FW, not the Motor FW!
Your Mr. Pfister posted a NFR related TestExport MOTOR Firmware on 4th February (first post on page 5 of this thread) which fully fixed all NFR related issues (but unfortunately introduced some Jolts with the same Firmware which now need to be fixed in the MOTOR FW as well) so how can the NFR issues now suddenly be Base Firmware related issues when they are fixed with a MOTOR firmware?!
Mr Böschen, my name is Volker Schäfer and I try to help with problems with the product with my comments, to improve it and possibly to help other users with experience.
I don't have to let them show me again with a wrong post, especially since I'm not "Adam Musiol"!
I replied to YOUR post where you said that the NFR issues are Base Firmware related - which they are not as proven by a new MOTOR FW already posted 3 weeks ago (of course to someone else and not to you) which fixed the NFR issues.
So the Screenshot of the answer from Marcel to Adam was correct and needed here to show that you are incorrect with your contradiction.
Mr Böschen, after this excuse and no apologies, you don't expect me to take you seriously anymore!? It's definitely a problem with the Wheel Base FW 69x, the Motor FW doesn't make it any better, but it's not the cause!
How can it be motor firmware, when you only downgrade base firmware to 429 (689) and leave motor firmware at 42, NFR problems and FFB pull on pause are gone?
Because the underlying issue is between the communication between Motor and Base but this communication problem needs to be fixed in the Motor Firmware, hence the provided NFR TestExport Firmware 3 weeks ago which also fixed the NFR related issues also with 691 Base Firmware.
In the end it doesnt matter if its Base Firmware or Motor Firmware: important is that the issue gets fixed soon.
I reverted to driver before but jolts were still happening, but when I starteg f1 2021 with my DD1 without fanalab only with control panel jolts were gone.
I dont know how but it worked and I am using 20 Nfr ..
Is it possible there is conflict between fanalab and control panel ?
Jolts are unrelated to Fanalab as they are a Firmware issue and happen on ITM and Analysis Screens and are not present (or at least way less present) on the default FANATEC screen.
The increased Jolts with using NFR is a negative side effect of the Motor TestExport Firmware from 3 weeks ago and are not happening with the regular Motor v42, only with the new TestExport MOTOR Firmware which fixes the NFR issues but has those nasty Jolts.
Hello Mr Böschen, it is now up to me to apologize to you. Since I didn't know anything about the Motor Test FW and I found again and again in my own test that the Base FW 691 caused the problem, it was clear to me. Please excuse my rude comment.
I am getting a hard system crash (BSOD with KERNEL_SECURITY_CHECK_FAILURE) every time I try to install the x64 version of the driver. I have tried with and without the wheel base (GT DD Pro) plugged in, and tried 3 different versions of the driver (439, 434, 429), and getting the same results 100% of the time.
System is AMD Ryzen 9 5950X / Gigabyte X570 Aorus Xtreme / 4x16GB DDR4 / RTX 3090 FE, running Windows 10 20H2. It has been completely stable for everything thing, but just for testing I've tried loading a fully stock BIOS config (no PBO or even XMP enabled), and it does not make any difference.
Have you ever got this error before on this PC? It might be faulty ram or hard drive or driver conflict or a too agressive antivirus software if you have any. Go through device manager if there are any devices with warnings. Disable antivirus protection in windows security options for the time of installing the driver. If this doesn't help run a r check of any type for a couple of hours. If you overclocked the CPU down lock to stock (although the code does not seem to be oc related). If nothing helps try only one bank of ram. Make an image of entire system partition with any free backup soft an reinstall windows. Run a disc check. This is all that comes to my mind.
I tried but id dint work ,installed driver but had problems installing manual motor firmware , those hex files , it always has warning ,even thou I deleted all fanatec files from pc
Comments
Hm but all these games should work perfectly fine with what you have, not sure why you should not be able to play them. Can you go more in detail about what the exact issue is?
the base was perfect ....
i saw an update and i wanted to do it was the 437 with firmware 691 ...... from that moment the steering wheel didn't work properly
in the Fanatec control panel the steering wheel is fully functional ..... that is, it follows my steering ..... this does not happen in the game.
as soon as I touch the crown, in game it completes the entire turn ... !!
I also installed the 439 but nothing has changed ... I also tried to go back to the previous drivers but nothing ... !!!
the only thing that makes it work is to put it in PC COMP mode ... !!
this is how my DD1 works .... !!!
can you tell me what to do ... !!!!
hello thanks MArco
You should go back to the driver 429 and also flash the firmware from it, but you have to start this manually in the firmware manager.
I can only advise against the 69x firmware and do not understand why it is offered as part of the official driver 439, even if you select the DD1 only this is listed.
Hi, just wanted to report that issue related to NFR is still happening in 439. Tested on F1 2021 and rFactor 2. When can we expect a fix?
Of course its still happening in 439 - it is listed in the known issues for a reason and does not magically fix itself... ^^
There is already a NFR TestExport FW available somewhere in this thread which fixed the NFR issues but introduced more Jolts.
Thats currently under investigation how to better fix the NFR issues without creating more Jolts, no ETA on when a fix is ready.
In the meantime continue to not use NFR.
May I correct them?
It doesn't continue to happen with driver 439, it occurs with wheel base firmware 690! I'm following the forum carefully and I'm not aware of any FW remedy, except for certain steering wheel problems. Since they're sticking with this 69x firmware despite these multiple issues, I suspect it's the long-awaited rewrite.
I can only say from my side, rather the "jolts"!
But they could help the user with a downgrade to driver 429, that's what this forum is for!
The NFR issues are related to Motor Firmware, not Base Firmware - so unrelated to Base Firmware 69x.
Not only can I, but I have to, clearly contradict them! I had already discussed the problem with Mr. Pfister and it is the Wheel Base FW, not the Motor FW!
Well then I have to clearly contradict you now.
Your Mr. Pfister posted a NFR related TestExport MOTOR Firmware on 4th February (first post on page 5 of this thread) which fully fixed all NFR related issues (but unfortunately introduced some Jolts with the same Firmware which now need to be fixed in the MOTOR FW as well) so how can the NFR issues now suddenly be Base Firmware related issues when they are fixed with a MOTOR firmware?!
Mr Böschen, my name is Volker Schäfer and I try to help with problems with the product with my comments, to improve it and possibly to help other users with experience.
I don't have to let them show me again with a wrong post, especially since I'm not "Adam Musiol"!
Hä, what?!
There was nothing wrong.
I replied to YOUR post where you said that the NFR issues are Base Firmware related - which they are not as proven by a new MOTOR FW already posted 3 weeks ago (of course to someone else and not to you) which fixed the NFR issues.
So the Screenshot of the answer from Marcel to Adam was correct and needed here to show that you are incorrect with your contradiction.
Mr Böschen, after this excuse and no apologies, you don't expect me to take you seriously anymore!? It's definitely a problem with the Wheel Base FW 69x, the Motor FW doesn't make it any better, but it's not the cause!
OK.
Must be Placebo then for everyone who reported that NFR issues are fixed with the mentioned Motor Firmware.
How can it be motor firmware, when you only downgrade base firmware to 429 (689) and leave motor firmware at 42, NFR problems and FFB pull on pause are gone?
I did it obviously but without the desired result ... !!! I await solutions ... ??? Maurice
Because the underlying issue is between the communication between Motor and Base but this communication problem needs to be fixed in the Motor Firmware, hence the provided NFR TestExport Firmware 3 weeks ago which also fixed the NFR related issues also with 691 Base Firmware.
In the end it doesnt matter if its Base Firmware or Motor Firmware: important is that the issue gets fixed soon.
Thanks . It's true. It doesn't matter anyway. It's just needs to get fixed already because this is getting ridiculous with all the problems.
I reverted to driver before but jolts were still happening, but when I starteg f1 2021 with my DD1 without fanalab only with control panel jolts were gone.
I dont know how but it worked and I am using 20 Nfr ..
Is it possible there is conflict between fanalab and control panel ?
Jolts are unrelated to Fanalab as they are a Firmware issue and happen on ITM and Analysis Screens and are not present (or at least way less present) on the default FANATEC screen.
The increased Jolts with using NFR is a negative side effect of the Motor TestExport Firmware from 3 weeks ago and are not happening with the regular Motor v42, only with the new TestExport MOTOR Firmware which fixes the NFR issues but has those nasty Jolts.
can I install regular motor v42 update via firmware update separately so I can fix this issue???
It will not fix the jolts and don't get your hopes up that it will be fixed this year.
Hello Mr Böschen, it is now up to me to apologize to you. Since I didn't know anything about the Motor Test FW and I found again and again in my own test that the Base FW 691 caused the problem, it was clear to me. Please excuse my rude comment.
How can I revert to last working driver and motor firmware and fix this issue , Nfr really has influence in f12021
Basically what I am asking is how to flash DD1 erase all firmware so far and install lets say driver 431 or later which has worked previously
I am getting a hard system crash (BSOD with KERNEL_SECURITY_CHECK_FAILURE) every time I try to install the x64 version of the driver. I have tried with and without the wheel base (GT DD Pro) plugged in, and tried 3 different versions of the driver (439, 434, 429), and getting the same results 100% of the time.
System is AMD Ryzen 9 5950X / Gigabyte X570 Aorus Xtreme / 4x16GB DDR4 / RTX 3090 FE, running Windows 10 20H2. It has been completely stable for everything thing, but just for testing I've tried loading a fully stock BIOS config (no PBO or even XMP enabled), and it does not make any difference.
Here's a video showing it happening: https://www.youtube.com/watch?v=afL8qxxr2L0
Uninstal, reboot, instal 429, reboot, update firmware-click manual and update everything manual.
Have you ever got this error before on this PC? It might be faulty ram or hard drive or driver conflict or a too agressive antivirus software if you have any. Go through device manager if there are any devices with warnings. Disable antivirus protection in windows security options for the time of installing the driver. If this doesn't help run a r check of any type for a couple of hours. If you overclocked the CPU down lock to stock (although the code does not seem to be oc related). If nothing helps try only one bank of ram. Make an image of entire system partition with any free backup soft an reinstall windows. Run a disc check. This is all that comes to my mind.
I tried but id dint work ,installed driver but had problems installing manual motor firmware , those hex files , it always has warning ,even thou I deleted all fanatec files from pc
Which hex files? You do not have to manually select any hex file.
So how then to revert , cause when I installed previous driver it dint revert motor firmware