Multicolored/Rainbow Texture Bug?

[Deleted6850917User]

OK so I've found older posts regarding this bug. It seems to have been around for quite sometime, but there never truly was a fix for it. People propose to just extract the BA2 files of the mod that is effected. I haven't tried that solution yet but I am curious if anyone has any updated information regarding this bug? So far I've gathered that it is an issue with the game properly reading a BA2 file.

Here's an example of it affecting me now with the Bundle of Tape Mod:

https://i.imgur.com/QU3ty0z.jpg

 

I've also had it affect ShinyHaxor's RPG before he uploaded a new version and somehow solved it? What is the cause and how can I fix it?

 

 

Info Regarding my Current Load Order:

I am currently at a 231 Plugin limit. I've never accounted this mod until now and I suspect it's because I've almost always never went above 200 plugins. Only recently did I decide to add in more mods. Is this bug only affecting people with a plugin limit of above 200?

[Deleted3082751User]

i would also suggest extracting the affected mod(s) ba2 files. loose files take priority, so doing this would then ensure its not a texture priority issue (and this would also ensure that its not a texture overriding the gun in question although its very unlikely unless you happen to be using multiple texture mods that edit the same gun).

 

secondly i have never experienced this issue myself, and i have always ran my game at the max esp limit (255) its not an esp limit issue. quite a lot of them mods are weapons which are all in 4k quality (i always choose the max quality offered). and not a single weapon has ever had issues with textures.

 

the issue does look like texture corruption. or simply the texture is not loading. which could mean that the esp for the gun is not pointing to the correct texture path, or 2, the ba2 archive does not have the same name as as the gun

 

also is your Fallout4Custom.ini setup like this:

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

or Do you have Additional Information on this Line --> sResourceDataDirsFinal= <--

For example:

sResourceDataDirsFinal=Scripts/ Textures/ (Etc Etc)

if its the latter, remove the additional information and leave it as sResourceDataDirsFinal= (as this could also be the reason why the texture is failing to load)

Edited September 13, 2017 by Guest

[RebornZA]

I can tell you right now, this is NOT a mod issue, this can happen even in a completely vanilla game.

I can also tell you that the fix of extracting every texture file WILL most probably make your game laggy as hell. Unless you have a SSD I assume.

 

The more mods you add that have BA2's makes the issue more noticable only because there are MORE ba2's for the game to #### up reading, but I assure you this happens on vanila install too, might happen less.

I have tried every fix out there, and the only thing left to try is get my hands on a ver 1.00 Fallout 4 to prove that this is a newer issue (1.05 and after) (Never had this issue on same PC when I played in 2015)

Edited October 28, 2017 by jaid11111

[Ra3000]

I can tell you right now, this is NOT a mod issue, this can happen even in a completely vanilla game.

 

I can also tell you that the fix of extracting every texture file WILL most probably make your game laggy as hell. Unless you have a SSD I assume.

 

The more mods you add that have BA2's makes the issue more noticable only because there are MORE ba2's for the game to #### up reading, but I assure you this happens on vanila install too, might happen less.

 

I have tried every fix out there, and the only thing left to try is get my hands on a ver 1.00 Fallout 4 to prove that this is a newer issue (1.05 and after) (Never had this issue on same PC when I played in 2015)

 

I've been looking for a fix forever, and i've never had this problem with past Bethesda games and we'd have heard about it from skyrim. So what's different? Glad to hear according to Jaid that this is a vanilla problem.

[noraimironhand]

This problem is associated with AMD Radeon video cards.

The RX xxx cards are affected as well as some older cards.

AMD is aware of the problem and to date have no intention of fixing it (the RX series is being replaced).

The most I have been able to get from them is that it is caused by Directx optimizations that Bethesda chose to use that are incompatible with the cards memory Architecture.

So if any of you uber-hackers want to try to fix it. I recommend that you do an online search for AMD Rainbow.

 

Hopefully someone with experience in this area can make a patch for the card as the game engine probably can't be altered without serious blow-back.

 

I personally am tired of having this random glitch forcing me to quit then reload the game.

 

I have done the extract all bsa files fix and it extends the amount of time between glitches.

[AGreatWeight]

I've only had this issue happen once to me, on a previous (and older) gpu, the Radeon R9 280. Admittedly, due to the sheer amount of retexture mods I was using at the time (as well as heavily customized .ini edits to alter the uGridstoload etc) I was punishing the card pretty heavily, and it was running exceedingly hot. The rainbow bug/texture corruption appeared as a direct result of that.

Reverting to a previous save, dailing back the .ini tweaks, as well as removing numerous texture overhaul mods resulted in that particular bug disappearing. I'm not saying that this will be a solution for everyone, just that it's something to bear in mind if the rainbow bug appears in your game. Check your gpu temps.