Fallout 4 1.3 Update Now Official!

[UlithiumDragon]

In response to post #34615300. #34623920 is also a reply to 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.

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

[Ethreon]

 

 

 

In response to post #34615300. #34623920 is also a reply to 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.

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 prostitute will still be dead, and Gamebryo is SOOOOO dated at this point it's not even funny...

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

 

 

 

And unity5 is build on unity4 which is built on unity3 etc. All engines go through this. An engine that comes out and never gets newer versions means it's a bad engine. I'll take the gamebryo that allows me this freedom of modding and open world over your shiny engines that can only function inside limited, tiny rooms. Anyway, whatever you did to your game is your doing. Beth can change the damn textures as they please, and you'll have to deal with it.

[Madrock]

"Fixed an issue where the player could no longer get Preston as a companion"

 

I am pretty sure that was a feature.

[DarkTitanV]

In response to post #34580070. #34593695, #34611525 are all replies on 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:)

UlithiumDragon wrote: 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...)

I don't see how you ffing up a texture is Bethesda's fault, that's like me making a mod wrong, and causing me to CTD then cry to Bethesda claiming how their engine is bad because my mod wasn't working. If I were you; I'd just try and find the problem in YOUR textures, which YOU added, updates can cause breaks, and mature people would fix them to work with the new engine update, instead of crying to Bethesda about why your mod 'works' even though it clearly doesn't, then flaming Bethesda about their engine for it.

In a short:
It's pretty childish you hating on them because of your own f*** up, :/

[DarkTitanV]

In response to post #34410705.

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?

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

[featherhead021]

Mine can't even start up. On steam it just says Preparing to Launch Fallout 4....

[shinthomas]

In response to post #34580070. #34593695, #34611525, #34672095 are all replies on 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:)

UlithiumDragon wrote: 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...)

DarkTitanV wrote: I don't see how you ffing up a texture is Bethesda's fault, that's like me making a mod wrong, and causing me to CTD then cry to Bethesda claiming how their engine is bad because my mod wasn't working. If I were you; I'd just try and find the problem in YOUR textures, which YOU added, updates can cause breaks, and mature people would fix them to work with the new engine update, instead of crying to Bethesda about why your mod 'works' even though it clearly doesn't, then flaming Bethesda about their engine for it.

In a short:
It's pretty childish you hating on them because of your own f*** up, :/

Actually, if the mod was working just fine pre-patch it was very likely something the devs changed. But Bethesda is the publisher, not the the dev. So yea, it's not 'their' fault. But the devs likely changed a few things that might break some mods. That's what happens you get patches.

[thekhajitslayer83]

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? Edited February 20, 2016 by thekhajitslayer83

[MasterVin]

In response to post #34772665.

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?

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

[bben46]

@cassellcorey: Your post and the replies are now gone - this is NOT the place and you are guilty of an attempt to hijack a topic that has nothing to do with your problem - We actually have separate forums for each of the over 230 games we support. Post your problem in the proper forum - make a new topic of your very own ( no extra charge for that) and give some information - "It's broke" is totally useless for trying to get help.

 

Or, you could read the stickies and FAQs for whatever game you are using As that is one of many things you didn't tell us, Here is a generic 'How to ask for help' post from my own blog.

http://s1.zetaboards.com/bbenlibrary/topic/5686144/1/?x=0#post949222