@Marcel, thank you for the reply. I was able to fix it before I saw this and thought you'd like to know because it was a strange one. I went into Windows Control Panel, Game Controllers/Devices and it was showing there as CSW 2.5. I double clicked it and it had been disabled somehow. I'd never seen that screen before and have no idea how it got disabled. But I clicked an enable checkbox and it's been fine ever since.
trying to update to 432 beta from 429. the wheelbase , DD2, fw updated ok. When trying to up date the motor fw the wheelbase is powered off and i get an error screen saying it could not communicate. Have tried multiple times on different usb ports.
Older F1 titles, I think F1 2021 should work by now though. COMP doesn't really have a downside, if you want you can use it all the time. if you like to know for sure, try everything with PC mode first and only use COMP if something doesn't work in the native mode.
I decided to go back to the release driver 429, I was able to revert the DD1 base firmware back to 689, is that the correct version? What version should motor firmware be?
When a game supports it, it will also support the base in native PC mode, so then you should have it int hat mod.
Games will use it to push recommended settings which work as a good baseline. We suggest game developers to make it obvious for example in the controller menu that this feature is available. In addition the display on the wheel will show dots to indicate that the values got changed but I think at the moment sometimes the dots vet shown even though no setups where pushed, we are working on a fix so they only show when a game really pushed settings.
When will these drivers function without causing BSODS with Battleye games? I recently tried to install driver 429. I used to be on 374, which is the last I have tested that did not have issues. Yet again, firing up Tarkov which uses Battleeye immediately causes a KERNEL_SECURITY_CHECK bluescreen. Uninstalling then driver will work, but the installing a different one, even 374 will have the same issue. Have to do a system restore where nothing newer than 374 was installed...
Your drivers are not signed correctly... Seriously starting to regret my DD1 purchase.
@Marcel - - Thank you for the reply and your question.
I went back and checked for each (ACC, AC, and ETS 2) and in all cases, with max graphics, the CPU load was between 35 - 50% and GPU was 55 - 90%. I did not see any spikes or overloads, even when I was able to have the task manager in view while racing and experiencing the lag. Once FFB is turned off, everything returns to normal.
FYI, my specifications for computer and firmware are:
Thanks for your reply, and I am still open to ideas? I have a Formula V2.5x wheel on order and I am interested to see if using it makes any difference in results with those titles.
Thanks for the information, we weren't aware of this yet.
Can you please provide windows event logs with the crash so we can have a closer look. It's weird that we are having an impact on games like Tarkov which doesn't make use of FFB wheels. You also mention BF 2042, which I play while having our drivers installed and I don't experience any crashes so far.
Does the base need to be turned on and plugged in for it to crash or is it enough to have the driver installed?
In some of the BattlEye related threads also other hardware like VR headsets are mentioned, what if maybe BattlEye does something wrong with their cheat detection?
Comments
@Marcel, thank you for the reply. I was able to fix it before I saw this and thought you'd like to know because it was a strange one. I went into Windows Control Panel, Game Controllers/Devices and it was showing there as CSW 2.5. I double clicked it and it had been disabled somehow. I'd never seen that screen before and have no idea how it got disabled. But I clicked an enable checkbox and it's been fine ever since.
Will Driver 432 move from beta to official version soon?
It's about time?
Soon, sure.
But not this 432 as it has too many issues. Will be a 433 or 434 ;)
thank you.
I will wait until then.
trying to update to 432 beta from 429. the wheelbase , DD2, fw updated ok. When trying to up date the motor fw the wheelbase is powered off and i get an error screen saying it could not communicate. Have tried multiple times on different usb ports.
How can i go back to 429.
Wanna to ask, which drivers and firmware will be the best for GT DD Pro?
Not really any idea other than handling it through our customer support and repair team, sorry
Older F1 titles, I think F1 2021 should work by now though. COMP doesn't really have a downside, if you want you can use it all the time. if you like to know for sure, try everything with PC mode first and only use COMP if something doesn't work in the native mode.
what does task manager say where the CPU/RAM load is coming from which might cause the performance loss?
I'll ask the dev what this could be related to.
Is another driver already installed or is this the first time you are trying to install one?
Does it help to remove the older driver first, in case you have that installed?
Does it work to install an older driver?
I decided to go back to the release driver 429, I was able to revert the DD1 base firmware back to 689, is that the correct version? What version should motor firmware be?
Thanks,
At the moment no game is supporting it yet.
When a game supports it, it will also support the base in native PC mode, so then you should have it int hat mod.
Games will use it to push recommended settings which work as a good baseline. We suggest game developers to make it obvious for example in the controller menu that this feature is available. In addition the display on the wheel will show dots to indicate that the values got changed but I think at the moment sometimes the dots vet shown even though no setups where pushed, we are working on a fix so they only show when a game really pushed settings.
432 of this channel
How to go back to a previous driver:
Before you do so it would be great if you could use the collect log function of the driver UI and upload them here.
When will these drivers function without causing BSODS with Battleye games? I recently tried to install driver 429. I used to be on 374, which is the last I have tested that did not have issues. Yet again, firing up Tarkov which uses Battleeye immediately causes a KERNEL_SECURITY_CHECK bluescreen. Uninstalling then driver will work, but the installing a different one, even 374 will have the same issue. Have to do a system restore where nothing newer than 374 was installed...
Your drivers are not signed correctly... Seriously starting to regret my DD1 purchase.
You are the first to ever report this issue so of course it could never have been investigated.
I have reported this issue several times in the past on these forums.
I have extensively tested it over multiple Windows installations. It happens without fail.
You also find other people on the web with the same issues. For example:
Other guy from this very forum: Fanatec products cause BSOD with battleye — Fanatec Forum
Fanatec Driver Package breaks the game.... : EscapefromTarkov (reddit.com)
Blue Screen every time I try to start PUBG. Error Code 'Kernel Security Check Failure' :: PUBG: BATTLEGROUNDS General Discussions (steamcommunity.com) (PUBG, also Battleeye solved by unplugging all Fanatec accessories before playing - which shouldn't be neccessary)
Battleye and Fanatec : Fanatec (reddit.com)
Trying to update to 432 beta. The wheelbase updated FW ok but I get the following error when the motor FW is being updated.
I have updated the drivers and FW on this system fine in the past. This is the first time I have encountered an error.
I have attached the
Fanatec logs.
In regards to my issue above, here are people experiencing it with BF2042, PUBG and FIFA:
Fanatec wheels causes Battlefield 2042 to crash on startup! : Fanatec (reddit.com)
@Marcel - - Thank you for the reply and your question.
I went back and checked for each (ACC, AC, and ETS 2) and in all cases, with max graphics, the CPU load was between 35 - 50% and GPU was 55 - 90%. I did not see any spikes or overloads, even when I was able to have the task manager in view while racing and experiencing the lag. Once FFB is turned off, everything returns to normal.
FYI, my specifications for computer and firmware are:
Computer: I9-10900K @3.70 GHz, 32 GB RAM, Nvidia 3080 GPU
Thanks for your reply, and I am still open to ideas? I have a Formula V2.5x wheel on order and I am interested to see if using it makes any difference in results with those titles.
New driver 433 available and first post updated
any feedback on this issue?
Thanks for the information, we weren't aware of this yet.
Can you please provide windows event logs with the crash so we can have a closer look. It's weird that we are having an impact on games like Tarkov which doesn't make use of FFB wheels. You also mention BF 2042, which I play while having our drivers installed and I don't experience any crashes so far.
Does the base need to be turned on and plugged in for it to crash or is it enough to have the driver installed?
Thank you for the log files, I've forwarded them together with your information and screenshot.
In some of the BattlEye related threads also other hardware like VR headsets are mentioned, what if maybe BattlEye does something wrong with their cheat detection?
we are investigating
I'm coming from driver 432 beta and I have DD2 with 690 base firmware (manually updated).
Do have to manually flash the base firmware again or is 433 the same as 432? Thanks.
Yes you have to manually flash the firmware once again to be on the very latest firmware.
tried to update to 433. when the updater gets to the motor firmware the wheelbase ,dd2, powers off and i get the following error.
attached are the logs.
Looks like a USB issue. Did you tried a different USB port directly on the back of your Motherboard?