wax2k

The mods do the same as before: they allow scrapping stuff. It's not the mods that trigger that glitch, it's you removing certain objects from the game, that are used in LOD rendering. It doesn't matter if you do that by using a mod or by deleting them manually via console commands. The issue was the same before Fallout 1.3. You obviously just didn't notice it before.

It doesn't say that. It actually says the exact opposite :wink:

Any texture mods? Like Gore Overhaul for example?

This is the issue. You have to enable the mod plugins to make them work.

You're either missing the archive invalidation setting in your Fallout4Custom.ini or you're missing the mesh files from AWKCR. Refer to the "CTD issues" section of this guide for further troubleshooting advice.

@Ryan1076R: on a new game without installing that specidic mod again, it should not be related. You're probably either missing the archive invalidation setting or you're missing meshes from one of your workshop mods. Refer to this guide for troubleshooting workshop mods and CTD issues.

http://www.nexusmods.com/fallout4/mods/10112/? has one.

Please refer to the Bugs section on that mod's page. It seems to be a common issue even after uninstalling it. You might have to revert back to an older savegame before installing that mod.

You said, you tried to re-enable them. That's not disabling/reverting/uninstalling/removing them. You also should keep all the latest mods disabled as long as you're testing and until fixing the issue and then you could start adding them back in one by one. Apart from that, crashes before or at the main menu mostly mean wrong load order or missing master files. So check the load order, see if NMM shows any plugin in orange/red in the Plugins tab and select it in case to see which file(s) it refers to as master. The master files have to be installed, enabled and above the referring file(s) in load order. If you can't manage to figure it out, export the load order with the export button in NMM's Plugins tab and post it here in spoiler tags.

Not if you did it right. It's just a plain text file. So as I stated:

You can switch views and you can change the categories to your liking.

The problem was exactly what I assumed it was. You launched the game from Steam or with Fallout's launcher which allows them to clear the plugins.txt. And as long as you don't make the plugins.txt read-only, it will happen again every time you don't launch the game from NMM but from Steam or with Fallout's own launcher.

Only launch the game from NMM by clicking the button in the upper left and leave NMM running. Do NOT launch the game from Steam or with Fallout's own launcher because that will clear your plugins.txt every time. And for double-safety: make the plugins.txt read-only and only allow NMM to override that when asked.

Did you remove any larger objects like hedges or even buildings with some sort of scrapping mod or by deleting them via console? Many of these are used for LOD rendering and will lead to this kind of visual glitch when standing/walking in the place where they used to be. That's the reason, why Spring Cleaning (the Scrapping mod with the most reasonable approach and the least bugs in my opinion) for example does not allow scrapping these by default.

Refer to this guide to get a working mod setup and troubleshoot CTD issues. And if still having issues afterwards, describe them and post your load order in text form in spoiler tags. You can use NMM's export button in the Plugins tab.

Umm... according to your load order, you didn't uninstall SSEx. And you didn't install Homemaker. Do that, see how it works, and if still having issues, post that load order.

And there you go: http://www.nexusmods.com/fallout4/mods/10129/?

Check if your Fallout4Custom.ini still has the archive invalidation setting. If not, put it in again. Make your plugins.txt read-only. Then launch NMM and allow it to override the read-only. Switch to the pluginstab and make sure the mod plugins are enabled there. Then launch the game with the button in the upper left. That should definitely work.

Old trick ^^

I'd bet on the coma :wink:

Haven't tried. Can you pick it up by holding E and carry it out of sight from everybody before actually taking it?

Well... no one said you had to drink them without taking a piss in between... try playing the flow heater! :D

Are you launching the game directly from NMM with the button in the upper left or from Steam or Fallout's own launcher?

Ok, in that case you'll have to go the hard way. - Please check your \Fallout 4\data folder for any custom leftovers. It has to look like this: \Strings \Video Fallout4 - Animations.ba2 Fallout4 - Geometry.csg Fallout4 - Interface.ba2 Fallout4 - Materials.ba2 Fallout4 - Meshes.ba2 Fallout4 - MeshesExtra.ba2 Fallout4 - Misc.ba2 Fallout4 - Nvflex.ba2 Fallout4 - Shaders.ba2 Fallout4 - Sounds.ba2 Fallout4 - Startup.ba2 Fallout4 - Textures1.ba2 Fallout4 - Textures2.ba2 Fallout4 - Textures3.ba2 Fallout4 - Textures4.ba2 Fallout4 - Textures5.ba2 Fallout4 - Textures6.ba2 Fallout4 - Textures7.ba2 Fallout4 - Textures8.ba2 Fallout4 - Textures9.ba2 Fallout4 - Voices.ba2 Fallout4.cdx Fallout4.esm Everything else is not vanilla and should be removed. I would even delete the files in \Fallout 4\data\strings since these might be modded as well. - Then delete the 3 ini files in \%userdata%\Documents\My Games\Fallout4 as well as the plugins.txt in \%userdata%\AppData\Local\Fallout4 - Verify game cache in Steam - Then launch the game once until you see the main menu and quit again. The Fallout4Custom.ini should now exist again. Edit it (and only this one) to again look like this: [Display] iLocation X=0 iLocation Y=0 [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= then save it and and launch the game. If that again doesn't work, you have some issue outside of the game. Could be driver or hardware issues.

Crashing before or at the main menu mostly means wrong load order / missing master files. In case you use NMM, check for plugins shown in orange / red in the plugins tab. They will show their master files on the right side when being selected. The master files have to be above them in load order. If you don't manage to fix it, post your full load order here in spoiler tags, so we might take a guess. Edit: on a closer look: you got a leading space in [ Display]. It should be [Display]. Dunno if that really leads to crashes, but fixing it can't hurt either way :wink: