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
The whole image should get screwed up due to the high weight of the "nuclear explosion" tokens. The correct behavior can be observed by removing one count of "pink barbie land, " from the prompt.
What actually happens:
Only the first column will get screwed up, even though "nuclear explosion" is in the common prompt.
Basically what happens is that the first column starts out with less than 75 tokens but then, due to token switching ends up with more than 75 tokens. This causes the tokens in the common prompt to be assigned to the first column and the tokens in the second column to be assigned to the first column.
Describe the bug
Here is a sample prompt that will trigger this bug:
street [:(nuclear explosion:3.0):0.5]
ADDCOMM
pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land, pink barbie land[:, pink barbie land:0.5]
ADDCOL
green scifi steampunk
Expected behaviour:
The whole image should get screwed up due to the high weight of the "nuclear explosion" tokens. The correct behavior can be observed by removing one count of "pink barbie land, " from the prompt.
What actually happens:
Only the first column will get screwed up, even though "nuclear explosion" is in the common prompt.
Basically what happens is that the first column starts out with less than 75 tokens but then, due to token switching ends up with more than 75 tokens. This causes the tokens in the common prompt to be assigned to the first column and the tokens in the second column to be assigned to the first column.
Environment
Web-UI version: v1.9.4
SD Version: 1.5
Other Enabled Extensions
The text was updated successfully, but these errors were encountered: