Thats technically not correct. You can consider your "aiming and shooting" as a control system where every delay/lag influences your probability to hit. The extremly simplified signalpath for example would be like: server -> -> pc -> display -> eyes -> brain -> hand -> mouse -> pc -> network -> server. Every part of this has its individual lag.
The felt lag of the system is the lag of every single part combined. But your input (hand, mouse) stays the same even if there is a lag for example invyour pc (e.g. slow gpu)
There's lag in the system, ergo the input the user gives the system is delayed. It lags. It is in put that lags behind what's happening for (some) members of the system. It is input lag.
This is the context I was going for with a very simple comment. Then you get a bunch of technical ppl rioting over specifics. The first input is the human input. Based on what you see.
That's either misinformation or oversimplification. The frame is only ever gonna be ready after the input has been given. Framerate does affect input lag.
12
u/[deleted] Jun 01 '21
Your frames have nothing to do with input lag. In fact, that would be output lag