TEXTURE_OPTIMIZATIONS striping issue

[DarianLStephens]

I'm not sure if this is a mod interaction or what, but with specifically this option enabled, I see this: When I turn it off, it's normal:

[DarianLStephens]

Seems to happen with most any mod installed. Tested with Botania and Thaumcraft separately, and Botania made the Gravel have the lines, while Thaumcraft + Botania made Sand have the lines. The weirdness makes me suspect something bigger is going on, unrelated to the actual mods, so for now I'll just leave that option off despite of the performance it brings, same with the Item Voxellizer problem reported in my other issue.

[FalsePattern]

This is a known buggy interaction between anisotropic filtering and mipmaps that gets exaggerated by the packing algorithm. If you set anisotropic filtering to 0, it should stop.

[DarianLStephens]

That's the weird thing, though... I do have Anisotropic Filtering disabled! And it doesn't show up with FalseTweaks itself, or even vanilla, I need to add some other mods to the mix. Unless that part's because there are more textures, and it's all being packed in to a single atlas or something?

[DarianLStephens]

Proof or something:

[FalsePattern]

Does it also happen with mipmaps set to 0?

[DarianLStephens]

Nope, but man does the game look bad:

I've also only seen Anisotropic Filtering cause problems with animated textures, never static. This is a new thing. Though it would be nice if AF could be fixed, because it does make stuff look a lot better. I live without because of the water thing, but if it could... I dunno, ignore water and other animated textures, at least? It would be appreciated.

[DarianLStephens]

Huh, as an experiment, this is what it looks like with maxed-out Mipmaps and Anisotropic Filtering: I don't know if that says anything, but it's there! The greyness on terrain is something I've never seen before back when I used Anisotropic Filtering more.

And here's Mipmaps + Anisotropic Filtering with FalseTweaks' TEXTURE_OPTIMIZATIONS disabled again:

[DarianLStephens]

For the heck of it, I also loaded up Vanilla 1.7.10 to test Anisotropic Filtering, and the incorrect color-change is there, too! But it's only visible on higher render distances, which explains why I never noticed it before since I used to always play on 8.

[DarianLStephens]

Found that the lines also seem to be fixed with 'MIPMAP_FIX' disabled. How unusual.

[AxolotlAccount]

Disabling MIPMAP_FIX from falsetweaks.cfg and disabling Anisotrophic Filtering from OptiFine options fixed the issue for me.