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
I'm not sure if is it a bug or is it correct but if I try to upscale a canvas of, for example, 5120x4096 I get an upscaled image of 8192x6144 but is cropped on the left and on top. I'm a beginner so maybe I'm doing something wrong.
Also, there's a way to select only the area of interest before upscaling?
Thank you very much in advance to anyone who will answer me!
Steps to reproduce the problem
I use Automatic1111 1.6.0rc
on windows 11
nVidia Tesla P40 with 24GB VRAM
realisticVisionV51_v51VAE-inpainting model
disclaimer: apologies for the extended delay, my brain is terrible and you shouldn't expect much from me
confirming buggy output size/dimension occurs at huge resolutions and theoretically shouldn't; i know "infinite" canvas size is mentioned but i really haven't done much in comically large resolutions like that so upscaling to sizes beyond any monitor i could conceive owning isn't something i've tried, but yeah, that shouldn't occur...
What happened?
I'm not sure if is it a bug or is it correct but if I try to upscale a canvas of, for example, 5120x4096 I get an upscaled image of 8192x6144 but is cropped on the left and on top. I'm a beginner so maybe I'm doing something wrong.
Also, there's a way to select only the area of interest before upscaling?
Thank you very much in advance to anyone who will answer me!
Steps to reproduce the problem
I use Automatic1111 1.6.0rc
on windows 11
nVidia Tesla P40 with 24GB VRAM
realisticVisionV51_v51VAE-inpainting model
What should have happened?
some sort of limitation/incompatibility ?
Commit where the problem happens
bf21c19
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Google Chrome
Browser Extensions/Addons
adblock plus
translator
ublock origin
AUTOMATIC1111 webUI Commandline Arguments
--api
Additional information
No response
The text was updated successfully, but these errors were encountered: