You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi,
i have posted this topic in both sd-webui-a1111 discussions and the sd-webui-forge discussions.
since i now tried to test it on 4 different installations, i decided to also post it here.
installation: "manual" a1111 (1.7.0) via git clone etc., with most recent version of controlnet extension.
installation: "v1.0.0-pre" a1111 (1.7.0) via sd.webui.zip file etc., with most recent version of controlnet extension.
installation: "v1.0.0-pre" a1111 (1.8.0) via sd.webui.zip file etc., with most recent version of controlnet extension.
installation: "sd-webui-forge", up to date, with its internal controlnet-version.
so, the difference is that the forge-installation does not use controlnet as an extension, but its internal one.
all of the first 3 installations do present that issue, the "forge"-version is the only one that does not.
that's what got me thinking that my isse might be related to the extension version of controlnet, thus me posting the issue here, too.
here's the issue:
the generation of an image with the help of a controlnet unit, while having hires.fix activated, results in 3 images: 1 txt2img-result and 2 images that are the low-res and the hi-res version of the preprocessor image.
no matter, which setting i choose in "hires-fix option", i always get both.
this also is the case when generating an image via api and setting up the payload accordingly.
any idea what might be causing this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
hi,
i have posted this topic in both sd-webui-a1111 discussions and the sd-webui-forge discussions.
since i now tried to test it on 4 different installations, i decided to also post it here.
so, the difference is that the forge-installation does not use controlnet as an extension, but its internal one.
all of the first 3 installations do present that issue, the "forge"-version is the only one that does not.
that's what got me thinking that my isse might be related to the extension version of controlnet, thus me posting the issue here, too.
here's the issue:
the generation of an image with the help of a controlnet unit, while having hires.fix activated, results in 3 images: 1 txt2img-result and 2 images that are the low-res and the hi-res version of the preprocessor image.
no matter, which setting i choose in "hires-fix option", i always get both.
this also is the case when generating an image via api and setting up the payload accordingly.
any idea what might be causing this?
Beta Was this translation helpful? Give feedback.
All reactions