Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Agreed it completely breaks any immersion. What's worse is that despite the outdated 2010s graphics you still need a powerful machine to run it properly.
Procedural generation was a mistake that UE5 wouldn't magically fix nor would it fix the terrible skill tree that makes progression feel like a slog. The tacked on outpost building and mediocre crafting also wouldn't suddenly be good just because it was on UE5 and the story would still be just as poorly written.
I don't hate Starfield, my playtime proves that, but the game needed to be more focused. They tried to do more than they were capable of doing and no engine would have fixed that.
TLDR: Starfield doesn't need a better engine, it needs better developers.
But fundamentally, it is not even the better worktool.
It might look "easy" due to its shiny colored windows and funny lines you pull around in the Editing Kit to connect functions, it seems like "coding for pre schoolers", but it's confusing, and equally hard to utilize, as just programming by manually typing in good old C# code.
I would say though that Starfield would have benefitted from UE in the way that at least the built-in glitches like object permanency issues, Stack overflows (or in Starfields case, RefID overflow) and other things would be a thing of the past, UE has a very decent garbage collection for unused Refs and other Variables, much much better than anything Bethesda could ever program.
The game would have, but it wasn't made in UE so there's no need to say "would could should" outside a few sentimental mentions.
It is what it is, and what it is, sucks, but can't be helped, it is what you get when Devs take 1 game engine, fail to make a new one, and just pile new features on the old engine, rebrand it as "BRAND NEW!" but that the Engine has references to Morrowind and Oblivion and Fallout 3 code and variables is the ultimate testament that they just copy paste an old outdated quarter century old engine, throw new funtions on it, and expect it to run.
I'm still trying to load this comment.
Can't be an engine problem though, because apparently the technical framework underlying a game has no effect on the game at all.
Because at the end of the day it's all about potato physics and the bugs those physics provide that adds that little extra Bethesda 'magic'.
Fixed that for you.
Besides UE5 engine has a lot problems too
I think Bethesda needs to spend a ton of time and money on re-developing Gamebryo/Creation/Creation+/Creation2 from the ground-up, instead of just patching and adding and spaghetti-coding it to death. Same game engine used for Morrowind for heaven's sakes. It's over 20 years old.