Closed 413-xx closed 3 weeks ago
Hey there. Thanks for the thorough report. I fixed the first issue (hires fix). I haven't used Adetailer and don't know how it works. So I'll have to look into it when I have some free time, but not making any promises!
Please update and let me know if the Adetailer issue still persist though. Cheers.
Well that was quick! Just tested, the update appears to have resolved both issues (hires.fix and adetailer). Thanks!
Cool. No problem.
So I’ve run into what may be a bit of an odd edge case..
I often switch between various SDXL and SD1.5 models, either as part of hires.fix or adetailer.
If I run the first pass with an SDXL model and the hires.fix pass with an SD1.5 model, NPW runs for the first pass but then errors out during the hires pass, giving the following on each step:
For what it’s worth, I’m not using latent upscale (if that makes any difference) for hires.fix.
It gets a bit interesting looking at the behavior with adetailer. If I run
batch count = 1
with an SDXL model for main generation then an SD1.5 model for adetailer inpainting. NPW runs on both the main SDXL pass and the adetailer SD1.5 pass. I was a bit surprised by this as I kind of expected it to throw the same error as hires.fix.However, if I set a
batch count > 1
, the following happens:The error it throws on the SDXL passes is:
I assume it’s a different error because the hires.fix case is erroring out on the SD1.5 passes, while the adetailer case is erroring out on the SDXL passes.
What I don’t understand is why it runs fine with SDXL primary gen + SD1.5 adetailer for
batch count = 1
. It’s like NPW is resetting for the swap from SDXL to SD1.5 when adetailer starts, but not resetting for the swap back to SDXL?Again I realize it’s probably an edge case but thought I would share in case there happens to be a simple fix. FWIW this extension has been extremely useful. Thanks!