Yesterday, 09:17
Hi Dan,
Thanks for the clips — I watched both. The longcat-q3 and especially the flux2-dev-int4 results are on another level vs classic havc/DDColor; the flux2 one indeed matches MagicHour's color choices (gold frame, navy suits, maroon curtains). Very impressive.
My hardware is what it is though: GTX 1650 with only 4GB VRAM, 16GB system RAM, i5 (12th gen), Windows.
Question: is there ANY way to run the Flux DiT path (HavcServerDiT / flux2-dev) on this hardware with script changes — e.g. a heavier quantization (q2/q3 GGUF), full CPU offloading of the text encoder, lower input resolution, tiling, or even pure CPU? Slow is fine — I can let it run for days on keyframes only, then propagate with CMNet.
Or is 4GB VRAM a hard wall for Flux no matter the tweaks? And if Flux is impossible, does LongCat or Qwen have a lighter variant that could fit this GPU?
Thanks again!
Thanks for the clips — I watched both. The longcat-q3 and especially the flux2-dev-int4 results are on another level vs classic havc/DDColor; the flux2 one indeed matches MagicHour's color choices (gold frame, navy suits, maroon curtains). Very impressive.
My hardware is what it is though: GTX 1650 with only 4GB VRAM, 16GB system RAM, i5 (12th gen), Windows.
Question: is there ANY way to run the Flux DiT path (HavcServerDiT / flux2-dev) on this hardware with script changes — e.g. a heavier quantization (q2/q3 GGUF), full CPU offloading of the text encoder, lower input resolution, tiling, or even pure CPU? Slow is fine — I can let it run for days on keyframes only, then propagate with CMNet.
Or is 4GB VRAM a hard wall for Flux no matter the tweaks? And if Flux is impossible, does LongCat or Qwen have a lighter variant that could fit this GPU?
Thanks again!