FK_高级贴图编辑器(旧)

In the node menu this shows up as FK_高级贴图编辑器(旧) - the "old" advanced texture editor from the juehackr/comfyui_fk_server pack. And the first thing to know is that it's a display node, not an editor that does its own thing. It has no outputs at all. Its whole job is to render the browser-based texture editor in the node's UI and show you the depth-fused composition. All the actual image work happens in its sibling, FK_Node (FK_图片编码转换), which encodes images to base64 strings and feeds them in here. Wire them up wrong and this node just sits there looking empty.

How it works

The pipeline is: load your images → FK_Node converts them to base64 PNG strings → those strings flow into background, depth, and Texture here. The three *code fields - backgroundcode, depthcode, Texturecode - are auto-generated once that wiring is live. The tooltips on all three say it plainly: "使用 FK_图片编码转换 节点自动生成" (auto-generated by the FK image encoding node). So leave them alone. The node hands the base64 up to the pack's web front-end, and that front-end draws the editor you actually interact with.

The "depth-fused" part of the name comes from the depth input. Feed it a proper depth map - grab one from a depth preprocessor like Depth Anything, MiDaS, or ZoeDepth - and the editor layers the texture with depth in mind rather than just pasting it flat. That's the feature that made this pack stand out when it shipped.

Why "old" matters

This is generation one of the texture editor, and the design shows it. Because there's no IMAGE output, the edited result never flows back into the graph - you're looking at the browser, tweaking, and re-running. That round trip through base64 strings also makes the wiring awkward. The pack's own successor, FK_gjttNode2 (FK_高级贴图编辑器(新)), takes IMAGE inputs directly and returns a composited IMAGE you can wire onward into a save node or a VAE encode. If you're starting a workflow from scratch, use the new one. Reach for this node when you're loading an older workflow that already uses it and you don't want to rewire.

Install

It's a standard pack install - nothing node-specific:

cd ComfyUI/custom_nodes
git clone https://github.com/juehackr/comfyui_fk_server.git
# then, from your ComfyUI python environment:
pip install -r ComfyUI/custom_nodes/comfyui_fk_server/requirements.txt

Restart ComfyUI after that. ComfyUI Manager works too - search the pack title. Two things to know up front: the pack needs Node.js (it runs a side server for its editor UIs and will npm install into its own server/ folder on first launch), and requirements.txt only pulls PyCryptodome and pybase64. No model downloads, no API keys for the editor nodes themselves.

Troubleshooting

• The editor shows nothing. FK_Node hasn't executed or its STRING outputs aren't connected. The base64 strings are literally the only thing this node renders, so trace those wires first.
• Don't hand-type the code fields. They're huge base64 blobs and the tooltip says to let FK_Node generate them. Pasting junk there is a great way to confuse the UI.
• The editor UI won't open. That's the Node.js side server not running. Watch the ComfyUI terminal for FKServer: lines - if you see "未检测到NodeJs" (Node.js not detected), install Node and restart.

One honest caveat that applies to the whole pack: it ships some obfuscated code, so you're installing on trust. For these display-side nodes the visible logic in tietu_node.py is plain enough to read; it's the newer editor nodes that are encrypted. If you're security-conscious, run it in a disposable venv before you trust it on your main machine.