lllyasviel / lllyasviel/stable-diffusion-webui-forge

Can't replicate image generation after update

Open
#1,650 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Under Construction
Dominant language
Python
Stars
13k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hi all,

I recently updated my version of Forge which I'd been avoiding due to previously breaking installations.

I was on: f0.0.17v1.8.0rc-latest-276-g29be1da7

and have updated to: f2.0.1v1.10.1-previous-483-g33b5b9d2

Everything worked fine and I can now run Flux within Forge which was the purpose of the update.

HOWEVER, **I can no longer replicate images using the same image metadata**. Origin of the test images is [this post](https://www.reddit.com/r/StableDiffusion/comments/1exxd3e/teaching_my_kid_to_use_stablediffusion_and_krita/) just for clarity lol.

This is the image made using **the old Forge install**:

![image](https://github.com/user-attachments/assets/29892bcb-7e5f-48cc-a8ad-13fee0dc4fec)

The image metadata is as follows:

> score_9,score_8_up,score_7_up,1girl, (MARCILLEDONATO:1.2), BLONDE HAIR, SINGLE BRAID ,covered in green spiders, witch ,Billie Eilish, fantasy witch, witch, (half shot:1.4), BREAK witches hovel, fantasy house, potions background,spiders, (green spiders:1.2), swarm,
>
>
>
>
> Negative prompt: score_6, score_5, score_4, rating_explicit, rating_questionable, source_pony, realistic, photo, 3D, render, 3d, photorealistic, (bats:1.3)
>
> Steps: 40,
>
> Sampler: Euler a,
>
> CFG scale: 7,
>
> Seed: 666666721,
>
> Size: 832x1216,
>
> Model hash: 44d3daf083, Model: 7thAnimeXLPonyA_v10,
>
> VAE hash: 735e4c3a44, VAE: sdxl_vae.safetensors,
>
> Clip skip: 2,
>
> RNG: NV, "*I had a comment regarding this but looks to be deleted, my response: Ahh, that was to do with seed *generation* (how the "random" number generator works).
>
>It's got to do with how it creates random seeds, NOT anything do to with how the image generates, especially given that I'm specifying a specific seed.*"
>
> Lora hashes: "darkstyle: 8046fb0ecc46, Marcille_PonyXL: d4b765526e19",
>
> Version: f0.0.17v1.8.0rc-latest-276-g29be1da7

And this is an image made using the same spec, imported across into Txt2Img from the png info tab in the **new Forge install**:

![image](https://github.com/user-attachments/assets/4be8ab2e-a5db-49a8-9069-59b0c9c72028)

The image metadata is as follows:

> score_9,score_8_up,score_7_up,1girl, (MARCILLEDONATO:1.2), BLONDE HAIR, SINGLE BRAID ,covered in green spiders, witch ,Billie Eilish, fantasy witch, witch, (half shot:1.4), BREAK witches hovel, fantasy house, potions background,spiders, (green spiders:1.2), swarm,
>
>
>
>
> Negative prompt: score_6, score_5, score_4, rating_explicit, rating_questionable, source_pony, realistic, photo, 3D, render, 3d, photorealistic, (bats:1.3)
>
> Steps: 40,
>
> Sampler: Euler a,
>
>**Schedule type: Automatic,**
>
> CFG scale: 7,
>
> Seed: 666666721,
>
> Size: 832x1216,
>
> Model hash: **a881029f19**, Model: 7thAnimeXLPonyA_v10,
>
> RNG: NV,
>
> Lora hashes: "darkstyle: 8046fb0ecc46, Marcille_PonyXL: d4b765526e19",
>
> Version: f2.0.1v1.10.1-previous-483-g33b5b9d2,
>
> **Module 1: sdxl_vae**

Highlighted are the bits that I can see are different.

I also don't seem to be able to specify ClipSkip 2 within the "XL" radio selection in the new top right of this interface though it appears that's applied automatically.

I've also set the UI to "All" mode and set everything as before and comes out wrong.

I've also done a grid using all the different **"Schedulers"** as those are now new options that weren't there before but none of them produce the right output image.

----------------------

Here is an image of my generation UI in the **old forge** post-completion showing the image generated and the obvious settings:

![image](https://github.com/user-attachments/assets/b2091f0b-0900-4bde-808e-9e483e6827ed)

And here is one in the **new one**:

![image](https://github.com/user-attachments/assets/e8970942-97f4-4a57-995f-87eb835776df)

**Everything is being created with the same models and LoRAs being loaded from the same folders. All launch arguments are identical: `--cuda-stream --pin-shared-memory --cuda-malloc` and I've run both versions with and without.**

---------

### Am I just being totally stupid?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the generation with the supplied prompt, metadata, model, LoRAs, seed, and launch arguments on both Forge versions. Compare the old and new outputs and settings, especially the model hash, scheduler or schedule type, ClipSkip, and VAE; done means identifying the changed behavior and restoring matching output or documenting the incompatibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.