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
After generating a couple of images in version 4.2.8, invoke stops creating proper images. Whenever this happens, the issue seems to persist until invoke is restarted - every single new generation produces a blur of colors like in the example below.
After restarting invoke, i generated the exact same image (same seed and metadata) which created a normal output:
What you expected to happen
Generating images with identical metadata should have reproducible results.
How to reproduce the problem
Sadly i can not pin down the cause yet. It feels like switching models a lot between generations (i.e. queuing up the same prompt with different models for comparison) makes this issue appear more often.
I tested 4.2.8rc2 only briefly, but had the same issue once in the release candidate as well.
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this problem?
Operating system
macOS
GPU vendor
Apple Silicon (MPS)
GPU model
No response
GPU VRAM
No response
Version number
4.2.8
Browser
Chrome
Python dependencies
No response
What happened
After generating a couple of images in version 4.2.8, invoke stops creating proper images. Whenever this happens, the issue seems to persist until invoke is restarted - every single new generation produces a blur of colors like in the example below.
After restarting invoke, i generated the exact same image (same seed and metadata) which created a normal output:
What you expected to happen
Generating images with identical metadata should have reproducible results.
How to reproduce the problem
Sadly i can not pin down the cause yet. It feels like switching models a lot between generations (i.e. queuing up the same prompt with different models for comparison) makes this issue appear more often.
I tested 4.2.8rc2 only briefly, but had the same issue once in the release candidate as well.
Additional context
No response
Discord username
No response
The text was updated successfully, but these errors were encountered: