What causes horrible results like this?

[githubUser01946]

First off the prompt is there and the correct inpainting model is selected.

[githubUser01946]

Also, can I run this outside of Webui?

[zero01101]

generally you'd see results like that when the requested resolution is way too small for the output size/reticle, i.e. you've got sync resolution disabled and a really low resolution setting (or if using the dream tool, you've left HRfix enabled over a completely empty region but this looks like you've already got image content so it's probably not txt2img HRfix related)

Also, can I run this outside of Webui?

openOutpaint actually started as a standalone webpage; the extension is merely a convenience :) just download the zip of the codebase

extract it to a new folder somewhere, adjust your webUI user script accordingly, run webUI, run the included openOutpaint launch script, and navigate to http://127.0.0.1:3456

[githubUser01946]

Ok so how do I fix this?

[zero01101]

my recommendations would be ensuring you're using synced resolution/reticle size (in general really but mentioned for img2img because of your posted image), or making sure you've got reasonable settings for HRfix and disabling it if you're not using it in txt2img; aside from that, uh... maybe make sure you're using the right VAE?

regarding the resolution, you can check the parameters sent to SD in your browser's console as well as the raw POST request in the networking tab to check that the requested params are what you've input, but yeah, really we don't have much control over what SD gives us back in response to the request parameters

[githubUser01946]

There's only one vae installed, the usual one most people have.

…

On Thu, 2 Feb 2023, 3:30 am tim h, ***@***.***> wrote: my recommendations would be ensuring you're using synced resolution/reticle size for img2img, or making sure you've got reasonable settings for HRfix if txt2img; aside from that, maybe make sure you're using the right VAE? you can check the parameters sent to SD in your browser's console as well as the raw POST request in the networking tab to check that the requested params are what you've input, but yeah, really we don't have much control over what SD gives us back in response to the request parameters — Reply to this email directly, view it on GitHub <#191 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4ADEB3R7LZ7XCFHZIG2OADWVMS5NANCNFSM6AAAAAAUMTSKMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[zero01101]

i couldn't even begin to guess what the "usual one most people have" would be given the incredible number of models floating around out there, some in .ckpt, some in .safetensors, some with VAEs baked in, some not, but regardless, without further information i'm not sure what to tell you; like i said, ensure you're using appropriate resolutions for your requests to the API either by the sync res checkbox or HRfix... also as mentioned, you can check the parameters received as response from the API from your browser's devtools console tab

or the params you sent via the network tab; look for the POST request to txt2img or img2img

[zero01101]

yeah i'm really going to guess it's something like this

[ghost]

I had these responses when I was using "highres fix". Deactivate it, and it will render normal images on no background at all. If you've done it, select the sd-1.5 inpainting model.

[githubUser01946]

I didn't have that ticked but it does seem to have gone away. At least I know now what to do if it happens again.

…

On Tue, 7 Feb 2023, 5:33 am artreloaded, ***@***.***> wrote: I had these responses when I was using "highres fix". Deactivate it, and it will render normal images on no background at all. If you've done it, select the sd-1.5 inpainting model. — Reply to this email directly, view it on GitHub <#191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4ADEBYQYJP7MLNZCGI6FQDWWHNENANCNFSM6AAAAAAUMTSKMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[joshyy1312]

I got this when I dream/img2img a zone smaller than 384px in any direction