skip_cfg_above_sigma value has changed for NAI Diffusion v4.5 Full model

[evanjs]

What Happened?

It seems like skip_cfg_above_sigma has a different value for nai-diffusion-4-5-full / NAI Diffusion v4.5 Full
Of course, this only matters when Variety+ is enabled
Otherwise, skip_cfg_above_sigma is null

It seems the value is now 58 rather than 19

---

Lazy patch in my fork

evanjs@7de95ad
We probably want to handle it more robustly, but I half hardcoded the value on my end for now.
Not sure if that's even valid or if the adaptive values need to be factored into the existing calculation.

But after this change, I get much more similar outputs between ComfyUI_NAIDGenerator and NAI

---

What does it look like on the NAI end?

This is the closest to "official" details I can find re what NAI is doing on their end
This is simply an excerpt of the JS from the web client
Note that I have removed the other settings normally returned with each model and listed only cfgDelaySigma (skip_cfg_above_sigma)

Client code excerpt

function eK(e) {
    switch (e) {
        case "stable-diffusion":
        case "nai-diffusion":
        case "safe-diffusion":
        case "waifu-diffusion":
        case "nai-diffusion-furry":
        case "curated-diffusion-test":
        case "nai-diffusion-inpainting":
        case "safe-diffusion-inpainting":
        case "furry-diffusion-inpainting":
            return {
                cfgDelaySigma: 19
            };
        case "nai-diffusion-2":
            return {
                cfgDelaySigma: 19
            };
        case "nai-diffusion-xl":
        case "nai-diffusion-3":
        case "nai-diffusion-3-inpainting":
        case "nai-diffusion-furry-3":
        case "nai-diffusion-furry-3-inpainting":
            return {
                cfgDelaySigma: 19
            };
        case "nai-diffusion-4-curated-preview":
        case "nai-diffusion-4-curated-inpainting":
        case "nai-diffusion-4-full":
        case "nai-diffusion-4-full-inpainting":
            return {
                cfgDelaySigma: 19
            };
        case "custom":
            return {
                cfgDelaySigma: 58
            };
        case "nai-diffusion-4-5-curated":
        case "nai-diffusion-4-5-curated-inpainting":
        case "nai-diffusion-4-5-full":
        case "nai-diffusion-4-5-full-inpainting":
            return {
                cfgDelaySigma: 58
            }
    }
    return {
        cfgDelaySigma: 19
    }
}

[sirius422]

That's correct, I also noticed this difference while capturing packets. However, there's actually a small issue with your implementation. The skip_cfg_above_sigma in V4.5 is also derived by taking the square root of the pixel count ratio and then multiplying by the base value of 58. You can verify this by testing with small resolutions in the web client (such as 640x640).