P: Generated images violate user guidelines

I would agree. I got a warning over a common word (don't remember what it was, now) that wasn't being used for anything remotely related to sex. But it was a word that COULD be used for that purpose. I would've thought AI could detect the context of the photo. I did report it. 

I honestly can't see it happening anytime soon. I'm not a kick on the backside off 70, so I reckon I'll be pushin up the daisies before it get's released. FAR too many bugs yet.

"Is there an expected release date yet?"

Well, considering that Photoshop's Neural Filter for Depth Blur was first introduced in July of 2021 and that it still remains in beta, I think it will be quite some time before we see a fully working version of Generative Fill. 🙂

Hi @Pete.Green , as we do see all more clearly now, putting a period (aka full stop) often fixes this problem (experienced beta users no do know this, while newcomers are still annoyed as they fear restrictive censorship behind this message and forget that it is still a beta version. I felt the same way at the beginning, first the excitement, then the disillusionment. I now find that this trick kills the message 99% of the time, and I see Firefly as a great addition to the daily workflow. Sure, it doesn't have the genrative abilities of other AI's, but that's not the point either. For corrections of any kind, which is the main part of Photoshop work, it's a great tool, and a real timesaver.

Three short questions and a suggestion:
1. What exactly does the period trick do behind the scenes on the programming side? (no company secrets, just to better understand the prompt logic)
2. Is there a general page from Adobe whith prompt tips and keywords, or is this planned for the release?
3. Is there an expected release date yet?

Regarding the unloved hint: Why not provide a direct feedback option right away in this modal? I think that would be a clear win-win situation, both user experience, as well as feeding your feedback database

Find attached a small demo, which would make me as a user way happier than the suspected blue (well, orange) lights of the vice squad 😉

Cheers, Phil

agree 100%

I'm just not sure Adobe's idea of 'improving the product' is the same as mine.

The introduction of this Ai feature seems to me to be being used to force restrictions on our use of the software which didn't exist before.

That doesn't feel like progress.

I don't care about whether it's a text prompt or a selection that is causing an error in Generative Fill. Why there are Adobe introducing any limitations at all?

I am aware that Ai could be used to create illegal content (just as Photoshop has always been able to), but are all of us millions of legitimate pro / enthusiast photographers and creatives REALLY going to be told by Adobe what we can and can't create in future, just because a tiny number of criminals could use it for nefarious purposes?

I know we are in beta, but I am presuming this auto-limitation is intended to be carried through to the release version?

If so, this really is ridiculous dictatorial big-brother stuff and I hope Adobe has a serious rethink.

I've tried it using any number of non-alphabetical characters (#, ^, ), etc.) and they all fix the same issue as using a period. Since some people prefer to just post to this forum rather than take the time to read it, maybe Adobe should update their guideline violation warning to include "Try again using a period or other non-alphabetical character as a prompt." 😉

@Sebastian292242075jds thats the point of participating in a beta test - help the team improve the product.

using a period (".") worked, i hope Adobe team figures this out 

Try adding the period ( or full stop ). That little workaround helps for most generations.