Collection of GPT-image-generator 2.0 issues, bugs, and work-around tips (check first post)

LarisaHaster:

I tested in API with gpt-image-2

What will exhibit “the pattern” more highly is image input, which can be done on the edits endpoint. Lets send your two images for a new amalgam to gpt-image-2, at medium quality (and mandatory “high” input fidelity):

The mood and subject of a new image reflects these past images. However, there is no sunset - the image is just well lit by an overcast and gloomy sky. Sparse pine trees are seen. The castle keep is more a ruins, with tattered flags and chinks in its brickwork.

The output:

Now lets keep on iterating.

This aged ruins is transformed back in time into the same castle keep in its heyday, with noble knights on the path and the castle reconstructed to a noble fortress in its original form, without signs of death or gloomyness.

What this model cannot help but add is sunsets…

This noble fortress is transformed forward in time to a gloomy shade of its former self oozing death and defeat and destruction. The castle keep is more a ruins, with tattered flags and chinks in its brickwork, and the road is wet and rutty with evidence of battles past.

All requests contained the same second image, while iterating on the first.

After just a few passes, we see that the symptom is there: mottled clouds, highly-textured mud, and overlay of a tight blotchy pattern to everything drawn. The API is not immune, even when you control everything sent in input size, quality, output resolution. You trying on virtual clothes will be just as damaged.

Is this intentional, so that output images become unworkable before you can see after several rounds, the model has transformed your identity and ethnicity from an input picture into something unrecognizable, as with prior models making social media rounds?

Prompting 'a quirky mousy girl', with details (click for more details)