Is there an existing issue for this?
What should this feature add?
Load community GGUF builds of the LTX-2 (2.5) transformer. Today installation is refused in
configs/main.py with "GGUF-quantized LTX-2 checkpoints are not supported yet"; bf16, Comfy int8_tensorwise and
header/marker-named nvfp4 single files load.
Alternatives
Use the int8 or nvfp4 single file.
Additional Content
The full matrix of what loads today is in #9726 (Model Format Support page).
Is there an existing issue for this?
What should this feature add?
Load community GGUF builds of the LTX-2 (2.5) transformer. Today installation is refused in
configs/main.pywith "GGUF-quantized LTX-2 checkpoints are not supported yet"; bf16, Comfyint8_tensorwiseandheader/marker-named nvfp4 single files load.
Alternatives
Use the int8 or nvfp4 single file.
Additional Content
realrebelai/LTX-2.5_GGUFs,Abiray/LTX-2.5-Distilled-GGUF,vantagewithai/LTX-2.5-GGUF.unsloth/LTX-2.3-GGUF, ~371k;QuantStack/LTX-2.3-GGUF) are LTX-2.3, which InvokeAIrefuses regardless of format (only 2.5 is supported). The refusal message should stay clear for those.
Main_GGUF_*_Configfingerprinted by keys (GGUF headers often name another architecture), a loader that keeps quantized Linears packed and unpacks the rest withunpack_ggml_at_load, and the denoise node'speak_dequant_transient_bytes, which already counts GGUF layers (fix(model-cache): reserve the GGUF dequantization transient in every node #9709).The full matrix of what loads today is in #9726 (Model Format Support page).