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
so this appears to be saying that the game does have major programming faults, just not in the way the other guy says.
Yup lol.
No denying Bethesda struggle on the tech side. They are using a game engine from 1997 afteral and just renamed it.
i would call whatever "bug" is causing this disastrous performance a programming fault. merely renaming it a bug doesn't really change the fact that the devs' incompetence is responsible for it, even if the particular manner of that incompetence is not represented properly by the original article.
i acknowledged what he posted what the hell are you talking about? dishonesty would be pretending there aren't massive issues just because some guy got the mechanics wrong.
Part of the issue is the game is coded for Vulkan and then translated into DX12. I get why they do that as it's easier to port. However, the Xbox and Windows don't use Vulkan well. Since this is a Windows and Xbox game, it was silly to do it this way. It should have been coded with DX12 from the ground up.
pc specs are pointless. it's the game, not the pc.
but just to shut anyone up about me needing to upgrade in order to run this Xbox 360 tier game:
RTX 3090
i9-11900k
4x16 GB DDR4
On an SSD