>>939450733
>I can try to help if you have issues.
My main issue is just that I'm using a MacBook M3 Pro and not something with a beefy NVidia GPU, and I don't really think you can help with that, but I appreciate the offer!.

>>939450733
>I have never understood what the BREAK means in the prompt.
It's an Automatic1111 thing. By default, it doesn't really do anything in Comfy, but there are a few custom nodes that make it work. In my Chroma gens, I'm using the creatively-titled node "CLIPTextEncode with BREAK syntax"; in my SDXL gens, "CLIP Text Encode++" which is a little more powerful but doesn't seem to want to work with Flux-based models for some reason.

Basically, it tells the language processing bit to break up the keywords going into the image processing bit at the BREAK, which helps a little bit with keywords in a prompt bleeding out to other parts of your image. E.g., if you gen "Cute girl in a red scarf standing in front of a car" vs "Cute girl in a red scarf BREAK standing in front of a car", the car is a lot more likely to come out red in the first example than the second.

The native comfy way to do that is to use ConditioningConcat nodes to wire a bunch of different chunks of prompts together, and that's what the BREAK syntax nodes are doing behind the scenes, but that gets really annoying really quickly, especially if you want to concat more than one chunk together because you need to concat the concats too and it's just a big mess.