Object Set Show Texture Space

Another of this pack's ObjectSet_ property-toggle nodes: Object Set Show Texture Space sets object.show_texture_space, a boolean that draws a wireframe bounding box in the viewport representing the object's "Generated" texture coordinate space - the bounds Blender uses when a material's texture mapping is set to Generated rather than UV.

How it works

When a texture is mapped using Generated coordinates instead of a UV unwrap, Blender derives the mapping from the object's bounding box in its own local (texture) space. That box is normally invisible - this property just draws its wireframe outline in the viewport so you can see exactly what bounds a Generated-mapped texture is being projected onto. It's a debugging visualization for texture mapping, not something that changes the mapping itself, and it sits alongside object.show_name and object.empty_display_type as one of a small cluster of pure viewport-display properties this pack happens to expose as nodes, presumably because generate_blender_types.py wraps Blender's object properties wholesale rather than picking and choosing which ones are actually useful in a headless graph.

The inputs and outputs that matter

• value - boolean, default false. true shows the texture-space wireframe box in the viewport; false hides it.

Output is the same BPY_OBJ.

How to install it

ComfyUI Manager: search "Avatar Graph" and install. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/avatechai/avatar-graph-comfyui, cd avatar-graph-comfyui && pip install -r requirements.txt, then restart. The whole pack needs Python 3.10.x because it embeds Blender via bpy, which only ships wheels for that version - a newer environment either fails the install or leaves the blender-category nodes absent. macOS/Linux: dedicated conda env at 3.10. Windows: Avatech's prebuilt Python-3.10 ComfyUI zip, pack installed through Manager afterward.

Common issues & troubleshooting

You're not using Generated texture mapping, and this looks pointless. It genuinely is, in that case - Avatar Graph's own image-to-mesh pipeline (Object Mesh From Texture, "Plane Texture Unwrap" in the README) works via real UV unwraps, not Generated coordinates, so this toggle is unlikely to matter for a typical avatar build. It's here because it's part of Blender's full object-property surface, not because it's central to this pack's normal workflow.

Purely a viewport aid, no functional effect. Same as the other ObjectSet_ nodes: this changes what you see while editing in Blender or the pack's live preview, not the object's actual data, texture mapping, or the exported .glb/.gltf. If you're debugging a texture problem in the actual output, this toggle won't surface it - check the material's mapping type instead.

Not in the README. Correct - it's one of the pack's lower-level blender-category nodes, auto-generated from Blender's own object properties via generate_blender_types.py, not one of the roughly seven higher-level Avatech nodes the README documents by hand.