You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user moves model files to another folder, the model database continues to remain stale.
Here's the example scenario:
Let's say I add a bunch of LoRA's in a folder C:/models/loras which has a bunch of safetensors files.
I boot up Invoke and the client recognizes these new models and registers them to the database and the client.
Now let's say I do some local file management and now instead moved these LoRA's to C:/models/loras/styles
When I boot up Invoke next, the ModelInstallerService as expected, reports that the LoRA's registered are now missing from their location.
Here's where the problems begin:
The Model Manager UI does not reflect these missing models in anyway. So it is not possible to tell at a glance from the UI which of the models files are not there. This needs to be referred to from the console. The Model Manager should mark this.
There doesn't seem to be a way from the Model Manager UI to update these paths to a new path. So it basically becomes a dead entry.
If you notice, the new path of these LoRA files are also in the same folder hierarchy where they should be recognized automatically by Invoke. But they do not register the new paths because the files share the same names as those existing in the database already. If the file names are same, then maybe we should update these paths automatically? This could be a problem for Diffusers sub models which have the same names but should not be an issue for checkpoint paths maybe? Because Diffusers are detected by the folder name in most cases.
What you expected to happen
The Model Manager UI should visually indicate the missing model files somehow
The Model Manager UI should have an option to update these paths either manually or automatically.
The ModelInstallerService should probably override the database entry with the new path if the model with the same name is detected under the same folder hierarchy.
How to reproduce the problem
No response
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered:
The short answer is you aren't allowed to move models around in the models dir. That's an application-managed directory
#6122 hides the missing models from the API response
A more involved but maybe better UX would be to extend the model config class w/ a flag indicating if the model is physically present or not. This would alos require UI changes to communicate that the model is missing.
Omitting the model entirely seems like a good compromise to me. It encourages the user to look at the terminal to see what's wrong.
Is there an existing issue for this problem?
Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
RTX 4090
GPU VRAM
24GB
Version number
main
Browser
Chrome / Firefox
Python dependencies
No response
What happened
When a user moves model files to another folder, the model database continues to remain stale.
Here's the example scenario:
C:/models/loras
which has a bunch ofsafetensors
files.C:/models/loras/styles
ModelInstallerService
as expected, reports that the LoRA's registered are now missing from their location.Here's where the problems begin:
What you expected to happen
How to reproduce the problem
No response
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered: