Good ways to find out what mod might be causing problems?

[Tailas]

I went to play XCOM2 today, but when I went to launch the game through NMM, it immediately goes into a Not Responding state and never recovers. I had to close NMM and relaunch it.

 

I then tried to launch through game through Steam instead. I got the game launcher to load (where you can deactivate/activate mods), and clicked on Play, and it also went into a Not responding state.

 

The game worked fine yesterday and I played for about 3 hours without any issues. I played until i had to go to bed, and then was thinking about playing all day while I was at work. I came home and went to play, and that's when the issue started. No new mods were downloaded or installed.

 

I did notice however, that XCOM2 itself had an update today. I'm thinking that one of the mods I have installed wasn't updated accordingly.

 

What would be the best/easiest way to find out which mod is causing the problem?

[davidlallen]

This is our first experience with an update. Although the patch notes make it seem like the changes are minor, so far we don't have a way to know about mod incompatibility. We can be pretty sure that since this is the first time, no modder even knows how to tell what to update, or whether they have to. I am sure the community will work this out.

 

I have a slow disk, and it took almost two hours for the update to finish. I have heard that this is due to a huge amount of disk activity in the update process, but I don't know exactly why. When I first downloaded the game, the validation step took almost four hours. That was really frustrating. So first, make sure your update and validation is really finished.

 

If you deactivate all the mods temporarily, and start a new game, are you able to play at all? Once you get to where you can play, then start turning mods back on a few at a time.