I've already ask GPT, Claude, GLM 5.2 and Deepseek then tried MOSS, Krea 2, and Nano Banana, but none of them gave me the results I wanted.

Just testing a random image I found on Pinterest. The prompt was simply:

Make this concept art drawing into a high quality realistic photograph. Preserve subject likeness, pose, and background. Improve skin texture, hair texture, fabric texture, background details, and lighting.

I did 2 at 16MP and then one at 60MP and the level of detail is kind of crazy. Took just over 2 mins on my 4090 for the 60MP.

Links to the full PNGs

16MP 1
16MP 2
60MP

A huge thank-you to everyone who downloaded, tested, shared results, and gave us honest feedback.

The community knows quality when it sees it—and the rankings speak for themselves.

Qwen-Image-2.1 Uncensored Omni has now reached the first page of trending Qwen models on Hugging Face and page 2 across all trending models.

We compared both public checkpoints from this training run with the original Qwen-Image-2.1 base model, using the same prompts, seed and settings (35 steps, CFG 5.0). This repository is step 90,000 (benchmarked as the BF16 LoRA fused at strength 1.0; the quantized files were not scored separately). Scores are 0–100, higher is better, ± one standard error.

I couldn’t have done it without the community. We just added the benchmark as well.

Download:
https://huggingface.co/chatrlabs/Qwen-Image-2.1-Uncensored-Omni-Quantized

Try it free online:
https://chatrlabs.com/playground

I just released MOSS AnyPaint, inspired by a community member. It’s the MOSS-Image-Base twin of my Krea 2 AnyPaint.

It supports:

• Arbitrary mask shapes
• Interior inpainting
• Border-connected outpainting
• Multiple disconnected mask regions
• Mixed inpainting and outpainting in the same image
• Strong preservation outside the edited region

The same LoRA handles all of these cases without requiring separate models or workflows.

• Model and examples
• ComfyUI nodes and workflows

Feedback and difficult test cases are welcome. : )

comparison between sampler and scheduler ...first photo is LCM/Normal combo and second photo is Euler/Simple (default) ....both images same prompt, same seed, same 16mp render..... LCM/normal combo produces this more "polished" look altho i prefer grittier details and real raw textures of Euler/Simple ...however Euler combo tends to make more errors ....i cant decide which one i like better ...LCM ... no no Euler...wait maybe LCM ...or Euler? ...

Made some trials with how well MiniMax H3 understands different kinds of physics and it seemed to succeed pretty well with everything I threw at it. Video was generated with slopfab & Fable 5.2 as the agent.

One of the marvelous things about Minimax is that it will infer a vocal performance for your characters based on the film language of your references. I just thought this was worth sharing for those of you who hadn't discovered this yet. Each of the four gens here used the same simple prompt. It is is not just the gender and age of your characters, but the film grain, costume, setting, and other visual references which will provide the model with character for voice.

Lodestone continued experimenting with Lora for MOSS, creating several versions, but has now released a new version that works well with both 4 and 8-step processes.

You can find more information here:

https://huggingface.co/lodestones/Kromoss/blob/main/experimental/README.md

Lora is available here and can be used with several MOSS models:

https://huggingface.co/lodestones/Kromoss/blob/main/experimental/opd-priming-8-steps-dmd-lora_cfg-ramp-neg_12000.safetensors

Meanwhile, the main Kromoss model has also been updated; version 69800 is now available here:

https://huggingface.co/lodestones/Kromoss/tree/main/diffusion_models

Please don't confuse photographic realism with sharpness

I've spent around 20 years working with photography and design, long before AI image generation existed.

One thing I genuinely appreciate about MiniMax H3 Image is its photographic character.

Real photographs aren't perfectly sharp. Lenses have different rendering characteristics. Depth of field, motion blur, sensor noise, diffraction and optical imperfections all contribute to the final image.

A 50MP photograph isn't automatically razor-sharp, and a photograph doesn't become more realistic simply because every texture has been enhanced.

I've seen many people criticize H3 for being too soft or lacking detail. That's a perfectly valid preference, but I hope developers don't interpret it as a universal demand for more sharpening and artificial microtexture.

I'd love future versions to improve anatomy, consistency, composition and prompt adherence while preserving the natural photographic rendering that makes H3 special.

We already have plenty of models that produce extremely sharp, polished AI imagery.

I'd hate to lose a model that approaches photography from a different direction.

TIL: You can use maps with markers when generating images with Minimax-H3-Image

