Fallout 4 Beta 1.3 Update

[SharraShimada]

beth are just a pathetic now trying to block mods so everyone is forced to use their shitty bethesda.net BS site later so they van control all mods! i think it's time we started boycotting all patches from here on. perm lock your steam into offline mode

 

Bethesda disables mods for BETA!!!! patches with very good reason. They want the feedback on theyr work, and no complaints on "oh my... whiney scream, my mod xyz does not run with a BETA-patch". So, if you dont like it, dont use it. Yes it is that easy. Beta patches are NOT made for everone to use. You have to know what your are doing, and if not, screw yourself, but dont bother others, if someting, not designed for patch3 is not working.

[ZombieTech]

@SharraShimada Problem is, from everything I've read, Bethesda were proudly boasting that this specific new beta-patch would NOT interfere with mods... and it instead interferes quite massively. (Not to mention, in the early goings of the initial release of Fallout 4, there were some major issues, that so many were told was fixed by getting the beta-patch... now it turns out the beta-patch is becoming the cause rather than the solution.)

Quoted straight from my NMM: "Total Plugins: 152 | Active Plugins: 145 | Total Mods: 270 | Installed Mods: 195 | Active Mods: 191"... there's no way in hell, I'm going to go through each and every single mod to see which one is conflicting and which ones I have to disable. If Bethesda can't patch without breaking mods, then I'm fine with the game as is... haven't had too many issues. Only real issues is an occasional conflict with mods causing a CTD, or loading too much into one cell also causing a CTD... other than that, can't recall any real major issues I've had or run into. -_- *shrugs*

Edited January 17, 2016 by ZombieTech

[NexusFiles]

Is the beta patch worth it?

[HolyDeath3000]

I did reinstall of all textures mods that I had. And so far with latest beta patch not a single crash yet. This is from simply loading my save game as well. Yesterday with the previous 1.3 beta patch it would crash on many of the texture mods. Also I should point out that load times is back to where I had it before Beta 1.3. It's not that long anymore :smile:.

 

I speak of Beta 1.3.47 For those who haven't realized new update was today.

 

 

The amount of mods Installed are 92 Mods and 93 Plugins enabled.

[Varsy]

when i load my game after updating (i was in Diamond City) i tried FT to Sanctuary, then CTD happends. But when i just tried to leave Diamond City it happens over and over again. I switch off load of mods, all blood overhaul/texture mods, eyes mods and nothing happend..

[Gilibran]

I think people are overreacting a bit on the whole mod issues with each beta patch. Though the game is being modded does'nt mean Bethesda supports it. It's very simple, as long as the official modding tools for Fallout 4 are not released yet they do not have to take modded games into account when they make a patch. The patch is meant for a vanilla FO 4 not a modded one at this point.

 

Now they are not stupid and know there's already tons of mods out, so they probably do think about that when they make a patch and try not to screw things up, but honoustly they really do not have to at this point. It's a bit early to think they do it because they want to monopolize modding imho.

[HolyDeath3000]

I think people are overreacting a bit on the whole mod issues with each beta patch. Though the game is being modded does'nt mean Bethesda supports it. It's very simple, as long as the official modding tools for Fallout 4 are not released yet they do not have to take modded games into account when they make a patch. The patch is meant for a vanilla FO 4 not a modded one at this point.

 

Now they are not stupid and know there's already tons of mods out, so they probably do think about that when they make a patch and try not to screw things up, but honoustly they really do not have to at this point. It's a bit early to think they do it because they want to monopolize modding imho.

 

I have to agree. I found out that only one mod so far out of my 100 something mods have caused CTD's in game. From reading through Steam Forums and official Fallout 4 forums on Bethseda site, people have crashed at specific points in the game with only vanilla game. No mods used at all.

 

I should point out that if you run Debris setting on max settings, from what I have read, it has caused crashes in specific areas I believe. I distinctively remember reading it about one of the settlements actually that is some manor of sorts.

[steve40]

The beta patch works terrific on my game. It eliminated the lag spikes I was getting in areas like Boston Commons and Swan Lake. This fix alone makes the update worthwhile for me!

 

I did get CTDs on loading my saves, but it was due to Gore Overhaul having a corrupted texture file (gorebasebits_s.dds), and re-saving the texture in the correct format (3Dc) eliminated the CTDs. That is the modder's fault, not Bethesda's.

 

There is nothing broken with Invalidate Archives after the beta patch, it still works, as do all of the 30 or so plug-in mods and many many hires texture mods that I'm using (after fixing Gore Overhaul of course). The beta patch did not disable any of my mods. It did not mess up my ini files.

 

Removing the Invalidate Archives setting will cause a lot of your mods to be overridden by default files, hence eliminating whichever badly made mod was causing your crashes. The suggestions that Bethesda is nefariously sabotaging your mods is simply defamatory and ignorant. Really folks, we don't need this sort of misinformation in the modding community.

Edited January 21, 2016 by steve40

[bladexdsl]

 

beth are just a pathetic now trying to block mods so everyone is forced to use their shitty bethesda.net BS site later so they van control all mods! i think it's time we started boycotting all patches from here on. perm lock your steam into offline mode

 

Bethesda disables mods for BETA!!!! patches with very good reason. They want the feedback on theyr work, and no complaints on "oh my... whiney scream, my mod xyz does not run with a BETA-patch". So, if you dont like it, dont use it. Yes it is that easy. Beta patches are NOT made for everone to use. You have to know what your are doing, and if not, screw yourself, but dont bother others, if someting, not designed for patch3 is not working.

 

oh yeh that how come it wipes your plugins.txt in the current official patch unless you make it read only explain that?!

Edited January 21, 2016 by bladexdsl

[HolyDeath3000]

 

 

beth are just a pathetic now trying to block mods so everyone is forced to use their shitty bethesda.net BS site later so they van control all mods! i think it's time we started boycotting all patches from here on. perm lock your steam into offline mode

 

Bethesda disables mods for BETA!!!! patches with very good reason. They want the feedback on theyr work, and no complaints on "oh my... whiney scream, my mod xyz does not run with a BETA-patch". So, if you dont like it, dont use it. Yes it is that easy. Beta patches are NOT made for everone to use. You have to know what your are doing, and if not, screw yourself, but dont bother others, if someting, not designed for patch3 is not working.

 

oh yeh that how come it wipes your plugins.txt in the current official patch unless you make it read only explain that?!

 

 

Because they want people to not edit plugins for the first year so they can get legit feedback about the game that needs fixes. They made it clear that mods were not supported for the first year. And considering the recent updates being beta, of course they are going to try to lock modding for the time being. It's not to sabotage but to make it less likely to be modded and easier to fix bugs.