Get ControlNet Data (Texturaizer)

This is the node that hands you every ControlNet Blender configured for a render, bundled as one dictionary. You'll rarely use its output directly for anything visual on its own - it's the input the pack's two other ControlNet nodes are built around: Texturaizer_ApplyControlNets applies the whole list at once, and Texturaizer_ExtractCNData reaches into it by index to unpack one entry at a time.

How it works

Same read pattern as every other getter in the pack: point directory_optional at Texturaizer's export folder, or leave it blank and it checks the addon's configured global directory, or hand it an already-loaded dictionary via data_optional if you've chained it from a Texturaizer_GetJsonData node upstream (the usual way to avoid reading the export file more than once per run). What comes back specifically is the ControlNet configuration Blender exported - however many ControlNets were set up for this render, each carrying its own type, model, preprocessed image, strength and step range under the hood.

The outputs that matter

• controlnets - a dictionary, described in the tooltip simply as "Texturaizer JSON data." This is the list that feeds Texturaizer_ApplyControlNets's cn_data input directly, or Texturaizer_ExtractCNData if you want to pull one entry at a time and build your own apply chain.
• data_hash - the standard debug-only fingerprint every getter in this pack outputs; not meant to be wired into your generation graph.

That's the whole node. It's a pass-through with a specific field selected, and its value is entirely in what it feeds downstream - pair it with Texturaizer_ApplyControlNets for the fast path, or Texturaizer_ExtractCNData when you need to inspect or manually route a single ControlNet's settings.

Installing it

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

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

then restart ComfyUI. No extra dependencies, no bundled models - the actual ControlNet weight files referenced inside the dictionary this node returns still need to be present in your controlnet folder, loaded by Texturaizer_CachedCNLoader or a standard loader.

Where people get burned

This node returns whatever Blender exported - if you configured zero ControlNets for a scene, controlnets comes back essentially empty, and anything downstream expecting entries (Texturaizer_ExtractCNData with a nonzero index, especially) will have nothing to unpack. If a ControlNet you configured in Blender doesn't seem to be reaching ComfyUI at all, this is the node to inspect first - check its data_hash changed after your last export, which tells you whether ComfyUI actually picked up fresh data from Blender or is still looking at a stale read. And, as with the rest of the pack: without the Blender addon in the loop, directory_optional left blank points this at a global directory that only means something once the addon has configured and written to it.