We aim for a BMR Hotfix Release this year as that product is actually not in a good shape and we want to (finally) give this product some much needed love.
Nobody has the time to read through every single post on this forum. Had I not seen this post I wouldn't know you were aware of the issue as I'm having the same one in addition my DD2 will not even update the wheel base firmware. It's stuck in a loop of reconnect your wheel properly and enter bootloader mode. With the arrival of Corsair to add the leadership and customer service you clearly lacked before hopefully that extends even into this realm, the forum.
After installing driver 464 with latest Firmware 1.3.0.1 for my GT DD Pro, i had one base disconnect today during qualifying in Gran Turismo :(
The button on the base shined red. I had to restart the base to get it working again. I thought this is fixed? It was fine with the last 2 updates(i don't remember which driver had new firmware for my wheel) and now this happend.
Also the Force Feedback feels off at times. It feels like clipping - it makes a rattling noise and FFB just stops for a few seconds and then it comes back. Never had this before.
oh my what a nightmare this DD Extreme is becoming. Had driver 462 working for the last few months without an issue. Thought finally something that was working as intended.
Then suddenly in the middle of an LFM race yesterday, the wheel decided to disconnect, I had to quit as no buttons on the wheel responded. I opened the fanatec control panel thinking something must've gone wrong. Saw new driver notification and updated to 464.
Lo and behold, again during another LFM race, the wheel disconnected again. This time, the WQR message showed FW version 0.0.0.0 and there was no wheel being detected. Full disclosure, I am using the DD Exteme + Podium Endurance Button Module + Porsche wheel + universal hub v2. Restarted the base and wheel was recognised. I thought may be it was a once off. Now scared of losing more ELO and SR, tried an offline race, yep disconnected again and same issue.
I've gone back to 462 driver and manually installed all the drivers again for all the components. If this doesn't work, I'm gonna throw this POS in the bin and go buy another system. After spending more than $4000 this is now a joke. I am quite thankful to all the updates and messages by Maurice but clearly this has to change for the better and it cant be just one person answering all the engineering questions / clarifications.
You can't see much in the video, but when the disconnect happened the Playstation popup appeared which told me the USB device is disconnected, then the menu opens by itself and the autopilot starts driving. The disconnect happened when i just looked back. But since this is a random issue, i don't know what triggered it. :/
The Base was in Playstation Mode(blue) and when the issue appeared the button shined red.
I touched another car slightly and the base disconnected. When this happened the PS5 froze completely for a few seconds(i had no moving image) and i had to restart the base. This killed this race for me....
We tried on multiple PCs here and didn't get a false notification on any. You can ignore the notification but if more people have it we still want to find out whats going wrong to find out how we can make the notifications correct for everyone.
I have the Podium Wheel system, 4 wheels, V3 Pedals, E-brake and GT7. I've been on 455 and everything seems okay except for an un-driveable Bugatti Chiron that has violent speed wobble. I've been following this thread for weeks because I am afraid to brick what I have for all the problems these new updates present.
This is not how updates are suppose to work, not at all. quite the opposite.
geez there are some people here that lack understanding of things.
I'm not sure if it will help but your play stations are barely able to run the programs that they run at the best of times. they are borderline at best
include some high graphic draw and you're going to get freezing at random times for what seems like no reason.
on the pc I go to event viewer and 99% of the time it's the amd software resetting itself because it timed out, but it shows itself as a pc or wheel freezing. have some patience. these guys cop some crap unfairly
This is good to hear. Is there a timeline for the other DD+ issues (specifically the issues with the CS UH V2)? Like the APM top paddles not working and fifth button cluster not working as well.
When entering a game menu while driving it can happen in some games that the FFB effect doesn't get canceled which results in the wheel turning to one side. (this got now fixed for the Podium DD but can still happen on the CSL DD. We will now apply the fix for the CSL DD as well)
this exact same issue can cause because sometimes your hardware sends out 2 axis message for the game
2 axis are totally different compared 1 axis, and it needs different methods for handle it, and sometimes it even hard if hardware have huge delay
@Allan Lehtla I dont know what you currently have with 2 Axis vs 1 Axis but neither the oscillations nor the wheel pulling to one side when opening a game Menu are Axis related. The oscillations are a game issue, the wheel pulling is a firmware issue where a FFB effect does not get properly canceled but stays active which will be fixed early next year with a fully rewritten CSL DD Base and Motor Firmware where the whole communication is overhauled, but as said this has nothing to do with Axis.
Comments
driver or firmware?
As already said multiple times now, the new driver available notification is a false positive. Just ignore. Will be fixed tomorrow.
We aim for a BMR Hotfix Release this year as that product is actually not in a good shape and we want to (finally) give this product some much needed love.
Nobody has the time to read through every single post on this forum. Had I not seen this post I wouldn't know you were aware of the issue as I'm having the same one in addition my DD2 will not even update the wheel base firmware. It's stuck in a loop of reconnect your wheel properly and enter bootloader mode. With the arrival of Corsair to add the leadership and customer service you clearly lacked before hopefully that extends even into this realm, the forum.
After installing driver 464 with latest Firmware 1.3.0.1 for my GT DD Pro, i had one base disconnect today during qualifying in Gran Turismo :(
The button on the base shined red. I had to restart the base to get it working again. I thought this is fixed? It was fine with the last 2 updates(i don't remember which driver had new firmware for my wheel) and now this happend.
Also the Force Feedback feels off at times. It feels like clipping - it makes a rattling noise and FFB just stops for a few seconds and then it comes back. Never had this before.
I've never seen new driver releases have so many regressions and bugs.
New drivers are supposed to be an improvement not pedal backwards.
Solution: Time to get new devs.
No.
oh my what a nightmare this DD Extreme is becoming. Had driver 462 working for the last few months without an issue. Thought finally something that was working as intended.
Then suddenly in the middle of an LFM race yesterday, the wheel decided to disconnect, I had to quit as no buttons on the wheel responded. I opened the fanatec control panel thinking something must've gone wrong. Saw new driver notification and updated to 464.
Lo and behold, again during another LFM race, the wheel disconnected again. This time, the WQR message showed FW version 0.0.0.0 and there was no wheel being detected. Full disclosure, I am using the DD Exteme + Podium Endurance Button Module + Porsche wheel + universal hub v2. Restarted the base and wheel was recognised. I thought may be it was a once off. Now scared of losing more ELO and SR, tried an offline race, yep disconnected again and same issue.
I've gone back to 462 driver and manually installed all the drivers again for all the components. If this doesn't work, I'm gonna throw this POS in the bin and go buy another system. After spending more than $4000 this is now a joke. I am quite thankful to all the updates and messages by Maurice but clearly this has to change for the better and it cant be just one person answering all the engineering questions / clarifications.
Same problem as mine as mentioned above.
Exact same as my problem, was absolutely fine before there was a "new update"... any solution?
You can't see much in the video, but when the disconnect happened the Playstation popup appeared which told me the USB device is disconnected, then the menu opens by itself and the autopilot starts driving. The disconnect happened when i just looked back. But since this is a random issue, i don't know what triggered it. :/
The Base was in Playstation Mode(blue) and when the issue appeared the button shined red.
https://youtu.be/qM3uptx313s
4 month ago, before 457 this happened:
https://www.youtube.com/watch?v=-k7UzdJ3SB8
I touched another car slightly and the base disconnected. When this happened the PS5 froze completely for a few seconds(i had no moving image) and i had to restart the base. This killed this race for me....
I didn't get a reply but is it right to say that i should just ignore the download available icon for now?
The issue should already be fixed.
im guess what you mean is, user needs close his fanatec control panel and open again, otherway he still may see that message
there is a people who run they pc 24/7
We tried on multiple PCs here and didn't get a false notification on any. You can ignore the notification but if more people have it we still want to find out whats going wrong to find out how we can make the notifications correct for everyone.
True. I would expect one to restart the app if something is weird but maybe that was not done
Please fix the firmware issue. Pedals do not save settings !!!!!!! BRF and Deadzones specifically.
CSL Elite V2 on GT DD PRO wheelbase.
I have the Podium Wheel system, 4 wheels, V3 Pedals, E-brake and GT7. I've been on 455 and everything seems okay except for an un-driveable Bugatti Chiron that has violent speed wobble. I've been following this thread for weeks because I am afraid to brick what I have for all the problems these new updates present.
This is not how updates are suppose to work, not at all. quite the opposite.
Oscillations in GT7 are game related and normal. Not much you can do.
I'm currently using version 464 of Fanatec Control panel and v2.01.54 of fanalab. You can see the firmware versions in the photo
its fixed now guys, it was a bit clunky to get it sorted which is the first time for me in 10 years but its fine now
thanks for your help
thats probably your console having a tantrum by the looks of it. it happens
geez there are some people here that lack understanding of things.
I'm not sure if it will help but your play stations are barely able to run the programs that they run at the best of times. they are borderline at best
include some high graphic draw and you're going to get freezing at random times for what seems like no reason.
on the pc I go to event viewer and 99% of the time it's the amd software resetting itself because it timed out, but it shows itself as a pc or wheel freezing. have some patience. these guys cop some crap unfairly
This is good to hear. Is there a timeline for the other DD+ issues (specifically the issues with the CS UH V2)? Like the APM top paddles not working and fifth button cluster not working as well.
to you know if hardware sends out to other hardware that it support 2 axis then game developer also try it best for make it work as 2 axis
but same-time sometimes i see that fanatec sends out that hardware have only 1 axis and that is a butter smooth with zero oscillations
the most higher part is, users dont see this kind that data by default unless if they are actually developers self
if hardware sends sometimes out 2 axis and sometimes it sends out 1 axis, i would call-it a some sort weird bug
Known Issues
this exact same issue can cause because sometimes your hardware sends out 2 axis message for the game
2 axis are totally different compared 1 axis, and it needs different methods for handle it, and sometimes it even hard if hardware have huge delay
@Allan Lehtla I dont know what you currently have with 2 Axis vs 1 Axis but neither the oscillations nor the wheel pulling to one side when opening a game Menu are Axis related. The oscillations are a game issue, the wheel pulling is a firmware issue where a FFB effect does not get properly canceled but stays active which will be fixed early next year with a fully rewritten CSL DD Base and Motor Firmware where the whole communication is overhauled, but as said this has nothing to do with Axis.
difference between 1 Axis vs 2 Axis
1 Axis can stay in same place what value you give him, while 2 Axis starts push the FFB signal to one direction ,
if signal gets lost form game then hardware push hardware FFB based to the this last info what it had, either to left side or right side
the exact same reason it also very hard control the oscillations with 2 Axis
what i not still get tho, why hardware sends out sometimes 2 Axis and sometimes 1 Axis message to the developers
fanatec need Abandon shit code driver and rewrite all hardware drivers in the new fanatec drive and fanalab two in one software
On Podium DD1 you can get around this issue by setting your base to PC COMP mode.
At least this has solved it for me