Skip to main content
Participant
May 23, 2023

P: Generated images violate user guidelines

 

So as you can see, it's a PG-13 relatively inoffensive image of a woman in a bunny outfit. The top worked fine, and I was able to complete the top ear, which is cool. When I tried to extend the bottom with generative fill, though, I got this warning. They're just a pair of legs wearing stockings, and I wanted to extend it.

It feels like a false flag - though I could be wrong? I find myself thinking it would do the same for women in swimsuits.

Figured I'd share here.

1085 replies

Known Participant
July 24, 2023
Try entering a single period in the dialog box, then hitting enter
That is the workaround I'm using now.
Participant
July 24, 2023

Turns out, just putting a black square over the centre of a person also allows it to work. 

Participating Frequently
July 24, 2023

Using the period option definitely is working as a work-around for the time being. I was skeptical that it would work but it is in fact working.

And now that I'm not getting constant errors I can finally see the power of this new tool. It is like turning photography into magic. Quite astonishing. And it even works on illustrations as well. Completely blows content-aware fill out of the water without question.

Participant
June 8, 2023

Hello, I am using the new beta generative feature and I am finding that it is not adhering to the prompts I am using and I belive it is a censorship issue, I work in making swimwear and lingerie and that sometimes involves plus sized models and it appears like the images of the bikinis I make are for some reason violating the guidelines when there is no pornographic content in the image. Is swimwear considered breaking the guidelines? Is being overweight in violation of the guidelines? Is there a problem with showing too much skin on the system where it wont adhere to the edit even if it is not considered pornographic although a bit revealing?

 

Overall its a great concept and Ive seen some great work done with the service but very restrictive to the industry I am in which makes me very sad that even in this day and age we cant show anything above the knee

 

The ai was actually putting new clothes in all of the images I was attempting to update. lol.

Kevin Stohlmeyer
Community Expert
Community Expert
June 8, 2023

Hi @RED444222 can you supply some examples of images, results and the prompts used to show how it's failing? It would help illustrate the issue.

Graham24508943nobd
Known Participant
July 24, 2023

The admin should pin this info everywhere on the Beta pages. Might stop a lot of people giving up completely

Known Participant
July 24, 2023

Thanks for the reply. Big Ai Brother is definitely watching us. About an hour after my post, I was on YT, on nothing to do with this and was prompted to watch a video by Unmesh Dinda in which he demo'd putting a period (full stop) in the box. For sure Google is aware of every beat of our hearts! 

Anyway, late last night I tried it on several images I'd given up on, and it works great!

Thanks again. Great to know the answer would have surfaced here if G hadn't been eavesdropping and taken the situation in hand.

 

Graham24508943nobd
Known Participant
July 24, 2023

as has been mentioned many times, try using a period ( or full stop for UK users ),  in EVERY generative message, even using that in a blank space stops 99 % of the stupid guideline errors.

Participant
July 22, 2023

Hello,

I'm writing to you because I've been having a problem since today (haven't used the beta version of Photoshop for a little while).

Many times when I try to AI-generate an image on top of another one of mine, without even entering any text, I get an error telling me I'm doing things against Adobe's policies. Except I don't generate anything illegal because it's just stone textures, moss, etc... which for once is quite unpleasant because there's no reason why it should prevent me from working.

I can tell that I am on the latest version of Photoshop beta (uploaded today, July 23, 2023), that I'm on Windows 10.

 

Looking forward to your potential feedback or improvements,

 

Tom S.

Inspiring
July 21, 2023

Well said, Kevin. A year ago, none of this would have been possible! 

Participant
July 21, 2023

More and more I'm getting this message come up when I'm doing very simple things like removing people or objects from the edge of frame with generative fill. Today it won't even extend a black curtain without giving me this message, what could it be possibly generating that would go against guidelines when it's a black blob? It's almost becoming a useless tool because I'm forced to manually remove these things. So much promise but it's hampered by these stupid messages.

Kevin Stohlmeyer
Community Expert
Community Expert
July 21, 2023

Hi @Kenneth259883092lw8 are you entering any values in the Generative Fill prompt?

Kevin Stohlmeyer
Community Expert
Community Expert
July 21, 2023

Hi @Preston29196145tevi level set - you do realize you are voluntarily participating in a beta test phase for software correct? Constructive dialog is always welcome and helps move the progress forward. The software will get better but understand this is the first instance of Generative Fill AI in Photoshop. There is going to be growing pains. But also if this impedes workflow so much (keeping in mind this is only to be used for non-commercial work) - you always have the option to stop testing and move to the general public release to do your work. No one is blowing off replies in here and the team is monitoring.

 

The blank issue has been noted so much in this and other threads that at this point I would personally consider it user error if someone posts "I left it blank and it gave me an error" without reading the thread they are posting on.

 

I'm certain this and other errors will be addressed well before this is finally released to the public in a new version of PS. But at this point hammering the same issue over and over in a rant does nothing to help.

Known Participant
July 22, 2023

Hi there,

Editing a very crowded wedding. Found it impossible to get unobstructed photos of guests, so have been using Lightroom's remove tool where possible then flipping the image to PS Beta to do the rest. 

I am getting incredibly frustrated with Generative Fill, On 70% or more of the attempts I've made I get the 'violates guidelines' error. I get that when trying to remove people's heads which are right in the lower center of the frame like this one. This is cropped to about 20% of the frame. 

 

The policy doesn't really explain to me why it is a cardinal sin to remove an out of focus, overexposed face from a photo. I mean GF works great when it does but in cases like this I have to find other photos of tables with similar content and composite the image.

 

I think it's time for Adobe to have a tune up chat with Cardinal Dontletemdoit. He is far too conservative in making a sin out of doing this. I'm almost to the point of not even trying to use GF because it literally won't let me remove a spooky hand reaching into the frame and touching someone's shoulder.

 

Clone stamp, Spot Healing, Content Aware Fill etc. all work on those things and I absolutely do not understand what the problem is with Generative Fill. Is this just something they want to show off but don't really want us to use?

 

On that image I used Content Aware fill, which obliterated the head then I deselected all but that layer and ran GF after selecting the messed up area. 

Despite the fact that there are now no heads or body parts or Nuclear Codes ,,,I still got the same message:

 

This is completely NUTS!

 

Participating Frequently
July 21, 2023

Hi Kevin,

 

Sorry for being blunt, I will try to channel that into more constructive dialog.  You have to understand how maddening it can get trying to work with Gen Fill at this point.  Last night 100% of the time if I selected something and left it blank it wouldn't render.  That is unaccepatble.  My tone is always very direct though and I feel the need to be so with the response.  The point of all of this is to use it and not have a ridiculous thing impede workflow.  I can appreciate that things worked for you but it doesn't work for me.  The larger point is that somehting is broken in the Gen Fill code that is causing really bad amateur type errors.  Please look at this through the end users eyes.  Why does it most of the time if I leave it blank, give me guidlines window?  It shouldn't do that even in beta software.  I hope you guys are taking it seriously and not just going,"Well, it worked for me so it isn't a problem."