Opening status menu in Pipboy causes game crash

[Gamer-02842]

I open up my Pipboy, click on "Stats", about 1 second of lag, and Fallout 4 crashes. Information will be provided upon request.

f4se.log

[Sgt. Marge]

Couple basic questions:

 

Are you using a mod manager, and if so and it's Mod Organizer 2, are you running "Loot" and hitting the sort button afterwards?

 

After sorting mods you'll need to probably manually sort your adult mods via the suggestions in the Up-To-Date Adult Guide.

 

Does this happen mid way through a play through or on a brand new game?  In other words, has this been a stable mod load and then all of a sudden it's crashing?

 

Are you using Buffout?

[Gamer-02842]

11 hours ago, Marg597 said:

Couple basic questions:

 

Are you using a mod manager, and if so and it's Mod Organizer 2, are you running "Loot" and hitting the sort button afterwards?

 

After sorting mods you'll need to probably manually sort your adult mods via the suggestions in the Up-To-Date Adult Guide.

 

Does this happen mid way through a play through or on a brand new game?  In other words, has this been a stable mod load and then all of a sudden it's crashing?

 

Are you using Buffout?

I use Nexus mod manager.
This is happening on a new save, I'm using as similar load that was stable  I just can't find which mod(s) is not working right.

[Sgt. Marge]

19 minutes ago, Cobra_007 said:

I use Nexus mod manager.
This is happening on a new save, I'm using as similar load that was stable  I just can't find which mod(s) is not working right.

 

Since the issue is reproducible, if no one else has suggestions you could always do the 50 - 50 method of troubleshooting.  Which is to say, if you disable half your mods, making sure that the ones you keep enabled also have their dependencies (other mod requirements) enabled, then test.  if it crashes, disable by half again.  once you get it to not crash enable a few mods at a time until it crashes again, keeping track of which mods you are enabling and ensuring that you are also enabling dependencies.  Maybe that would narrow it down to the problem mod(s).

 

 

[Gamer-02842]

19 hours ago, Marg597 said:

 

Since the issue is reproducible, if no one else has suggestions you could always do the 50 - 50 method of troubleshooting.  Which is to say, if you disable half your mods, making sure that the ones you keep enabled also have their dependencies (other mod requirements) enabled, then test.  if it crashes, disable by half again.  once you get it to not crash enable a few mods at a time until it crashes again, keeping track of which mods you are enabling and ensuring that you are also enabling dependencies.  Maybe that would narrow it down to the problem mod(s).

 

 

I forgot I could do this, I fixed it, Horizon was the cause if this is happening for anyone else.

[Sgt. Marge]

32 minutes ago, Cobra_007 said:

I forgot I could do this, I fixed it, Horizon was the cause if this is happening for anyone else.

 

It sounds like you have something that's conflicting with Horizon, there's another post here discussing Horizon + AAF and it can work together.  So you may want to check it out, and check the Horizon method for making compatibility patches, and check that last post in the thread about using FO4Edit to check things if you want to see if you can get it to work with your load order.  But at least you've got it narrowed down which is cool.