unet unexpected: ['__index_timestep_zero__']

#193
by Theoldsong - opened

model weight dtype torch.float8_e4m3fn, manual cast: torch.bfloat16
model_type FLUX
unet unexpected: ['index_timestep_zero']

Using the v15 model, the message 'unet unexpected: ['index_timestep_zero'] 'appears. Does it affect usage?

I plug and played v15 into same settings/workflow as v14.1 and it works great.

I'm not getting this error, perhaps because I am using my custom "fixed" qwen node. I do know this is a new parameter in Qwen Edit 2511. Can you share a screenshot of your workflow?

EDIT: It doesn't seem related to the TextEdit node. I have seen that index_timestep_zero thing referenced in some new Qwen Edit 2511 workflows, like this:

image

... but unsure what it does or why it is needed... seems to work fine without it, at least in my testing (but it hasn't even been out for 24 hours, so we are still tinkering...)

I'm not getting this error, perhaps because I am using my custom "fixed" qwen node. I do know this is a new parameter in Qwen Edit 2511. Can you share a screenshot of your workflow?

EDIT: It doesn't seem related to the TextEdit node. I have seen that index_timestep_zero thing referenced in some new Qwen Edit 2511 workflows, like this:

image

... but unsure what it does or why it is needed... seems to work fine without it, at least in my testing (but it hasn't even been out for 24 hours, so we are still tinkering...)

https://huggingface.co/Phr00t/Qwen-Image-Edit-Rapid-AIO/blob/main/Qwen-Rapid-AIO.json

I used this workflows

Sign up or log in to comment