Bikini Bottom Twitter
Ahoy, me buckos! Welcome to Bikini Bottom Twitter! Your digital reef for the latest salty gossip and treasure tales! And while you're at it, be sure to drop by the Krusty Krab for a delicious Krabby Patty so I can get yer mon- err I mean, 'cause they're the best treat under the sea!
Rule 1 - This is Bikini Bottom Twitter, all posts should be Spongebob related in "(Old-School) Twitter-like" form
Rule 2 - Political posts, as long as it follows rule 1, will be permitted, so long as you behave yourselves.
Bikini Bottom Municipal Code §33-07: Anti-Tankie Ordinance Residents are prohibited from circulating tankie ideology or other authoritarian propaganda on Bikini Bottom Twitter. Offenders will be permanently banned from BPT by the BBPD faster than Plankton is ejected from The Krusty Krab.
Rule 3 - Please no reposts within the last couple days, at least
Rule 4 - All posts should be at least above a "Squirdward-krusty-krab-shift" level of effort
Rule 5 - Be chill, be a Patrick not a squidward.
view the rest of the comments
60 FPS was fine 15-20 years ago. These days I need my games to run at 120 FPS+. 60 looks like a slide show and you can really feel the input lag when you move your mouse at that framerate.
Input lag is not in any way related to frame rate. Fix your keyboard or use a faster game engine or whatever.
Input lag is massively affected by framerate and it's easy to prove. Go into your PCs display settings and lower your desktop's refresh rate as low as it'll go (30Hz or lower). Then move your mouse around on the desktop and you'll understand exactly what I'm talking about.
Think about if for a minute: let's say you click your mouse in between frames. That click isn't going to register until the next full frame. The lower your framerate, the more likely this will happen, leading to more input lag. This is so obvious once you spend 15 seconds to actually think about it, that I can't believe I even have to explain it to you.
Since when are mouse inputs tied to individual frames?
Neither to action you perform nor the reaction from the Programm should be delayed, only the visual feedback you get.
Sure some older Programms don't use internal ticks bit instead use the framerate for that, which leads to a lot of issues with higher framerates as well, but they are few and far between.
Input in many games are tied to frames, and this isn't necessarily a bad thing. Sure, you could poll for inputs faster, but you have to pick some rate, and framerate is a reasonable one. It certainly shouldn't be slower, and faster isn't really useful because the player can only respond at framerate speed. Faster just creates more processing that needs to be done without much gain. Sometimes there's interpolation to figure out what they would have clicked on/shot at at a sub-frame timing though, to make fast actions accurate, without a ton of extra processing.
Physics is almost always not tied to framerate, because the player response isn't what matters usually.
Regardless, a longer time to see the response is equivalent to response time.