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
I checked for similar issues and couldn't find any.
My WebUI and Unprompted are both up-to-date.
I disabled my other extensions but the problem persists.
Describe the bug
I'm sorry for my bad English, so I was used a screen capture.
It appears that the results of [set width] and [set height], which should have been applied when batch_count=X, have been applied to the image with batch_count=X+1.
I am not sure if I understand the issue correctly. Based on your prompt, Unprompted will [choose] a random width and height of 256|512|768 and your screenshot shows that it selected 256x768 for the third image. This is an expected outcome.
If you want the batch count to determine your image dimensions, you need to pass batch_real_index into the _case kwarg of your [choose] blocks. Here is an example:
What I meant to say is that the image size chosen by Unprompted is different from the actual image size.
In the example image, the third image is a square, but the "Size" is 256x768 (it matches the actual size of the fourth image).
This seems to have a negative effect, such as not applying the correct resolution when generated with Hiresfix.
Thank you for clarifying - I see what you mean now. It seems there is a "delay" in updating the width and height properties of a batch process by 1 image. Very strange. It seems to be happening regardless of hires fix on my device.
I will re-open this issue and investigate further.
Due diligence
Describe the bug
I'm sorry for my bad English, so I was used a screen capture.
It appears that the results of [set width] and [set height], which should have been applied when batch_count=X, have been applied to the image with batch_count=X+1.
Prompt
Negative Prompt
Other settings and the issue example
Prompt
No response
Log output
No response
Unprompted version
9.16.1
WebUI version
1.6
Other comments
No response
The text was updated successfully, but these errors were encountered: