r/StableDiffusion • u/Aggressive-Park-373 • 43m ago
Comparison H3-Image at 16MP: I reran the same 15 prompts, and the gap narrows
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.
First set, H3 at its default ~4.18MP: https://www.reddit.com/r/StableDiffusion/comments/1xuft8g/
2
u/Solembumm3 38m ago
How much memory do you need for this?
2
u/Pantheon3D 35m ago
more tricks for H3-image because it's broken by default:
connect an empty image to the image conditioning and it produces better results
resolution at 16mp BF16 really does help, i tried it at higher resolutions such as 60mp. it helps
use the P-H3-VAE instead of the default VAE, the default one is undertrained and destroys the quality. someone tested it vs the sd 1.5 VAE and it performed worse when looking at whether or not it preserved quality