Minecraft PBR - Save Bedrock RTX

Bedrock RTX resource packs are picky about filenames - a normal map must be called _normal, and the MER texture needs exactly the right suffix or the engine ignores it. Minecraft PBR - Save Bedrock RTX is the output node that names things correctly for you, the Bedrock counterpart to Save labPBR in the same pack.

What it does

Give it the three outputs of the Pack Bedrock RTX node - albedo, normal, mer - plus a filename_prefix, and it writes the set with Bedrock's naming conventions:

minecraft_pbr/material_00001.png         (albedo)
minecraft_pbr/material_00001_normal.png  (DirectX normal)
minecraft_pbr/material_00001_mer.png     (MER)

The nice touch is the suffix logic: the node looks at the channel count of your mer input and picks the right extension automatically. RGB input → _mer.png. RGBA input (SSS enabled, i.e. MERS) → _mers.png. You can't misname it, because you're not choosing - the channel count decides.

Everything else matches its labPBR sibling: files are written as linear PNGs (no gamma applied, no alpha dropped), into ComfyUI's output folder, sharing one auto-incrementing counter per run. Set a slash in the prefix to make a subfolder, and the albedo previews in the UI.

Inputs that matter

Three IMAGE inputs (albedo, normal, mer) and filename_prefix, default minecraft_pbr/material. Like all the save nodes in this pack, the prefix doubles as a path, so textures/blocks/stone would write straight into a textures/blocks/ layout your resource pack can pick up.

Install

ComfyUI Manager → Install Custom Nodes → search "comfy-ui-minecraft-pbr", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/jasonjgardner/comfy-ui-minecraft-pbr
# then restart ComfyUI

No models, no extra dependencies - the whole pack is pure torch math plus Pillow, and ComfyUI already ships both.

Gotchas

The _mer vs _mers split is the thing to keep straight, and it's decided upstream by whether you turned on compute_sss in the packer. Building for RTX ray tracing? That gives you _mer, and the SSS alpha wouldn't be read anyway. Building for Vibrant Visuals? You want _mers, so enable SSS before you save. And as always with this pack, don't route the packer's outputs through stock SaveImage - the _mers alpha is a real data channel, and stock SaveImage would throw it away.