i feel i need to clarify something. Generally speaking I get around 60-80fps in TOW at 1080p, mainly because I cap it at 80fps which is my display's max refresh rate (i use vsync, need that smoothness).
Ok, so if the game does 60-80fps, and it only drops to low 60s when it is in a heavy area, it stands to reason that if I were to suddenly cap the framerate to 30 it should then never, ever dip below 30... right? Because even in a heavy area it was doing low 60fps, so capping it to 30 should mean that it will always then remain at 30fps.
...Except the game doesn't. When running around it will sometimes drop 1 or 2 frames, dipping from 30fps to 28 or 27. THAT is what I mean by frame-drops. It should never drop frames when it's already in a performant state, in my example under the 30fps cap. If a game does something like this then it means it's dropping frames and it's not related to the actual performance, since the frame rate is already so low that it would never reach that frame bottom.
That's how you know a game has bad frame-pacing. Normal, well-performing games, don't behave like this: a normal well-performing game, which averages 60-80fps, if capped to 30 would then never, ever dip a single frame below 30.
That's what I mean by frame-pacing, or by "frame drops". The fact that a game fluctuates between it's normal frame averages, in my case between 60-80, is NOT considered "Frame dropping". that's just normal operation.
People aren't looking for this and rarely notice it.