You mean “Bethesda to this day?”
It’s in Unity, isn’t it? So rather than multiplying the speeds by Time.deltaTime when you’re doing frame updates, you just don’t do that. Easy peasy. They’ve got that real “Japanese game devs from twenty years ago” vibe going.
bigmclargehuge@lemmy.world 3 months ago
ms_lane@lemmy.world 3 months ago
They fixed that with 76, Both 76 and Starfield have physics untied from framerate.
bigmclargehuge@lemmy.world 3 months ago
Thats great to hear. Not surprised about Starfield tbh, but I am surprised they fixed it for F76, considering it relies largely on the same tech as F4, which does have that limitation.
Zoboomafoo@slrpnk.net 3 months ago
Or even a decade ago. Dark Souls 2 had some enemies’ attack animations tied to frame rate, like the Alonne Knights. So they attacked incredibly fast on PC compared to console.
Weapon degradation was also tied to framerate :(
xavier666@lemm.ee 3 months ago
Minecraft has this wonderful mechanism where everything is dependent on game-tick/server-tick, which is independent of player FPS. Why do modern developers keep using FPS for game physics?
Baleine@jlai.lu 3 months ago
Minecraft is different because it uses a client and server pattern, separating the physics and display loops completely
Annoyed_Crabby@monyet.cc 3 months ago
Huh, now i know why that particular enemy are janky as heck in every aspect.
Cornelius_Wangenheim@lemmy.world 3 months ago
At least Gearbox isn’t spending a year+ denying that the problem exists.