I'm not really sure how this is even possible, but:
Here's MC with no mipmapping and no anisotropic filtering (AF):
Here's with only AF turned on (16x):
Not much noticable difference in this scene. And with only mipmapping turned on (4x):
The grass and other transparent textures suddenly have darker, more jagged edges around them. And with both AF and mipmapping turned on:
With both options on, suddenly two new problems appear. In the very distance, moire patterns have shown up, the very thing mipmapping is designed to eliminate. Also if you look closely at the top of the tall grass near the middle, there are black lines at the edge of what would be the bounding box. They don't appear on nearby grass, only further away ones, meaning ones that are using mipmap LOD1+.
Here's another scene that shows why playing with both options off isn't perfect. This is with both options off:
Notice the moire patterns on the sand and water. Now with mipmapping turned on:
Moire patterns are gone, mipmapping did it's job, but again the transparent textures have gotten darker and more jaggy. And with both AF and mipmapping on:
Black bands/moire patterns have shown up in the water and sand further out, making things much worse.
Here's the same scene without a resource pack, options turned off:
And both turned on:
A fairly good improvement. The cactus has developed holes in the model and there are moire patterns in the extreme distance in the sand, but most of the problems seen with a resource pack aren't present.
This is all on a fresh install of minecraft, no mods whatsoever, not even optifine or forge. And no, optifine doesn't fix the issue. So what's going on here? Didn't 1.7 do away with the texture atlasing to (at least I'm guessing, I don't know the actual motivation behind the change) allow mipmapping to work? Why do these features only seem to work for the default super-low res textures and not with resource packs? And no, the resource pack is not using the old atlasing format, all the textures are individiual files.
Tech specs incase they're of any importance:
MC 1.7.10, using MultiMC launcher
Resource pack is Sphax x64 for MC17
Nvidia GeForce GTx 570, driver version 337.88
Windows 7 64 bit
Java 1.7.0_67 64 bit
I think it might be because of the resource pack, but i don't play with Antostropic Filtering / Mipmapping that often.
EDIT: Nevermind, saw the other pics, i have no idea how those things work
Rollback Post to RevisionRollBack
I support these threads:
To post a comment, please login or register a new account.
Here's MC with no mipmapping and no anisotropic filtering (AF):
Here's with only AF turned on (16x):
Not much noticable difference in this scene. And with only mipmapping turned on (4x):
The grass and other transparent textures suddenly have darker, more jagged edges around them. And with both AF and mipmapping turned on:
With both options on, suddenly two new problems appear. In the very distance, moire patterns have shown up, the very thing mipmapping is designed to eliminate. Also if you look closely at the top of the tall grass near the middle, there are black lines at the edge of what would be the bounding box. They don't appear on nearby grass, only further away ones, meaning ones that are using mipmap LOD1+.
Here's another scene that shows why playing with both options off isn't perfect. This is with both options off:
Notice the moire patterns on the sand and water. Now with mipmapping turned on:
Moire patterns are gone, mipmapping did it's job, but again the transparent textures have gotten darker and more jaggy. And with both AF and mipmapping on:
Black bands/moire patterns have shown up in the water and sand further out, making things much worse.
Here's the same scene without a resource pack, options turned off:
And both turned on:
A fairly good improvement. The cactus has developed holes in the model and there are moire patterns in the extreme distance in the sand, but most of the problems seen with a resource pack aren't present.
This is all on a fresh install of minecraft, no mods whatsoever, not even optifine or forge. And no, optifine doesn't fix the issue. So what's going on here? Didn't 1.7 do away with the texture atlasing to (at least I'm guessing, I don't know the actual motivation behind the change) allow mipmapping to work? Why do these features only seem to work for the default super-low res textures and not with resource packs? And no, the resource pack is not using the old atlasing format, all the textures are individiual files.
Tech specs incase they're of any importance:
MC 1.7.10, using MultiMC launcher
Resource pack is Sphax x64 for MC17
Nvidia GeForce GTx 570, driver version 337.88
Windows 7 64 bit
Java 1.7.0_67 64 bit
EDIT: Nevermind, saw the other pics, i have no idea how those things work