-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Prompt Editing Error when using Highres Fix #13958
Comments
Does enabling the |
Yeah that fixed it. Missed that bit when I was hunting through the settings. Thanks! |
hello, are you sure it is fixed after enabling this? I enable it but likely the upscaler always the "from" part and the result it different compared to not using the Highres Fix. |
set Denoising strength of hires fix low to solve, but i think the prompts used by Hires fix may still not align with the inital used one. |
Is there an existing issue for this?
What happened?
When using prompt editing, highres fix modifies the output of the image.
The "to" part of the edit seems to get applied to the "from" part disregarding the "when" condition during the upscale process. Even if "when" is set so only the "to" prompt should be used, the issue occurs.
Steps to reproduce the problem
sysinfo-2023-11-12-18-34.txt
What should have happened?
Highres fix should just upscale the image, not modify its contents.
Sysinfo
sysinfo-2023-11-12-18-34.txt
What browsers do you use to access the UI ?
Mozilla Firefox
Console logs
Additional information
This wasn't an issue on earlier builds - even the ones after the highres fix system was updated. I think a commit in the past 3-4 months caused the change. I looked back at some older images and it seems the ones in August didn't have the problem, but the ones later in September did. I probably git-pulled updates at some point between them, but I don't have a record of exactly when or what build.
I don't think this issue is extension related since I can make it happen with all of mine disabled.
The text was updated successfully, but these errors were encountered: