As you can see, in the program it’s listed with “_paths”
I think it’s unable to find the correct file because it’s not there. I’m about to test to see if the original yaml is detected, the one with the original name i.e. “extra_model_paths.yaml”
The test was not successful. It did not detect that yaml nor read from it. This is a major bug.(edited yaml not detecting other model directories)
The ONLY partial way I found around this is to make a symbolic link in the my documents/comfyui folder replacing the models folder in there with the model folder link that has models in it already, but I’m still missing the models that I have on other drives.
The original file from ComfyUI, extra_model_paths.yaml. Typically you would edit this example file and leave it in the same place as main.py.
The config file used exclusively in the desktop app, extra_models_config.yaml. This is generated and maintained by the desktop app. This lives in %APPDATA%\ComfyUI on Windows. Other locations are in the user guide.
If you are not seeing models in custom nodes, they likely need to be updated to support multiple paths. Please let us know which ones! We can likely help the authors get them updated.
If you are not seeing models loaded in core ComfyUI nodes, though, then that is a bug in desktop.
I appreciate the last reply was some time ago, but I wonder if there is any documentation/best practice/how-to guide that can be used as a reference for how custom nodes should be implemented to respect the search paths defined in extra_model_paths.yaml?
Digging through the source of a couple of nodes I use, I see a lot of variations on roughly the same theme of:
model_path = os.path.join(model_directory, model_name)
if not os.path.exists(model_path):
etc. etc. and depending on exactly how these are implemented, some of them seem to use the preferred default override directories specified in extra_model_paths.yaml just fine, others of them work to load models from those directories, but will still download to the default models/ location, and some of them ignore it altogether.
Yes, I could just create symlinks for every folder, but it feels like extra_model_paths.yaml is the intended way of solving this problem, it’s just that not every custom node respects it (e.g. Florence, Whisper, FaceRestore are just three examples I’ve encountered this morning that don’t).