Hello. Let me introduce myself. I am the developer of the Bash pro Active H-shifter. I have been playing and testing hardware with AMS2 a lot, since the game was released. I have seen a lot of changes and improvements in the game overall, which I'm very happy for. However, since the v1.5 update, something with H-pattern gearbox physics went terribly wrong. I can't tell exactly when, I skipped almost a year playing AMS2, after the Bash pro went into production. I remember having a blast with the BMW E30 group A with a dogbox H-pattern, rev matching, shifing with and without clutch. But now, shifting times have become unbearably, game breakingly slow. No other game exaggerates "mechanical shifting" delay this much. Especially with cars that are meant for the race track. I have a video for reference, from AMS2 v1.4.xx times, before this break in the gameplay flow happened. I really hope this will be addressed. Thank you for hearing me out.
I checked every possible setting, tried most combinations on and off. I'm familiar with AMS2 options menu. I will make a comparison video side by side with the old and new physics. I can't comprehend how this design choice to make shifting so slow, was intentional. Unless there is something I'm totally overlooking.
I just drove the BMW M3 E30 Group A at Hockenheim with manual h-pattern transmission and there was no issue shifting without clutch - besides shifting from 1st to 2nd gear. If you do this you have to be very careful and patient. Other than that there is no delay. You should post a video where we can see your ingame inputs. In your video above we can't see them because of the overlayind pedal cam.
This is just a stab in the dark, but could the "minimum shift delay" setting be to blame? I'm not sure if it even works for H-pattern controls, but it does set a minimum time between shifts for sequentials, at least. I'd imagine if that was set to the maximum (1 second or more I believe?) it could potentially prevent the next gear change to even register before that minimum amount of time has passed. Anyway, I hope it works out! Been looking at the BASH pro ever since I first heard of it. Definitely hope to get one once I can afford an upgrade to my gear (but preferably I'd like to be able to afford my rent first, haha).
Thanks for the tip with the "minimum shift time" setting. I'll have to check it out when I get home. I never realized there was a setting like this. I hope it's as simple as that. Could it be something for debouncing sequential gear switches, to avoid double shifting? It just messes with H-pattern. That could be an explanation.
Yup, that's what it's meant for. Can be pretty useful in some cases, such as my ancient G25 shifter. Works fine in H-pattern, but when I switch to sequential mode just looking at it can result in an accidental upshift (or two), so this definitely comes in handy in that case. Like I said, I am not 100 percent sure it affects H-pattern inputs, but it if does, that could certainly explain quick shifts not being recognized until well after the fact.
Okay, I checked the "minimum shift time" setting at home. I had it set to 50. That pretty much solves the case. I must have changed it when I played more with paddle shifters. In every game I have known so far, AC, rF2, LFS, this setting was always measured in milliseconds. In AMS2, the setting of 50 means 500ms. That is exactly how slow shifting was to me. Thanks for clearing this up. I will update the BASH pro user manual, to let people know this setting must be set to 0 when using the H-shifter.
Your explanation should be in the game. It's very helpful. In my options "minimum shift time" was/is set to 0. That is the reason why I had/have no issues I guess.