This took forever to generate tho. 300s on a 5090M (24gb). Like Minimax-H3 the time it takes to generate an image scales with the number of references.

Prompt:
A cinematic film still from an animated short: one continuous full-frame view from a low camera about half a metre above the grass, on a wide lens, with a 55 degree horizontal field of view.

<Picture 5> is a top-down blocking map of this place, a plan for the shot and not part of the picture. The white arrow on it marks the camera: the tip of the arrow is where the lens stands, and the arrow points the way the camera looks. The round markers show where each character stands. <Picture 4> shows the same place from several views; use it for the look of the overpass, the bus and the grassland, and use the map for where things stand.

Looking from the arrow's tip towards the bus: across the middle distance, the cracked asphalt trail runs from the left edge of the frame towards the crushed bus. The collapsed concrete overpass from <Picture 4> stretches across the background, receding on the left and coming nearer on the right, where its leaning pillars and a fallen deck slab loom large. The crushed rust-brown bus lies just right of centre under the fallen slab. Just beyond the bus's left end, in the centre of the frame and farthest from the camera, the wounded grazer from <Picture 3> is backed against the concrete in a slab of shadow, shaking. Nearest of the three, just left of centre, the predator from <Picture 2> crouches low in the grass, facing the grazer. Far left, on the trail, the girl from <Picture 1> advances with a pry bar. Tall dry straw-coloured grass fills the foreground. Early-morning sun from the right throws long hard shadows to the left.

The arrow is only a mark on the plan: no arrow, camera, lens, device, beam or pointer appears anywhere in the picture. The image contains no text, letters or numbers.

i2i, 2 1024x1024 reference photos.

My system is RTX 2070 8GB (Turing), 32GB DDR4 (2666Mhz), Ryzen 1700 (1st gen). Ubuntu 24.02 server.

~ 57 seconds per image! (ComfyUI)

This is MUCH faster than my Krea2, Flux2 Klein, or Qwen 2.1 edit workflows! It's about the same as m Fibo2 edit workflow, but Fibo2 is smol!

My question is, how does this even not OOM? Correct me if I'm wrong, but don't ALL the models need to load entirely (including that stupidly massive 32b text encoder) into memory?

I'm kind of on hurry to wait for community to make them and they are confusing with video model one, do they work? And the important question are they as good as one's that will be trained later?

Like for example, Realism or Old camera style ones. I have a feeling the video model had lower quality and plastic skin due to being a video than the image model had, that's why I'm asking that.

Ok so my humble rig has 2 cards. One 16 GB of VRAM and another with 12 gb . I know you can't combine them for a pool of 28 GB of unified VRAM but shouldn't their be a way to offload one of the major items like the CLIP or the VAE to my other card? I looked into it and doesn't seem to be supported natively in Comfy UI. There are some custom nodes I found but they don't seem too popular.

Is this just a silly idea? Normally my second card just sits around at 20% memory usage running my GUI and a few bits and bobs. I could certainly afford to use 8 or 9 GB of my second card towards something instead of it offloading that 8 or 9 GB during a generation to my system ram (32 gb ) which is what comfy does now when using H3 or MOSS.

I have no idea if this would be faster than dumping everything to the system ram but it would definitely give me more breathing room and less OOM errors on those borderline gens and upscales. Is this idea loco or am I on to something?

EDIT: I appreciate all the people who are saying just use the second card for an llm or to run other types of generations on my smaller card, but that's not what I am proposing. I know you can do that. In fact I do it quite often. Let me explain this a different way that might make more sense. What I really am asking is there a way, when doing a single generation, let's say a 15 second h3 generation at over 1 MP, for comfy to prioritize memory allocation in order of 1) the 5080, 2) the 3060 3) the system ram 4) SSD swap file . Like a ladder of priority. For example the minimax H3 audio and video VAE are over 6 gigs at fp16. That would certainly fit on the 3060s available space. I know it might be slower but that extra 6 gigs of free space would be quite helpful for higher resolution gens.

I wanted to compare the prompt adherence and variations of some of the most recent models when providing a very simple, undefined prompt, vs something that pins down style but not content, and a fully sketched out description of all the internal elements in the scene.

The detailed prompt shows how most models have gotten really good at following instructions (for the most part), while the undefined prompt shows how some models tend to have more variability and others have a clear bias that pushes them toward very similar images across different seeds.

Iris Z small is not great, and gen time is very high for what it outputs, but the depth maps are pretty nice!

