The important thing is the textures, of the models in the photos. I was the problem with my PC, they changed it automatic 1111
I'm not disabled, I'm not tense, the other problem is your comments.
I like somewhat short comments.
Enjoy
Description
FAQ
Comments (6)
NOT Flux models misleading base model designation :(
It's still only SD1.5 models!
Models Base designation tells people which workflow to use, by mislabeling it you created confusion and some people ie noobs might not figure out why it's not working for them :(
So, Stop calling them Flux 1.S models when they are not based on that architecture, they don't need Flux based Clip or vae models to run, therefore they are not Flux base model!
It's still ONLY SD1.5 model trained on Flux generated output, which doesn't make it Flux base model!
You just confuse people who might try to run it as Flux model workflow & it won't work :(
Otherwise, it's great model with great generated output images!
Automatic 1111 forge in UI (SD, XL FLUX, ALL)
@MagicArt35 You miss understand what base model is.
It's NOT what models are mixed in that defines what base model is!
It's what underlying structure of model that loads up!
In this case it loads up as SD1.5 model!
I use ComfyUI & InvokeAI so when I load your model it recognizes it as SD1.5 base!
It does NOT recognize it as Flux model.
When I load in Comfy workflow for SD1.5 all I need to load is your model alone.
BUT when I load Flux workflow, it will need also to load Flux model + Flux Text Encode + Flux Vae.
I'm just saying for model card in base model it should be designated as SD1.5 model NOT Flux!
You can still name it as SD15+Flux-mix-V-x.etc for model title!
BTW I've said it before output images generated from these models is great!!!
you did good job creating these model's.
i would love to download, it is too big! needs to be pruned thanks.