[Bug]: Prompt working but when accepting picture, it only keeps the area it was looking for and cut the rest of the image outside the box. about openoutpaint HOT 11 CLOSED

I can add eventually some extra info, for me it works on Firefox, Edge and Brave don´t work,

from openoutpaint.

disclaimer: apologies for the extended delay, my brain is terrible and you shouldn't expect much from me)

i'm completely unable to reproduce this; you're saying that after you send an image from the extras tab and place it on the openOutpaint canvas, then try to outpaint using it with a region other than 512^2, it only renders a 512^2 area after selection/confirmation? could you possibly get a screen capture video of this happening?

also try enabling debug mode under the debug info tab when you try to outpaint, see if the submitted image/mask are the wrong size somehow...

from openoutpaint.

same for me, only newly generated image stays, rest is gone

from openoutpaint.

This happens to me too. When using Dream or Img2Img, when accepting the result (clicking Y), the area outside of the rectangle that was selected disappears. One can work around it by adding a new image layer and running Dream/Img2Img there, but if one tries to merge the image layers the "outside" area disappears again. Happens in Chrome and Edge for me, but not in Firefox. I suspect that it's a browser update that caused this, as it seemingly suddenly started happening without a change to openOutpaint ...

from openoutpaint.

I just noticed that there's a separate repository for the webui extension. I put in a similar report 2 days ago in the general openOutpaint (my bad), and have the same results, re: Chrome and Edge. I agree it's probably a browser issue.

from openoutpaint.

Same here. It used to work for me, but recently started to do this in Chrome. I can get the missing image data back if I select back history, then select the latest history and it pulls it all back together, but definitely a new issue.

from openoutpaint.

more disclaimer: i warned you my brain is terrible and you shouldn't expect much from me lol

confirmed misery on chrome/edge/chromium-based browsers regarding single-laryer content removal - current workaround is to ensure new layer per dream option is enabled in settings. layer merging failure is likely related to same new "feature" but i'm not smart enough to know how to fix it yet...

from openoutpaint.

moved to main openOutpaint repo even though original issue was indeed extension-specific via send-to button, this is obviously a chromium vs base openOutpaint grumbling

from openoutpaint.

probably should've closed as duplicate of #268 a while ago... continuing there

from openoutpaint.

closing for real this time

from openoutpaint.

seems chromium upstream is really seeming to be the culprit here; if anyone still affected could confirm the findings in #268 (comment) that'd be awesome :)

from openoutpaint.