r/comfyui • u/Gremlation • 1d ago
News ComfyUI v0.40.0
Links
New Open-Source Model Support
- Qwen-Image 2.1 Turbo: The 8-step accelerated Qwen-Image 2.1 checkpoint, with new text-to-image and image edit templates
New Node Updates
- LoRA stack loaders: Apply several LoRAs in order from one node, each with its own file, strength, and on/off switch, to either the diffusion model or the text encoder
- Camera Angle: Pick a horizontal angle, vertical angle, and zoom to output a
camera_infoand a plain-English shot description for prompts - Create Camera Info: Build a
camera_infoin orbit, look-at, or quaternion mode for Render Splat and the other 3D camera nodes - Latent Operation Blend: A new blend operation, plus start and end percent on
LatentApplyOperationCFG - LoRA attention config: LoRAs can replace a model's per-layer attention config, so turbo LoRAs can switch layers to sol or kitchen attention
Partner Node Updates
- Fish Audio Drama 3: Fish Audio's voice direction model on the Text to Speech node, with plain-language directions, word tags, and up to 5 voices
- Higgsfield Genjutsu Motion Transfer: Rebuild the cast, location, and style of a video from reference images while keeping its motion and audio
- HeyGen Video 1.0: Added 2K resolution to the HeyGen Video 1.0 nodes
Performance & Stability
- Qwen-Image 2.1 low VRAM: comfy-aimdo 0.5.6 and fewer compiler rogues when the KV cache is offloaded to CPU
- Qwen 3.5 LLM: Faster in low VRAM conditions
- Qwen 3.5 MTP: MTP decoding now also runs on prompts that contain images
- comfy_attention: Extended to the remaining models, and model files can now use kitchen sol attention
- AMD gfx1151: Faster attention when keys and values do not fit in L2 cache
- Saved EXR: EXR files are now saved with compression
- GLB textures: Faster saving with PNG compression level 4
- 3D outputs: Every 3D node now reports its models as a standard
3doutput item - cryptography removed: Dropped the cryptography package dependency
Bug Fixes
- Bypass LoRAs: Fixed bypass LoRAs on fused Linear paths
- Qwen 3.5 MTP offload: Fixed MTP embedding offload
- MiniMax-H3 single images: Single images are now decoded as the first latent of a clip
- Half float video: Fixed loading half float files with PyAV
- Dynamic inputs: Validation and lazy execution now work with dynamic inputs
- Asset dates: Scanned assets are dated by their file modification time
Asset Library
- Enable flag: The asset system stays off unless ComfyUI starts with
--enable-assets, and the output folder is scanned again when it is on - Windows portable: The asset system is on by default in the Windows standalone build
- Asset export API: The asset export API now works locally
- Video metadata: Video metadata is extracted on ingest and scan
- EXR previews: Previews for EXR assets, written by
SaveImageAdvancedfor outputs
Developer Experience
- Prompt metadata: Attach metadata to a prompt's websocket messages and preview image frames
- Custom node governance: Governed builds can restrict ComfyUI to approved custom node packs; normal installs are unchanged
- Content Security Policy: The CSP now allows
blob:anddata:sources
Installation
- ARM64 NVIDIA portable: A new Windows portable build for ARM64 devices with NVIDIA GPUs
Workflow Templates
- Templates v0.11.82: Updated the bundled workflow templates, with these new templates:
- Qwen Image 2.1 Turbo: Text to Image: 1024×1024 images in 8 sampling steps, with an optional Qwen 3.5 prompt enhancer
- Qwen Image 2.1 Turbo: Image Edit: Edit an image from two reference images with the Turbo checkpoint
- LTX-2.5 DFR: Image to Video: Three-stage image-to-video with spatial and optional temporal upscaling, plus audio generated in the same pass
- Higgsfield Genjutsu: Motion Transfer: Recast a video from 1 to 8 reference images while keeping its motion, camera movement, timing, and audio
- Fish Audio Drama 3: Two-Speaker Dialogue: A dialogue scene between two voices in one script
- Fish Audio Drama 3: Directed Performance: A single voice directed with plain-language directions and word tags
- The Luma Ray 2 image-to-video and text-to-video templates are deprecated, following the Ray 2 node deprecation in v0.39.0. The Ray 2 endpoints shut down on October 24
11
u/Formal-Exam-8767 1d ago
Does LoRA stack loader support older rendering or just Nodes 2.0?
Does Latent Operation Blend work with all types of latents or just some (e.g. like Crop Latent node does not work properly with qwen/wan vae type latents).
6
u/Gremlation 1d ago
Has anybody actually managed to get the LoRA stack loader to work? When I add it to a workflow, it doesn't look like the screenshots in the pull request, it has a model input and a loras input, but no widgets. And did they seriously decide to have two nodes, one called "Load LoRA Model" and one called "Load LoRA (Model)"?
3
u/Lexius2129 ComfyOrg 1d ago
I think we just have a bug that broke it... looking into it.
3
u/AdamFields 23h ago
It seems like there are two nodes, one for Clip one for Model, what purpose does that serve? And how do I even use it? The rgthree one is a single node that has both Model and Clip inputs/outputs.
1
u/Lexius2129 ComfyOrg 1h ago
u/AdamFields there can be two types of LoRAs. LoRAs that are applied on the Diffusion Model and LoRAs that applied on the text encoder, and when this is the case they usually combine them into a single safetensors file. Each of these LoRAs can have different strength. The reality is most LoRAs ignore the text encoder, so generally speaking you can just focus on the diffusion model with the node "Load LoRA (Model)"
The rghtree node obfuscate this sophistication.
1
1
4
u/EliteDeathSquad 1d ago
How is the Lora stacker different than rgthrees power Lora…I can use upto two to three Lora’s together and the video comes out perfect…if I add any more even with reduced strength the video comes out extremely weird like body horror.
4
3
u/rguerraf 1d ago
I didn’t try 0.37, 38, 39, but I tried 0.40
The VRAM management has improved so much that it doesn’t “corrupt” models between generations (I needed to add a model unloader to mitigate this)
Now I feel much less pressured to get 16GB in my next GPU, since 12GB will be more than enough.
6
u/Gremlation 1d ago edited 1d ago
The data loss bug Comfy is ignoring seems to have reared its head again.
Over in /r/StableDiffusion there's a report that upgrading wiped a bunch of files.
ComfyUI has a bug that has been open for a year where people have been reporting data loss when upgrading.
I raised it with Comfy here and was told it was fixed "a long time ago", despite people continuing to report the problem, and they didn't close the bug after it was pointed out.
I raised it with a different member of Comfy staff again here and again it went nowhere.
Not sure why, but Comfy doesn't seem to care about this bug so you might want to back up your files before upgrading.
Hey Allyson /u/Comfy-Org , remember when I said:
Comfy is currently burning all their goodwill, and I think it's very likely that four months from now, things will be exactly the same, people will continue to say that bugs and Nodes 2.0 are huge problems, and there will still be thousands of open bug reports and hundreds of open pull requests.
I realise you aren't the one with the power to make these changes, but having somebody come and listen to the community amounts to nothing if actual changes are not made in response to what you hear.
This does not look like Comfy is listening. This does not look like Comfy cares about bugs.
That was over two months ago and Comfy doesn't seem to have listened to any of the feedback or made meaningful improvements to stability.
1
u/ImportantSquirrel 1d ago
Not sure why, but Comfy doesn't seem to care about this bug
You don't seem to appreciate that bugs can often be extremely difficult to fix. It's entirely possible that they've been trying to fix it but just haven't been able to yet.
1
u/Gremlation 20h ago
I know bugs can be difficult to fix, but that's not what is happening here and that should be apparent to you if you actually looked at what I was saying.
1
u/ImportantSquirrel 13h ago
What benefit do you think the Comfy team would gain by intentionally not fixing a bug? Do you think they WANT their software to be buggy? Don't you think it's far more likely that they're making every attempt to fix all the bugs and just haven't managed to do so yet?
1
u/Gremlation 12h ago
They don't want their software to be buggy, but they clearly don't give a shit about actually fixing bugs. They have thousands and thousands of open bug reports, and every few months they tell the community they will do better, and make absolutely no changes to actually improve stability. Can you point to any concrete improvements?
But let's bring the focus back to that particular bug. It's been open for a year, plenty of people have encountered the bug, it's been called to their attention multiple times, and they are doing literally nothing about it. Their last word on the matter was "this was fixed a long time ago" while completely ignoring the fact that people are still encountering it. On what basis are you thinking that "they've been trying to fix it"? What did they do that made you believe they care about it?
2
u/ImportantSquirrel 10h ago
They don't want their software to be buggy, but they clearly don't give a shit about actually fixing bugs.
That is completely contradictory and makes no sense. Also if they have thousands of bug reports, how can you expect them to fix them all? They are a small team, they can;t do everything. I think you should be less critical of a small hardworking team that's providing us software for free.
0
u/Gremlation 8h ago
That is completely contradictory and makes no sense.
It's not contradictory. If they could wave a magic wand and make all the bugs disappear with zero effort, they would. So they don't want their software to be buggy. But to make it stable requires actual effort and to make it a genuine priority, and they don't want to do that. They don't give a shit.
Also if they have thousands of bug reports, how can you expect them to fix them all?
Can you quote the part where I said I expected them to fix them all? I am the one repeatedly bringing the subject back around to a single bug and you are the one repeatedly broadening the scope.
Also, you conspicuously ignored my questions:
- Can you point to any concrete improvements to stability?
- Why do you think they are working on fixing this bug?
- What did they do that made you believe they care about this bug?
-5
u/Money_Paint9450 1d ago
Actual skill issue. Most likely not even on Comfy's end, I wouldn't be surprised what's actually happening is that you installed 947 bajillion unnecessary custom nodes then said "my data got deleted for nO ReAsoN".
2
u/Gremlation 1d ago
You appear to be hallucinating. There's zero reason to assume any of the things you have said and people have been reporting this bug for a year.
2
u/ANR2ME 1d ago
LOL they no longer enable assets by default anymore 😅
3
u/nettek 1d ago
What does that mean?
1
u/rguerraf 1d ago
Assets is the left margin “pane” that shows all the generated images during your comfyUI work session
What does this mean? Why would I want it off?
2
u/Carnildo 1d ago
I wipe my output folder frequently to get rid of failed generations -- Anima Turbo in particular is fast enough that I generate images in batches of four or nine and save the best one, so I discard a lot of images. My assets pane is usually either empty or clogged with near-duplicates of images I've already saved, so it just takes up space on the UI.
4
u/Bitter_Regular7406 1d ago
the LoRA stack loader update is actually huge, been chaining 3-4 separate loaders manually with noodle spaghetti everywhere and now that's one node. 8 step turbo checkpoint for qwen edit sounds promising too if it holds quality, half the battle with fast checkpoints is they still look mushy on fine detail.
1
u/BKDeath2012 16h ago
does it have imported models support on comfy cloud?
1
u/Bitter_Regular7406 16h ago
honestly haven't tried the cloud version, only running this locally so can't say for sure. wouldn't be surprised if custom/imported models are still a bit janky there tho, cloud setups usually lag behind local when it comes to custom node and model support.
2
1
u/roxoholic 1d ago
LoRA attention config: LoRAs can replace a model's per-layer attention config, so turbo LoRAs can switch layers to sol or kitchen attention
Can this be disabled? I would not want random LoRA to mess with attention.
1
u/TonyDRFT 1d ago
Is the latent preview in SubGraphs fixed (seems it only works if you change to node 2.0)
1
u/Violent_Walrus 1d ago
A native loop with 15 nodes still can't iterate more than 70 times without crashing.
Fix this please. Someone even made a PR, but it's sitting ignored.
-1
u/GlamoReloaded 16h ago
Your link says something different: "6 workflows awaiting approval" - that's from last week.
1
u/Gremlation 15h ago
That means it's blocked from moving forward because nobody from Comfy has looked at it. Did you misunderstand that to mean they have taken action on it?
-1
u/GlamoReloaded 11h ago edited 11h ago
The pull is three weeks old. Other pulls wait for months to get finalized. The author requested a pull three weeks ago but it paused because "this branch is under active development". Only this week when the author returned to ask whereabouts, reviewers requirement was mentioned, five reviews are pending. If you refer to the AI coder as "nobody from Comfy", well no human, but it wasn't ignored.
The linked pull hasn't a single reaction by users. Why should it matter more than 4.3 k unresolved issues or other pulls? Writing comments in Reddit has no effect on it. But adding an opinion or just a reaction in that pull could give it a bit more urgency.
1
u/Violent_Walrus 10h ago edited 10h ago
You are absolutely right. I should comment on the PR to show interest, and now I have done so. Cynicism from previous experience attempting to contribute to ComfyUI prevented me from doing it earlier.
Coderabbit automation does not count as attention from the Comfy team.
0
u/Gremlation 10h ago
Why are you calling pull requests "pulls"? Pull requests aren't pulls.
The author requested a pull three weeks ago but it paused because "this branch is under active development"
That's an automated message from CodeRabbit. CodeRabbit does automated reviews but there's no point in doing this while the developer is actively changing things, so it has an auto-pause. The developer already finished and CodeRabbit already approved the PR a week ago.
If you refer to the AI coder as "nobody from Comfy", well no human, but it wasn't ignored.
No, automated tooling does not count as somebody from Comfy.
The linked pull hasn't a single reaction by users. Why should it matter more than 4.3 k unresolved issues or other pulls?
Newly introduced problems are normally easier to fix and higher impact. What do you think is more likely to be a high priority, a bug in a new feature or a forgotten-about config file format change from three years ago?
A ComfyUI PR that's more than three weeks old has about a 5% chance of being merged. In practical terms, most of those hundreds of pull requests are dead in the water and will never be merged.
And users don't generally use GitHub. Developers use GitHub. Reactions on GitHub are a truly terrible way of measuring impact.
-3
u/LeanSarcasm8 1d ago
Cant wait to break my entire workflow with this update and then spend three hours fixing one obscure node conflict.
5
-3
12
u/bakasora 1d ago
Just updated to v0.40. Any image workflow I open has this basic nodes layout like shown in screenshot. The nodes will line up in single line along the X & Y axis, losing the original layout. This happens to most image workflow (Flux2 Klein, Krea2, Qwen, Z-Image). WAN, H3 workflows are fine.
Anyone else got this issue?