Closed ChiaYen-Kan closed 10 hours ago
@ChiaYen-Kan Hello there! I'm here to help you with any bugs, questions, or contributions you may have. Let's work together to solve the issue you're facing.
The issue you're experiencing with generating white images when using DirectML with fp16 in the adetailer module is not documented in the repository. However, there are a few steps you can take to troubleshoot and potentially resolve this issue:
Check for Updates: Ensure that both the adetailer module and the SD.Next framework are up-to-date. Sometimes, bugs are fixed in newer versions.
Compare Logs: Examine the logs for both fp16 and fp32 to identify any differences or errors that might indicate why fp16 is failing. The logs you provided might contain useful information.
Fallback to fp32: If fp16 is not critical for your use case, you might want to continue using fp32 as a temporary workaround.
Report the Issue: Since this seems to be a bug, consider reporting it to the maintainers of the adetailer module with detailed logs and steps to reproduce the issue. This will help them investigate and potentially fix the problem in future releases.
Unfortunately, there is no specific documentation or known issues related to DirectML and fp16 in the adetailer module that could provide a direct solution to this problem [1][2].
To continue talking to Dosu, mention @dosu.
Adetailer generates the mask, and requests inpainting back to the backend. These hardware-specific issues are specific to that backend, and not something I can fix.
Describe the bug
i use SD.Next adetailer version is v24.8.0 when use directml + fp16 to fix face is generate white image but use directml + fp32 is ok i test the v24.9.0, but is also generate white image
Screenshots
fp16
fp32
Console logs, from start to end.
fp16 log fp16.txt
fp32 log fp32.txt