Is there an existing issue for this problem?
Install method
Invoke's Launcher
Operating system
Linux
GPU vendor
Nvidia (CUDA)
GPU model
No response
GPU VRAM
No response
Version number
main branch
Browser
No response
System Information
No response
What happened
When using the Flux.2 Klein models, which accept more than one reference image, the reference images seem to be presented to the denoiser in random order. That is, if I have images named A, B, C and they are ordered that way from left to right in the frontend's reference image list, the backend sometimes receives A, B, C, sometimes C, A, B, and so forth. This makes it impossible to refer to each image by its order in the way that's documented, such as "image 1"
What you expected to happen
I expect the images to be presented to the conditioning and denoising steps in exactly the order they appear in the frontend, ordered from left to right.
How to reproduce the problem
No response
Additional context
No response
Discord username
No response
Is there an existing issue for this problem?
Install method
Invoke's Launcher
Operating system
Linux
GPU vendor
Nvidia (CUDA)
GPU model
No response
GPU VRAM
No response
Version number
main branch
Browser
No response
System Information
No response
What happened
When using the Flux.2 Klein models, which accept more than one reference image, the reference images seem to be presented to the denoiser in random order. That is, if I have images named A, B, C and they are ordered that way from left to right in the frontend's reference image list, the backend sometimes receives A, B, C, sometimes C, A, B, and so forth. This makes it impossible to refer to each image by its order in the way that's documented, such as "image 1"
What you expected to happen
I expect the images to be presented to the conditioning and denoising steps in exactly the order they appear in the frontend, ordered from left to right.
How to reproduce the problem
No response
Additional context
No response
Discord username
No response