Public Service Announcement. If you've been dealing with unusually long load times in Fallout 4, this fix may be for you. We can confirm it has made a significant impact for some people.
People... This issue isn't because of your computer. It's probably because you can't handle V-Sync with your mods.
Try this, go to C:\Users\XXX\My Documents\my games\Fallout4 > open fallout4prefs.ini (or wherever you saved it to)
change: -------------------- iPresentInterval=1 (If your value was already set on 1 then set it to 0) save>close> and set the file back to read-only.
If you're still getting long loads, try toning down your shadow details a bit.
This should cut your loading times significantly to about 5-15 seconds.
Note: This is only for people who've been getting load times up to a ridiculous 1 minute or more. This may also make your frame rate too fast for small areas like when entering a building. You'll have to make sure your frame rate is set to cap at 60fps.
It worked a little too well for me, if I set the value to 0 (from 1), the navigation in the start screen becomes oversped, pressing up or down just races the selection to the top or bottom. Just lightly tapping up or down reacts normally, but clearly the game is not handling this solution very well, and perhaps there are other similar issues too.
tl;dr - If you're suffering massive load times for fast travel and entering doors: 1) Start the game 2) Go to Settings -> Gameplay 3) Turn "Save On Travel" off.
If that was what was causing your problem, you will see results immediately.
------------------------------------------
I originally found this thread a few days ago, because my up-to-date Fallout 4 began experiencing massive load times on fast travel, or when moving through doors. My loading times early on were between 15 and 30 seconds, but this ballooned to minutes (sometimes eternities).
My fallout4custom.ini file already had... bInvalidateOlderFiles=1 sResourceDataDirsFinal=
... in it. I tried adding... [General] iNumHWThreads=4 ... as was suggested, which seemed to help a little. What really helped was purging a bunch of save files, but the slowness quickly returned. After some experimenting, I narrowed it down to the autosave on travel feature. My best guess as what is wrong is that the game has one thread validating old autosave files before saving a new one in competition with the thread that is trying to load the place you're arriving. There is most likely a coded delay upon suspected deadlock (to avoid ramping up the CPU by having the shut out thread endlessly poking at the lock) which is causing these absurd delays. Deleting old autosaves eliminates the validation step which is why you'll get a temporary reprieve if you delete them.
This problem seems to be specific to Save On Travel (which happens during quick travel AND when moving through doors) and when hitting quickload at the wrong time. It's far less severe with Save On Wait/Sleep, and non-existent with Quicksave and manual Save.
Hope this helps someone. It was a really annoying problem for me before I tracked down what was going wrong with the game on my machine.
I am unable to open NMM for Skyrim. This has been the case for the past three or four upgrades. It acts like it is going to open, but just sits there with the "progress bar" going but moving no further and not opening. Any ideas on how to fix this? Please. TonyB Witcher 2 and 3 work as does Fallout New Vegas and the Dragon Ages. It is only Skyrim that it does not work with. Right now I am trying to let it open while I do other things to see if maybe it just takes it a long long long time to open. :-)
found a FIX for the annoying super long load times, works for me, give it a try:
add this to all 3 fallout4 ini files in "Documents\My Games\Fallout4" put it under the "General" section: iNumHWThreads=X where but feel free to experiment
Am I the only one in these comments who has a great decrease in loading times without any other issues piling up behind it? Great beta patch for me!
After some hours playing, I have noticed some ctd's which I have NEVER ever gotten since first playing FO4, but wether that is mod related or beta patch related or even a combined issue I do not know, still great loading times though
i tried the beta patch for a bit, but i kept getting stuttering, like the old skyrim large-save bug - but mroe often, about every 20 seconds.so i uninstalled it, hope it doesnt carry over to live.
Have you tried Windows mode - full screen? That helps with stuttering A LOT for me, actually it totally removed stuttering. Playing back on FULLSCREEN literally does my head in with the way it seems to skip frames here and there. Horrible.
borderless fullscreen is the only way i play anything. cant stand game windows not allowing screen roaming, or minimizing when i decide to tab to another window
spent about 15 mins testing out what went live before work, fortunately whatever issue it was, was worked out during beta. seemed to be smooth sailing.
102 comments
Comments locked
A moderator has closed this comment topic for the time beingTry this, go to
C:\Users\XXX\My Documents\my games\Fallout4 > open fallout4prefs.ini
(or wherever you saved it to)
change:
--------------------
iPresentInterval=1
(If your value was already set on 1 then set it to 0)
save>close> and set the file back to read-only.
If you're still getting long loads, try toning down your shadow details a bit.
This should cut your loading times significantly to about 5-15 seconds.
Note: This is only for people who've been getting load times up to a ridiculous 1 minute or more. This may also make your frame rate too fast for small areas like when entering a building. You'll have to make sure your frame rate is set to cap at 60fps.
1) Start the game
2) Go to Settings -> Gameplay
3) Turn "Save On Travel" off.
If that was what was causing your problem, you will see results immediately.
------------------------------------------
I originally found this thread a few days ago, because my up-to-date Fallout 4 began experiencing massive load times on fast travel, or when moving through doors. My loading times early on were between 15 and 30 seconds, but this ballooned to minutes (sometimes eternities).
My fallout4custom.ini file already had...
bInvalidateOlderFiles=1
sResourceDataDirsFinal=
... in it. I tried adding...
[General]
iNumHWThreads=4
... as was suggested, which seemed to help a little. What really helped was purging a bunch of save files, but the slowness quickly returned. After some experimenting, I narrowed it down to the autosave on travel feature. My best guess as what is wrong is that the game has one thread validating old autosave files before saving a new one in competition with the thread that is trying to load the place you're arriving. There is most likely a coded delay upon suspected deadlock (to avoid ramping up the CPU by having the shut out thread endlessly poking at the lock) which is causing these absurd delays. Deleting old autosaves eliminates the validation step which is why you'll get a temporary reprieve if you delete them.
This problem seems to be specific to Save On Travel (which happens during quick travel AND when moving through doors) and when hitting quickload at the wrong time. It's far less severe with Save On Wait/Sleep, and non-existent with Quicksave and manual Save.
Hope this helps someone. It was a really annoying problem for me before I tracked down what was going wrong with the game on my machine.
TonyB
Witcher 2 and 3 work as does Fallout New Vegas and the Dragon Ages. It is only Skyrim that it does not work with. Right now I am trying to let it open while I do other things to see if maybe it just takes it a long long long time to open. :-)
add this to all 3 fallout4 ini files in "Documents\My Games\Fallout4"
put it under the "General" section:
iNumHWThreads=X
where
but feel free to experiment
Core i7 2600K @ 4.2Ghz, 16GB ram, 4GB GTX 770
After some hours playing, I have noticed some ctd's which I have NEVER ever gotten since first playing FO4, but wether that is mod related or beta patch related or even a combined issue I do not know, still great loading times though
Finally you do something right, bethesda.
did anyone else experience this?