Get Flux Guidance (Texturaizer)
Read the guidance value Blender set, instead of hardcoding 3.5
- data_optional
- flux guidance
- data_hash
A one-value getter: it retrieves the Flux flux_guidance setting from Blender's exported scene data (or a directory you point it at) so you're not hardcoding a guidance value into your graph and forgetting to update it when you change it on the Blender side.
Why this is its own node, not just a number
Flux doesn't use classic CFG the way SD 1.5 and SDXL do. Flux Dev is guidance-distilled - the "guidance" slider adjusts a value baked into the model rather than running a real unconditioned pass, which is also why Flux has no working negative prompt and doesn't pay CFG's usual doubled generation cost. The community treats mixing the two up as a real mistake worth correcting on sight - "You wrote CFG when you should have written Flux guidance and now you think it's funny? They are two different things and CFG doubles the time for generation" is the kind of pushback you'll see if you ask about it. The default is 3.5; people commonly run lower (1.8–2.2) for a less "plastic" look, or push it to 4–4.5 alongside realism LoRAs. Having a dedicated getter for this value - rather than folding it into a generic settings dictionary - makes sense given how specific and easy to mismanage it is.
The outputs that matter
flux guidance- aFLOAT, described in the tooltip simply as "Texturaizer JSON data" (the tooltip text is generic here, but the field itself is exactly what the node's name says: the guidance value). Wire it directly into whatever guidance input your Flux sampling setup exposes - typically a Flux Guidance node sitting between your conditioning and your sampler.data_hash- the standard debug-only fingerprint every Texturaizer getter outputs; not something to wire into your actual generation path.
How it reads its data
Same pattern as the rest of the "Get" family: directory_optional points it at Texturaizer's export folder, leaving it blank falls back to the addon's configured global directory, and data_optional lets you hand it an already-loaded dictionary (typically chained from Texturaizer_GetJsonData) so the export file only gets read once per run even with several getters active.
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 - it's a data read, not a model.
Where people get burned
The most common way to misuse this node is wiring its output into a plain CFG field on a non-Flux checkpoint - the value only means what it means for Flux's guidance-distilled sampling; feeding a Flux guidance number into an SDXL or SD 1.5 CFG slot will just behave like an oddly-scaled CFG value, not the thing it was tuned for. And as ever with this pack: without Blender's addon actually exporting a value, directory_optional left blank is pointing at a global directory that has nothing meaningful in it - if the number coming out looks stale or wrong, check the addon exported after your last change in Blender before assuming this node is misreading something.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| directory_optionalopt | STRING | — | |
| data_optionalopt | DICTIONARY | [object Object] | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| flux guidance | FLOAT | Texturaizer JSON data. |
| data_hash | STRING | Hash value for debugging purposes. |