Jump to content

Photo

New to Fallout 4 modding, game recently crashing

fallout 4 ctd crash load order terminal ready weapon desktop advice tips

  • Please log in to reply
6 replies to this topic

#1
Lazarus91

Lazarus91

    Stranger

  • Members
  • Pip
  • 9 posts

Hey people,

 

Currently new to the world of modded Fallout 4 after coming over from modded Skyrim. Things have been going pretty good, still new to the game and such but i've run into a problem I haven't been able to figure out.

 

Whenever I try to access a terminal or ready/unholster my weapon, my game crashes to desktop. I've tried to narrow down my issue by disabling my .esp files and cleaning my existing save file, but no luck. I've also done a fresh install for Fallout and my mods as well. Still nothing, I have about 72 mods in total, so I doubt it has anything to do with having too many. I currently use Vortex for my mod manager and use the loot plugin within it to organize my load order.

 

All my mods are currently up to date with the lastest versions. My game is also up to date and currently running 0.6.21 of F4SE.

 

My mod list (in order oldest to newest):

Spoiler

 

My current plugins load order:

Spoiler



#2
HeyYou

HeyYou

    Resident poster

  • Supporter
  • PipPipPipPipPip
  • 9,307 posts

Live Dismemberment - BrutalNoHeadshots.esp
Live Dismemberment - LiebermodeNoHeadshots.esp
Live Dismemberment - RegularNoHeadshots.esp

 

I think you only want to use one of those.

 

Aside from that, I am not seeing why your game should crash when it does...... Did you do anything for archive invalidation? Or version checking?



#3
Lazarus91

Lazarus91

    Stranger

  • Members
  • Pip
  • 9 posts

Live Dismemberment - BrutalNoHeadshots.esp
Live Dismemberment - LiebermodeNoHeadshots.esp
Live Dismemberment - RegularNoHeadshots.esp

 

I think you only want to use one of those.

 

Aside from that, I am not seeing why your game should crash when it does...... Did you do anything for archive invalidation? Or version checking?

No luck with the .esp you mentioned. And not to my knowledge, the only other thing I did outside of these mods was update the .ini files to allow mods to be used by the game.

Version wise, all mods are up to date and so is the game. The game is at 1.10.163 and f4se is at 0.6.21



#4
shaggy08251993

shaggy08251993

    Fan

  • Members
  • PipPipPip
  • 424 posts

As someone who has had to do WAY more troublshooting for mods than anyone should ever have to in a single life time, change up your enable/deselecting method. First, make sure vanilla Fallout 4 runs fine before installing any mods.

 

Then, for the sake of time, don't enable/disable mods one at a time, unless you want to waste 5 years of your life lol. Break them into halves, then quarters, and so on.

Example: install the first half of all your mods, start a NEW game. It HAS to be a new game. If it's something related to a script, the only way for changes to take effect are via new games. To save time from going through the entire intro, use the "coc" console command to warp to somewhere that has a terminal. "coc sanctuaryhillsext" is a good one. Then "player.setav speedmult 300" so that you move faster (since your character will be stuck at the default walk speed of the intro section).

Anyway, if everything works, then you know the first half of your mods are good. Disable them, and enable the second half. Rinse and repeat. If it crashes, then you know it's something in the second half. So then break the second half into two more halves, and test each of those.

 

Repeat until you narrow it down. Once you know which one it is, you can try opening it in F4Edit to see if a conflict is causing it. If so, fix it. If not, just delete the mod.


Edited by shaggy08251993, 12 July 2020 - 07:27 PM.


#5
Lazarus91

Lazarus91

    Stranger

  • Members
  • Pip
  • 9 posts

As someone who has had to do WAY more troublshooting for mods than anyone should ever have to in a single life time, change up your enable/deselecting method. First, make sure vanilla Fallout 4 runs fine before installing any mods.

 

Then, for the sake of time, don't enable/disable mods one at a time, unless you want to waste 5 years of your life lol. Break them into halves, then quarters, and so on.

Example: install the first half of all your mods, start a NEW game. It HAS to be a new game. If it's something related to a script, the only way for changes to take effect are via new games. To save time from going through the entire intro, use the "coc" console command to warp to somewhere that has a terminal. "coc sanctuaryhillsext" is a good one. Then "player.setav speedmult 300" so that you move faster (since your character will be stuck at the default walk speed of the intro section).

Anyway, if everything works, then you know the first half of your mods are good. Disable them, and enable the second half. Rinse and repeat. If it crashes, then you know it's something in the second half. So then break the second half into two more halves, and test each of those.

 

Repeat until you narrow it down. Once you know which one it is, you can try opening it in F4Edit to see if a conflict is causing it. If so, fix it. If not, just delete the mod.

So I downloaded a new save game that takes place just before exiting the vault. Just for kicks I left all the mods on and installed that I mentioned prior. Everything is working normally; terminals, weapons and so on. The game doesn't just crash, so it might be my original save file. This leads to a new problem maybe since i've tried cleaning my save file to fix this but didn't have any luck.



#6
HeyYou

HeyYou

    Resident poster

  • Supporter
  • PipPipPipPipPip
  • 9,307 posts

 

As someone who has had to do WAY more troublshooting for mods than anyone should ever have to in a single life time, change up your enable/deselecting method. First, make sure vanilla Fallout 4 runs fine before installing any mods.

 

Then, for the sake of time, don't enable/disable mods one at a time, unless you want to waste 5 years of your life lol. Break them into halves, then quarters, and so on.

Example: install the first half of all your mods, start a NEW game. It HAS to be a new game. If it's something related to a script, the only way for changes to take effect are via new games. To save time from going through the entire intro, use the "coc" console command to warp to somewhere that has a terminal. "coc sanctuaryhillsext" is a good one. Then "player.setav speedmult 300" so that you move faster (since your character will be stuck at the default walk speed of the intro section).

Anyway, if everything works, then you know the first half of your mods are good. Disable them, and enable the second half. Rinse and repeat. If it crashes, then you know it's something in the second half. So then break the second half into two more halves, and test each of those.

 

Repeat until you narrow it down. Once you know which one it is, you can try opening it in F4Edit to see if a conflict is causing it. If so, fix it. If not, just delete the mod.

So I downloaded a new save game that takes place just before exiting the vault. Just for kicks I left all the mods on and installed that I mentioned prior. Everything is working normally; terminals, weapons and so on. The game doesn't just crash, so it might be my original save file. This leads to a new problem maybe since i've tried cleaning my save file to fix this but didn't have any luck.

 

Yeah, If the game still crashes after cleaning, but, doesn't with a different save file.... I think that one is toast.



#7
Lazarus91

Lazarus91

    Stranger

  • Members
  • Pip
  • 9 posts

 

Yeah, If the game still crashes after cleaning, but, doesn't with a different save file.... I think that one is toast.

I kind of had a feeling, i'm going to try to save it but more than likely i'll just have to start a new game. Oh well, happens. Thanks and i'm still open to tips from anyone







Also tagged with one or more of these keywords: fallout 4, ctd, crash, load order, terminal, ready weapon, desktop, advice, tips

Page loaded in: 1.091 seconds