this post was submitted on 31 Aug 2023
580 points (98.7% liked)
Games
31990 readers
1 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And here I thought that tying game speed to CPU speed was a concept that died in the early 90s...
Pfft-- Japanese devs are still doing this stupid shit nowadays. It's no wonder their in-house PC ports are usually hit or miss.
I mean with From Software in particular I am surprised they do PC ports at all. They clearly loathe the platform, and they seem to refuse to even have a single programmer that knows anything about PCs that isn't from Wikipedia, nevermind owns one. Their ports are always so laughably bad in all technical aspects, they feel like comedy.
Dark Souls 1 had the stupid 30 fps cap and rendered at 720p and then stretched it. But otherwise it was very stable and bug free, totally playable from beginning to end. Dark Souls 2, Scholar, 3, Sekiro, and Elden Ring were all fantastic ports, rock solid 60 fps, all the settings that you could ask for, and ran great. If I was picking on a Japanese dev that did shitty ports, wouldn't really have picked From.
I mean just looking at Elden Ring here:
All of these would be trivial except maybe the stuttering if they had developers that regularly do PC games. They're just part of basic development or basic UX evaluation.
Apart from your first point, I think this just indicates that they hate m+kb users. There is a reason people say that people that use m+kb in a souls game are masochists!
Bethesda games up to the Xbox 360 era were mostly processor-bound prior to community patches.
Oblivion on the 360 would actually secretly reboot your console during long loading screens to clear the cache when it started running out of RAM due to memory leaks. Bethesda is hilarious.
Let's not forget that in fallout fucking 76 speed was tied to framerate on launch. An online game. With a beefy compy and graphics set to low, you could look at the ground and absolutely zoom across the wasteland.
Mind you, that error was already patched in fallout 4, so they literally copy pasted an old version of 4 to base 76 off of. Here's hoping starfield isn't literally just skyrim with space textures added.
That game was so fucked I actually blocked out my memories of playing it. Now all I remember is going to the office to get fans to get screws to repair my shit because I was trying to upgrade something and my guns broke because weapon degradation is fucking bullshit.
I heard that Bethesda was being told by Microsoft to adapt the Idtech engine that runs Doom and Id games to be moddable, and (if you can believe this) media are reporting that it's the "least buggy Bethesda game on launch to date" so maybe something did happen. Or they're lying.
Talking about starfield? I guess I wouldn't be surprised that they're being forced to shape up, and the reviews seem pretty good so far. I'm still gonna give it a few months before looking at it seriously though. I tend to wait on all triple A games just because how launches traditionally go (baldurs gate being an exception, girlfriend was too hype to wait).
I play a lot of games on Gamepass so I am basically just renting it.
Bold of you to assume anything wil ever change with their total lack of QA.
I thought that was Morrowind on the OG Xbox? Or did they do that on both? Still a hilarious fix, I remember Morrowind taking so long to load and thought it was due to the cheese collection I was building up in Balmora.
Haven't played any Japanese games recently?
Nope. It's been years.