lllyasviel / lllyasviel/stable-diffusion-webui-forge

AssertionError: You do not have CLIP state dict! and blue screen if using both text_encoder + VAE, also blurry images

Open
#2,778 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I was trying to create an image with a certain checkpoint (It's my first time doing this so I'm not sure if I can link it here since it's NSFW) and I ended up getting this error

![Image](https://github.com/user-attachments/assets/0d3e8ab0-f814-424e-9bad-9f47b9fc6f6e)

I asked the guy from the video I followed on youtube what to do and he sent me a github link that told me to download both of these

![Image](https://github.com/user-attachments/assets/2e2762c8-1021-4260-be32-37702ab963b2)

https://huggingface.co/lllyasviel/flux_text_encoders/tree/main
https://huggingface.co/black-forest-labs/FLUX.1-dev/tree/main

Deepseek told me fp16 would be better for my case since I have a weak 6gb vram card (1660 super) and 16gb ram

After installing both the Text encoder and VAE I tried first generating with just the Encoder but it didn't work, then when I tried running both as someone on that forum said my computer immediately got a blue screen with a out of memory error

Also worth mentioning I've barely able to generate anything with ForgeUI, it always creates something blurry or kinda hazy, the sole exception was when I tried doing something with anime and it worked normally

![Image](https://github.com/user-attachments/assets/0aeea7b9-1e7e-4117-9ebb-01b51179eeff)

These are my checkpoints, the first one created a total blur for me when I tried using it, middle one is the one I'm currently having problems and the last one worked for anime but when I asked it to do a simple cat it left it all hazy but that was a few days ago so I don't remember the configs I used for it

Suffice to say I'm a complete newbie to this stuff, I also used ComfyUI and it was alright but it was taking way too long to do images and the UI was kinda complicated so I decided to go back to ForgeUI

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

No source file or test is named. Start by recording the exact ForgeUI checkpoint, text encoder, VAE, settings, and hardware, then reproduce the assertion and out-of-memory failure using the linked FLUX files; done would require a minimal reproducible case or confirmed compatibility guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.