text2image-gui icon indicating copy to clipboard operation
text2image-gui copied to clipboard

number of rendered images is off in subsequent renders

Open xanathon opened this issue 3 years ago • 6 comments

The problem I reported yesterday on Discord with the beta version of 1.4.0 is the same with the finished version from itch.io: I render a first sequence of three images and get three images, a subsequent render with the same seed and with or without changed parameters only renders two images out of three. See attached image, left top you can see that three images are set, bottom right you can see that only 2/2 were rendered.

In addition to that: the "render" button stays at "cancel" and the progress rotator thingie on the top keeps rotating. Did not happen with the earlier version (1.3.x)

image

xanathon avatar Sep 21 '22 18:09 xanathon

Can you reliably reproduce this?

n00mkrad avatar Sep 21 '22 18:09 n00mkrad

yes. after every restart and with different phrases and settings I get the same problem.

xanathon avatar Sep 21 '22 18:09 xanathon

I have to correct that. If I close the UI and restart, my CUDA device is no longer detected. image

Edit: But it renders images anyway ...

xanathon avatar Sep 21 '22 18:09 xanathon

That must be a simple for-to or loop-until problem somewhere, because if I increase the number of images to render to four, only three are rendered, if I change it to 5 only 4 are rendered. So maybe somewhere there is a < instead of <= in a for loop or something like that.

xanathon avatar Sep 21 '22 18:09 xanathon

That must be a simple for-to or loop-until problem somewhere, because if I increase the number of images to render to four, only three are rendered, if I change it to 5 only 4 are rendered. So maybe somewhere there is a < instead of <= in a for loop or something like that.

That can't be the problem because it works fine for me.

n00mkrad avatar Sep 22 '22 08:09 n00mkrad

"It works for me" is always a very bad support answer. That may be so but does not invalidate the fact that it does not work here.

Instead of saying "it works for me" (which is never productive and never yields results) you probably should give me additional options to solve this problem. Are there logs somewhere? I do not think something on my system is the problem, since this bug did not happen in 1.3.x, so it must be something that was invented in 1.4.0.

xanathon avatar Sep 22 '22 09:09 xanathon