[Bug]: Stable diffusion (v1.9.0 - 1.9.3), img2img-images "denoising strength" BUG

[xiaoooan]

Checklist

• The issue exists after disabling all extensions
• The issue exists on a clean installation of webui
• The issue is caused by an extension, but I believe it is caused by a bug in the webui
• The issue exists in the current version of the webui
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

In the situation I encountered, when using Stable Diffusion Webui (v1.9.3) and Forge (v1.9.0), BUG situations will occur.

When I use img2img-images, the denoising strength is adjusted to 0.65 or other values. The denoising strength parameters of the images generated by img2img-images all show 0.4. Then I import the image parameters, and the denoising strength is automatically set to 0.4, which is not what I set. Certain parameters, this is a BUG.

It was normal to use V1.8.0 version before, but it will be invalid after V1.9.0 - 1.9.3.

Steps to reproduce the problem

1. Put the image into img2img-images, set the denoising strength to 0.65, click Generate, the parameter value of the generated image shows "0.4"
2. Place the image in the img2img-images prompt, click the arrow button below, and the parameters are automatically set, but the denoising strength displays "0.4" instead of the "0.65" I set.

What should have happened?

Stable Diffusion V1.8.0 Under normal circumstances, the value I set for img2img-images denoising strength will be the same as the value of the generated image. After V1.9.0-1.9.3, it becomes invalid BUG.

What browsers do you use to access the UI ?

Google Chrome

Sysinfo

Forge : sysinfo-2024-05-06-22-29.json

Stable Diffusion Webui : sysinfo-2024-05-06-22-47.json

Console logs

There is no CMD error message.

Additional information

System : Windows 11
CPU : I5-9400F
GPU : RTX3060
RAM : 32GB
Stable Diffusion : V1.9.3  • python: 3.10.6  •  torch: 2.2.0+cu121  •  xformers: 0.0.24

[w-e-w]

that is very strange I can say for sure that it's working correctly on my end
have you tried disabling all third party extensions
maybe there's some weird interaction with certain extension

[cassiebug23]

I had this issue as well. I had to reinstall A1111 to fix it.