[Feature Request]: My suggestions and a problem report regarding Head Swap V1 Flux 2 Klein 4b_9b

Open
  • Is something wrong?
#762 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
computer-vision, machine-learning, performance

Research direction

The issue does not identify a file, test, or workflow entry point; begin by reproducing the Head Swap V1 Flux 2 Klein 4b_9b workflow in the latest ComfyUI, particularly with 9B plus LoRa. Done would require agreeing which acceleration, VRAM-cleanup, muting, and negative-conditioning changes belong in the template and resolving or documenting the final VAEDecode stall.

Written by the indexing model from the issue text.

Description

enhancement
Description
  1. Insert acceleration nodes like tea cache or nunchaku (effective for Flux) to accelerate LoRa using Turbo;
  2. Add nodes like cleanGpuUsed to clean up VRAM;
  3. Connect nodes like Fast Muter (rgthree) to manage which nodes are muted or enabled.
  4. Negative warning words related to Flux2 Klein should be ineffective (especially when CFG is set to 1). Generally, adding a ConditioningZeroOut node to skip them is faster and less prone to errors. My understanding comes from the official website and other developers; I don't fully understand the principles, so please forgive me if I'm wrong.

I encountered a problem during use: when running Head Swap V1 Flux 2 Klein 4b_9b in the latest version of Comfyui, it gets stuck at the final VAEDecode node. Switching to the desktop and refreshing skips it. This happens frequently with 9B+LoRa. However, this doesn't happen when others use your workflow mix (zit+face swap). How can this be resolved?

Additional information

No response

Dominant language
TypeScript
Stars
1.5k
Forks
270
Avg merge
7h 23m
Merged PRs (30d)
65

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Comfy-Org/workflow_templates

All issues in Comfy-Org/workflow_templates

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.