-jason

This problem still persists as of 1.21.10 in RTX, deferred rendering, and even with shaders off. I've attached three screenshots of my pack, JG RTX v1.0.0, experiencing this bug on the yellow wool texture. You can see the MER map of another texture bleed into the base color map of the wool texture.

The textures affected shift based on what is present in the terrain atlas. I believe the problem stems from the addition of the decorated pot texture to the terrain atlas. The shaders are not unpacking the texture sets correctly when this block is present in the atlas. I assume it is because the decorated pot texture is 2:2.

Here is a workaround:

Before starting Minecraft, browse to com.mojang\minecraftpe and look for the file options.txt. Find gfx_raytracing: and set it to 0. Try opening a world with RTX off. Let the textures load, then re-enable RTX with the semicolon key while in game. If RTX comes on, everything will be glossy. Close and reopen the world and the RTX textures will hopefully start working at that point.

I agree with MadHatter. It's very discouraging to see a feasible feature like this unsupported. The short response from Mojang makes me think this issue was prematurely closed.

How would this interfere with a resource pack stack? Wouldn't a resource pack without block variants be able to override one without variations? Example:

Lower texture pack

{
  "texture_data": {
    "dirt": {
      "textures": [
        {
          "path": "abc"
        },
        {
          "path": "xyz"
        }
      ]
    }
  }
}

Higher texture pack

{
  "texture_data": {
    "dirt": {
      "textures": "123"
    }
  }
}

One could then merge this JSON data to get the dirt texture set path equal to "123." Suppose the 123.texture_set.json file didn't have a MER or normal map defined: Minecraft would not show base layer "123" with the MERs and normal maps from the "abc" or "xyz" textures in the lower resource pack.

So what's the problem?

Please reconsider this issue! Texture variations in Minecraft with RTX would be a game-changer for resource pack developers.

This affects a resource pack I've created too. You can see the source on GitHub:

https://github.com/jasonjgardner/jg-rtx/blob/master/development_resource_packs/JG-RTX/textures/blocks/soul_torch.png

https://github.com/jasonjgardner/jg-rtx/blob/master/development_resource_packs/JG-RTX/textures/blocks/soul_torch_mer.png

https://github.com/jasonjgardner/jg-rtx/blob/master/development_resource_packs/JG-RTX/textures/blocks/soul_torch_normal.png