Created just for my own purposes
version more artfull and less NSFW, if you want NSFW use special LORAs - it works fine. https://civarchive.com/models/1295758/nsfw-fluxorwan-22orqwen-mystic-xxx?modelVersionId=2009929
Description
FAQ
Comments (17)
whats new in this version?
One more unet and lora merged
By far the best Flux model I've tried (and I've tried many of them). Works really well with a wide range of Flux Dev loras as well which is great!
I tried 3 times to download V3.0 and each time the download failed in the end.
Any idea what might be causing this.
its regualar things with CIVITAI, you dont believe how hard to upload model to site
i tried to upload full model with vae and t5: mission impossible
@FASCIUM Thanks for your replies, my 4th trial also failed. I'll try again later or tomorrow.
Does not produce unclothed or any nudity regardless of the prompt used. The posters images all use a separate lora to produce unclothed images. NSFW tag is inappropriate and misleading.
Check your prompt. Others have generated NSFW. See the gallery.
can't post V3 pics, because civitai misidentifies the model as this
and they do not react to a ticket filed about that 3 weeks ago.
edit: and that is a real pity because this is an EXCELLENT model, i love it
Sometimes this happens when a model is renamed or relocated, and the UI calculates the new model's sha, and it matches some other model. You can of course download it again, but I don't think there's any point, I'm constantly upgrading and refining all the models. I plan to create a new model.
As my experience shows, even after you download the model and work in it, it creates new paths, routes and points and it already changes, so the stability of the model is a rather conditional concept
I found out the problem - CIVTAI few days ago begin to change names of safetensors files - early downloded models with correct names not always recognizing correct on CIVITAI!!!!!!
i just re-downloaded v3, the new file also gets misidentified as the model linked above.
v4 also gets identified as that model
v2 is recognized as v2, and overruled by a "manually added" v4 tag.....
complete mess caused by civitai
i'm using SwarmUI, comfy backend, which is theoretically supported by civitai (and i've checked my pics with the prompt inspector bot, they are correctly tagged with the right model)
@snotty I double-checked in Forge - everything is fine and the ID is fine... I don't work in Swarm and can't check.
ok, i got the tip leading to an explanation via the swarmui discord:
CivitAI Auto V3 Hash for your V3 model:
29CE1AD66F71
SwarmUI hash for your model:
29ce1ad66f71589b256004742374cfbd351a3bfbbe1e9cf12182d3709b15f521
and the Auto V3 hash for the model it gets identified as:
29CE1AD66F71
so, civitai shortens hashes to save space/compute, and it goes wrong
@snotty @snotty sadly, buth truth....to many UIs, too many standards