well. no idea either why you even try that old drivers if they even exist. but not my business
you basically try drivers that old that even PlayStation 5 not existed yet
"I never updated before and worked perfectly"
also by reading your comment , it could be also that something happen with your hardware
hardware by default are similar like robotic they todo same thing over and over again, if you see weird behavior what you never seen before then something may happen
Just because some devices work and some don’t doesn’t mean we definitely have different versions of the same product in circulation. Every component in there works within a tolerance of its intended operation. When you have multiple devices running at the edge of these tolerances in the same device this can cause issues in firmware by increasing the overall tolerance to beyond where a the manufacturer ever expects them to be. Finding which components are actually causing the issue isn’t a small task either as every individual component may be working within its own tolerance so when they look into it everything looks fine on the surface. These issues are not limited to Fanatec. Every single manufacturer of every single electro mechanical device experiences the same issues with every new product. Most of these can be ironed out before release but because these tolerances are so small and the sample base that can be used for testing is tiny compared to sold products it is inevitable that some of these issues will only rear their heads after release. Unfortunately, things can then deteriorate once these issues do rear their heads because the fix can then “break” other areas of the firmware. As annoying as it is for the end user it is the nature of software development. An example I’m experiencing at the moment with Apple. They have broken the “Ask to buy” feature in the App Store. I can’t agree to any requests remotely for my children to get an app because the system doesn’t work and hasn’t done for around a year ish. I work around it and assume at some point it will get sorted out.
you seems clearly not get how stuff work, company self does change things sometimes, like try lower the cost and get more profit by removing or change current component factory to some other one. and because this is mass production, all the hardware what comes at that line are same
and when they realize if they make bad decision. they actually not get profit because they need repair those hardware instead
but because hardware is controlled by firmware, they are sometimes possible also fix those by this way instead.
highest problem what i see, if they force people use older firmware because new ones not want work correctly anymore. how then people can use they new hardware's?
and i talk about products what is not even discontinued
We have been going backwards it seems with improvements to drivers and firmware.
I keep getting catastrophic freezes over large FFB spikes causing about 2-3 where my FFB freezes completely essentially wrecking your race. I have noticed this while practicing for the Daytona 24.
Is this a known issue that will be fixed prior to Daytona 24? I have had my DD1 for 4 years now with zero issues until most recent driver and Fanalabs crashing.
I identically had these problems with my DD2 but with 464 it’s all been solved ! Not 1 misshifts and not 1 FFB loss… Tested many races with or without latest Fanalab ! On iRacing for referance ! Don’t purely take my word for it… Look at my Youtube channel with many vids, With Fanalab, without Fanalab, with Fanatec wheel, with non Fanatec USB wheel,… all are ok regarding misshifts and FFB losses. You’ll see many races which means I truly tested !
I ended to the wall at Daytona when FFB lost 1-2 seconds FFB when battling hard,… so was annoying but lucky me it’s solved !
My DD1 is useless now, Does anyone know if the DD2 still has these same issues? I'd like to stay in the Fanatec ecosystem but need a solution ASAP with Dayton 24 approaching
Good to know, but I have stopped running Fanalab and have not had a disconnect or FFB freeze issue. Perhaps it is just the latest Fanalabs that was causing the issue. Now I just initially use Fanalab to load my profile and then I close it out. Fingers crossed, because the FFB feels great otherwise
Allan thanks it seems you have right. After i correct a well known Fanatec issue pic attached i could update to 464 and everything are working very well.
I am scared to downgrade the firmware from all the horror stories of bricking your wheelbase if done incorrectly but may be my only option.
The DD1 has been a daily driver for last ~ 5 years so honestly if it needs to be replaced and that solves it, I am not too upset, if that works of course.
I had a WQR FW do that on GT DD X (CSDD+) once. It was quite a few driver versions ago now. I just kept trying. One time it went to 83% so I knew I was getting somewhere.
Start over, try different USB ports. Uninstall all Fanatec drivers and software and reboot. Install Drivers and reboot. Then hook up wheel base and try again. Not sure your exact issue but sounds similar to the one I had.
i buy myself as well CSDD+ and yes there exist this problem. current solution seems that if user does hardware restart then it also allows install WQR FW, but yes steering wheel needed be also removed before todo WQR install
Is the reversed shifting on the shifter 2 port a known issue? I just got a CSL hub and noticed the issue
DD+
base 2.2.4.0
WQR 1.1.0.3
CSL Universal Hub V2 FW: 8
Basically the downshift/upshift of the shifter plugged into shifter 2 port becomes reversed when a CSL Hub is attached. It works normally with all my other wheels (DD Extreme, Podium Hub, V2.5, CS UH X V2, McLaren GT3)
Here are the two malfunction issues with the WRC steering wheel:
1. The speed display on the Podium BMR shows garbled characters.
2. In GT7, the cursor moves to the top-right corner of the screen on its own after entering the menu. In EA WRC, the buttons become unresponsive, making the game unplayable.
I have an issue where my CS DD is "not working" and stuck in Fanatec Firmware Updater when I turn on the hardware and open the Fanatec Control Pane.. Has anyone else had a similar Firmware update loop?
It happens about 50% of the time I would say. If I turn the base on and I turn the wheel, if there's absolutely no weight there, I know it will be in Update Mode and won't work in Sim.. If I open the Fanatec Control Panel, it immediately goes into Firmware Update Mode and updates. The update appears to work, as there are no errors and it completes successfully and then the hardware works perfectly. The next time I come to my rig, it's 50/50 as to whether the device works right away or is stuck in update mode and needs to update the firmware again. I haven't been able to work out any correlation between my actions and the update requirement.
All firmware is reported as up to date in the Control Panel and I've never had this one driver releases prior to 464.
Try backdating your firmware to 454 or 455. I had an issue and that was how I recovered it. I think although don’t quote me on it you can go as far back as 453. Once you get it to update you should be able to then put 464 back in.
as you not give detailed info im guessing here randomly.
depends what update it shows and needs, but if its WQR ,
you need remove the steering wheel first, make the base restart
and then try make the firmware update
it does not allow make WQR install if you steering wheel is also connected turning that time. so you would be so called forever loop if you not todo it right way
Comments
Well i tried with 352, 355 and 364 as well, after few minutes crashed (with any wheels 3 of mine). No idea.
well. no idea either why you even try that old drivers if they even exist. but not my business
you basically try drivers that old that even PlayStation 5 not existed yet
"I never updated before and worked perfectly"
also by reading your comment , it could be also that something happen with your hardware
hardware by default are similar like robotic they todo same thing over and over again, if you see weird behavior what you never seen before then something may happen
There are bugs in both button boxes on GT7, which makes me laugh so hard
Now both wheels are working well. (i did not do anything till yesterday….)
Just because some devices work and some don’t doesn’t mean we definitely have different versions of the same product in circulation. Every component in there works within a tolerance of its intended operation. When you have multiple devices running at the edge of these tolerances in the same device this can cause issues in firmware by increasing the overall tolerance to beyond where a the manufacturer ever expects them to be. Finding which components are actually causing the issue isn’t a small task either as every individual component may be working within its own tolerance so when they look into it everything looks fine on the surface. These issues are not limited to Fanatec. Every single manufacturer of every single electro mechanical device experiences the same issues with every new product. Most of these can be ironed out before release but because these tolerances are so small and the sample base that can be used for testing is tiny compared to sold products it is inevitable that some of these issues will only rear their heads after release. Unfortunately, things can then deteriorate once these issues do rear their heads because the fix can then “break” other areas of the firmware. As annoying as it is for the end user it is the nature of software development. An example I’m experiencing at the moment with Apple. They have broken the “Ask to buy” feature in the App Store. I can’t agree to any requests remotely for my children to get an app because the system doesn’t work and hasn’t done for around a year ish. I work around it and assume at some point it will get sorted out.
you seems clearly not get how stuff work, company self does change things sometimes, like try lower the cost and get more profit by removing or change current component factory to some other one. and because this is mass production, all the hardware what comes at that line are same
and when they realize if they make bad decision. they actually not get profit because they need repair those hardware instead
but because hardware is controlled by firmware, they are sometimes possible also fix those by this way instead.
highest problem what i see, if they force people use older firmware because new ones not want work correctly anymore. how then people can use they new hardware's?
and i talk about products what is not even discontinued
We have been going backwards it seems with improvements to drivers and firmware.
I keep getting catastrophic freezes over large FFB spikes causing about 2-3 where my FFB freezes completely essentially wrecking your race. I have noticed this while practicing for the Daytona 24.
Is this a known issue that will be fixed prior to Daytona 24? I have had my DD1 for 4 years now with zero issues until most recent driver and Fanalabs crashing.
I identically had these problems with my DD2 but with 464 it’s all been solved ! Not 1 misshifts and not 1 FFB loss… Tested many races with or without latest Fanalab ! On iRacing for referance ! Don’t purely take my word for it… Look at my Youtube channel with many vids, With Fanalab, without Fanalab, with Fanatec wheel, with non Fanatec USB wheel,… all are ok regarding misshifts and FFB losses. You’ll see many races which means I truly tested !
I ended to the wall at Daytona when FFB lost 1-2 seconds FFB when battling hard,… so was annoying but lucky me it’s solved !
https://m.youtube.com/channel/UCQycoV0brcTHdctF9pYCY7Q/videos
Fanalab crash self is maybe something else and nothing todo with drivers
My DD1 is useless now, Does anyone know if the DD2 still has these same issues? I'd like to stay in the Fanatec ecosystem but need a solution ASAP with Dayton 24 approaching
i went back with my DD2 the older firmware because i not like any kind weird anomaly
Good to know, but I have stopped running Fanalab and have not had a disconnect or FFB freeze issue. Perhaps it is just the latest Fanalabs that was causing the issue. Now I just initially use Fanalab to load my profile and then I close it out. Fingers crossed, because the FFB feels great otherwise
Driver install just hangs, Stops about 50%. Been installing for over 2 hours
Anyone else experience this?
Fanalab itm feature is the only thing what i can think off about this. send too much data out what is not actually allowed may freeze the chip
Allan thanks it seems you have right. After i correct a well known Fanatec issue pic attached i could update to 464 and everything are working very well.
good that this resolve it, myself actually not been use QR1 sometime now, QR2 self come little better clamp what holds that shaft in place better
Just did a test session at Sebring in iRacing and massive freeze and crash with no Fanalab running.
I tried going back to driver 463 and previous Fanalabs and still crashes.
Does anyone know how I can search error logs to see what exactly is happening?
The FFB completely freezes in a locked position for about 3-5 seconds and sometimes the screen freezes as well.
it's not the driver self, but perhaps firmware
using only older driver self may tell nothing because firmware is that what handles the hardware
also check your cables and so on as well just in case
last thing of-course can be that your hardware self starts fall apart, but usually that is very last
I am scared to downgrade the firmware from all the horror stories of bricking your wheelbase if done incorrectly but may be my only option.
The DD1 has been a daily driver for last ~ 5 years so honestly if it needs to be replaced and that solves it, I am not too upset, if that works of course.
i do not know if that is your hardware issue or not. that's why usually user needs self test it.
but people been talk 464 this and that. so there could be problems with that
I had a WQR FW do that on GT DD X (CSDD+) once. It was quite a few driver versions ago now. I just kept trying. One time it went to 83% so I knew I was getting somewhere.
Start over, try different USB ports. Uninstall all Fanatec drivers and software and reboot. Install Drivers and reboot. Then hook up wheel base and try again. Not sure your exact issue but sounds similar to the one I had.
i buy myself as well CSDD+ and yes there exist this problem. current solution seems that if user does hardware restart then it also allows install WQR FW, but yes steering wheel needed be also removed before todo WQR install
otherwise it just may show 0.0.0.0
Yeah I downgraded to the 455 FW and no problem so far 😎
@Maurice
Is the reversed shifting on the shifter 2 port a known issue? I just got a CSL hub and noticed the issue
DD+
base 2.2.4.0
WQR 1.1.0.3
CSL Universal Hub V2 FW: 8
Basically the downshift/upshift of the shifter plugged into shifter 2 port becomes reversed when a CSL Hub is attached. It works normally with all my other wheels (DD Extreme, Podium Hub, V2.5, CS UH X V2, McLaren GT3)
Here are the two malfunction issues with the WRC steering wheel:
1. The speed display on the Podium BMR shows garbled characters.
2. In GT7, the cursor moves to the top-right corner of the screen on its own after entering the menu. In EA WRC, the buttons become unresponsive, making the game unplayable.
Both are known Firmware issues to be fixed early this year.
I have an issue where my CS DD is "not working" and stuck in Fanatec Firmware Updater when I turn on the hardware and open the Fanatec Control Pane.. Has anyone else had a similar Firmware update loop?
It happens about 50% of the time I would say. If I turn the base on and I turn the wheel, if there's absolutely no weight there, I know it will be in Update Mode and won't work in Sim.. If I open the Fanatec Control Panel, it immediately goes into Firmware Update Mode and updates. The update appears to work, as there are no errors and it completes successfully and then the hardware works perfectly. The next time I come to my rig, it's 50/50 as to whether the device works right away or is stuck in update mode and needs to update the firmware again. I haven't been able to work out any correlation between my actions and the update requirement.
All firmware is reported as up to date in the Control Panel and I've never had this one driver releases prior to 464.
Any troubleshooting tips/logs/advice etc? Thanks!
Try backdating your firmware to 454 or 455. I had an issue and that was how I recovered it. I think although don’t quote me on it you can go as far back as 453. Once you get it to update you should be able to then put 464 back in.
as you not give detailed info im guessing here randomly.
depends what update it shows and needs, but if its WQR ,
you need remove the steering wheel first, make the base restart
and then try make the firmware update
it does not allow make WQR install if you steering wheel is also connected turning that time. so you would be so called forever loop if you not todo it right way