EmperorVukodlak

This is what I've found in my own testing, there is no one mod to blame for crashing in the specific areas for most of these cases nor does it seem to be any one combination. I don't have any mods altering the area around Monsignor plaza. Yet I'll get crashes in that area. If I turn them all off I can enter but as I turn them back a few at a time the performance in that area gets worse until instant CTD. Doesn't matter what order I turn them back on in, two day of testing doesn't reveal a smoking gun, and looking at load orders of people complaining of similar problems doesn't reveal anything either. It just seems past so many mods active the area becomes unplayable new or old games. Now In the past I've gotten around this by slowly circling the crash zone saving every so often and inching closer and closer until I can finally enter the necessary building in the area or even wander around. The fact that if I enter slowly enough and from the right angle I can explore the crash zone led me to believe the game is crashing because there isn't enough RAM to load the area OR the game is using up all available ram to load the area and there isn't anything left. So I added the following line under [General] in the fallout.ini file. iPreloadSizeLimit=8388608000 This insures the game allocates 8GB of my 16GB of ram to the game and just like that I could walk into the problem areas. No fussing with load orders, no making merged mods with FO4Edit. That one line problem solved, remove the line problem comes back. You could also try adding the line bPreemptivelyUnloadCells=1 But I did not find that necessary. Now if you use say the Mod Organizer you'll have a unique Fallout.ini under each profile so you'd need to add that line to all of them.

I agree I want to see the Soul Reaver! I was just coming in to suggest that.