When driving the Class 101 on the PS5, something has happened to the D-pad sensitivity as even a gentle press on this to change gears sends it flying from 1st gear straight through 2, 3 and 4 to neutral. This was not an issue on TSW5 on the PS5.
Hi, sorry about this issue popping up in TSW6, could you send it over to Submit a request – SUPPORT CENTER so the team can look into it? Thanks.
I’ve tried it Vern and it’s just the odd mapping due to the reverser and gears being on the same buttons. Neutral is with the control in the cab towards you but first gear is with the the control furthest away so when you go from neutral to first gear the control in the cab whips all the way to the top of its travel. You have to press the button for each gear change as well, so the sensitivity can’t change. It’s behaving the same way it always has, at least as it always has since the immersion control scheme was introduced in TSW2.
I think you’ve misunderstood. It’s working correctly. Sensitivity doesn’t enter into it as each gear change requires a separate press of the button. It can only move by one gear at a time. It’s exactly how it was in TSW5. The movement you are seeing when it quickly goes from one end of the control’s travel to the other in the cab when you press the d-pad once is just it going from neutral to 1st gear because they are at opposite ends on the control lever in the cab, and not it going through all the gears in one shot due to a sensitivity issue. One more press of the d-pad and you’ll see it come back towards you into 2nd gear. Neutral is with the lever towards you and first gear is with it furthest away.
No I haven’t misunderstood, one press ran through the entire gear range from 1 to Neutral. Anyhow logged with Support so will see what they have to say.
It does travel all the way round when going from Neutral to 1st but that’s how it’s mapped to the controller and every subsequent gear change then requires a separate press on the d-pad, which is why I’m saying controller sensitivity can’t come into it. You have misunderstood the controller mapping, that’s all. Support will tell you it’s working as intended. I’m trying to explain why that is.