"zero uncond" vs "null uncond" with VPred SDXL — AC-Evo 2.5EP

This workflow is for comparing `zero uncond` with `null uncond` on a current vpred model; its named components indicate text and latent inputs, sampling, VAE decoding, and saved image outputs.

Suggestion · not verified

The workflow lists checkpoint loading, text encoding, conditioning adjustments, scheduling, sampling, VAE decoding, and image saving; connections between these stages are not specified.

The named `EmptyLatentImage` and `CLIPTextEncode` indicate latent and text-conditioning inputs, while `VAEDecode` and `SaveImage` indicate decoded images saved as outputs.

Suggestion · not verified

It is listed as a `Workflows` item using the `Illustrious` base model and published by `6DammK9`.

Before use, verify that these named items are available: `KSampler`, `VAEDecode`, `ConditioningZeroOut`, `ConditioningAverage`, `CheckpointLoaderSimple`, `SamplerCustom`, and `CLIPSetLastLayer`.

Suggestion · not verified

Also verify `KSamplerSelect`, `SaveImage`, `EmptyLatentImage`, `CLIPTextEncode`, `BasicScheduler`, `ModelSamplingDiscrete`, and `at-step00394590.safetensors`.

Suggestion · not verified

The described use case involves switching a finetuned model’s objective, such as from `eps` to `vpred` or from `vpred` to `RF`.

The description warns that a math special case can cause drastic differences between WebUIs and ComfyUI.

The listing does not specify a usage license, so verify reuse terms before using it.

Suggestion · not verified