Replies: 2 comments 1 reply
-
At the moment it seems like load_model in the sd_models script does not account for/read config files (likely incomplete? Comparing to A1111 setup of this file) If you wanted a rough workaround , update the line in the model_base which currently checks if it is an EPS model and instead replace the return 'c' value to V_PREDICTION, this allowed me to get VPRED models to load and function. Note though that this does break all other models that do not use it, so you will have to change this back if so, which may be annoying depending on how often you change models. To add on: there is likely a way to set the Model_Type variable fetched from the checkpoint directly (likely via a merger) but I have no idea how to do that. |
Beta Was this translation helpful? Give feedback.
-
The workaround helps a lot, thanks! Hopefully there will be support for config files in time. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I use an SD1.5 model that requires a custom .yaml file to work properly because it uses parameterization: "v" like SD2 models do.

In the original webui I simply put the yaml in the same folder as the checkpoint with the same filename and it gets loaded automatically. Is there a way to load this yaml with the model in Forge?
The difference to v1-inference.yaml is rather small overall, just two new lines but without it the outputs are broken.
Beta Was this translation helpful? Give feedback.
All reactions