Issue still not fixed, I tried it early this morning and the same over-sensitivity of the DS4 when you lose traction is still there. Why doesn't PD even test that at all. The DS4 is fine until you break traction then the sensitivity goes way up to where you can go from neutral to lock way too fast it feels almost like you lost power steering and the wheels get thrown to whatever direction you turned to first. The increase in speed may mitigate some of the issue like I tried before the patch and in the Demo but high speed drifting will still plant you in a wall due to lack of correctness in steering. Something is causing a change in DS4 sensitivity whenever traction is broken and that is what PD needs to fix. Where do I go to complain and describe this to them, since they obviously didn't check the Beta forum post. The onscreen read out of wheel position is still out of calibration with range of analog stick movement. This is still a temporary fix and a band-aid in my eyes. I need specific instructions on where to post this bug for PD to actually look at the problem plaguing DS4 inputs under specific circumstances. Heck when you do flat out hard launches you get the same problem and worse with the speed of steering causing more harm than good IMHO.
@Lord Protector, What you're experiencing as lag is actually your steering input being read too acute. If you check replays of any of your drifts when you start to drift use the in car view and watch to see when the avatar goes to lock. When the avatar goes to lock the wheels of the car do immediately end up at lock but it is traveling towards that, which means the game has already decided more steering angle than you actually wanted, which turns into the absurd snapping from one direction to the next as you battle to counter steer your way out of this. It's not actually lag but the game still correctly moves the steering through it's course but if your DS4 is being read too close to it's movement then it's getting too much input. How can light taps to lock on the analog stick register as full lock in the wheel, that shouldn't be happening and what seems to be happening in direct relation to drift is fighting the forces applied by traction of the steering wheels(that bite). The bite is a normal result of what is going on with lateral forces applied to the tires, problem is all our inputs are read incorrectly(way too close to 1:1) leading to more input transmitted to the steering wheels of the car. This explains starting a drift and then the moment you steer into the drift the car literally wants to go where the wheels are turned i.e right turn drift, the car steering is a bit left(DS4 will probably reach lock and you steer left completely off the road). Should not be reaching lock, the DS4 should not be registering lock in the first place. PD has always had this down, it works that way at a standstill you have to hold the analog in lock for the wheel to actually steer there and if you let go while it's still on it's way it will register that you canceled lock respond accordingly. So why in the world is it not responding correctly when you drift?
Feels like FFB you experience with a wheel may be bleeding into DS4 control mapping(when traction is broken) or my original idea that we are getting oversensitive steering input reads when we break traction. Those are the only two things I can think of to explain the insane way the steering goes nuts under traction loss.
thanks
I am very eager to try it after work
I've seen more smoke come off my last cigarette.
