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
"all the problems" isn't exactly descriptive. name the problems
thats what you get when someone draws conclusions from a game made on an engine, rather than the engine itself.
its baffeling to me how many people think they know the engines limitations without having actual access to the engine
But ok, I am a generous god, here: https://youtu.be/E7kCFkFi0Cc?t=387
imagine posting a 20 minute video talking about starfield, and not the engine, to somehow prove the engine has issues? yeah, you aren't good at this, are ya?
For anyone who wanted Starfield to not have 1000 loading screens every 15 seconds. Yeah the engine is the problem. The engine itself will never allow the games Tiles to be tied.
I also find it amusing that YOU can't come up with anything, you have to rely on some youtube video that supports "your" conclusion. One that was handed to you by some youtuber no doubt.
Try again.
their APPROACH with their world design doesn't tell you anything about their engine
as for the "how many loading screens", comparing the amount of loading screens to the size of the explorable map, it is actually not that many