Load Latent Upscale Model and VAELoader KJ issue

#14
by fzshyi - opened

Hi RuneXX, I am using LTX-2.3_-_I2V_T2V_Basic.json and have encountered two issues:

  1. The Load Latent Upscale Model can find ltx-2-spatial-upscaler-x2-1.0.safetensors in the directory, but cannot find ltx-2.3-spatial-upscaler-x2-1.0.safetensors, while the Load Upscale Model can find the two.
  2. I used ltx-2-spatial-upscaler-x2-1.0.safetensors to execute the workflow, but the VAELoader KJ node reported an error, whether it's Kijai's or unsloth's vae model:

屏幕截图_9-3-2026_145727_127.0.0.1
屏幕截图_9-3-2026_145712_127.0.0.1

Is there something wrong with me?

Use regular standard Comfyui VAE loader for the video vae (as it is in the original workflow)
That should fix it ;-) the VAE KJ node is for the audio vae only

image

And the latent upscaler is here : https://huggingface.co/Lightricks/LTX-2.3/tree/main

Also a little "guide" here on where to find them and where to save them:
https://huggingface.co/RuneXX/LTX-2.3-Workflows/discussions/10

I keep getting the same error with the standard Comfyui VAE loder. I made sure to double check all files are correctly placed + ComfyUI has latest version as do all plugins. Same error as above.

image

PS: This is from "LTX-2.3_-_FL2V_First_Last_Frame_Injection.json" workflow.

Have you updated ComfyUI to the latest?

First of all thank you runexx.
After upgrading ComfyUI from 0.15.1 to 0.16.4.
The first issue still exists. The files have been downloaded and placed in the specified directory. Can help check the result, the two loaders detect different results.
2026-03-10_105328
2026-03-10_104800
2026-03-10_104852
The second problem has been solved. It can run successfully whether using ComfyUI's or KJ's vae loader.
Now the issue is that the ltx2 upscaler is obviously not suitable. Although the process can run through, the effect is not good.

I found out that there is also a latent_upscale_models folder that should be put there, hahaha.

yes you are not the first that did his ;-).
But you figured it out, its a different upscaler

Sign up or log in to comment