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
This is ... maaaaaaybe going to be addressed for PC but I don't know whether the consoles, and it's a big maybe, we do not know what they will be addressing but we've been told from Bethesda that an update will come this year. Only speculation is available as to what exactly it will be addressing.
Not sure what you're expecting from this update. And how the problem isn't related with what I said in the first place? All the things I have listed are directly related with memory leaks, because obviously all the things you have listed yourself causes an overload in the game. And therefore a memory leak.
Yet, it has been 8 years that problem exists in the game and they have done nothing about it.
I've read about some people expeculating the crashes/freezes are somehow related with the companions A.I, in which their movement algorithm behavior cannot determinate what is traversable terrain, or because it has to calcule colision for every object in the area or calculate routes to determinate what is traversable terrain, or something like that. And because the area is overloaded with stuff the code becomes a mess and causes the freezes/crash/fps drops issues.
This theory comes from reports that when they don't bring any followers/companions to the known problematic areas, the crashes and freezes doesn't seems to happen, or at least they are less frequent. But I have yet to confirm this myself.
The problem is the area itself, it happens in that spot regardless of your companions, though yeah they absolutely get caught up on terrain if you turn your back on them. But either way, nothing to do with your mention of "far harbor release". It was there before.
Are you actually convinced and believing that the developer support team is sitting on Steam forums, 8 years after the release, and taking notes on issues on Xbox?
They're releasing their biggest title yet, a completely new IP, and the biggest exclusive title for Microsoft. I'm pretty sure people are fairly busy right now and will be in the immediate, very hot post-release window.
Fallout 4 ought to receive a big next-gen update this year. If that happens, in a month or two we might hear something about that. Either way, they don't and won't dedicate any resources to work on anything in parallel to that bigger update.
Long story short- wait for the upcoming, universal F4 update.
Maybe they have, but that doesn't mean anything on its own. Teams that were acquired after F4 was released, and never had anything to do with its development, that are preoccupied with something else, won't go knees deep into F4's code to rework it.
In the end- Bethesda Game Studios is Bethesda Game Studios, and while Bethesda Softworks is overall big, we're not talking about corporate size and structure mirroring something present within Ubisoft.
In more ways than one BGS is a rather peculiar entity, and you can't just grab some people 'off the streets' and tell them to straighten 8yo game made on Creation Engine.
It's not Call of Duty where people from support dev studios can tune it to tweak weapon stats and release new map packs for the upcoming season.
None of us works in BGS and nobody knows how many people are assigned to work on the update, how long they've been doing it and what is the actual status.
SeniorVP in BGS, Pete Hines when asked about the update replied like that:
Dunno if you heard but we are shipping a new game in 3 weeks. Bit of a priority. When we have an update, we will share it.
https://twitter.com/DCDeacon/status/1689762227258052608
All left is speculation and expression of personal demands 'they should do this or that' but it's irrelevant- the only known thing is the update that aims to modernize Fallout 4 across all platforms, and before it no other work will be done, nor people doing that are gathering feedback, they had 8 years to do that.
Playing Bethesda games on consoles is asking for trouble. F4 GotYE is dirt cheap and it's highly advised to play it on PC, where there are numerous ways to fix, tweak or simply brute force through problems.
Xbox One is simply old hardware and not getting younger nor a priority for devs, unlike SeriesX or PS5.
I've owned this game since it dropped and got the season pass the moment it was available, so ... yeah I doubt that it started then, you may have *noticed* it on your later experiences. It was always there. The main map didn't change anywhere near that area, for far harbor, v88, or the automaton and nuka minor map changes. Blaming them somehow seems ... kinda silly since they were all released within 1 year of the game's release, and it's always had the issue.
Either way, if you're on a console you should not hold your breath for any fix.
Thing is, when they have people paying full price for their games they should at least have some consideration with their costumers. I don't want to pay for a broken game or a defective product that will be forgot like that. You have no idea how expensive full price games are in my country and I pre-ordered Fallout 4 back at the day. Thank god I've learned my lesson since then and never pre ordered anything again.
It is even worse if the game launches like this and on next few months it is still getting any support they kept releasing new content, DLC or whatever for the game while straight up not adressing or ignoring serious gamebreaking issues like that. They can get problems in law because of stuff like this you know. Back then I complained about the issue when it first happened way back in 2016. Complained in 2018, 2019, 2021 and I'm complaining now yet again. Game got a bunch of updates during this time and the problem was never sorted out.
I guess is a good thing MS carefuly accopanied Starfield development from up close, otherwise if was left on the hands of Bethesda alone the game would probably launch with similar problems like this one.