Chris Bauer

For anyone else coming here from searching, you'll want to pay close attention to the "Everything now lives in the invokeai directory" section in the 2.2.4 release note here: https://github.com/invoke-ai/InvokeAI/releases/tag/v2.2.4

I was getting the same error with a custom inpainting model. I made progress on it by importing it using the command line instead of the UI like I had...

I was able to work around this issue by using the `convert_model!` [command](https://invoke-ai.github.io/InvokeAI/installation/050_INSTALLING_MODELS/?h=model#converting-legacy-models-into-diffusers) to switch to diffusers then importing (importing happened automatically after converting).

Actually, I figured this out. The inpainting model's configuration file was not set in the model manager. Pointing the config file setting to the config file in my local filesystem...