Baggins

Traversal is technically possible yes, but it’s not possible to traverse at a speed which would be feasible or fun, indicating that their engine isn’t capable of unloading and loading new assets in fast enough as you move around. Probably the same reason that even Neon needs to be hard split in half instead of just unloading the assets from the part of the city you’re not at at the moment.

Speeds that the above mentioned mod adds. Until CK is added the debate of switching of one space map to another seamlessly is useless, since the current implementation is missing the hook to load the next map whilst the same hook is implemented between ship take off and space (even when player is not at the helm). Yeah, but New Atlantis is much bigger and allows the player to boost pack from the MAST top floor to another skyscrapers roof and then get down to commercial level and trade stuff without any load screens, at least on PC.

And bruh blaming the S with no information is asinine when not a single other game struggles with traversal on it, including massive open world’s like GTAV, Cyberpunk, Flight Simulator and even other space sims like NMS.

Expect of course if there were dev stories related to it sprinkling out periodically, latest being from Baldurs Gate 3 devs: https://www.pcgamer.com/baldurs-gate-3-dev-shows-off-the-level-of-optimization-achieved-for-the-xbox-series-s-port-which-bodes-well-for-future-pc-updates/

It's worth noting that out of all the platforms that Larian has developed its masterpiece for, the Xbox Series S is probably the most restrictive. This is because it only has 8GB of high-bandwidth memory, to store the game while running and use as VRAM (the remaining 2GB gets used for system functions).

The graphs start at the beginning of September, with the game using just over 5.2GB for general game RAM and around 3.5GB for VRAM. By November, though, Larian had shaved this down to 4.7GB and 2.3GB respectively. The RAM reduction is a pretty decent 10% drop but the reduction in VRAM usage is a massive 34%.

Other devs have stated these: https://www.gamesradar.com/xbox-series-s-could-bottleneck-some-next-gen-games-developers-suggest/

Gneitling pointed to the "almost non-existent" RAM increase from current-gen systems to Xbox Series S as a major pain point. Also "it always scaled on PC" is nonsense. Every AAA game in the past decade or so has their assets made once so they run on min spec. Increasing sample counts a bit here and there for high settings isn't what you could truly have done with more power. Min spec matters.

The article has many such remarks from other devs as well. So why couldn't the segmentation of Starfield be because of Xbox Series S? Keep in mind the latter article is now roughly three years old.

stuff to work with more continuous travel.

I bet you would be surprised if you were to find out that it is possible already. In space one can already move from one planet to another, only thing that is missing is the loading of new space "map" on demand. And more importantly move from one planet to another and then dock with spacestation. As shown by https://www.nexusmods.com/starfield/mods/3541.

And on planets the landing zones aren't placed in a vacuum, topological details like mountains are visible from adjacent zones. As shown by https://youtu.be/Fy0eG7MFSTM?si=ZwaE3OzmEf9IxbwZ&t=841 by 2kliksphilip.

Now you might ask the very obvious question: why isn't this correctly implemented to allow seamless travel in both space and on planets in vanilla Starfield? We may know only after someone does full introspection what happened during development but my speculative guess is that Xbox Series S which is much weaker than X is the primary reason for all this segmentation in all aspects of Starfield.

deez NUTS