Fallout 4 1.3 Update Now Official!

[RiOrus2]

For me this causes CTD after 2 minutes of playing, happened 7 times last night at university point. Never had any CTD up until this point with 60+ mods installed.

Not installed / uninstalled / changed any mods. In fact I'm having trouble downloading mods from Nexus right now anyway, weirdly.

 

Specs if interested:

i7 4770K at 4.2GHz

2 x EVGA 980Ti in SLI

Z87 Sabretooth Mobo

Crucial M500 SSD

WD Blue 2TB HDD

Amongst other things.

 

Edited February 2, 2016 by RiOrus2

[RiOrus2]

In response to post #34088275.

ahycb wrote: I updated f4se, ran LOOT, and then used the f4se launcher to launch the game (as I always do). I have 50 mods installed. I played for about 10 minutes with no problems so far.

what interests me is how the hell you managed to get LOOT working for fallout 4? Edited February 2, 2016 by RiOrus2

[Skitkjell]

Sadly the Gore Overhaul isn't the only mod causing issues. I'm running little-to-no gameplay changing mods, and mostly (around 100+ -.-) retexture mods. And some settlement mods. I get a CTD as soon as I enter build mode. I've tried disabling the settlement mods to no avail. I'm just going to revert back to 1.2 until this has been sorted. Damn shame! It was a pretty hefty patch, with LOADS of improvements! First time a Bethesda-patch has screwed mods up on this scale ever :D

[Skitkjell]

In response to post #34088275. #34095225 is also a reply to the same post.

ahycb wrote: I updated f4se, ran LOOT, and then used the f4se launcher to launch the game (as I always do). I have 50 mods installed. I played for about 10 minutes with no problems so far.

RiOrus2 wrote: what interests me is how the hell you managed to get LOOT working for fallout 4?

Same here. It's all weird with my FO4 x) I've resorted to manually sorting them.

[swissper2]

In response to post #34071015. #34071450, #34071620, #34071680, #34072505, #34072540, #34072595, #34073190, #34073450, #34073500, #34074510, #34084490, #34084545, #34085065, #34088565, #34089440, #34090300, #34091345, #34091585, #34092545, #34092940, #34093350, #34093820, #34094175 are all replies on the same post.

Nordland1 wrote: For me, this fixed the CTD!

(I got CTD 5-10 seconds after the game started.)

And after some research in my mod list i found that "The Gore Overhaul" was the culprit.
I still got the mod activated in NMM but I renamed the "gore" folder (the mods texture folder) so it won't load. And after that no more CTD's.

arroya wrote: so what folders name did you change again? I want to try this. I am running EBT as well

Nordland1 wrote: Sorry I mixed up two mods.
For me it's "THE GORE OVERHAUL" mod who was causing the CTD.
Not "Enhanced Blood Textures".

I renamed the folder "Gore" by just adding a Z (zgore).
You will find the folder in ".../Data/Textures/Gore"

(I edited my first post with my new findings)

arroya wrote: ok just renamed it. because i have gore overhaul as well lets see if it works Ill send you a pm I dont want to clog the thread. Check your messages

MadveD12 wrote: I also disabled "The Gore Overhaul" and CTD 5-10 seconds after the start of the game disappeared.

iiicragiii16 wrote: It worked! Thank you sir

Panaorios wrote: Thank you so much. This worked for me!

grapser wrote: Thanks for the fix. XD

Nordland1 wrote: Glad that I could help! :)

MickeyMcE wrote: Interesting I uninstalled "The Gore Overhaul" mod after reading this and it appears to have fixed my ctd as well for now. Good find, I was just getting ready to go through my mods and play the uninstall reinstall game. Thanks for saving me the headache.

St4rkill3r wrote: Worked here too.At the start i was unable to play 5 mins long without a ctd.Now i did the rename of the folder and i played like 30 mins without problems so far, thanks a lot sir for the tip!

Centerman wrote: Uninstalled Gore Overhaul and this worked. It corrected the CTD 5-10 seconds after game start. I still get a random CTD during what seem to be bloody battles. I'm disabling Mods little by little to find the additional culprit.

billxsand wrote: Ugh thank you so much I should have checked the nexus first... uninstalled and reinstalled everything multiple times, lololol

manofglory wrote: You sir! win the prize

scag318 wrote: work for me! THX!

Desie wrote: What if we don't use that mod? I see everyone talking about this but I don't use it. Should I install that mod and then do what you said? ;aifejwakfa;oiewajfldskja CTDDDDDDDDDDDDD

