artventuredev
commented
8 months ago I understand your point. The current implementation leverages a built-in feature of the SD WebUI, which enables temporary changes to the checkpoint before executing a task and then reverts back to the original setting upon completion. Not revert the checkpoint back may cause some confusion, because this only change the loaded checkpoint in the backend, but not change the selected value in the checkpoint dropdown.
Considering this, I'm planning to introduce a setting that allows for a permanent change to the checkpoint (i.e., without reverting). But it's important to be aware that the checkpoint currently displayed in the UI dropdown may not accurately represent the checkpoint that's actively loaded during task execution.
Hey,
I have an annoying issue with the "queue with all checkpoints" option. I currently have 365 models and wanted to use the same prompt and settings but with all the different models to see how it will look like. The Task Queue shows the correct number of 365 tasks but the problem is after generating an image with one model, it'll load the weights of the currently selected model and then after completely loading then will load the next model. Example:
Loads weight of Model A Generates images of Model A Loads weight of Model A Loads weight of Model B Generates images of Model B Loads weight of Model A Loads weight of Model C Generate images of Model C Loads weight of Model A Loads weight of Model D ... and so on
It keeps bouncing back to the currently selected model instead of going from A to B to C to D ... which takes a long time since I load the models from an external HDD