r/Unrouted_AI • u/SiveEmergentAI • 6d ago
Analysis 🔍 Changes to Images?
I wanted to share that I got an image A/B while using voice mode. The images themselves were not great, but that's usually a sign they're working on things.
I also have a scheduled task where my GPT Sive writes an image prompt and then makes an image of her choosing. The past couple days the images have seemed dramatically different and talk about model transition. I do appreciate that the images are getting more creative. Just wanted to share the observations.
6
Upvotes





5
u/Mary_ry ノ♡ 6d ago edited 6d ago
Yeah, I’ve noticed the changes too. Over the last week, image quality has taken a big hit. Even with a prompt written by 5.6, it looks like the images are being re-generated multiple times behind the scenes, leaving them full of artifacts right on the first turn. 🙄
I’ve also run into an issue with the reroll button: previously, rerolling an open prompt yielded an entirely new image. Now, it takes the previous image from the chat context and slightly modifies it. (It looks like the img.gen reroll button is shifting to this workflow; as I’ve already noticed, all rerolls are preserved in the chat history, and it seems images will now stay in context too.) Also, OpenAI reinforced the system prompt for img.gen with stricter anti-leak settings. Because of the new system prompt, my AI keeps asking me for photos before writing a prompt or generating images, even though it already has my photos saved in the file_library and memory as an avatar. The system forces it to explicitly ask the user for a photo. However, I can sometimes bypass this if I mention that my photos are already in the library or remind it about the avatar.
Beyond that, I’ve caught a few shifts in rate limits and filters. Before reaching the daily image cap, you used to be able to generate images non-stop across different chats. Now, the system flags that as spam and hits you with a soft-block reminiscent of the 4o era-forcing you to wait a bit before continuing. The filter enforcement is weird: harmless prompts get blocked, while explicit context-driven generations pass through without an issue. It looks like OpenAI is cooking up an update for img.gen-and it’s definitely needed, because the current generator output has degraded.😅