When creating a pack, A PBR texture cannot be used inside of the texture variants or it loses it PBR properties. This has nothing to do with multiple pack or inter operability as the original ticket was closed upon. In 1 pack you can in the block definitions json file refer to the same target textures for 2 blocks. If you define a block json file. And you use variants the Physical Based Rendering objects are dropped. If you do not use the variant settings the Physcial based rendering files are used by the game engine
So TLDR, When using the variants settings, even if all of the variants have PBR files, the minecraft RTX engine ignores them, even if only 1 variant is defined. If you do not use variants the PBR textures work as intended.
Linked issues
Attachments
Comments 8
Is this an ongoing issue in the latest version (1.17.2)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.
it is in 1.17.0, 1.17.1, and 1.17.2.1.
To Repro, you must clearly have an RTX enable graphics card. Attach that pack i put in the jira, and place "coal" or "coal blocks" and dirt. Dirt is set up to use a PBR file that is not tied to variants. Dirt is tied to the EXACT SAME pbr file. and doesn't render the normal or MER file.
This is the terrain texture data to explain that in detail.
{{ "num_mip_levels" : 0, "padding" : 0, "resource_pack_name" : "vanilla",
"texture_data" : {
"dirt" : {
"textures" : { "variations" : [
{"path" : "textures/blocks/dirt/dirt"}
, {"path" : "textures/blocks/dirt/dirt1"}, {"path" : "textures/blocks/dirt/dirt2"}, {"path" : "textures/blocks/dirt/dirt3"}, {"path" : "textures/blocks/dirt/dirt4"} ] }
}, "coal_block" :
{ "textures" : "textures/blocks/dirt/dirt" }
, "coal_ore" :
{ "textures" : "textures/blocks/dirt/dirt1" }
}, "texture_name" : "atlas.terrain"}
For clarity so you don't have to open it up the texture files are named 0.png 1.png ect. So the only way for the dirt block to find the png is to actually look in the JSON. however it is not finding the MER or the Normal.
This is a really simple pack designed to only express this 1 bug.
I would check in the beta... but getting into the beta is such a hug pain in the bum.... It is about 6 hours of work to change between the beta and normal....
@ravinmaddhatter Try the Bedrock Launcher if you haven't already. Back up everything beforehand, enlist into beta, delete MCBE, & when you install the launcher you can create a profile & play any release or beta version. I use it & it makes bug testing much easier. It's understandable if you don't trust 3rd party software of course!
A better title for this issue would be "Texture variations only support MER colour arrays" since I've discovered that they do in fact load an MER only if it is set through a colour array value in the texture set. They still do not support MER images nor do they support heightmaps or normals.
I cannot links these, but this was the one that was closed with a resolution that makes absolutely 0 sense.
MCPE-110361
Nowhere in the entirety of the ticket did we mention multiple packs interacting.