Input Lag Being Ignored - Learn From Your Competitors

[ThorCoolguy]

A couple weeks from release now and the tone from iniBuilds continues to be that input lag doesn't exist and the flight model is perfect.

 

The flight model may or may not be great; I can't tell, because I'm still getting a delay of 1/2-1 second between stick deflection and aileron response. Yes yes yes, I know, it's a big aircraft, I get how physics works. There is a delay between a roll command and the *start* of aileron movement. That has nothing to do with the mass of the aircraft or even its roll rate or sensitivity. It's a bug.

 

So far the response from iniBuilds has been some variant of "git gud" - the plane is sensitive, you just don't know what you're doing. That's very frustrating.

 

Just to light a bit of a fire, it's worth noting that one of your competitors had a similar issue with input lag. They not only took it seriously (and fixed it), they wrote this about the problem:

 

"A while ago some of our customers complained about input lag and sent in some tickets. We did a first round investigation and observed a measurable lag between a control input and the sidestick animation - but seeing as the animation is not tied to the flight controls, it wasn't a concern. The tickets did not, however, stop - and so we took it to the second round where we started building in some diagnostics and trying to figure out what was going on. And boy, did we find out. For a not insignificant number of users, we found the time it took for the aircraft to calculate and translate control values could be as much as 300 ms. Whilst this didn't affect everyone, it was unacceptable."

 

Please start taking the input lag problem seriously. It's real.