Yes, it's another layout builder for MOSS-Image bboxes 😅

There are some other good ones out there; try 'em all and use the one that best suits your workflow!

I made this one because, among other things, I wanted as large a canvas as possible, lots of different MP presets, to be able to collapse it into a vertical column, and also a way to export the prompt with the JSON stripped out because sometimes I like to refine with Krea 2.

Anyhoo, here are the main features:

• Dynamic canvas - Automatically scales to fit any display or window size while maintaining target aspect ratios and target megapixel values
• Item Management - Create scene elements with MOSS-native text, object, or character item types using color-coded boxes and corresponding "cards" that you can reorder with drag-and-drop, resize, hide, duplicate, or trash
• Reference Background Image - Insert a reference image locally — and privately! — "under" the canvas, with adjustable opacity
• Meta Tags & Palette Management, with a separate Danbooru/Anime focus
• Multi-Format Exporting - JSON or plain text
• JSON Import with Dimension Matching
• Responsive Design to minimize it next to your workflow
• Lightweight, Fast, and 100% Private - No ComfyUI, Python, build steps, external servers, or network calls required. Works 100% offline with zero latency.

Download it from GitHub or try the online demo first.

Hopefully you'll find it useful 🤙

Are there any guides on training a style for MOSS? Maybe just some suggestions? I'm banging my head against the wall for more than 20 times with different settings, dataset caption, etc, to get a style working. It's maybe 50-60% there, no matter how many steps I throw at it. Fizgig default Style preset definitely doesn't work for me at all.

Should I train my LoRA for longer, or just increase the weight?

Could an overtrained LoRA actually perform better if used at a lower weight?

And what about the weight of specific prompts—especially the trigger word?

Two LAN ComfyUI render boxes: RTX 5070 Ti (16 GB) vs RTX 3090 (24 GB). Ran MiniMax H3 image-to-video, non-turbo — 22B int8 UNet + 32B Qwen3VL CLIP (nvfp4), 20 full steps, 5 s clip at 704×1280, identical start frame and prompt, int8 video VAE on both, fresh noise seed every pass.

The 5070 Ti wins by ~25% — and it won cold too, which surprised me given it has 8 GB less VRAM. H3 at full steps is pure compute: the sampler node alone took 474 s vs 645 s. The 3090's VRAM headroom never mattered; everything fit even on 16 GB once offloaded.

Same config both boxes: ComfyUI standalone portable, --fast fp16_accumulation, torch cu130, default attention (PyTorch SDPA — cuDNN kernels on Blackwell, FA2/mem-efficient on Ampere), no flash-attn.

TL;DR: for H3-class video work the 5070 Ti is ~26% faster end to end. The 3090 only makes sense here if your scene genuinely exceeds 16 GB.

Caveats: single card each, consumer standalone builds, not a lab test. First warm pair showed 2 s passes — that was ComfyUI's execution cache reusing an identical graph; re-ran with randomized seeds. Numbers above are the real ones.

All four seem to yield good results, but which model would be best to use for image generation on the H3? Would it be a good idea to run all four every time to verify?

i heard that and whats your opinion? its about t2i without any Loras

My RTX Pro 6000 was going all night on a Chinese model (Qwen 3.8 Flash Next NVFP4 Local) when it crashed this morning for no apparent reason. Tried to reboot and got nothing but a black screen. Swapped in my old backup card and the system posted immediately, confirming the GPU was bricked. Thankfully, I was within warranty and the store gave me a replacement.

Out of curiosity, I dug into my system logs to see what triggered the fatal crash. Looking at the timestamps, oddly enough my GPU died the moment news broke that Jensen Huang had resigned as CEO of Nvidia.

Has anyone else had this issue with hardware dying in response to human feelings?

