{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif32gbbtm2b6xaprbfvtmfyhws74fkhg4zst5rtxctdjijvi7vjtu",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mk2le3n3rn32"
  },
  "path": "/t/ive-hit-a-wall-please-help/175450#post_2",
  "publishedAt": "2026-04-22T02:08:27.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "1st movie clip! - #7 by kdalts3759",
    "docs.comfy.org",
    "github.com",
    "reddit.com",
    "huggingface.co"
  ],
  "textContent": "Continued from 1st movie clip! - #7 by kdalts3759. I haven’t used ComfyUI myself, so I can’t say for sure, but…:\n\n* * *\n\nYou can make this work **without** a better GPU right now.\n\nWhat is happening is that you have hit **two different walls at the same time** :\n\n  1. a **tooling wall**\nComfyUI Manager / ReActor / custom-node install problems\n\n  2. a **workflow wall**\nlong stitched video + identity drift across clips\n\n\n\n\nThose are separate problems, and they need to be solved in the right order.\n\n* * *\n\n# The most important thing first\n\n## Reinstalling ComfyUI usually does **not** fix this kind of problem\n\nWhy not?\n\nBecause the usual causes are:\n\n  * wrong folder\n  * wrong Python environment\n  * missing node dependencies\n  * frontend cache / missing Manager UI\n  * a custom node that downloaded but did not actually import\n\n\n\nThe official ComfyUI custom-node docs explicitly separate **installing the node files** from **installing dependencies** , and they tell you to restart ComfyUI, refresh the browser, and check startup logs for failed imports. (docs.comfy.org)\n\nSo the fact that reinstalling ComfyUI changed nothing actually fits the normal failure pattern.\n\n* * *\n\n# Your biggest clue\n\nYou said ReActor is in the **`custom_model`** folder.\n\nThat is almost certainly the wrong place.\n\nFor ReActor, the official install path is under:\n\n\n    ComfyUI/custom_nodes/ComfyUI-ReActor\n\n\nnot `custom_model`, not `models`, not a safetensors folder. The ReActor README documents manual installation as a **custom node repo** inside `custom_nodes`, followed by a requirements install step. (github.com)\n\nSo the first big correction is:\n\n  * **custom_models / models** = where model files go\n  * **custom_nodes** = where node repositories go\n\n\n\nIf a node repo is in the wrong place, ComfyUI will never load it as a node.\n\n* * *\n\n# What I think is happening in your setup\n\nIn simple language:\n\n## Problem A — Manager is probably on disk, but its UI is not loading properly\n\nThat would explain:\n\n  * “installed”\n  * folder exists in `custom_nodes`\n  * but **no button anywhere**\n\n\n\nThere are similar Manager issues where the button disappears after updates or frontend/menu changes, even though the repo is present. (github.com)\n\n## Problem B — ReActor is either in the wrong folder, or its Python packages were never installed correctly\n\nThat would explain:\n\n  * downloaded from GitHub\n  * seems present\n  * but no node in search\n  * reinstalling ComfyUI does nothing\n\n\n\nThere are multiple ReActor reports online where users say it is “installed” but still fails to show up because the import fails or the install script never completed properly. (github.com)\n\n## Problem C — your workflow is asking too much of long stitched clips\n\nThat would explain:\n\n  * good-looking short clips\n  * but characters drift by the end of the stitched sequence\n\n\n\nFor that part, the fix is not “download more LoRAs.” The fix is **anchor-based continuity** : I2V, first/last-frame control, and repair of bridge frames. The official Wan tutorials are already built around those kinds of controls. (docs.comfy.org)\n\n* * *\n\n# What I would do, in exact order\n\nDo **not** try to fix everything at once.\n\nUse this order.\n\n* * *\n\n## Step 1 — stop adding more models for now\n\nRight now, more downloads are hurting you.\n\nThey are:\n\n  * eating disk\n  * adding confusion\n  * making it harder to tell what works\n\n\n\nFor the next few days, keep only a **small working set** :\n\n  * one base workflow\n  * one base model\n  * one or zero LoRAs\n  * three anchor stills\n\n\n\nThat is enough.\n\n* * *\n\n## Step 2 — fix the folder structure first\n\nYour `custom_nodes` folder should look roughly like this:\n\n\n    ComfyUI/\n      custom_nodes/\n        ComfyUI-Manager/\n        ComfyUI-ReActor/\n\n\nIt should **not** look like this:\n\n\n    ComfyUI/\n      custom_model/\n        ComfyUI-ReActor/\n\n\nor this:\n\n\n    ComfyUI/\n      custom_nodes/\n        ComfyUI-ReActor-main/\n\n\nor this:\n\n\n    ComfyUI/\n      custom_nodes/\n        ComfyUI-ReActor-main/\n          ComfyUI-ReActor/\n\n\nThat last “nested GitHub zip folder” mistake is extremely common.\n\n* * *\n\n## Step 3 — fix ReActor the official way\n\nAfter moving ReActor into `custom_nodes`, install its requirements using the **same Python that ComfyUI itself uses**.\n\nThat part matters a lot.\n\nThe ReActor README shows manual install using ComfyUI’s Python and its `requirements.txt`, and the repo also provides helper scripts such as `install.bat`. (github.com)\n\n### If you use ComfyUI portable on Windows\n\nUse the Python inside your ComfyUI folder, not a random Python on your PC.\n\nSomething like:\n\n\n    python_embeded\\python.exe -s -m pip install -r ComfyUI\\custom_nodes\\ComfyUI-ReActor\\requirements.txt\n\n\nor go into the ReActor folder and run:\n\n\n    install.bat\n\n\nThe exact wording comes from the project’s own install instructions. (github.com)\n\n### Why this matters\n\nA very common beginner problem is:\n\n  * repo is in the right place\n  * but requirements were installed into the **wrong Python**\n  * so the node still fails import when ComfyUI starts\n\n\n\nThat exact pattern comes up again and again in similar cases online. (reddit.com)\n\n* * *\n\n## Step 4 — launch ComfyUI from a terminal and read the startup text\n\nThis is the part most beginners skip.\n\nThe startup console is the truth.\n\nLook for anything like:\n\n  * `IMPORT FAILED`\n  * `ModuleNotFoundError`\n  * `No module named ...`\n  * `ComfyUI-Manager`\n  * `ReActor`\n\n\n\nIf a custom node downloaded but did not import, the console usually tells you why.\n\nThe official docs tell you to check startup logs for failed imports, and real issue reports show that a folder being present means nothing if startup still says `IMPORT FAILED`. (docs.comfy.org)\n\n* * *\n\n## Step 5 — hard refresh the browser\n\nDo this after restarting ComfyUI:\n\n  * **Ctrl + F5** on Windows\n\n\n\nWhy?\n\nBecause Manager has a UI/frontend part. Sometimes the backend is there, but the browser is still showing an older cached interface.\n\nThis is especially worth trying if:\n\n  * the folder exists\n  * startup looks mostly okay\n  * but the Manager button still never appears\n\n\n\n* * *\n\n# If Manager is still missing\n\nIf Manager still refuses to show its button, do **not** let that stop the whole project.\n\nYou can still work manually.\n\nThat is important.\n\nManager is helpful, but it is not required for the workflow itself.\n\nSo if Manager keeps failing, the priority becomes:\n\n  1. get one custom node working manually\n  2. get the video workflow working\n  3. come back to Manager later\n\n\n\n* * *\n\n# How to make the workflow work **without** ReActor\n\nThis is the part I really want to stress:\n\n## ReActor is optional for your project\n\nUseful? Yes.\n\nRequired? No.\n\nYou do **not** need a faceswapper to make the basic continuity workflow work.\n\nWhat you need is:\n\n  * a good pair anchor\n  * a clean shot handoff\n  * a controlled sit-down transition\n\n\n\nThat can all be done without ReActor.\n\n* * *\n\n# The simplest working workflow for your exact film on 8 GB\n\nUse the official **Wan 2.2 5B** path because the ComfyUI tutorial is specifically aimed at making that workable on **8 GB VRAM**. (docs.comfy.org)\n\nThen do this:\n\n* * *\n\n## Phase 1 — create three stills first\n\nMake three “anchor” images:\n\n### Anchor A\n\nBoth characters walking side by side\n\n### Anchor B\n\nBoth characters standing / arriving near the bench\n\n### Anchor C\n\nBoth characters seated on the bench\n\nDo **not** continue until those three stills look right.\n\nThat is the casting stage.\n\n* * *\n\n## Phase 2 — Shot 1: walk\n\nUse **I2V** from **Anchor A**.\n\nKeep it short.\n\nGoal:\n\n  * small body motion\n  * small camera motion\n  * same faces\n  * same outfits\n\n\n\nAt the end, save the **best final frame**.\n\n* * *\n\n## Phase 3 — repair the bridge frame\n\nNow inspect the last frame from Shot 1.\n\nIf the faces slipped, fix that frame **as a still**.\n\nThis is where people often think they need ReActor.\n\nYou do not.\n\nYou can repair one bridge frame:\n\n  * with a still-image workflow\n  * with inpainting\n  * or even outside ComfyUI if necessary\n\n\n\nFor your project, the last-frame repair is just a way of giving the next shot a cleaner starting point.\n\n* * *\n\n## Phase 4 — Shot 2: approach bench\n\nUse the repaired last frame from Shot 1 as the input image.\n\nAgain use **I2V**.\n\nGoal:\n\n  * slight slowing down\n  * slight repositioning near the bench\n  * no actual sit yet\n\n\n\nAt the end, save the best frame where they are standing near the bench.\n\n* * *\n\n## Phase 5 — Shot 3: sit\n\nThis is where I would stop using plain I2V and switch to **first/last-frame**.\n\nUse:\n\n  * first frame = best standing-near-bench frame\n  * last frame = **Anchor C** (seated)\n\n\n\nThe official FLF tutorial is exactly for this kind of controlled transition. (docs.comfy.org)\n\nThat gives the model much less freedom to “recast” the pair.\n\n* * *\n\n## Phase 6 — Shot 4: seated\n\nNow return to **I2V** , using the good seated frame as input.\n\nThis shot should have only gentle motion:\n\n  * breathing\n  * small glance\n  * subtle posture change\n\n\n\nBench shots are where you can safely create duration.\n\n* * *\n\n# What to do if a face drifts\n\nKeep the fix small.\n\nUse this rule:\n\n## If only one key frame is bad\n\nRepair the still, then continue.\n\n## If a short span is bad\n\nUse a short repair tool or short inpaint run.\n\n## If the whole clip is bad\n\nRegenerate that shot from the earlier trusted frame.\n\nDo **not** try to rescue a completely broken shot by piling on more LoRAs.\n\n* * *\n\n# One more important quality fix\n\nIf you see weird flicker or color blinking, do not assume it is all identity drift.\n\nThere is a documented ComfyUI issue where Wan output shows **blinking/discoloration** with **VAE Decode (Tiled)** , while standard **VAE Decode** does not show the same effect. (github.com)\n\nSo for finals, if memory allows:\n\n  * use **standard VAE Decode**\n  * keep tiled decode only for rough previews\n\n\n\nThat can remove one whole layer of “why do my people look different?” confusion.\n\n* * *\n\n# My recommendation about LoRAs right now\n\nVery simple:\n\n## Use fewer LoRAs, not more\n\nFor your current stage, I would choose one of these:\n\n  * no LoRA\n  * one utility LoRA for faster previews\n  * one carefully tested style/identity LoRA\n\n\n\nI would **not** stack several unknown LoRAs until your workflow is stable.\n\nIf you want faster previews, **Wan2.2-Lightning** is worth looking at because it speeds generation up a lot. That is useful for testing handoffs and anchor strategies. (huggingface.co)\n\nBut again: Lightning helps **speed** , not identity memory.\n\n* * *\n\n# My bottom line\n\nYou do **not** need to wait for a better GPU before making progress.\n\nYou **do** need to simplify.\n\nThe real path forward is:\n\n  1. fix the custom-node install structure\n  2. stop relying on Manager status messages alone\n  3. stop treating ReActor as mandatory\n  4. build the film from anchors + I2V + FLF\n  5. repair only the frames that matter\n\n\n\nThat is how I would make your workflow work **right now** on 8 GB.",
  "title": "I've hit a wall - please help"
}