The following issues have been addressed:
- With certain cars, the [Force Feedback Max. Torque] value found in the [Steering Characteristics] page within the [Steering Controller] category of the [Options] screen in the [MENU] (accessible by pressing the START button) was not working as intended.
So is it back to normal for g25/g27?Hotfix just released:
all good now bud they fixed it, feel free to downloadI will not download this update until they fix this problem.
Hotfix just released:
I wonder what factors caused the bug to hit. I mean clearly in this thread we saw some (mostly G25) users were hit by it but seemingly not others....Hotfix just released:
Hotfix just released:
ThanksIts not as strong as before the update but it certainly feels heavier on the wheel now!
I can confirm it's heavier. Not quite as heavy as pre 1.12, but you can feel the resistance. I'd say 10 is equivalent to 5 pre-update now. Epic turnaround time on PD's part 👍👍👍 If this is Codemasters we'll be waiting a month for the patch
I've also finished testing controller sensitivity and wheel rotation:
Controller sensitivity doesn't do much. There's a little change but it's not meaningful. Best to leave it at zero to keep the steering ratio 1:1.
Wheel rotation makes the most impact. 670 or 450 degree seems the way to go now. 240 is too twitchy.
Adding camber also helps increase the "feel" when loading the wheel through long turns.
**IN SUMMARY**
For Logitech wheels, to increase resistance as much as possible:
- Set Max Torque & Feedback Sensitivity to 10
- Set Rotation to 670 or 450 (depending how twitchy you like your inputs) (see here if you don't know how: https://www.gtplanet.net/forum/threads/g27-g25-dfgt-undocumented-wheel-lock-settings-guide.286646/)
- Leave Controller Sensitivity at 0
- Try increasing your car's Camber settings
It's not as it was before, but at least it's drivable now. Hopefully PD will refine things again over future patches 👍
Looking forward to trying this update. Please check me on this, but I think the 'Controller Sensitivity' setting applies only to the DS3 per the in-game setting description.
And it's back to dead FFB.Heavier?yes,lively and intuitive?no.
Looking forward to trying this update. Please check me on this, but I think the 'Controller Sensitivity' setting applies only to the DS3 per the in-game setting description.
And it's back to dead FFB.Heavier?yes,lively and intuitive?no.
Either way, I think I caught more potential spins on Sierra in one day than in months of previous play.
Such a relief that the horrible, weightless feeling in our wheels was unintentional and that PD jumped on it so quickly. I hope other Fanatec users can report on this quick update, because I'm anxious to play again when I get the chance.
they fixed it? 👍👍👍👍👍 please someone gimme some setting to try later on at home for the DFGT i was driging at 5/
IMO that was one of the worst things about the new FFB, it was way too easy to catch/correct mistakes. It should take some skill to save a spin, not just a simple correction. Sure, this makes it more fun for people with lesser skill, but it dampens the fun for skilled players.
Also, I was driving a couple FF's yesterday and noticed that I could steer out of my understeer, meaning that when the car started to understeer I could just turn the wheel more and instead of getting more understeer I got more grip. That's not right. Hopefully the ninja addressed this to some extent.
IMO FF's are messed up from corner entry to exit. The only place they are accurate is in a straight line. Driving them just seems too arcade and I don't enjoy that feeling so I put them in the back of my garage for the most part although in a moment of weakness I did try to tune a couple of them for my garage early on in the game. When you drive the Abarth in AC, you'll see just how fun FF's can be.Also, I was driving a couple FF's yesterday and noticed that I could steer out of my understeer, meaning that when the car started to understeer I could just turn the wheel more and instead of getting more understeer I got more grip. That's not right. Hopefully the ninja addressed this to some extent.