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
The game needs to drop all buff from ram and refresh it, then it's fixed. I've seen few more location that were like that, like that door at the junkyard NE from Sanctuary etc.
Basically it does the same thing but in less steps. By loading the game polygons from scratch when you are *already* in close proximity to the problem area, it ends up only loading the local (higher density) version of the area, and not loading the distant (lower density) version first, as it would do if you walked up to the area from afar. The bug seems to be that it's failing to remove the distant low density version when you get close enough to load the local high density version, so it's ending up with both present at the same time.
and i know it isn't my computer as i just had a clean install of windows 10 off new drives freshly installed. New samsung 500g ssd where i am playing fallout from. So no software issue, and hardware was fully tested. All drivers up to date.
i7 4770k, gtx 780 Ti superlocked, 16gb ram, etc..
Are they even aware of this bug? Hopefully there is a fix in the works.
Put
bUseCombinedObjects=0
in the [General] section of your Fallout4.ini (or make it 0 if it is already set to 1)
maybe that will help.