Stuck on the new game loading screen

[chefshat]

My LO is:
UF4P
Workshop Framework
HUDFramework
SS2
SS2 chapter 2
SS2 extended

And that's it. When I start a new game, it just sits on the black screen with the loading icon forever. If I deactivate SS2, it starts up fine. Please help?

(On PC, using Mo2)

 

[Mystical Panda]

The SS2 that you installed, did it already include the 'extended' data? If so, try deactivating that and see if it works. If not, low memory can cause resource(free mem) thrashing, including the memory available to the gpu.

 

[chefshat]

I just installed the main SS2 file off of Nexus. It installed the Extended add-on automatically. But I did try disabling the Extended and it still doesn't work. I don't see how I would have low memory. I've run Fo4 with tons of heavy mods before and had no issue, and this is happening with literally nothing but SS2 and its components.

 

[Mystical Panda]

I just installed the main SS2 file off of Nexus. It installed the Extended add-on automatically. But I did try disabling the Extended and it still doesn't work. I don't see how I would have low memory. I've run Fo4 with tons of heavy mods before and had no issue, and this is happening with literally nothing but SS2 and its components.

It's just a possibility- I didn't know your system specs and I've encountered low-mem thrashing before. Ok, so it's not a hardware-resource issue... then it has to be a data issue? There was one issue where the loading screen seem to ILS for me when starting a new game- it had something to do with 'waiting for input'(no idea why), but the intro wouldn't start until I pressed a key like ESC or TAB(as an example and didn't try a right-mouse click). I had to wait until the loading was going to transition between actually loading data and showing the intro movie- then I pressed a key. For me, this happened with a fairly heavy modded game awhile back. I have a heavy modded game now and don't have that problem so it was more than likely a 'mod' I used previously had data that 'confused' the engine and kicked it off it's 'stride' or my load order is better tuned now. I'm not really sure on that either way.

 

[chefshat]

It's just a possibility- I didn't know your system specs and I've encountered low-mem thrashing before. Ok, so it's not a hardware-resource issue... then it has to be a data issue? There was one issue where the loading screen seem to ILS for me when starting a new game- it had something to do with 'waiting for input'(no idea why), but the intro wouldn't start until I pressed a key like ESC or TAB(as an example and didn't try a right-mouse click). I had to wait until the loading was going to transition between actually loading data and showing the intro movie- then I pressed a key. For me, this happened with a fairly heavy modded game awhile back. I have a heavy modded game now and don't have that problem so it was more than likely a 'mod' I used previously had data that 'confused' the engine and kicked it off it's 'stride' or my load order is better tuned now. I'm not really sure on that either way.

I did NOT expect that to be the answer but in fact pressing enter made it proceed to the intro. How strange, because the loading icon was still cycling and I clicked and pressed other keys and only Enter worked. Anyway, thanks!

 

[Mystical Panda]

Your welcome! I'm thinking that something is firing off behind the scenes- like a message with an ok prompt(as an example), but since the viewport(interface) is the primary loading screen(new game) it must be 'behind' or invisible- yet still awaiting input. I do have XDI installed so that may have somehow been related previously though it doesn't happen now.

I have no idea why 'mods' with quests don't wait to fire when the player actually discovers Sanctuary, or exits the vault- other than mods that changes player skills or stats(like Be Exceptional).

 

[GuardianMF]

Your welcome! I'm thinking that something is firing off behind the scenes- like a message with an ok prompt(as an example), but since the viewport(interface) is the primary loading screen(new game) it must be 'behind' or invisible- yet still awaiting input. I do have XDI installed so that may have somehow been related previously though it doesn't happen now.

I have no idea why 'mods' with quests don't wait to fire when the player actually discovers Sanctuary, or exits the vault- other than mods that changes player skills or stats(like Be Exceptional).

Indeed, for some reasons some prompts can be displayed right before the intro, giving the illusion of an infinite loop because the screen is still black (or possibly white). Those prompts are normally displayed later, most notably after exiting the vault. Last time it occurred to me, I'm pretty sure it was a prompt from the Working Aquariums mod that got in the way, but I've seen a number of reports over the years and no one knows what causes this issue.

 

[msalaba]

If I deactivate SS2, it starts up fine.

What version of SS2 do you have installed? IIRC, the latest version is 2.3.2b
Kinggath fixed a ton of bugs in v2.3.2. Its possible a bug may have slipped into the startup code. Its trying to display a message before its possible to do so.
Double check <Steam Install Path>\Fallout 4\data\scripts\ for loose files.

I've seen a number of reports over the years and no one knows what causes this issue.

Because most mod authors do not know that this is possible. Simply adding PlayerRef.WaitFor3dLoad to a script before displaying a message will prevent this.
I learned this and many other power of Todd things while making my Fast Start mod.