Nope, has nothing to do with recommended FFB settings.
Difference in FFB Feeling is purely because PC uses a different FFB code compared to console.
And the "new" FFB code is worse than the old one, no setting can make it as good as the old code.
One more update: i reseated the metal collar and i removed the wheel from my metal rig to check if improper grounding was the problem. it did not work. i see some people went through the same issue here, but no one replied as to what fixed it.
I totally agree ACC's FFB is now much worse. I don't understand how Kunos how he can do that and not fix it and go back. There is nothing wrong with going back. Maybe Fanatec would have to put some pressure here hahahaha!!! :)
Hey just wanted to inform, that Fanatec confirmed that they working on a fix for this.
Interesting, I find that the new physics and FFB is better than old but you have checked the FFB on code level?
So I took the compatibility mode yesterday and must say that here the FFB is crisper and comes closer to the old.
Although I can't say for sure that there haven't been changes to the way the FFB is derived from the physics in the latest ACC release, what I can say is that in a properly physics-based FFB system any changes to the physics itself may be felt through the FFB. "Worse" FFB may well be the side-effect of actual improvements in physics. In this case they naturally won't "go back" to the old physics.
The physics changes and FFB changes which both came with newest ACC update are unrelated.
In theory they can switch back to the old FFB with the new Physics just fine.
Ok, I suppose you know better :)
Not completely driver-related, but I have an interesting problem. I am myself a hobbyist sim developer, have a CSL DD and recently bought a new desktop PC. My previous computer that I also use for development is a gamer laptop (6 yrs old, but doing relatively well).
Now the issue: all sims I tried (iRacing, rFactor2, Raceroom) seem to have the same FFB on both computers, except for my own sim. I use the same Fanatec drivers, same binary build of my program and naturally, the same Fanatec hardware and profile; but while the FFB is smooth as it should be on my laptop, it is very rattly and grainy on the new computer. I'm pretty baffled by this, especially since it's my own sim where the FFB is "acting up". Even though the new computer is much faster, the controller input polling and FFB output rate are fixed, so frequency should not affect things.
Since it's my program, I will eventually get round to logging the input and FFB output values and timing, but even until then I wanted to note this strange behavior.
In the FAQ it is stated that you should use the directinput API to communicate with the controller, which I do. I don't know if there is any support that I can get from Fanatec as a hobbyist developer, so I wrote this note in the driver forum :)
I have been saying this since 1.8.12. Earlier it was same.
Can you tell me your settings in Base and ACC. Was really surprised how different the FFB is in Komp mode, as if the DD 8Nm was not yet properly implemented in ACC, because otherwise the FFB should be the same.
Crap forum software deleted my comment after edit on phone.
Other setup for Honda, Porsche:
Remember in car FFB scaling.
when this update arrives in short ????
Still no exact ETA but "very soon".
It's a matter of days, max. a few weeks but I more think days.
Great! Does it change the feel a lot or...? Can one wish updated ACC recommended settings also.
FFB is a subjective matter and usually no one likes the same settings, but still, using so much ACC damper together with NDP and FFB will easly lose detail.
Try with ACC damper 0 or, if some damper applied do not go above 10%, use NDP 15 and check if you find FFB more detailed that way.
I ran this through my Fanatec translator and got a date of August 12th?
can someone HELP
gone to update my wheelbase(poduim dd1 ps4) to this firmware and its totally stopped responding the base just turns on for a few seconds and then seems to shut down
on the control panel its not connecting no more
I think your translator is broken...
I ordered a M4 wheel day one at 6:46am Pacific time, was promised june, now it's supposed to be september, we'll see.
I ordered DD1 that was suppose to show up in december 2018, I got it in April 2019. Not to mention they first showed it in 2017.
The QR2 was suppose to ship with the M4 GT3 wheel, now it's soon after.
This company has an incredibly poor track record of delivery. I'm sure the driver probably will show up before august, but it's almost june and all it takes is one last minute bug to slip software by 2-3 weeks. I wouldn't be surprised at all with a july delivery.
I am not yet on this current driver. Should I update to this before the next major update or should I wait for the next driver update?
I would wait.
I have tried everything to get my base back up and running with no luck
I've researched this error through the forum so looks like my base is a £1600 door stopper for now
it's worked perfectly until this update what an complete joke
Looks like the base is bricked as WQR failures cant be fixed by the customer.
You need to contact the support to start the RMA process.
Fixed it mate if anyone needs help with error just give us a message
massive money making spin if Fanatec have include this to create issues and work load
Would you care to share how you resolved the issue on your own? I'm sure it would help others in a similar situation.