Hi there! I think there's a problem with AMS2's pedal deadzone, in which it not only wrong cuts the bottom range/deadzone (to a value lower than expected), but it also cuts the top range as well, which shouldn't happen. I made this quick graph showing what happens on my pedals: I'm currently running Linux, but this happens on Windows 11 + GHUB as well, so it's not OS-specific. I also made a video showing the problem here in case you'd like to see it:
even if there was a odd compression happening at these extreme values , i don’t see an issue as why would anyone need more than 10% Dead zone unless they have a significant issue with their hardware .
Maybe for Pro-grade hardware, but for regular run-of-the-mil G29 there's a rubber stopped that starts engaging at about 50-55%, before that I have zero feeling on the pedal and it's extremely light. And when the rubber starts engaging you can think of it as if it's the brake pads biting on the disks, so that's the sort of behavior I'm mostly used to.
Oh…. G29 pedals… Clean your potentiometer and google squash ball pedal mod . I’m only guessing, but with that much deadzone, and the resulting lack of travel of pedal sensor , it might be that the game is only seeing a roughly 50% brake and not able to go to 100% when calibration occurs. ( but in the video, you never re-calibrate ? ) But theoretically it should be that that peak of roughly 70% is converted to full pressure in car .
I think it could be that this is how the Madness Engine works. But for essentially all other sims I calibrate first (which is showing the game what my full range is) and then I set my deadzone based off of that. So in no other game I play do I need to recalibrate after setting a deadzone. But I'll try that in a bit and report back.
