With some USB issues there is a disconnection sound but not always.
If I understand correctly you've downgraded the firmware and turned off power savings at the same time so there is a chance that the power saving was at least part of the solution. You could try again with the new firmware while keeping the power saving settings off, if the issues happen again then it's due to the firmware, if not then it was because of the power saving.
Having a direct connection to the motherboard is good, the only thing which could still play a roll if too many other things are connected to the same controller (USB2.0/USB3.0), sometimes its worth to try a different kind of port.
USB issues can be really difficult and weird. I'm currently also fighting some at home because my USB sound card and wireless keyboard have connection issues, first I thought a BIOS update would help because AMD chips had some USB issues with earlier BIOS, then later I found out that some settings like PCIE speed and Global-C State can have an impact. I think the second helped for a while but now they are back, super weird. I remember suggesting someone here on the form to also try these settings but for him they didn't have an impact, but it also was a different kind of issue regarding noisy FFB with some USB ports.
You are playing FM7 on PC, Xbox One or Xbox Series?
Which products are your using?
The rest was working fine and only the FFB did not work?
Did you test it also in another game?
Was the FFB working when pressing the test button in the driver?
Normally nothing should have changed regarding this and when I tested FM7 lately it worked fine. But if I know what setup you have I can give it another try.
Thank you for having an open mind. This is the Fanatec way and not presuming something.
Compatibility mode Csl DD, second batch. Driver newest 447
Ffb 100, peak, NDP off, nfr off, nin, off, int 1, fei 100, for 100, spr 100, dpr 40-50
Gain 90, Damper 20, Dyn. Damping 100
I adjust per car with keys the FFB and it is around 90-95. On McLaren it is 92.
Thanks the FFB has been getting just better with rewrites! I would like to get more road detail out of the base and if I go to int 0 there is but way too much noise and with 1 a lot is drowned
Thanks for the videos and log files, we will have a look what might be going wrong.
I was also in situations when 0 was to grainy but 1 was to much and wanted to try 0.5 for example, but i mostly use 2.
Have you tried to use normal PC mode instead of Compatibility Mode? Some games handle bases differently and in compatibility mode the game will see it as a CSW V2.5. ACC works fine with PC mode and comp mode is not need.
I would suggest to disable the ingame Damper which you have at 20 and instead use NDP if you want some additional damping. The Dynamic Damper you can keep, that one is great, but from my testing NDP works better than the in-game (static) Damper setting which feels more harsh and more like friction, could also be that this kills some of the detail because of that.
Something came to my mind, I think the boot up procedure and FFB not working are related.
Something you can try:
On the base side there should not be a functional difference between both modes because all that changes is the ID and name of the USB device. Then it could be that the game is handling both different and whatever they do with the CSW V2.5 different you seem to like more.
I wrote a most detailed answer but edit lost the text. Well short version for me the Comp mode feels much better. Might be how ACC emulates CSW or something. NDP feels weird and is there lag or something because I can’t catch slides as easy.
Ok, I try to ask Kunos if there is software side something. Strange then anyway if you are certain that they are the same. Should try Wheelcheck but can’t be bothered.
Tried NDP again and it is ok. Takes away directness but maybe gives forgiveness to the inputs.
Can the next firmware of cls dd pro solve this problem?
One of the next Firmwares, yes.
Hi, have a DD1 and BME, upgraded to 447 (direct from 439). Now Fanalab tuning menu doesn't match with DD1/BME. SEN on BME sais 2450, Fanalab 1180. FFS on wheel PEAK in Fanalab LINEAR and so on.
Any suggsetions what might be wrong?
Suggestion is to update your FanaLab to version 1.66 if not already done. Usually such issues only occur when you use an old FanaLab Version which is not compatible with the new driver...
Thanks, just found 1.66 and looks like it solved it.
or with the latest driver 447
does the mobile app also work?
Can it be solved by firmware, or can the problem of hardware be solved by the motor firmware?
So I decided to update to driver 445 (because the risk was "minimal" and the new driver would " MASSIVELY improve the FFB" after the automatic firmware update i immediately got the "update mode: wireless quick release" error. after all the trouble shooting, repairing, reverting , restaring, rebooting, reloading and a whole night wasted i made a support ticket. so now i'm blogging again instead of gaming.
Needless to say I can't tell you how sorry i am right now.
"Sleeping" hardware issue my ass, I'm not an electrical engineer and I understand this is a very complicated electro-mechanical device, but if it works good for a month and then the second you update, it bricks up, this is most likely a software issue. I was a mechanical design engineer for a german electronic automotive supplier and I know the software and hardware engineers are always pointing the fingers at each other. I bet 10 to 1 it was a software engineer that calls it a "sleeping" hardware issue.
Thanks alot Fanatec
No, the grainy issue can not be fixed via Firmware.
Unfortunately the issue still persist, it had happened twice since the firmware was downgraded to 439 and USB power saving disabled. The motherboard I am using is a ASUS Z690 TUF, it only comes with USB 3.2 ports. I have just attempted your suggestion of removing and reattaching the shaft, going to monitor this over the next few days and see how it goes.
Yes NDP hinders movement a bit but so does the new Damper setting of ACC. Of course also depeonds on how high you use each of both.
i´ve updated yesterday from 443 to 447 - and it works fine.
today i have the problem that the SEN setting "Auto" does not work in rFactor2 anymore. If i set it manualy to e.g. 450 it works, but on "Auto" i have always 1440 degrees and a very slow reaction inside the game.
I´ve reinstalled the driver and set up the controller config new - no changes. Tried some car and track combinations - everytime the same.
No changes in the driver ui or fanalab profiles from yesterday to today...
CSL DD + Formula V2.5x
rFactor 2 - latest public build (1130)
SEN AUTO is currently bugged. It is recommended to NOT use AUTO atm until the issue is fixed.
thx Maurice - then i go back to 443 and waiting for an update :-)
Have a nice weekend.
It should also be bugged in 443.
yeah, i´ve seen it... :-(
can you say how much time will go on to fix it?
No ETA yet.
Missed this in the known issues.
Is that affecting PS5/consoles as well using the DD pro or is that just in the windows driver?