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
Google "papyrus stack dump".
Basically there so many scripts running in the save that the papyrus engine is overloaded and shuts down. Then things like AI processing cease. Usually a definite sign is when you go somewhere and all the NPC's stop dead in their tracks and don't move.
You can enable papyrus logs and confirm thats what is happening.
There is also third possibility. Something has royally messed up your alias checks. That may, or may not, be related to Papyrus spam. It can be caused by careless use of console or broken/removed mod file.
Could any of these scenarios be true?
If your curious to see what your game is doing you can go here:
C:\Users\%User%\Documents\My Games\Fallout4
And add this to Fallout4Custom.ini
It will create a log folder where you found Fallout4Custom.ini
For Reference:
https://www.creationkit.com/fallout4/index.php?title=Enable_Debug_Logging