jerryh72 wrote: People who don't have that mod have the same ctd problem , this same problem came with the last update not just this one . If even the first update came out before i already put to many hours in too be able get a refund on this s#*! game , but no they let you play a stable version a few weeks before making it worse instead of better . If they want to fix it they should start by either using NewVegas or skyrims already working controls , dialog , animations , using the same format so we could just copy past mods from Skyrim too Fallout 4. No they use a completely different language , as if to say F;[]=-.u to the players modders and the Nexus mod site !

blackmumba1 wrote: Yeah, worked for me too, which is a relief because I was thinking I would have to reload the game and play vanilla FO4. Though, the update also revived Swan for some reason, not sure why, but I got to kill him again, so there's that

Centerman wrote: The Gore Overhaul caused a quick CTD. Got rid of it but I still crash but now only in a firefight with Raiders or Super Mutants. Disabled every Mod and .esp but still crashed during a fight. Deleted the .ini files and ran plain Vanilla FO4. Game did not crash and ran well. I suspect it's a stray texture, mesh, or something that is in the game directory.

TheFinestSake wrote: THANK YOU!

hanageboubounosuke wrote: You are a hero.

julio131 wrote: but...but I don't use that MOD and still get CTD 5-10 seconds after the game started. :(

tardmehigh wrote: Thank you so much! Have used like 2,5 hours trying "this and that" with no luck. Again, thank you

Nordland1 wrote: If you still get CTD's with mods installed then try with disable the whole Textures folder without uninstalling the mods.
Beacuse (as far as I know) there is no mods that runs with scripts yet, so there is a big chance that it is textures or meshes that are causing the CTD's.

I'm not an expert on these things but this is how I found out that it was the Gore Overhaul that was causing problems for me.
I have been playing for about 1h and still no CTD.

Confirmed. Fixed the CTD for me also.

[Eruadur]

In response to post #34082170.

Nostalgiaheart wrote: This really suck - everytime Bethesda does something - something breaks.......I should have waited before buying.

Or: should have waited installing mods ( third party software ) . Because I'm sure the game runs perfectly without any mods at all, right ?
Blame Bethesda all you want....

[Eruadur]

In response to post #34089375. #34090240, #34090460, #34090640 are all replies on the same post.

Desie wrote: Is there a way to revert back before the update? I have 200+ mods I'm not willing to go through...Jesus. The humanity.

russw1138 wrote: ONE - you should be applauded for figuring out how to make 200+ mods work at all. TWO - if you are smart enough to figure out how to get 200+ mods working you should have been smart enough to make steam work in offline mod and thus not get the patch

nik0li wrote: What a useless and douchy comment. Well done russ.

russw1138 wrote: douchy? maybe... useless? not so much. what is useless are screaming at the sky posts about how auto update sucks when the simple work around is to run steam in offline mode to prevent getting patches your not ready for

+1 Russ

[brokefoot]

For many of us, we use mods that replace textures. And for many of us, we edit our ini files so that these mods can function in-game. But for most of us, the latest patch has messed up our game in some way. Why is this so and how do we fix it ? Well...

 

You need to remove your previous ini files and use the launcher once to create new ones.

-Why ? Because there are new additions and...

 

Make sure any personal Fallout4.ini edits are moved to Fallout4Custom or your game won't load.

-Why ? Because with the new patch, most if not all additional lines in the Fallout4.ini will lead to CTD.

 

Look through your retexture mods, removing them one by one until your game loads.

-Why ? There are a few mods out there that use 'bogus' texture formats and will result in CTD since the new patch.

 

For me, the culprits were my edits to the Fallout4.ini instead of being in Fallout4Custom.ini and also a really old retexture mod that changed the color of laser beams.

 

Yes, seriously. Just those two little things. I'm back to a fully functioning game w/ a total of 84 'mods' (28 of which are plug-ins).

Edited February 2, 2016 by brokefoot

[ryuuou]

In response to post #34088275. #34095225, #34095350 are all replies on the same post.

ahycb wrote: I updated f4se, ran LOOT, and then used the f4se launcher to launch the game (as I always do). I have 50 mods installed. I played for about 10 minutes with no problems so far.

RiOrus2 wrote: what interests me is how the hell you managed to get LOOT working for fallout 4?

Skitkjell wrote: Same here. It's all weird with my FO4 x) I've resorted to manually sorting them.

You can get working LOOT from here: http://www.nexusmods.com/fallout4/mods/5310/?

[Knowidee]

250+ Mods played last night, All working

 

I did however uninstall any MODs that were / are bugfix based:

 

simple bug fixes

companion bugfixes

Many Perk Fixes (incl. Makanars Perks)

 

Basically, having MOD manager open with the patch notes and removing all that is addressed within the patches, should eliminate any conflict