-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: Error with starter model dreamshaper 8 and certain schedulers #6368
Comments
I'd guess it's picking up algorithm-type 'deis' from the default scheduler for the model which is DEISMultistepScheduler, and using that in the scheduler config for the DPM schedulers. It's probably going to need a check for this in the code which picks other f the values to change (algorithm type would seem most sensible to me, so DPM using its default value) unless the InvokeAI team give us a way of changing the scheduler parameters. |
Just confirming that this is happening with dreamshaper 9 inpaint and the Orthodox Christian Iconography LoRA if you wanna test. |
I had a similar issue and attempted to fix by updating the below files. afterwards, i can see the image generating in the UI but as soon as it reaches 100%, the entire images turns black.
This was the error message in UI for me: and error message in CMD: |
Hi got this problem too |
I have the same issue |
Is there an existing issue for this problem?
Operating system
Linux
GPU vendor
Nvidia (CUDA)
GPU model
No response
GPU VRAM
24
Version number
4.2.1
Browser
FF
Python dependencies
No response
What happened
When using the starter model
dreamshaper 8
(ordreamshaper 8 inpainting
) and some schedulers, generation fails during denoising.Only these schedulers trigger the error:
The starter models tab installs a diffusers version of the affected models. When using the checkpoint version of this model, there is no error.
What you expected to happen
All the schedulers work.
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: