lllyasviel / lllyasviel/stable-diffusion-webui-forge
Hypernetwork support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Checklist
- The issue exists after disabling all extensions
- The issue exists on a clean installation of webui
- The issue is caused by an extension, but I believe it is caused by a bug in the webui
- The issue exists in the current version of the webui
- The issue has not been reported before recently
- The issue has been reported before but has not been fixed yet
What happened?
I cant get hypernetworks to work in Forge. No errors are given. it just doesn't work.
Steps to reproduce the problem
Install brand new Forge UI. Put any hypernetwork in the hypernetwork network folder. In forge UI, click on the hypernetwork from the tab, use trigger word if it exists. Hypernetwork never activates, never renders. Can verify also by locking in the seed generating the image without hypernetwork and then with. Same image generates no change at all.
What should have happened?
Expect the image to change based on hypernetwork loaded.
What browsers do you use to access the UI ?
No response
Sysinfo
New Forge UI, RTX 4090, Windows11.
Console logs
None.
Additional information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with a clean Forge UI installation and reproduce the issue by placing a hypernetwork in the hypernetwork network folder, selecting it from the Forge UI hypernetwork tab, and comparing images with a locked seed. Done means the selected hypernetwork changes the generated image as expected.
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
- Needs clarification
- Newbie friendliness
- 25/100