Get Material Tile Data (Texturaizer)

The companion node to Texturaizer_CircularVAEDecode - that node does the actual seamless-tiling decode, and this one reads the settings for it out of Blender's export instead of you setting them by hand in ComfyUI every time. If you're generating a texture for a material that needs to tile on a mesh, this is how Blender's own material setup (which axes need to repeat, and how far into the denoise process the tiling behavior should kick in) reaches your ComfyUI graph.

How it works

Same read pattern as the rest of the pack: directory_optional, the addon's configured global directory if left blank, or an already-loaded dictionary via data_optional. What it extracts specifically is the material-tiling block of Blender's export - whether the material needs to tile on the X axis, the Y axis, both, or neither, and at what point in sampling the tiling behavior should start.

The outputs that matter

• start step - an INT. The tooltip is generic ("Texturaizer JSON data"), but the field name is specific: this is presumably the sampling step at which tiling-aware behavior should begin, letting a render spend its early steps forming composition normally before tiling constraints kick in for the later, detail-forming steps. Given the pack has no dedicated "tiling-aware sampler" node, the most direct use is as a reference point if you're building a custom step-range setup - for straightforward use, wiring tiling directly into Texturaizer_CircularVAEDecode at decode time covers the common case without needing this value at all.
• tile x / tile y - both BOOLEAN. Whether the material should tile along each axis independently. This maps directly onto Texturaizer_CircularVAEDecode's tiling dropdown: both true means enable, one true means x_only or y_only, both false means disable - you'd translate these two booleans into that single dropdown choice yourself, since the two nodes don't wire directly into each other.
• data_hash - the standard debug-only fingerprint.

Installing it

ComfyUI Manager → search Texturaizer → Install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/LatentSpaceDirective/ComfyUI-Texturaizer

then restart ComfyUI. Pure data read, no models or extra dependencies involved.

Where people get burned

The two booleans and the Circular VAE Decode node's single tiling enum don't connect automatically - there's no node in this pack that converts tile x / tile y into the matching enable/x_only/y_only/disable choice for you, so if your textures aren't tiling the way Blender's material setup says they should, check whether that translation actually happened somewhere in your graph rather than assuming this getter or the decode node is at fault on its own. And, as always with this pack's getters: with no Blender addon actually exporting, an empty directory_optional is reading from a directory that doesn't have anything in it yet.