-
Notifications
You must be signed in to change notification settings - Fork 41
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
Img2Img/Inpaint don't respect Max size/Base size #150
Comments
Can you screenshot the console output? Should log "img size: ...x... -> ...x..." somewhere. |
Related: I think upscaling is broken independently of this bug. While that aspect isn't reproducible on the main branch, I suspect it is there. On @JasonS09 's ControlNet branch, the resolution setting is respected (when you have controlnet enabled anyways, which goes down a different code path), but the image isn't run through an upscaler and the output is grainy. I am quite certain it did work before the latest WebUI update. |
@Interpause Case 1: Case 2: Case 3: Case 4: Case 5: info: Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug 1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] |
I seem to have solved the problem, but I'm not sure if I did it the right way. |
Img2Img/Inpaint don't respect Max size/Base size. Creating a rectangle selection of 768X768 will cause an image to be generated at 768x768 instead of whatever is specified in Max Size. Txt2Img doesn't have this issue.
The text was updated successfully, but these errors were encountered: