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
While currently you can specify a model to download from hugging face via the models.yaml file. Having the ability to specify a custom file directory to load pre existing models from would be very beneficial.
I for example have fluxgym installed on a hdd, and have my model folder installed on a much faster ssd.
The file names of the files i have may also not quite match those from the original flux dev repository, but they are still the expected safetensor files (for example).
I don't want to have to worry about the models unnecessarily downloading ~40GB of files i don't actually need, or taking forever to read from the hdd into memory once they have. This would easily solve both of those problems.
Note this isn't limited to the flux model, but the clip and text encoder models also, which i also have located on my ssd.
(It seems adding labels to github issues is a restricted thing)
The text was updated successfully, but these errors were encountered:
While currently you can specify a model to download from hugging face via the models.yaml file. Having the ability to specify a custom file directory to load pre existing models from would be very beneficial.
I for example have fluxgym installed on a hdd, and have my model folder installed on a much faster ssd.
The file names of the files i have may also not quite match those from the original flux dev repository, but they are still the expected safetensor files (for example).
I don't want to have to worry about the models unnecessarily downloading ~40GB of files i don't actually need, or taking forever to read from the hdd into memory once they have. This would easily solve both of those problems.
Note this isn't limited to the flux model, but the clip and text encoder models also, which i also have located on my ssd.
(It seems adding labels to github issues is a restricted thing)
The text was updated successfully, but these errors were encountered: