ma1025

A Fallout 4 version of the Skyrim program.

I just rename Fallout4Launcher.exe to Fallout4LauncherBACKUP.exe and renamed f4se_loader.exe to Fallout4Launcher.exe.

I'm not sure if I can link to a mod that's offsite (it was here before but it's removed now). Do a Google search for Fallout 4 Save Game Editor and it should be the first result. Open your save file with it and on the left expand "Plugin Info > Plugins" and it should have a list of the mods you were running for that save file.

Maybe the savage deathclaw mesh with both horns could be used for the mythic deathclaw or something?

That hat was 10/10. Would like.

If it's the timescale thing, I wrote a fix for it if you wanna give it a try. https://forums.nexusmods.com/index.php?/topic/3717695-sleepingtimescale-set-to-0-pitch-black-help-please/?p=33742910 If it's an imagespace effect getting stuck, I've got a batch file you can run that clear all vanilla IMODs http://www.nexusmods.com/fallout4/mods/9852?

I was crashing in the same area for a long time. It might be different for you, but for me it was meshes in meshes/SetDressing/LightFixtures. I just deleted that whole folder and it fixed the CTD for me. If it's something different for you, you can find the problem by using the old method of archive invalidation, (adding , TEXTURES\, MUSIC\, SOUND\, INTERFACE\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX\, VIDEO\ to your sResourceDataDirsFinal=STRINGS\ ) and take one section off at a time. Example: sResourceDataDirsFinal=STRINGS\, MUSIC\, SOUND\, INTERFACE\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX\, VIDEO\ loads everything besides texture replacers. If the game still crashes at the door, add TEXTURES\, back in and remove the next one (MUSIC\,) until you remove the replacer type that allows you to get through it without CTD. In my case, it was meshes but I didn't know which one.I'm going to use my situation as the example. Once you find out it was meshes or whatever that was causing the crash, reactivate the normal style of archive invalidation and go to the Meshes folder. Make a new folder in there called BACKUP or something and drag all your mesh subfolders into it. Then just put back a handful of folders at a time and try to go through the area until it crashes again. Once you crash again, keep putting one folder back into the BACKUP folder at a time until the game doesn't crash anymore. That will narrow down the specific folder containing the problem. Then you can do the same thing to narrow down specific files if you have to. Once you have the problem fixed, make sure you put all your subfolders back where they should be. It takes a while and it pretty tedious with how many times you have to launch, crash/close, move files, relaunch but it's the best way I've personally found to fix specific file-related CTDs.

I'd love something for this too.

Are you using any interface mods like DEF_UI or something similar? If so, reinstall it and make sure you choose an option that matches the aspect ratio of your monitor (like 16:9 and so on). If not then you could try using one of the widescreen fixes. UWPU - Ultra Widescreen Patches Updated Widescreen Fix PA Rainbox HUD FIX (just in case)

Some people were having shadow issues with a new nVidia driver update. Try disabling ambient occlusion (or use HBAO+ occlusion).

I kept crashing everytime I tried going a normal route so I ended up having to start at Red Rocket near Sanctuary, head straight west, and sort of straddle the "You Cannot Go That Way" border all the way down. I jumped down a lot of rocks.

Recon scopes and recon sensors on armor use the red diamond to mark enemies on-screen and on the compass.

I had a crash due to Textures/Water/WaterTileHumpy_n.dds and Meshes/SetDressing/LightFixtures/LightbulbOff.nif Everything's been fine since deleting these files (so far).

Did you update your nVidia drivers? Others have had this and a shadow problem result from it. Try changing your ambient occlusion from SSAO to HBAO+ or just disable it completely.

I kept crashing on the monorail right after "the largest manmade structure in Nuka-World" every time. Deleting Textures/Water/WaterTileHumpy_n.dds fixed it.

Then you could try using Generator - Fusebox to place a new power source inside the house. Then you can just pull a wire off of that (assuming you attach wires to it, I'm not using that mod myself).

You need to use a few of the little power conduits to sort of bend the wire in through a doorway or window. http://i.imgur.com/z8IUQMk.jpg

What do you mean? Does the camera not move up and down with the right/left mouse buttons?

Are you using Oni Vanilla Hair Re-Texture? If you are, try removing it or using the vanilla color/new alpha version.

I watched a video once saying that you had to use the launcher to physically change the overall game quality to low, then reset all your other settings back to their higher settings. Start at 1:17. This will alter your .ini files so make sure you make backups just in case.

I posted this in your other thread but I'll copy it here too in case you don't check there. === From what I can find, the i7 930 is a quad core, not an 8 core (though it does have 8 threads with hyperthreading). Anyway, iNumHWThreads= (despite what the name implies) should be set to the number of physical cores you have so change that to iNumHWThreads=4. You have two different uGridstoload settings. It's set to 9 in your Fallout4.ini and 5 in the Prefs. On top of that, your uGrids also seems a bit high for the engine. If you want it higher than the default 5, 7 would work while being more stable than 9. Changing it is a little more tricky though. Just lowering the value and trying to load your game will cause it to crash. If you do change uGrids to 7 (in both .ini files), also change: uGridsToLoad=7 uInterior Cell Buffer=64 uExterior Cell Buffer=64 You can also make a backup of the .ini files you have now and try playing with the config tool.

From what I can find, the i7 930 is a quad core, not an 8 core (though it does have 8 threads with hyperthreading). Anyway, iNumHWThreads= (despite what the name implies) should be set to the number of physical cores you have so change that to iNumHWThreads=4. You have two different uGridstoload settings. It's set to 9 in your Fallout4.ini and 5 in the Prefs. On top of that, your uGrids also seems a bit high for the engine. If you want it higher than the default 5, 7 would work while being more stable than 9. Changing it is a little more tricky though. Just lowering the value and trying to load your game will cause it to crash. If you do change uGrids to 7 (in both .ini files), also change: uGridsToLoad=7 uInterior Cell Buffer=64 uExterior Cell Buffer=64 You can also make a backup of the .ini files you have now and try playing with the config tool.

This is just a shot in the dark (lol) but in either Fallout4.ini or Fallout4_custom.ini, do you have an altered fLightLODFadeMin/fLightLODFadeMax setting? The defaults should be: fLightLODFadeMin=0.0000 fLightLODFadeMax=3000.0 In the same file there's also: fSpecularLODFadeStart=0.0900 fSpecularLODFadeEnd=1.0000 fRefractionLODFadeEnd=0.0300 fRefractionLODFadeStart=0.0250 fEnvmapLODFadeStart=0.0900 fEnvmapLODFadeEnd=0.1000

It almost sounds like the timescale problem like here. Open the console (if you're in survival mode and can't, use this mod to enable it) and type "show timescale". If the value is 0, then that's probably the cause. You can change it by using "set timescale to XX". The default was 20. If that was your problem and your screen is already black then try following my directions further down the thread.

For a problem like this, you may want to also post the files present in your Scripts folder. If there's a bunch, just take a screenshot so you don't have to type them all out. Immersive Generic Dialog is the update to Immersive Settler Dialog though, so disable the settler one.