MC-43010Non-standard texture resolutions cause rendering errors with mipmap
This occurs whenever the dimensions of a texture are a non-square number (24 x 24) or any odd-numbered resolution (7 x 7), mipmaping is set to any non-zero value, and anisotropic filtering is set to 0.
At significant distance, any face with a strongly acute angle to the player will simply not render correctly, making the terrain rendering appear choppy. For odd-numbered resolutions, this may also cause the edges of the tiles to disappear even at relatively close distances.
The easiest way to recreate the issue is to set mipmaping to 4 and anisotropic filtering to 0 with any pack that uses non-square-numbered block resolutions. Although this problem is visible with any non-zero mipmaping setting, it is most easily visible when set to 4. A super-flat world demonstrates the effect most dramatically.
Environment
Java 7 Update 40 (64-bit), Window 7 Home Premium 64-bit
Attachments2
Created Issue:
Non-standard texture resolutions cause rendering errors with mipmap
This occurs whenever the dimensions of a texture are a non-square number (24 x 24) or any odd-numbered resolution (7 x 7), mipmaping is set to any non-zero value, and anisotropic filtering is set to 0.
At significant distance, any face with a strongly acute angle to the player will simply not render correctly, making the terrain rendering appear choppy. For odd-numbered resolutions, this may also cause the edges of the tiles to disappear even at relatively close distances.
The easiest way to recreate the issue is to set mipmaping to 4 and anisotropic filtering to 0 with any pack that uses non-square-numbered block resolutions. Although this problem is visible with any non-zero mipmaping setting, it is most easily visible when set to 4. A super-flat world demonstrates the effect most dramatically.
Environment
Java 7 Update 40 (64-bit), Window 7 Home Premium 64-bit
Attachments2
- Unresolved
- Open
- Unconfirmed
- graphic graphic_settings mipmap nonstandard oddvalues render texture visual_bug
- 1.6.4
Please update the affected versions. I can confirm this for 1.7.10 and 17w27b using the PrimeCraft resource pack.
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
Mog (Ryan Holtz)A comment with security level 'global-moderators' was removed.
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
What's the point of using non power-of-2 resolutions with active mipmapping ?
@Kumasasa: Because it looks nice? I don't see what you're getting at.
Some resource pack artists may want to use a resolution that falls in-between the standard resolutions, and Minecraft's mipmapping feature has a problem with that currently. No self-respecting resource pack creator wants to tell people not to use their pack because of a rendering issue. A lot of us were psyched about the new RP format because it would allow us to do things like this.
To put it another way: if all texture resolutions are going to be supported by Minecraft, then all texture resolutions need to be supported by Minecraft. It's really that simple, at least to me.
I just wanted to know if there is a concrete application for this or if it's a matter of principle.
Keep in mind that implementing your request in Minecraft may break the compatibility with older graphics cards (because ARB_texture_non_power_of_two
is implemented since OpenGL 2.0 : http://www.opengl.org/registry/specs/ARB/texture_non_power_of_two.txt ) and even if the capabilities claim supporting, the hardware may not support it ( http://aras-p.info/blog/2012/10/17/non-power-of-two-textures/ ) and falls back to software rendering -> Complaining about FSP drop.