12 anlas were left in here. exactly enough for one upscale at 0.62 noise. it is indeed Christmas. four perfect fingers.
>>39633079kek, nobody likes the kind of shit I have absolutely the most fun doing: 混ぜるな危険
they're all my worst performers. and when I forget it, somebody adds the tag within the first hour.
>>39633332No problem!
>This will make upscaling my old shit much easier!It will certainly make them look better, if you use the latent upscale option it's not that far off from using hi-res fix. The PR had some comparison images I think.
I just wish the batch img2img option had a way to read the prompt/negative prompt information from each image, keep the sampler/steps/resolution/cfg the same as what you set them
or even lock them individually, like keep the sampler I choose, but maybe read the cfg from the input image, and then process the batch. Also, IDK if I'm retarded or what, but batch img2img writes NO metadata.
>>39633348>>39633492NTA but
my sisters are aware of mine and I already fret about posting stuff that'd make me enable the "suggestive" flag. If I post R18 stuff I'll have to dump it on exhentai or make a second one too...>>39633507I had very bad luck with denoising above 0.6 with latent upscale on. Or with trying to exceed 1152/768 in either direction with it on.
>>39628772Not a request, but a question. Assuming VRAM isn't at all an issue, is there a technical "upper ceiling" to how much you can upscale/hi-res fix an image before it goes to shit? I was trying to make WUXGA backgrounds yesterday and they were ALL garbage. I actually wanted to do WQXGA
2560x1600 but the slider in the UI stops you at 2048. It still had VRAM to spare too, but the images were beyond shit at 1920x1200 already.