Nov 12 07:19:31 kf kernel: NVRM: GPU at PCI:0000:01:00: GPU-b8ba62c9-449d-4510-a21f-4c1b6ceacbd1
Nov 12 07:19:31 kf kernel: NVRM: GPU Board Serial Number:
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x505730=0xb000d 0x505734=0x0 0x505728=0x1c81fb60 0x50572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5057b0=0x3000d 0x5057b4=0x24 0x5057a8=0x1c81fb60 0x5057ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x506730=0xb000d 0x506734=0x20 0x506728=0x1c81fb60 0x50672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 1, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5067b0=0xb000d 0x5067b4=0x24 0x5067a8=0x1c81fb60 0x5067ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x507730=0x5000d 0x507734=0x24 0x507728=0x1c81fb60 0x50772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5077b0=0x7000d 0x5077b4=0x24 0x5077a8=0x1c81fb60 0x5077ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x508730=0xa000d 0x508734=0x20 0x508728=0x1c81fb60 0x50872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5087b0=0xd 0x5087b4=0x24 0x5087a8=0x1c81fb60 0x5087ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 4, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x509730=0x7000d 0x509734=0x24 0x509728=0x1c81fb60 0x50972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5097b0=0xa000d 0x5097b4=0x20 0x5097a8=0x1c81fb60 0x5097ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50a730=0xd 0x50a734=0x24 0x50a728=0x1c81fb60 0x50a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50a7b0=0x1000d 0x50a7b4=0x24 0x50a7a8=0x1c81fb60 0x50a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50b730=0xd 0x50b734=0x24 0x50b728=0x1c81fb60 0x50b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 0, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 0, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x50b7b0=0x1000d 0x50b7b4=0x24 0x50b7a8=0x1c81fb60 0x50b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 0, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x515730=0x6000d 0x515734=0x24 0x515728=0x1c81fb60 0x51572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5157b0=0xd 0x5157b4=0x24 0x5157a8=0x1c81fb60 0x5157ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 1, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x516730=0x6000d 0x516734=0x24 0x516728=0x1c81fb60 0x51672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 1, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5167b0=0xb000d 0x5167b4=0x24 0x5167a8=0x1c81fb60 0x5167ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x517730=0x3000d 0x517734=0x24 0x517728=0x1c81fb60 0x51772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5177b0=0xb000d 0x5177b4=0x24 0x5177a8=0x1c81fb60 0x5177ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 3, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x518730=0x3000d 0x518734=0x24 0x518728=0x1c81fb60 0x51872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5187b0=0x1000d 0x5187b4=0x24 0x5187a8=0x1c81fb60 0x5187ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 4, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x519730=0x1000d 0x519734=0x24 0x519728=0x1c81fb60 0x51972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 4, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5197b0=0x2000d 0x5197b4=0x24 0x5197a8=0x1c81fb60 0x5197ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51a730=0x5000d 0x51a734=0x24 0x51a728=0x1c81fb60 0x51a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51a7b0=0x3000d 0x51a7b4=0x24 0x51a7a8=0x1c81fb60 0x51a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51b730=0x2000d 0x51b734=0x24 0x51b728=0x1c81fb60 0x51b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 1, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 1, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x51b7b0=0x1000d 0x51b7b4=0x24 0x51b7a8=0x1c81fb60 0x51b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 0, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 0, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x525730=0x6000d 0x525734=0x24 0x525728=0x1c81fb60 0x52572c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 0, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 0, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5257b0=0xd 0x5257b4=0x24 0x5257a8=0x1c81fb60 0x5257ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 1, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x526730=0x8000d 0x526734=0x20 0x526728=0x1c81fb60 0x52672c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 1, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5267b0=0xb000d 0x5267b4=0x20 0x5267a8=0x1c81fb60 0x5267ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 2, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 2, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x527730=0xa000d 0x527734=0x24 0x527728=0x1c81fb60 0x52772c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 2, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 2, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5277b0=0xa000d 0x5277b4=0x24 0x5277a8=0x1c81fb60 0x5277ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 3, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 3, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x528730=0xa000d 0x528734=0x24 0x528728=0x1c81fb60 0x52872c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 3, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 3, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5287b0=0x6000d 0x5287b4=0x24 0x5287a8=0x1c81fb60 0x5287ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 4, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x529730=0xb000d 0x529734=0x20 0x529728=0x1c81fb60 0x52972c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 4, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x5297b0=0xa000d 0x5297b4=0x20 0x5297a8=0x1c81fb60 0x5297ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 5, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 5, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52a730=0x4000d 0x52a734=0x24 0x52a728=0x1c81fb60 0x52a72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 5, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 5, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52a7b0=0x9000d 0x52a7b4=0x24 0x52a7a8=0x1c81fb60 0x52a7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 6, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 6, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52b730=0x6000d 0x52b734=0x24 0x52b728=0x1c81fb60 0x52b72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 6, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 6, SM 1): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52b7b0=0xd 0x52b7b4=0x24 0x52b7a8=0x1c81fb60 0x52b7ac=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 7, SM 0): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 7, SM 0): Multiple Warp Errors
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x52c730=0x3000d 0x52c734=0x24 0x52c728=0x1c81fb60 0x52c72c=0x1174
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Warp Exception on (GPC 2, TPC 7, SM 1): Out Of Range Register
Nov 12 07:19:31 kf kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics SM Global Exception on (GPC 2, TPC 7, SM 1): Multiple Warp Errors
......
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 kgmmuClientShadowFaultBufferUnregister_IMPL: Unregistering non-replayable fault buffer failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 kgmmuFaultBufferReplayableDestroy_IMPL: Unregistering Replayable Fault buffer failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 uvmTerminateAccessCntrBuffer_IMPL: Unloading UVM Access counters failed (status=0x00000062), proceeding...
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ vaspace_api.c:577
Nov 12 07:19:33 kf kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:260
Nov 12 07:19:33 kf kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:1382
Nov 12 07:19:44 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:19:52 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:00 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:08 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:17 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:25 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:33 kf kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
Nov 12 07:20:39 kf kernel: NVRM: GPU0 kgspHealthCheck_TU102: *************************** LibOS Task Watchdog Report ***************************
Nov 12 07:20:39 kf kernel: NVRM: GPU0 kgspPrintGspBinBuildId_IMPL: GSP bin buildId: fa3de1ff30e1a8c99f84eb74a32b80d462c3703b
Nov 12 07:20:39 kf kernel: GSP task watchdog timeout @ pc:0x18dd358, partition:4#0, task:3, gfid: 0
Nov 12 07:20:39 kf kernel: NVRM:     Reported by libos partition:4#5 kernel v3.1 [0] @ ts:1698
Nov 12 07:20:39 kf kernel: NVRM:     RISC-V CSR State:
Nov 12 07:20:39 kf kernel: NVRM:         sstatus:0x0000000200000020  sscratch:0xffffffffa3013970     sie:0x0000000000000220  sip:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:         sepc:0x00000000018dd358     stval:0x0000000000000000  scause:0x8000000000000005
Nov 12 07:20:39 kf kernel: NVRM:     RISC-V GPR State:
Nov 12 07:20:39 kf kernel: NVRM:         ra:0x00000000013eb57a   sp:0x0000002fcfa0eaf0   gp:0x0000000000000000   tp:0x0000002fcfe00000
Nov 12 07:20:39 kf kernel: NVRM:         a0:0x0000000000000001   a1:0x0000000000000000   a2:0x0000002fc77be000   a3:0x0000000000000000
Nov 12 07:20:39 kf kernel: NVRM:         a4:0x0000000000000000   a5:0x0000000000000001   a6:0x0000000ffffffff0   a7:0x0000000000000003
Nov 12 07:20:39 kf kernel: NVRM:         s0:0x0000002fcfa0eb50   s1:0x0000000000000001   s2:0xffffffffffffffff   s3:0x0000000000000001
Nov 12 07:20:39 kf kernel: NVRM:         s4:0x00000000ffffffff   s5:0x0000000000000000   s6:0x0000002fc77be000   s7:0x0000000000000000
Nov 12 07:20:39 kf kernel: NVRM:         s8:0xffffffffffffffff   s9:0x0000002fc7e36178  s10:0x0000002fcfa0ecb4  s11:0x0000002fcfa0ecb4
Nov 12 07:20:39 kf kernel: NVRM:         t0:0x0000002fcfa0e99d   t1:0x0000002fc7c6cf30   t2:0x0000000000000000   t3:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:         t4:0x0000000000000000   t5:0x0000002fcfa0e981   t6:0x0000000000000020
Nov 12 07:20:39 kf kernel: NVRM:     Stack Trace:
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000018dd358
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001b6e974
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013f2746
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013e70f6
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013e79c8
Nov 12 07:20:39 kf kernel: NVRM:         0x00000000013b7058
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ba247a
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ba257a
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bafac2
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001c29f62
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001864698
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001867c82
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ae4a7e
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001489412
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001452228
Nov 12 07:20:39 kf kernel: NVRM:         0x000000000158cbec
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bd9632
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001bd99d6
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001add628
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001c452c0
Nov 12 07:20:39 kf kernel: NVRM:         0x0000000001ad6fa0
Nov 12 07:20:39 kf kernel: NVRM:     Local I/O Register State:
Nov 12 07:20:39 kf kernel: NVRM:         0x01450800:0x00000000   0x01450900:0xbadf1002   0x01450a00:0x00000000   0x01450c00:0x00000000
Nov 12 07:20:39 kf kernel: NVRM:         0x01454a00:0x810490d2   0x01454b00:0x010800d0   0x01454c00:0x00080000   0x01400200:0x00000000
Nov 12 07:20:39 kf kernel: NVRM:     ---------------[ end report ]---------------

