This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
The fact that the steering wheel stops responding in TDU is a fault of the last patch. Just press a button on the steering wheel and it starts working again. It also happens to people with a Moza steering wheel.
Thanks for the info.
I tried changing the game(TDUSC) options.
When using CS DD+, if I set the vibration option to 0, the disconnection issue did not occur.
When using CSL DD, if I set the vibration option to 100, the disconnection issue occurred with strong feedback such as collisions.
It seems that the allowable values for the parameters of CS DD+ are smaller than the allowable values for the parameters of CSL DD.
This may be because CS DD+ has more parameters than CSL DD.
It is common for calculations to become prone to overflow when the number of calculation parameters increases.
There are other issues with F1 2020, 2021.
When using CS DD+ (COMP V2.5 mode), the FFB was lost.
When using CSL DD (COMP V2.5 mode), there is no problem.
PC mode is unusable due to a different problem (I suspect it's a game-side problem).
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is a known F1 game issue, not Fanatec driver. F1 20, 21, 22, 23 has the bug to sometimes lose the FFB (when you open the menu or after starting the race... you have to minimize the game or press Alt+Tab or unplug/plug the usb cable to get the FFB back.). This is fixed in F1 24. PC Mode + CS DD + F1 22, 23 , 24 works fine BTW. There is no reason to use the CS V2.5 mode.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Stop your wild nonsense and plain wrong assumptions when you have no clue what you are talking about please!
Known Issues
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)
Natural friction can start to feel weird after some time of driving. In case you experience issues with NFR, we suggest to turn it OFF for now. (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)
The steering input jump issue was greatly improved so the issue happens a lot less than before. Full fix expected for one of the next versions.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
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)
Natural friction can start to feel weird after some time of driving. In case you experience issues with NFR, we suggest to turn it OFF for now. (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)
The steering input jump issue was greatly improved so the issue happens a lot less than before. Full fix expected for one of the next versions.
Tell me something new..
But these known issues have nothing to do with what you previously talked about.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is a known F1 game issue, not Fanatec driver. F1 20, 21, 22, 23 has the bug to sometimes lose the FFB (when you open the menu or after starting the race... you have to minimize the game or press Alt+Tab or unplug/plug the usb cable to get the FFB back.). This is fixed in F1 24. PC Mode + CS DD + F1 22, 23 , 24 works fine BTW. There is no reason to use the CS V2.5 mode.
Thanks for the info.
I'm not asking for the game bugs to be fixed.
When I want to drive on a course that doesn't exist now, I want to play F1 2021 etc.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
How long are you going to let this troll go on? He tries to come off as someone who just wants to help, and then comes the subtle undermining of Fanatec (sometimes not so subtle). I'm so fed up with the put downs of Fanatec; if he doesn't like Fanatec, then why is he even here
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
How long are you going to let this troll go on? He tries to come off as someone who just wants to help, and then comes the subtle undermining of Fanatec (sometimes not so subtle). I'm so fed up with the put downs of Fanatec; if he doesn't like Fanatec, then why is he even here
dude. its not like or not like, it's about tell what user thinks. so they may learn something and make themself better. if you ass lick them all the time , then nothing changes to better way
if you constantly ass lick, it may turn into a Narcissism and in end they not care anything anymore expect themself
i not know about you, but i want that Fanatec would be best company in market, as i invested money for they product
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Why there's always non-stop whining and assumptions out of nowhere in these driver feedback threads...
I agree 457 was a mess and vent a bit back then. But honestly there's no need to constantly direct the thread to a wrong track. Just share your workaround or feedback here and let go of your anger somewhere else, perhaps General Discussion, not in this thread.
Here I just want to see if there's any glitch in 462 before I upgrade. So please, stay on the topic.
I would sincerely like to go back to topics related to the FREAKING Driver 462. Its been a while since we had a new driver release, so we should all focus on the issues/glitches related with this driver exclusively and no other banter , arguments of any sort. Please.
I have been rock solid with driver 455 since day one with my CS DD+ playing GT7 on my PS5. No FFb or any issues. As a matter of fact, things are so solid that i didnt even bother upgrading to 456 or 457. Is anyone using 462 having any issues with GT7+ PS5 like FFB drop or Freeze?
Any information would be helpful.
Thank you and please dont feel compulsory to respond unless you have any actual information, you know who you are.
Glad fanatec is making progress with their drivers. Keep up the work.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Why there's always non-stop whining and assumptions out of nowhere in these driver feedback threads...
I agree 457 was a mess and vent a bit back then. But honestly there's no need to constantly direct the thread to a wrong track. Just share your workaround or feedback here and let go of your anger somewhere else, perhaps General Discussion, not in this thread.
Here I just want to see if there's any glitch in 462 before I upgrade. So please, stay on the topic.
what glitch you searching exactly? they mostly focused for disconnect issues
as far i understand they released those beta firmware what they been testing in one package.
best would be if you try out, and then tell if you find any. its 462 after all. they been make some changes
Comments
People should think more before they post something on the forum!🤦♂️
some companys todo this shit kind stuff for purpose. for make hardware lifetime shorter so users are forced buy new hardware
i not say that fanatec todo that. it's just i seen too may stuff in my lifetime
With your nonsense assumption you implied that Fanatec could even consider such a bullshit. Just stop it man.
then don't make this kind bugs what start look like scam
we would not talked this if you already would fixed that.
its not a new bug, its been here sometime now
Thanks for the info.
I tried changing the game(TDUSC) options.
When using CS DD+, if I set the vibration option to 0, the disconnection issue did not occur.
When using CSL DD, if I set the vibration option to 100, the disconnection issue occurred with strong feedback such as collisions.
It seems that the allowable values for the parameters of CS DD+ are smaller than the allowable values for the parameters of CSL DD.
This may be because CS DD+ has more parameters than CSL DD.
It is common for calculations to become prone to overflow when the number of calculation parameters increases.
There are other issues with F1 2020, 2021.
When using CS DD+ (COMP V2.5 mode), the FFB was lost.
When using CSL DD (COMP V2.5 mode), there is no problem.
PC mode is unusable due to a different problem (I suspect it's a game-side problem).
you need keep in mind that you sell hardware and not software, it not make it look very good with this constant bugs
@Mizuki Yoshizawa
This is a known F1 game issue, not Fanatec driver. F1 20, 21, 22, 23 has the bug to sometimes lose the FFB (when you open the menu or after starting the race... you have to minimize the game or press Alt+Tab or unplug/plug the usb cable to get the FFB back.). This is fixed in F1 24. PC Mode + CS DD + F1 22, 23 , 24 works fine BTW. There is no reason to use the CS V2.5 mode.
Gökhan Ogul
maybe, or maybe its a know bug that fanatec driver may not handle very well the DISCL_FOREGROUND
ok, had to say im not really fan for codemaster stuff, but i to know that fanatec have some issues in they own stuff
Stop your wild nonsense and plain wrong assumptions when you have no clue what you are talking about please!
Known Issues
Tell me something new..
But these known issues have nothing to do with what you previously talked about.
one issue can trigger multi issues, if fix one others may to leave behind as well
What?
Thanks for the info.
I'm not asking for the game bugs to be fixed.
When I want to drive on a course that doesn't exist now, I want to play F1 2021 etc.
So, I want CS DD+ to work like CSL DD.
there no point talk for you about this, you already previously tell that you are not developer
so we to may miss talk each other
@ Maurice
How long are you going to let this troll go on? He tries to come off as someone who just wants to help, and then comes the subtle undermining of Fanatec (sometimes not so subtle). I'm so fed up with the put downs of Fanatec; if he doesn't like Fanatec, then why is he even here
dude. its not like or not like, it's about tell what user thinks. so they may learn something and make themself better. if you ass lick them all the time , then nothing changes to better way
if you constantly ass lick, it may turn into a Narcissism and in end they not care anything anymore expect themself
i not know about you, but i want that Fanatec would be best company in market, as i invested money for they product
Maurice, for the overall good of the Forums, it's time for a complete ban.
you are maybe long time customer? Fanatec needs a new customers as well . as they are the ones who may bring more money.
but if products have problems they self may scare them off
sean pirtle
Don Collins
new users not see same way like you see.
they see that product not working and they just may go other way.
so software bug fixes are very important for a hardware what they sell.
Save it, cause I ain't buying. All you do is put fear into users, and drive them away.
save it self, if you been read this forum then you seen what been happening with the products for new customers
you are maybe happy Fanatec Forza Motorsport CSR steering wheel customer, who knows really
if you product works then what you scare anyway?
Maurice - 11 off topic posts on this page alone.
No offending each other!
sean, what i todo for you anyway?
i mean really if you start talk about some other user, you not expect any answer back?
Maurice - 12 off topic posts on this page alone.
462 is working fine for me, no FFB dropouts in over 6+ hours of racing.
we all know already that 462 works most off users, but it happens there are still some bugs what may need fixed
your info is not very informative tho, because fanatec have allot products
smh
Why there's always non-stop whining and assumptions out of nowhere in these driver feedback threads...
I agree 457 was a mess and vent a bit back then. But honestly there's no need to constantly direct the thread to a wrong track. Just share your workaround or feedback here and let go of your anger somewhere else, perhaps General Discussion, not in this thread.
Here I just want to see if there's any glitch in 462 before I upgrade. So please, stay on the topic.
I would sincerely like to go back to topics related to the FREAKING Driver 462. Its been a while since we had a new driver release, so we should all focus on the issues/glitches related with this driver exclusively and no other banter , arguments of any sort. Please.
I have been rock solid with driver 455 since day one with my CS DD+ playing GT7 on my PS5. No FFb or any issues. As a matter of fact, things are so solid that i didnt even bother upgrading to 456 or 457. Is anyone using 462 having any issues with GT7+ PS5 like FFB drop or Freeze?
Any information would be helpful.
Thank you and please dont feel compulsory to respond unless you have any actual information, you know who you are.
Glad fanatec is making progress with their drivers. Keep up the work.
what glitch you searching exactly? they mostly focused for disconnect issues
as far i understand they released those beta firmware what they been testing in one package.
best would be if you try out, and then tell if you find any. its 462 after all. they been make some changes