WanVideo Injection Tester

"Activation injection isn't doing anything" is the single most common complaint with this pack, and most of the time the render is fine - the setup is wrong. Either the editor never received the injection embeddings, the prompts are too similar, or patching got disabled somewhere. This node exists to answer that question in one run, before you spend minutes on a generation that was doomed from the wiring.

It's a pure diagnostic. Give it the model and text_embeds from your activation chain, and it reads the model's state back at you:

• whether the activation editor is actually configured on the model, with the active blocks and injection strength
• whether runtime patching is enabled and the injection embeddings are present
• the measured difference between main and injection embeddings, with a verdict: below 30% → "prompts too similar!", 30–50% → "effects may be subtle," above 50% → "should see clear effects"
• with show_details on, which dimensions differ most - the "where is this difference living" readout that helps you understand why an effect behaves the way it does

Output is a single test_results STRING. There's nothing to wire onward; it's a report node.

When to run it

Two moments. First, the obvious one: injection looks dead, run the tester, and it tells you whether to fix your prompts (amp the difference), your wiring (no injection embeds found), or your patching (patching disabled). Second, the subtle one: before you tune. If your prompts are already 70% different, you know the effect should be visible and any weirdness is downstream - no point amplifying something that doesn't need it. The tester converts "is this working?" from a vibe into a number.

Install

Part of fblissjr/ComfyUI-WanActivationEditor, so the pack install applies - with kijai's ComfyUI-WanVideoWrapper as the required prerequisite:

cd ComfyUI/custom_nodes
git clone https://github.com/kijai/ComfyUI-WanVideoWrapper   # required first
git clone https://github.com/fblissjr/ComfyUI-WanActivationEditor
cd ComfyUI-WanActivationEditor && pip install -r requirements.txt

Restart ComfyUI. ComfyUI Manager: search "ComfyUI-WanActivationEditor".

Gotchas

• It must sit after the editor in the graph, because it reads the config the editor wrote into transformer_options. Hook it to the model coming out of the editor, not the raw model.
• It reports on the two prompts' measured difference, which as the README stresses can be misleading: the projection layer normalizes, so a low difference number doesn't always mean the injection is dead. Combine the tester with the editor's log_level "Percent changed" readout - if the editor reports the context was replaced at your blocks, injection is working even when the percentage looks small.
• It can't see inside the generation. It's the pre-flight check, not the flight recorder - if you need proof the output changed, run one clip with injection and one without and compare.