Fallout 4 1.3 Update Now Official!

[Ethreon]

Suddenly new beta patch which adds some new items here and there. Wonder if they're new items or just copies already in the game files.

Also, DLC support.

[Fatalmasterpiece]

Still waiting for them to fix the hotkey weapon switching glitch...

 

but at least we will have more Meat Clutter soon! zzzz...

[Fatalmasterpiece]

In response to post #34772665. #34834180 is also a reply to the same post.

thekhajitslayer83 wrote: im having a problem where any mod weapon i download and install is invisible in the game happens with modded armor too.however mods that alter vanilla weapons seem to not be invisible in game i tried unistalling the modded weapons/armor and reinstalling but the issue persists i looked online and no one else seems to have the same problem as this? does anyone know how to fix it?

MasterVin wrote: I'm having the same problem...still looking for an asnwer

Sounds like you probably have installed the mod's files in the wrong folder. Check your file paths are correct.

Anyways this isn't the mod support forum so it's not the place to post requests for support.

[Fatalmasterpiece]

In response to post #34410705. #34672125 is also a reply to the same post.

RiOrus2 wrote: Still having CTD issues, at completely random times and locations.

So far, to try to rectify:

I've uninstalled all texture mods
deleted ini's and restarted game to create new.

Interestingly, doing this didn't create a fallout4custom.ini, only the fallout4.ini and fallout4prefs.ini. Incidentally, running the game without the fallout4custom.ini in the folder allowed for a stable gaming session for 2 or 3 hours, which is a vast amount more than the approx. 15 to 20 mins I normally get before CTD.

Obviously this would prevent me from using other mods but it's interesting it provided improved stability.

Anyone concur or explain?

DarkTitanV wrote: If you have Gore overhaul isntalled, update it, that is causing CTD. Just update it to v4.0

You shouldn't be having that many CTDs. Sounds like you have some bad mod installs. Texture mods will generally not cause CTDs like that. I would recommend a fresh install of the game after backing up your save files.

Anyways, this isn't the mod support forums :/

[Fatalmasterpiece]

In response to post #34615300. #34623920, #34624740 are all replies on the same post.

UlithiumDragon wrote:

 

 

 

In response to post #34580070. #34593695 is also a reply to the same post.

UlithiumDragon wrote:

*Sigh* I got bored of Fallout 4, and didn't bother trying to figure out WHY I was all of a sudden getting instant CTD's after the patch. Turns out it was one of my own damn mods - a bloody simple-ass texture mod...

I have no f*cking idea WHY THE HELL a simple "texture" would cause a game to violently implode, but as Bethesda games have been moving slowly towards MAXIMUM instability, who the f*ck knows...

I mean, ffs- it was just a simple recolor of the laser projectile from red to purple. It must be tied to the export settings I used in GIMP, though, since I have several other textures I've made that are in use that DON'T cause CTD's...

Either that, or the last patch changed how "gradients" work (which seems unlikely, as I have other mods installed that edit gradients...).

Eruadur wrote: So in short: you ff-ed up and you blame Bethesda for it.
Brilliant:)

Name one other situation where a bad texture would cause a game it VIOLENTLY EXPLODE, rather than just not show up, or not look right...

THis is NOT "my fault" - look, THIS is what was happening before when I had the encoding set incorrectly - the game just didn't render them correctly:

http://i.imgur.com/sBCAcUM.jpg

(He was supposed to be all white, no clue why not setting a compression type caused only certain parts of the coloring to change...)

 

 

 

Your modding is not officially supported, therefore whatever results it might incur are your fault only, as well as your own responsibility.

 

You are continuing to avoid my main question - how could a game be SO UNSTABLE that a *TEXTURE* would cause instant CTD's without even RENDERING said texture...?

>Because Bethesda game, and because Gamebryo.

KimberJ wrote: This is Creation Engine. Look it up on the wikipedia if you wana talk about it. I doubt anyone that read about it or worked with Skyrim/FO4 CE to make mods would make this claim that it's Gamebyro.

UlithiumDragon wrote: I just *KNEW* someone would call me out for calling it "Gamebryo".

It doesn't matter how many changes they made - the "Creation Engine" is still build ON TOP OF the Gamebryo Engine, and suffers from MANY of the same limitations and restrictions said engine possesses.

You can put some more makeup on the the body all you want, but that wh*%# will still be dead, and Gamebryo is SOOOOO dated at this point it's not even funny...

http://i.imgur.com/F2cqIOo.gif

Your gif of Todd Howard should be replaced by every Bethsoft fan who can't let go of whining about Gamebryo.

It's Bethesda's engine, who cares what it's called. The game runs stable for many people, myself included. If you installed some crap incorrectly it's your fault. No amount of whining is going to change that.

You wouldn't open up your PC chassis, pluck a single capacitor from your motherboard and then complain about how unstable your mobo is that it can't even handle losing a single little piece. Edited February 23, 2016 by Fatalmasterpiece