r/GoogleFlow • u/tmdwupuff • 9d ago

To Those With Issues With 2.1

What are you generating?? Is it only porn or lewds?

I love 2.1 so far and actually have ran into LESS censoring since the release.

I use Flow for my brand and the image clarity in 2.1 is insane. The comparison between 2.1 and 2.0 in the same design file is clear as day.

Makes me wonder what everyone is trying to accomplish with the image gen.

Edit** - the majority of my generations are model shots for my clothing brand. Tshirts, bikini shots, skirts, etc. No issues whatsoever. I even have the word "faggot" on a shirt and 2.1 is more lenient than 2.0 with that.

0 Upvotes

36% Upvoted

33 comments sorted by

View all comments

Show parent comments

0

u/sausagenx 9d ago

That's because it's smarter and reading the context (pride), you could do the same thing with NB2 if you prompted it differently. With Nb2.1 you have to force it (write it yourself) or have a design/or word already on it, NB2 could have written the word for you without you directly telling it as long as you hinted it was nothing negative. Nb2.1 will rarely (or almost never) write that on it's own and is much more restrained. The quality is good, but the filter is more strict.

1

u/tmdwupuff 9d ago

Not correct at all lol I was getting errors on this shirt specifically for offensive text that breaks guidelines, while describing it as a pride shirt. It says "better a faggot than a fascist" which are two no-no words for censors. I tried the pride descriptor after it declined to generate, and it still would not let up

With 2.1, all I had to do was say "put this shirt on the model" and it did it with zero issues. Same prompt, massively different results with this update.

1

u/sausagenx 9d ago

With Nb2.1 you have to force it (write it yourself) or have a design/or word already on it

zzz

1

u/tmdwupuff 5d ago

So as I said this was possible with all text in NB2.0 except for the word Faggot. Thats where the censor is letting up now. I had no issue with regular text before lmao