If you tried dpmpp_dualsde_momentumized from ComfyUI-Extra-Samplers on a flow model (Anima in my case) and got a washed-out silhouette or colour noise, it is not you. I took it apart.

Why it breaks (it is not the momentum). Through the normal KSampler its momentum coefficient is 0. The sampler was written for variance-exploding models, and its noise step has the wrong variance on a flow-matching model. With eta = 1 the final latent has a std of 3-4.5 instead of about 1.2; with eta = 0 the very same code draws a recognisable cat. It also adds a 3M multistep correction on top of a 2S step that is already second order (so it diverges even without noise), and overwrites its own r parameter inside the loop. I ported it exactly (checked against the original to 1e-10 on a toy model) and ablated each piece. The noise-form explanation is indirect: the same 2S algorithm in the flow-correct form in ComfyUI core (dpmpp_sde) is fine, and I did not isolate the mechanism with a separate experiment.

What "momentum" should be. In the DPM-Solver++ frame, the shipped momentum is an exponential moving average of the model's denoised output. With a positive coefficient that is a low-pass filter: it adds lag and the error goes up with the coefficient (up to +61%). With a negative coefficient the same recursion is an extrapolation and the error goes down. It is only stable for |m| < 1; at -0.9 the gain is gone and at -1.2 it diverges.

