Closed CS1o closed 6 days ago
@CS1o Hello there! I'm here to help you with any bugs, questions, or anything else you might need. Let's squash those bugs together! 🤖
To address the issue of custom Adetailer models not being recognized, ensure the following:
File Extension: The models should have a .pt
file extension, as Adetailer recognizes models with this extension [1].
Directory Structure: Place the models in the models/adetailer
directory. Additionally, ensure that any extra model directories are specified correctly in the ad_extra_models_dir
option, if used. These directories should be separated by vertical bars (|
) [2].
Model Validity: Ensure that the models are valid bbox detection or segment models. Invalid models will not be recognized [1].
Logging and Errors: Check the console logs for any error messages related to model loading. Adetailer provides error messages when it fails to recognize a model, which can help diagnose the issue [2][3].
If these steps do not resolve the issue, consider checking for any updates or changes in the Adetailer repository that might affect model recognition.
To continue talking to Dosu, mention @dosu.
Fixed.
Turns out when i switched from --ckpt-dir "Path to models/stable-diffusion" --lora-dir "Path to models/lora" etc. to just --models-dir "Path to the overall models Folder" a few days ago, the adetailer models then wont get recognised when they are still in the webuis models/adetailer folder and not in the new Path given by --models-dir. Makes sense as thats how it should work.
Describe the bug
Custom Models for Adetailer won't show up in the Adetailer selection.
Steps to reproduce
Update Adetailer to the latest Version. Download an adetailer compatible model from Civitai and move it into models/adetailer. Restart the Webui (Auto1111 or Forge) and the model wont show up under the Adetailer model dropdown.
Screenshots
Console logs, from start to end.
List of installed extensions