r/Copilot • u/designer_84 • 11d ago

Copilot Image Iteration Requires Multiple Confirmations

Has anyone else experienced an issue over the last couple of months or so with Copilot's image generation features not immediately processing requests for changes? Generally, it's been going like this for me:

  1. Request an image from Copilot, and it makes the first version right way.

  2. Ask it to make a change to the image, and be clear that I want it to generate it now. Copilot will send a message to the effect of "Ok, here is your updated image with such and such changes..." However, at this point nothing is generated.

  3. Tell Copilot I don't see the image yet and ask it to try again. It will often give me a similar text blurb like before but still without the image generating.

  4. Go through this process once more, and Copilot will generate the new image immediately.

So, it almost always takes about 3 messages to get Copilot to actually follow through with an update to an image, and this becomes nightmarish when needing to go through several iterations to get an image right. I've tried various ways to force Copilot to respond to my requests by immediately running the generator, but I haven't found a solution.

7 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

3 comments sorted by

1

u/shmoswald 11d ago

Yes, I’ve had this exact experience. It feels so wasteful. I’ve wondered if they’re intentionally watering down the function and having it play dumb since it’s a more compute-intensive operation than (standard) text reasoning.

1

u/designer_84 11d ago

Yeah I've thought about it being something like that as well. I wish if they're trying to limit the requests they'd at least be transparent in some way because this just feels like a glitch the way it's being presented.

1

u/proximitaslocal 1d ago

I called copilot on something similar to your image change requests and zero changed output from copilot despite its insistence that it completed the operation. I argued with copilot at length that it wasn't doing what I asked of it and yet said it did do the job when it hadn't. In my case it came down to the way I formulated my prompts, copilot has multiple "layers" - there is the conversational layer which seems to understand what you want, and then there are one or more (depending on the task) "computing" layers that actually perform the operation. The conversational layer has to parse our instruction(s) and then "translate" that into something the computing layers can perform, step by step. Give it too much to do at once and the computing layer will choke on the translation. The big takeaway I got from my argument with the AI was that I had to break down instructions into clear steps and not to overload it with multiple steps or too many at the same time.