Closed DLai126 closed 1 year ago
After seeing several cases, I don't believe the NAN issue has anything to do with adetailer, even if the issue only appears when using adetailer.
What we can do is try to change the prompts, models, VAEs, loras, embeddings, and weights we use and see if we can find a point where we don't get that error.
After seeing several cases, I don't believe the NAN issue has anything to do with adetailer, even if the issue only appears when using adetailer.
What we can do is try to change the prompts, models, VAEs, loras, embeddings, and weights we use and see if we can find a point where we don't get that error.
Thank you for your response. I have found that sometimes, when keeping the prompts, models, VAEs, loras, and weights the same, enlarging the image will succeed, while other times it will fail. However, I still really like the effects of adetailer, so it seems that I'll have to make do with using it.
Could be another issue with the recent Nvidia driver memory changes, but unsure. Only encountered this issue recently too, it was working fine before the driver update. Loading another model fixes it, but only for the first generation of that model, maybe related to how all the different models (yolo, etc., controlnet models, VAE and checkpoint) are loaded into memory.
I'm getting similar issues to this, I've noticed that it happens when using the Reference ControlNet to generate the image. If I turn off the controlnet it works as expected.
EDIT: Adding "--no-half" to the command line did fix things for me and I should've done it ages ago. Only use "--disable-nan-check" as a stopgap if nothing else works. Otherwise, ignore that advice.
The rest of the original message is still relevant though. I don't think this is an ADetailer issue. ADetailer only draws our attention to it because using ADetailer creates a second exposure to whatever process has the bug in it.
I've been encountering this too and my hunch is that it's some kind of memory issue, as it happens more often at larger resolutions. I have the controlnet extension installed but I'm not using it and it's happening to me frequently.
As the error says, it can be overridden by adding "--disable-nan-check" to your webui-user.bat file, but this only changes what happens when the error hits, as the zone failing to be generated will be replaced by a black square. If the error happens during primary generation, the whole image is replaced by a black square, and if it happens while ADetailer is processing, only the face becomes a black square.
It's not a solution at all, but it does mean that when generating multiple images, the process won't completely stop and you can still generate the rest of the images (or at least attempt to). I think this is still an improvement, since I'd rather have eight failed images in a set of 16 than the process canceling itself three images in.
And given that the generation can fail differently at two different stages, I agree that this is not almost certainly not an ADetailer bug and there's probably nothing the ADetailer team can do to address it.
redownload models. put in in seperate folder (fixed models) and give it a hard read only attribute. Use seperate checkpoint for adetailer, so it has to reload between txt2image and adetailer. also allow only 1 model in memory.
I've had no nans errors after doing that
Describe the bug
When I use "adetailer" in txt2img to generate an image, I move the image to img2img and use "Tiled Diffusion" to enlarge the image and enhance details using the tile functionality of controlnet. I also use "adetailer" again. However, the following error occurs.
Full console logs
List of installed extensions
No response