Hephaestos said: Lag is a term that console players do not understand....200ms is very large.... it makes competitive play barely playable.
Now if you have a 200ms lag just from the controls, you're gonna be at 300+ when playing online? that just suxs... |
Well, 4-5 frames at 30fps mean 133-166ms of rendering lag really.
I'm a PC gamer and I code for a living (though admittedly not games) so I think I can add something about that. The "lag" you see when trying to find a server to play online is the netcode lag (let's say it is 30-100 ms). The rendering lag and the netcode lag will not simply add up, it depends on how the game is coded because when I pull the trigger the action doesnt need to wait for the rendering to be over before it's sent to the server. That's why netcode is always asynchronous and uses predictive code for trajectories that are then adjusted.
@NJ5
Again, network lag and control responsiveness are two very different beasts. And you might not "see the reason", but if most console fps games have a control response time of more than 100ms, the devs must have chosen their performance tradeoffs with good reasons, given the limitations they had to work with.