[Bug]: Inpainting always give the same results

[ksampolski]

Is there an existing issue for this?

• [X] I have searched the existing issues and checked the recent builds/commits

What happened?

Inpainting doesen't work at all (always get the same input image result)

Steps to reproduce the problem

1. Go to inpaint
2. Upload photo, select marked content to original,
3. Regardless of your settings (de-noising etc). Always get the same result.

What should have happened?

Get properly inpainted picture

Version or Commit where the problem happens

version: 1.5.1

What Python version are you running on ?

Python 3.10.x

What platforms do you use to access the UI ?

Windows

What device are you running WebUI on?

AMD GPUs

Cross attention optimization

Automatic

What browsers do you use to access the UI ?

Mozilla Firefox, Google Chrome, Microsoft Edge

Command Line Arguments

--no-half-vae --opt-sub-quad-attention

List of extensions

No

Console logs

Everything looks like normal generation

Additional information

For test created new install -> no difference For test installed sd.next -> everything work ok.

[Siralob]

You will also need to add the --no-half option in command line arguments to work properly for whatever in-painting. e.g. Adetailer

[BoomSec]

You will also need to add the --no-half option in command line arguments to work properly for whatever in-painting. e.g. Adetailer

YOOO I UPGRADED MY GPU AND INPAINT HASNT WORKED SINCE. THIS REPLY FIXED IT! YOU ARE A LEGEND

[hellridergit]

Same issue here. If I were to open an issue it'd be word by word as same as OP's here, except for the launch flags.

I'd launch with no flags at all, or only with --lowvram (because on a 12GB VRAM it kept whining about unable to allocate 4.5MB).

I scoured the internet for solutions, and applied virtually all of them, to no avail. Then just now I stumbled across @Siralob 's post, and it fixed it. Just like that.

Now running with --no-half alone fixes the inpainting issue. OMG I struggled for days. Thanks @Siralob!