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

Taragonn:

For some users, image generation is not just a single prompt → single image workflow. In my case, I work in a long-running creative project with ChatGPT, where the conversation context is essential.

Yes absolutely, this is why I say it must be fixed, the “Start a new session” is only a workaround not a fix, and noise is still there, and like “Use less details” not working either for all users or situations. (I want details. And i make both, every image as a single, and story telling series.)

Best would be a option: 1 time prompt, and story prompt. And i have to check the difference between instant and thinking first, before i can say something. Maybe it does exactly this… I used 5.5 > thinking > standard, for now.

(I have to translate most from German to English first and then sometimes back … welcome in the club.) (Sorry to all if I make typos if I write quick a text before sleeping.) (… And I always have to search the English prompts too, I prompt in German.)

About lost conversations

You can ask ChatGPT to make you a summary protocol with all important data in it, to restart a new conversation/session with it. This lets you pick up the work again. Sometimes a conversation is so long that it slows down my browser, and I must open a new session to continue. The kick-start protocol should include all important points in a chat as a summary.

Actually if you lose the chats, they still exist. You can download them in the archive under your user.

It had a bug in the past, because it includes all pictures, instead only the text. (I have to see later if this is still so. Sorry if my info here is maybe not up to date.) In case the zip is damaged, do this:

• repair it with 7zip or another unpacker first
• and you should see a file named conversations.json or chat.html
• there the conversations are still inside, but you must search them maybe, if the file is very big.

Dev stuff

If I write a text which is more to the devs than the users, I will mark it from now on. I expect they know all better than me, but at the same time I see the issues. So I write some of my ideas what could cause the problem on a technical level too. (I do this to understand the background, so it helps me better how to get things better done on user side.)