RollFizzlebeef766

I second this. I have no objections to Nexus taking security precautions, but I have huge issues with Google tracking me that I raised the last time this issue came up.

Oh hey, thank you for addressing both of my concerns. I haven't logged in for a while and was really pleased to see you did that!

I have more of a programming issue to report. Like many people here, I have Google blocked by default. In my case, I have their scripts blacklisted unless I temporarily whitelist them. You have not put anything into the login form to indicate there is a captcha. If scripts from Google's domain are blocked, the login form looks exactly the same, but you get an error about the captcha failing. Please update the form to indicate there's supposed to be a captcha there. Not everyone whose computer has been set up with basic security is also technically adept enough to guess they need to allow more scripts. All you need is a NOSCRIPT block indicating "Please allow scripts from google.com to see the CAPTCHA" On a related note, have you considered just using someone else for the captcha? A lot of the people complaining are annoyed it's a Google captcha rather than just because it's a captcha.

The various fixes got discussed at length over here: https://forums.nexusmods.com/index.php?/topic/3700505-unusually-long-load-times-addressed-in-fallout-4-beta-patch-1347/ My own experiments with it were here: https://forums.nexusmods.com/index.php?/topic/3700505-unusually-long-load-times-addressed-in-fallout-4-beta-patch-1347/page-10&do=findComment&comment=39919700 The short of it is, there are some configuration options you need to update, you need to disable Save on Travel, and you need to regularly purge old save files. Regarding that last tip: As far as I can tell, Fallout 4's engine does some kind of sanity check on old save files every time it saves or loads at all. It also seems to either cache information on the save files or retains old data in files it was supposed to save over. So the more save files you have, the more the game chugs along. It's more prone to getting stuck in a thread deadlock around the time save files are up to half a gig. Cull your saves back down to 2 *new* normal saves and 1 quicksave PER CHARACTER whenever the game starts lagging. If you're not sure about deleting the save files, create a new directory and relocate them to it. That should have the same effect since the game won't know where to look to needlessly scan them. If you have a lot of characters, maybe just relocate all but the active character's saves in here instead of leaving any in the real save dir.

In response to post #39919700. Also, during my experimenting, I did try turning off VSync; all that did was make the lockpicking minigame go nuts.

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.