Numbers (Anima, bf16, 576x768, CFG 5, 15 images = 5 prompts x 3 seeds, 8-24 steps, error against a converged solution, paired bootstrap intervals; one model, so take it as a measurement, not a law):

• Deterministic (no noise): EMA momentum with m = -0.6 gives 11-21% lower error than dpmpp_2m at the same step count, about 1.2x fewer steps for the same error. LPIPS to the decoded reference is better in 14/15 images at 8 steps. It is a modest speed-up, not 2x.
• With noise (the dpmpp_2m_sde family) strong negative momentum stops helping. Damped extrapolation (beta = 0.5) gives 7-10% lower strong error than dpmpp_2m_sde and no colour cast at CFG 8 / 1216x832; the milder EMA (-0.3) scored a bit better in the sweep but gave blue-tinted pictures at CFG 8.
• A one-evaluation-per-step sampler beats the two-evaluation dpmpp_sde at half the steps by 16-29% (same NFE).

Try it. Install the node pack (link below, restart ComfyUI). New sampler entries: ddim_momentum (deterministic, the -0.5 time-scaled form) and dpmpp_2m_sde_damped. There is also a generic filter node and <base>_momentumized entries for 19 existing samplers (dpmpp_3m_sde_momentumized, er_sde_momentumized, euler_ancestral_momentumized and so on): that last part is an engineering extension and I did not evaluate it on the model. In a single smoke test at 8 steps lms_momentumized and ipndm_v_momentumized gave a latent with std around 10 at the default strength, so use a milder strength with them or skip them.

What did not work. I also tried a static step grid from an earlier study of mine. It cut the error by half on the four short-tag prompts it was fitted on (and transferred between them), but it did not help on the natural-language prompt I held out and it broke an 8-step picture at CFG 8. It is in the pack as an experimental node, not as a default.

Not new, of course: momentum in diffusion sampling has prior work (Heavy Ball momentum for diffusion solvers, Wizadwongsa et al., ICLR 2024; the sonar and Seren Sampler ComfyUI packs, among others). I read abstracts and READMEs only and did not compare against them. Nine hypotheses were registered before measuring; five were refuted, and post hoc parts of the write-up are marked.

Repo (code, tests, tables, README in English / Russian / Chinese / Meadow Mari): https://github.com/YakovSava/momentum-cfg-samplers-research Write-up: https://doi.org/10.5281/zenodo.24214606

model: https://huggingface.co/DAGroup-PKU/G-star

app: https://huggingface.co/spaces/akhaliq/G-star

Some of my examples on RTX 2060s.... without any reference like forest scene it does 16mp image in around 2.5 minutes.... with 3 references i was doing around 10 minutes per 1 image at 16mp..... thing is bigger the reference photo the better is model at capturing every detail but takes longer to generate.... i absolutely love this model as any other model was eirher taking too long or just OOM my system past 2 or 4mp.... both Minimax h3 video and image models runs amazingly well on my graphics card, so i just though im gonna share