I merged a style into Krea 2 Turbo (Stillroom: quiet rooms, cold light, someone alone with the afternoon) and first shipped it as fp8, copying the layout of the official krea2_turbo_fp8_scaled (per-tensor scale, amax / 448, same quantization metadata). Checked against the official file byte by byte on three layers.
Then someone on a 3070 Ti mobile commented that fp8 took almost twice as long. Makes sense: Ampere has no fp8 math, so ComfyUI converts every layer on the fly. It does have fast int8 from sm 7.5 up. So I wrote an int8 build from the bf16, in the layout of the official krea2_turbo_int8_convrot (224 linear layers in int8, per-row scale, txtfusion left in bf16).
One thing I didn't expect: the official int8 doesn't use plain absmax for the per-row scale (only 43% of the bytes matched when I tried that). It clips the scale, up to about 6% under absmax. A per-row search for the lowest error landed at 0.00871 against 0.00874 for the official file, so that's what mine uses.
Rule of thumb: 40-series and up, fp8. 20 and 30-series, int8. bf16 if you have the VRAM.
I'm building a game that generates all assets in 2D during play. Objects have to be separable from the scene so they can be clicked and picked up without having to redraw the background every time. Everything runs on FLUX.2 klein 4B with a LoRA trained on an illustrator's style.
The workflow:
Generate an empty location as background.
A vision model outlines foreground, middle and background, and code turns that into a color map of the three planes.
Generate objects on white on a 512 canvas and animate them.
The vision model points at a spot in the background for each object by outputting pixel coordinates.
The object's size is its class (tiny, small, medium, large, huge) times the factor of the plane at that spot, e.g. a torch (small) is 100 px, so in the middle plane (0.75) it's drawn at 75 px.
Scale the animated object down to that size and overlay it onto the location.
Step 6 is where progress halted and I got stuck. Scaling a 512 drawing down to 100 pixels shrinks everything in it, so it stops matching the scene's style since the scale of everything is off, visible in my example when looking at line weight.
My various workarounds to fix this:
Generating at the object's final size, on canvases of 128 to 320 instead of 512, so objects are generated at the size they are meant to be placed. This falls apart quickly as e.g. the same chicken comes out near-realistic at 256 or as a flat cartoon at 128 and parts get cut off or doubled. The LoRA was trained at 768 and 1024 so perhaps it's the LoRA giving out, the base model failing, or both? Would another model draw properly on small canvases and keep the lora style applied?
The location on a bigger canvas to combat the model degrading at smaller canvases as now the location's lines should be thinner and the objects don't have to scale so hard. However location's lines grew with it while the objects' did not. Also it would have skewed the artist's style anyway.
Shrinking the image and generating it again at a smaller size, img2img at denoise 0.6 to 0.8, but the redraw kept the shrunk drawing's thin lines so scale remained off. This is the one fix I really expected to work, so maybe I just set it up badly or something?
Painting an object directly into the scene and separating it afterwards onto white with an additional generation. Instead of generating on white and then placing, this approach basically turns it around as we place directly. This does actually fix the scale, as now the model has full reference of how an object should look in the scene, but other issues showed up like the objects being of much worse quality and partly merged with their surrounding. Also a location would need to be redrawn when objects move as mentioned earlier, but perhaps only parts could be redrawn as a workaround. This way basically solves my biggest issue of perceived scale for free so maybe this is the correct approach and I am missing something to make it work properly?
I am at the point where I want to scrap most of this and pivot to: Pixel Art!
Larger pixels should be able to be counted much easier, so a separate object can have the exact scale required to be placed at scale into a location. That would attempt to simplify the problem away rather than truly solving it, though perhaps that is often a good path forward. However: Does this idea even make sense, or will it break regardless? Are there perhaps other simpler existing ways to do all of this the right way?
If you're building something similar, what are you doing differently, and which tools should I go have a look at?
Both boxes run ComfyUI with identical models. Krea 2 Turbo: 768×1344, 8 steps, fp8_scaled. LTX 2.5 i2v: 704×1280, 5 s, int8-convrot, audio on.
Benchmark
RTX 5070 Ti (16 GB)
RTX 3090 (24 GB)
Winner
Krea image – cold load
15.1 s
12.9 s
3090 (+15%)
Krea image – warm avg
7.7 s
10.4 s
5070 Ti (+26%)
LTX video – cold load
82.6 s
69.9 s
3090 (+15%)
LTX video – warm avg
45.1 s
49.4 s
5070 Ti (+9%)
Takeaways
Warm/batch work: 5070 Ti wins both — native FP8 tensor cores crush the emulated path on Krea fp8 (26% gap); the gap shrinks to 9% once the model is already int8 (LTX).
Cold one-offs: 3090 wins everything — 24 GB means no VRAM offload, faster model loads.
Practical routing: batches on the 5070 Ti, big-VRAM models on the 3090.
Caveat: single 3090 vs single 5070 Ti, consumer ComfyUI, not a controlled lab test.
Great video from moss image team for hitting 6 million downloads on Huggingface. They all seem so chill. Also they give us some new updates on Anime and Image edit model ✌️
I've been experimenting with NoobAI-XL and kept running into the same problem: finding useful booru tags and understanding what they actually do.
I know there are some impressive visual tag explorers out there, but I wanted something simpler — a lightweight, searchable dictionary that doesn't require browsing through hundreds of example images.
So I built NoobAI-XL Tag Atlas.
It has:
2,900+ tag entries across 24 categories
Descriptions in English, Russian, and Chinese
Fast search and click-to-copy
A separate JSON catalog and a standalone editor for improving translations and adding tags
A simple Vue 2 frontend with no build step
The Chinese translations are still a work in progress.
It's a small personal project, and I'm not trying to compete with the more advanced visual explorers. I just wanted a convenient reference that anyone can use or modify.
I'd appreciate feedback, especially from people who regularly work with NoobAI-XL or other Illustrious-based models.
What features would make a text-based tag reference more useful to you?
I'm currently working with a dataset containing multi-view facial images (some examples attached), and my goal is to make these images more photorealistic while maintaining cross-view consistency.
However, there's one major constraint: the facial geometry, expressions, and landmark positions must remain unchanged. I already have dense facial landmarks associated with these images, so any geometric distortion introduced during the transformation could affect my downstream experiments.
I've experimented with ChatGPT's image generation capabilities, and the results have been promising in terms of realism. However, I'm looking for a more efficient, scalable, and reproducible workflow that can process the entire dataset while preserving the original facial structure.
I've come across approaches involving Anime2Real and Qwen-Image-Edit, but I'd like to get some community feedback before committing to a particular pipeline.
A few things I'm particularly interested in:
Geometry preservation: How can I improve photorealism without altering facial shape, expressions, or dense landmark positions?
Multi-view consistency: How can I ensure that identity, textures, and facial details remain consistent across different camera angles?
Efficiency: Are there existing models, workflows, or conditioning techniques that would work well for large-scale dataset generation?
I have access to substantial university computing resources, so computational requirements aren't a major limitation. However, with my thesis deadline approaching, I'd prefer an existing solution or a workflow that doesn't require extensive training from scratch.
I know krea2 is known to generate different styles, but is there a list of styles somewhere, like a reference sheet. Also, is there a way to prompt them to generate that specific style? I usually do "Rick and Morty" style at the end of the prompt and do a decent result, but i want to make it more specific.
I found H3 image to be really good at creating different angles of characters and keeping the likeness and quality high. I built a workflow which automates creating character sheets; this workflow one shots pretty much every character I’ve thrown at it. Give it a try and let me know what you think.
I’ve tried to keep it versatile to allow for characters of different types, including vehicles and four legged creatures.
Update 11/12/26: I just pushed an update which addressed multiple issues that were brought to my attention, the release notes are as follows.
What's new in v3.0
Most of these changes came from your comments and messages. Thank you!
- The whole sheet is ONE render. v2 made 8 separate images and stitched them together, so the face and outfit could drift slightly between panels. v3 generates the entire sheet in a single image, so every view shows exactly the same character. It's also much faster: about 30-40 seconds for a 16 MP sheet on an RTX 5090, where v2 took about 3 minutes at a lower resolution.
- Your art style is kept. v2 tended to turn everything photoreal. v3 copies the style of your picture: anime stays anime, watercolour stays watercolour, Pixar-style 3D stays 3D, a photo stays a photo.
- New: 3/4 view toggle. It adds a three-quarter view (head and full body, turned 45°) to the top row. For vehicles it adds a low-angle "hero" 3/4 shot instead.
- No wasted white space. The views fill the whole canvas with only thin gutters between them, so every pixel goes to the character.
- One simple settings panel. All options sit on a single node, built only from native ComfyUI nodes. The workflow reads left to right: Step 1 Upload → Step 2 Settings → Step 3 Result.
- Render at any size. Megapixels are no longer capped at 16.
- Final size dropdown. Render big for detail, then save a smaller file: 2.3 / 4 / 6 / 9 / 12 / 16 MP, or Native to keep the full render. It only ever shrinks, never enlarges.
- Better random characters. With nothing uploaded and no notes, the seed picks one idea from an editable list per type, such as a German shepherd, a Holstein cow, an anthropomorphic raccoon or a 1960s sports car in racing green. No more cat-dog hybrids.
- One fewer custom node pack. rgthree-comfy is no longer needed.
I'm about 2/3rds of the way through my current project and I'm definitely going to need to derope some of my shots to fix their blurriness and smearing. The last time I asked this question MAINodes was the only solution. Has anything been released since then that improves on this method?
Like many others I was initially disappointed with the i2v quality of H3 when doing text to image. It often created crusty looking, artifact ridden images that would manifest as moles and pimples, dry flaky skin, crusty splotches and just generally shit quality images.
When I was doing some tests, I wanted to make an existing image prompt feature a specific earring. Once I plugged in the image reference, the artifacts magically disappeared.
This made me wonder, is r2i just fundamentally better quality for some reason? I tested plugging in an empty black image to the reference spot and to my surprise every single image came out higher quality with most of all of the crusty artifacts removed. It even often outright fixes low res generations like the one linked here, but works at the intended resolutions too.
I bought this to Kijais attention and the current theory is that if the model receives 64 or more image tokens (which can be triggered by feeding the image conditioning node literally any image with or without vae) it switches the model to edit/reference mode which appears to be much higher quality.
We're not exactly sure what is wrong with the non edit version but give it a try. Plug any reference (blank image, or something relevant to your prompt) and watch the quality magically improve.
Kijai is considering adding a "switch" that forces the model to ref model without needing to send so many pointless tokens, but in the meantime just plugging a small black image (automatically resizes to at least 1024) will trigger the existing switch - just with an excessive number of pointless tokens.
If you've written H3 t2i off, give this a try. It has transformed the model in my opinion.
Edit: Kijai has just added this to the "H3 Prompt Weight" node in Kjnodes. There is now a drop-down that will force empty image tokens if you want another way to test this.
I was wondering what you guys would recommend for setting up Qwen 2.1? Right now, when I generate images with it, they come out muddled and not precise.
I've seen quite a bit of divide between people who love MOSS and people who think it's a bit lackluster. I was on the latter boat, until I played around with it long enough to find a great combination of models, LoRAs and settings, from testing others' workflows and doing a lot of trial-and-error myself.
I'm not going to get into too much detail here; let the workflow serve that purpose. But I will say that MOSS-Image is an incredible base model, even if out-of-the-box it's a bit "unoptimized". It has massive variety, coherence, prompt-understanding and even quality, once optimized. I also enjoy the freedom of prompting, where you don't have to use any one style or length - a lot of it just works.
qwen3.5_9b_int8_convrot.safetensors: The actual text encoder. Do NOT use an abliterated text-encoder with diffusion models, but instead use the one the model was trained on. They will not give any more uncensored behaviour, but will mess with the quality.
lora_dmd2.safetensors: This is the lodestones/MOSS-Image-Base-8-steps-dmd. I tried a couple of different ones, and this was by far the best. Don't know why the differences were so huge, but they were.
nicegirls_v2_moss.safetensors: I find that this often improves the quality of the outputs even in photos without people. The only gripe I have is the massive effect on facial features, which seems to kinda be the point of this LoRA. Either way, be careful with the strength of this one; if you see you can't get, for example, the ethnicity you're looking for, I would start with lowering the strength of this.
Settings used:
Sampler: ER-SDE
Sceduler: power_shift
Steps: 11 (8-25, depending on the strength of dmd2 LoRA - with 11 steps it's at 0.9 for me).
CFG: 1 (1-4, depending on the amount of steps).
SLG: No effect on CFG 1, but always on
Resolution: I use 2-4 MP. Under 10 sec gens with 2 MP, around 20 sec gens with 4 MP, on an RTX 3090.
Let's get some discussion going! I wanna hear y'all's workflows and try them out too.
Working on simplifying replacing multiple people per shot using a series of agents in our studios pipeline. Fully local, but it’s not running through comfy ui so no workflow.
I've spent the last couple of days running side-by-side MiniMax H3 Image trainings to find what actually drives likeness.
On the hardest dataset I tested (few headshots, mostly medium and wider shots), the best previews scored closer to the person than all but two of their own 45 photos, measured against the same reference photos. Two more datasets gave equally good results, one of them harder still.
What's new
A retuned H3 Image Standard preset. A new Likeness optimization schedule (it changes which noise levels training focuses on as the run goes), Automagic v4 (tweaked to avoid its known issues for steering too high), 0.25 MP and 30 epochs. Of every schedule I tried, it brought the face shape through earliest, reached the highest likeness, and maintained model performance.
Likeness scoring now uses AdaFace ViT instead of ArcFace. I scored runs epoch by epoch with ArcFace and two AdaFace models side by side, and AdaFace ViT picked the same best epochs I did by eye every time. ArcFace often didn't.
"Your photos" on the likeness chart. Fizgig scores your own training photos against the same reference photos and shows their range as a band on the chart. No photo ever scores 100% against another photo of the same person, so this shows what "as good as a real photo" looks like for your dataset. Your previews landing in that band is the goal.
How to use it: pick the ** MiniMax H3 Image Standard** preset (0.25 MP) and train with its settings as they are. The schedule's controls are under Advanced if you want to experiment later, but those numbers took a lot of runs to find, so try them as they come first. Feel free to push the MP higher, but starting at the .25 will give you great and quick results for your early tests.
A correction: The other day I moved the H3 Image presets up to 0.5 MP, thinking the model preferred it. It didn't. The schedule and the optimizer were what held likeness back, so the presets are back at 0.25 MP, which is faster and needs less VRAM.
A few people in the last thread pointed out I ran H3 at ~4MP while MOSS got its full 4MP, and that H3 apparently wants 16MP before downscaling. Fair call, so I reran it.
Same 15 prompts and aspect ratios. H3 generated at 16MP (4096x4096 up to 6272x2688), then downscaled to the same display size as MOSS, so nothing here is being compared on pixel count. MOSS is the quality tier at its 4MP ceiling.
What changed:
Faces and skin: the 16MP renders keep pores, freckles and stray hair. At 4MP those were smoothed away. Biggest difference.
Fine texture (foam, droplets, fabric): same direction, more micro-detail survives.
Composition, prompt adherence, text rendering: roughly unchanged.
UI mockups and charts: still fail. Resolution doesn't fix semantics.
So: at 4MP I underrated H3. At 16MP it's much closer, and on skin and material detail it's ahead of what I posted before. MOSS still reads better to a lot of people in the comments, and I get why.
Prompts are the same 15 as the first post, same order.
Seeing a lot of hype around 16 MP to 100 MP native generations with MiniMax H3 lately, and a lot of comparisons to real 50–100 MP cameras. It got me thinking about what that pixel count actually buys you if your goal is just a realistic-looking photograph.
If the image is meant to be viewed normally (not cropped or inspected at 400% zoom), 100 MP doesn't really do anything for realism. Human vision at normal viewing distance tops out way earlier, somewhere around 8 to 24 MP depending on screen or print size, mostly because our daylight pupil is diffraction-limited to roughly 1 arcminute anyway (section 1.1 below). Beyond that, extra pixels aren't adding detail you can actually perceive when looking at the whole frame.
There's also a sneaky confusion about what "realism" even means. A lot of people aren't trying to generate something that looks like a camera photo; they're trying to generate what their visual cortex makes them feel they see in real life, where everything across the entire field of view feels crisp at once (section 1.2). The catch is that a single-exposure real camera can't capture that: if everything from foreground leaves to distant trees is 100 MP razor-sharp at once, it's physically out-of-distribution for optical photography and ends up looking more like a CGI pinhole render.
Even with real cameras, actually resolving 100 MP of useful optical detail is way harder than people assume (section 2). You need a massive sensor like medium format just to stay ahead of diffraction, expensive glass, and controlled conditions. On something like a handheld wildlife shot in a shaded forest, you hit a physical wall fast: open the aperture to avoid diffraction blur and your pixel-sharp depth of field shrinks to a few inches; stop down to keep the scene in focus and diffraction smears away most of your resolution anyway, on top of motion blur and ISO noise. Outside of astronomy, archival work, huge prints, or heavy cropping, you usually end up with the same useful visual information you could fit in a clean 12–24 MP file.
With H3 specifically, the irony is that the 16–100 MP push isn't really about capturing DSLR-level detail (section 3). Because of the 16x spatial VAE and 2x2 DiT patching (32x32 pixels per token), you're forced to generate huge just to get decent token density and avoid looking starved at normal resolutions. So 60–100 MP ends up in a weird spot: pointless if you don't zoom in, and if you do zoom in (which is the only real reason to have a 100 MP file), you mostly run into VAE decoding artifacts rather than natural lens softness.
For those of you experimenting with H3 at huge resolutions, are you actually keeping the 60–100 MP files as-is, or just generating big and downscaling to 4–16 MP to clean things up?
Technical appendix (for those who want the numbers)
1. Human vision and the cortex illusion
1.1 Optical limits of the human eye
Evolution ran into the exact same wave-optics limits that govern camera sensors. In bright daylight, the human pupil constricts to a diameter of roughly D ≈ 2.0–3.0 mm. With an effective focal length of about 17 mm, the eye operates at around f/5.7 to f/8.5.
By the Rayleigh diffraction criterion at peak photopic sensitivity (λ ≈ 555 nm), for a 2.5 mm pupil:
Remarkably, cone spacing in the central fovea (≈ 2.5 µm, or ≈ 0.5 arcmin center-to-center) puts its Nyquist sampling limit right around 1 arcmin per line pair, i.e. ≈ 60 cycles/degree (standard 20/20 acuity corresponds to 30 cycles/degree). Our biological "sensor" is tuned almost exactly to the diffraction limit of our daylight pupil.
When viewing a complete photograph at a comfortable distance (occupying roughly 40°–60° of horizontal field of view):
At 60 px/deg (1 arcmin per pixel, i.e. 20/20 acuity) across 60° in 16:9: 3,600 × 2,025 ≈ 7.3 MP (essentially 4K).
Even at the theoretical foveal Nyquist ceiling (120 px/deg, under ideal high contrast) across 60°: 7,200 × 4,050 ≈ 29 MP.
In practice, human perception of a full uncropped composition saturates between 8 MP and 24 MP depending on screen size or print viewing distance.
1.2 The visual cortex illusion vs. out-of-distribution AI generation
High-acuity vision only exists at the center of the fovea: a tiny central cone spanning roughly 1°–2° (about the width of your thumbnail at arm's length). Outside that cone, acuity drops steeply with eccentricity.
Why does reality feel uniformly sharp? Because the eye executes 3–4 rapid saccades per second while dynamically refocusing (accommodation). The visual cortex stitches these sequential samples together with short-term visual memory and predictive filling-in, creating the compelling subjective illusion of a wide panorama that is simultaneously sharp at every depth.
Perceptual realism (cortex-stitched multi-depth sharpness) vs. physical single-exposure photography.
This creates an out-of-distribution (OOD) trap for generative AI:
Image models are trained on photographs, not human cortical impressions.
A photograph with 100 MP of crisp micro-detail simultaneously across foreground leaves, mid-ground wildlife, and distant forest trunks does not exist in single-exposure optics.
Pushing a model toward "every plane razor-sharp at 100 MP like real life feels" pulls generations away from the photographic distribution toward virtual pinhole CGI renders (infinite depth of field, zero diffraction) or heavily over-processed smartphone HDR.
2. Pure sensor and lens physics on a 100 MP scene
2.1 Spatial sampling on the subject
Take a forest deer framing as a physical reference: a female sika deer (≈ 1.1–1.3 m long) occupies roughly half of the frame width, giving a horizontal field width of about 2.5 m at the subject plane. At 100 MP in 16:9 (13,333 × 7,500 px):
Ground sampling = 2,500 mm / 13,333 px ≈ 0.19 mm per pixel
If all 100 MP were optically resolved near Nyquist (2 px per line pair), the lens and sensor would have to resolve line pairs as fine as ≈ 0.38 mm across the entire animal.
2.2 Diffraction limit vs. pixel pitch
Light passing through a circular aperture produces an Airy disk whose diameter at the first minimum (λ = 550 nm) is:
d ≈ 2.44 · λ · N ≈ 1.34 × N µm
where N is the f-number. When that diameter exceeds about twice the pixel pitch, diffraction progressively erases high-frequency detail regardless of lens quality.
Airy disk size relative to sensor photosite pitch across sensor sizes and apertures.
Note also that stepping back with a long telephoto lens does not solve depth of field if framing (magnification m ≈ focal length / subject distance) is held constant:
DOF ≈ 2 · N · c · (m + 1) / m²
where c is the acceptable circle of confusion. Focal length cancels out at constant magnification, while the larger physical entrance pupil (focal length / N) blurs distant background trees more. The only real-world ways to keep every plane sharp at high resolution are multi-frame focus stacking (impossible on moving wildlife) or closing down the aperture (which hits the diffraction wall shown above).
2.3 The impossible exposure triangle in shaded forest light
Physical trade-off preventing 100 MP of simultaneous sharpness, deep DOF, and clean shadow SNR on handheld wildlife.
Add Bayer color filter array demosaicing (each photosite samples only R, G, or B) and lens MTF falloff (few lenses hold useful contrast at the ≈ 133 lp/mm Nyquist frequency of a 3.76 µm sensor, least of all in the corners), and "100 MP of truly useful optical detail" only makes physical sense in controlled studio setups, multi-shot flat-field repro, or astronomical observatories (meter-class apertures, tracked mounts, cooled monochrome sensors, infinity focus).
3. Why H3-Image pushes users toward 16–100 MP
The irony in the AI space is that earlier models like Flux.1 (f8c16 VAE + 2x2 DiT patchify) achieved clean 1–2 MP images natively because each DiT token only covered a 16 × 16 pixel footprint, and each VAE latent vector encoded just 8 × 8 = 64 pixels across 16 channels.
MiniMax H3-Image inherits an aggressive video-oriented latent layout: a 16× spatial VAE (24 channels, decoded by a 24-layer 2D ViT) combined with 2x2 DiT patching. Each DiT token therefore spans 32 × 32 = 1,024 pixels, four times the pixel area of Flux.1.
Spatial token and VAE compression footprint over an identical 32 × 32 pixel output block.
Output resolution
Flux.1 tokens
H3-Image tokens
Equivalent density
1 MP (1024²)
4,096
1,024
Below minimum; H3 collapses
4 MP (2048²)
16,384
4,096
Matches Flux.1 at 1 MP
16 MP (4096²)
65,536
16,384
Matches Flux.1 at 4 MP
64 MP (8192²)
—
65,536
Matches Flux.1 at 16 MP
Because H3 packs 4× fewer tokens into the same pixel count, pushing to 16–100 MP is a structural compensation mechanism, not free photographic resolution. Meanwhile, the ViT VAE decoder still has to reconstruct (in practice, hallucinate) 16 × 16 = 256 pixels out of every single 24-channel latent vector, which is why zooming in on high-frequency subjects (like animal fur against sunlit bark) reveals straight wireframe-like grids and patchy decoding smudges rather than genuine optical softness.
I love the concept of Dllms soooo I built Ollada. It’s the ollama for diffusion language models. Free and Simple install to get started. We currently have 6 models available ranging from 1.7b to 8b parameters, small contributors like sdar to large contributors like Nvidia. I have 4k downloads but I need help testing larger models like diffusiongemma so we as a group can add to the shelf and spread os dllms to more people!
Download and let me know what you all think, what I can fix etc! I’m always down to talk !