It does require a bit of re-learning how to prompt. You have to be implicit about the stuff you want to see.

I've been fighting to get "dude sitting at the kitchen table" to not chop off his head at 16:9 for a good chunk of today. So far I haven't found the magic words...

@iam440 "subject looks at the viewer. the man keeps eye contact. the man contemplates existence. the man has a face expression of contemplation. the man has shaggy hair and thick eyebrows and a handlebar mustache."

I do know what you mean. I am being hyperbolic with this example, but like each of those sentences alone might give you his face. you just need to explicitly call things out. Essentially when i have a prompt that is cutting parts out, it's either because A) it doesn't mention it, only mentions the body or the action (like seated at a table), or B) it's using some weird description of the setting that would enforce my true subject to not be present. Sometimes this can be adjusted by putting the important part first (ie man sits at table, not table man sits at), or finding "anchor" phrases by cutting away sentences I am most unsure about.

the part about anchor phrasing really is key for any of these modern models. any time I have a really complicated prompt that isn't working, i try and compose it into the smaller blocks of different image generations to fine tune the prompt. I mean in this example, if the man sitting at the table was doing really complicated stuff, you might find you're losing the core point of the photo. If you can find a really simple version of the "a man is seated at the kitchen table reading a newspaper, god rays, glasses", and then compose that within the larger example, it's easier than figuring it all out at once.

The model is much more prompt adherent than anything else, not sure why you get this issue.

I've found this model to adhere to most prompts better than the default krea 2 turbo model

Don't confuse an issue in the model, with an issue in prompting. If you don't write down what you want to see, then sure: you don't get it.

Describe shoes: you'll get shoes and the bottom of a body. Describe hair, hairline, the space above the head, etc. you'll get that too.

Be EXHAUSTIVE, like you're writing a book, describing a new protagonist. Don't write just "a man sitting on a chair". Or, sure, you won't ever get what you're expecting.

@hawkfreedom1177 exactly, everything has to connect for it to look good

There is this Shot Size/Zoom Slider for Krea 2 that might help you out there: https://civitai.red/models/2785002/pornmaster-krea2-shot-size-slider

@crappypornthrowaway Uh, are you sure you don't mean "explicit"?

@PaperTyger No, implicit. Explicit prompting is easy. When I say implicit prompting I mean more, like, phrasing things in such a way that the model knows more about what you mean.
To give you an example, let's say I want a high angle view of a POV blowjob, but I keep getting lower angle views. Repeatedly saying "High angle, high angle" won't help much. But I can do things like say "the floor is visible behind her head", or remove references from things that make it prefer a lower angle. E.g. if I say "Takes place inside a luxury apartment", then the model wants to include things like furniture and windows, which require a lower angle.

In OP's case, if he's getting headless pics, implicit prompting is things like "She is looking at the camera", rather than "head included".

@crappypornthrowaway Fair enough! Thanks for the clarification.

Hard to help you without providing any prompts/configs

PERV

Try the DPO version. Its much better and has its own turbo built in basically. Use it at 8 steps with 1 cfg. The base is more for training on.

@Ada321 thanks for tips.. Agreed, after some more runs on the kroma base at 50 steps, it started to act odd and not produce good runs (as you say more for training). Got lucky at first. B/c i actually prefer RAW krea 2 a lot more than turbo (at 50 steps), I was thinking that logic with Kroma would hold, but I don't think it holds.. seems much more temperamental than the regular raw for image generation. anyway, thanks lodestones.. great work :) I will try the DPO. .(update: tried dpo and its awesome @! )

Euler A might work despite being riskier, and the SGM Uniform scheduler allows a model to work harder on an image because a latent still gets more noise in the middle steps instead of linearly falling off with Simple (and thus resulting in less sharp details). So I am with Euler A + SGM and then upscale with SeedVR2 7B, it fixes artefcats to some extent.

euler + simple - the key is your prompt - describe every detail .. every.... detail... and if you don't wanna go insane have an LLM do it for you lol - i highly encourage you to create a template text document that structures from head to toe every detail a character requires - and then instruct the LLM to fill in any missing details you omit from your initial concept - then go on to environment and style - style being like the camera type used , the focus , the lens, and leave that towards the tail end of the prompt and you'll have a god tier image.

template order of importance: Character A , Character B if applicable , character details head to toe , clothing head to toe details , Actions , Environment, lastly Style. in that order.. you'll probably have to go back and forth with your LLM to create a substantial full fledged non-bias dynamic template that is a swiss army knife it'll take you a bit but once done you'll have it for future uses and your prompting capability will go through the roof...