Forge Announcement (June 8) #801
Replies: 73 comments 116 replies
-
Oof, F in the chat boyos |
Beta Was this translation helpful? Give feedback.
-
I just created a github account just so I can comment here: This announcement has broken my heart, I have been using forge for months and I was hoping that someday you would come and say that you would continue to update it. For me it is impossible to use A1111 on XL models, I have tried a thousand ways and the VRAM consumption and time is very high compared to forge, I don't know what kind of black magic you have used to create forge but it is a real pity that you abandon the development. I have installed the DEV version of a1111 you are talking about with those “improvements” you are talking about. But I still have the same problems as always, for a simple image in XL, with a lighting model of 8 steps, a1111 takes more than 2 minutes to create it, consuming all the VRAM, instead in forge, the same image with the same model, does not take more than 10-12 seconds, for things like this it is impossible for me to switch to A1111 in its current state, I do not know what problem I have that forge works much better. I hope you change your mind and do not abandon the development, it is the best program without doubt for this kind of things, and hopefully someday you can continue updating it and helping those people who have a humble computer. I don't know how difficult it will be to implement the VRAM and u-net improvements in a1111, but I sincerely believe that no matter how difficult it is, it should be the number 1 priority of the A1111 developer, it completely changes absolutely everything and I don't understand how at this point, after demonstrating that forge handles VRAM in a wonderful way, the dev of A1111 is not trying to implement this. Because it would be the biggest revolution for the program. Sorry for my english and if you didn't understand what I said, I'm using a translator while I'm crying. |
Beta Was this translation helpful? Give feedback.
-
This is very sad news to me. I believed and hoped until the last that you would continue this wonderful project. I like Forge very much and it will be very hard for me to give it up. My heart is broken... |
Beta Was this translation helpful? Give feedback.
-
I just got a friend into using Forge, and to see this announcement made me feel a little annoyed, since his PC already can barely handle the size of SD, but atleast it would run unlike on A1111. I could be wrong, perhaps it runs on par with Forge now (the last time I used A1111 was probably in March), and besides I was already thinking of just letting him remote access my copy. ¯_(ツ)_/¯ |
Beta Was this translation helpful? Give feedback.
-
no point of using automatic1111 if they don't implement VRAM optimization like in forge, in seems like the dev branch did nothing in that regard |
Beta Was this translation helpful? Give feedback.
-
I compared forge vs A1111 on the dev branch, and A1111 seems to be generally faster on SDXL on a RTX 4090, BUT without using loras. The moment you add a LoRA, A1111 takes a good while to start to do inference. Then it's the same or faster. Not sure what is happening on that side. Anyways, really thanks for all your work on Forge. |
Beta Was this translation helpful? Give feedback.
-
Would you please reconsider? |
Beta Was this translation helpful? Give feedback.
-
Ok, so if I understand correctly the speed optimizations from forge will be implemented in automatic 1111 2.0. What about VRAM memory optimizations? you said that unet-patcher and modern memory management will not be implemented currently. Will they ever be implemented in automatic 1111? I hope so, it's good that automatic 1111 is getting faster, but my main problem with automatic 1111 is that I don't have much VRAM ( I have a 1060 6gb). Could they be added in automatic1111 2.1 or a future version?🤔 |
Beta Was this translation helpful? Give feedback.
-
If you want to continue using the old ver forge program, remember to delete the update script “update.bat”, avoid accidentally clicking on it |
Beta Was this translation helpful? Give feedback.
-
I think this is great news. I have paid some attention to the developpments in A1111 dev branch, the devs there have pulled some phenomenal improvements to inference speeds in the last few weeks. I'd like to think forge's incredible inference pipeline was the push in the back that they needed to actually go and address the issue. I also think it's great that this repo will live on to test some other features that are "costly" to implement right now in A1111. This sounds like a good compromise. Cheers to the team! Keep going guys, your work is useful to thousands of people :) |
Beta Was this translation helpful? Give feedback.
-
Is it possible to switch our install to the dev branch of A1111? Or do we need a brand new install? If we can switch, can someone give directions? |
Beta Was this translation helpful? Give feedback.
-
The reactions in this thread are disappointing. Lots of whining about a free tool which will continue to function just as it always has. There's no need to switch to anything else if the current version already works. Forge is a great project and I'm excited to see where it goes in the future. |
Beta Was this translation helpful? Give feedback.
-
We don't care about a1111 or forge; we are just very happy that you are back, our old friend. We missed you |
Beta Was this translation helpful? Give feedback.
-
Showing up after over 4 months of inactivity (zero bug fixes), just to break our installs, so we have to use 'git checkout 29be1da' & 'git reset --hard' to make them work again? You're a jerk. A highly gifted dev, initially helpful, but ultimately the most frustrating developer I've ever dealt with on Github. You hate production artists, don't you? You love the MidJourney and FoOocus type users, who can only create with text. Your work is aimed at replacing us, not empowering us. I think you want art for the masses (no artists/everyone an artist), and you've never intended to cater to existing artists in any way. I feel like ControlNet became used by artists incidentally and you broke it and stopped developing it, possibly as a result. I'm not gonna kiss your ass like everyone else here, since I'm giving up SD and Deforum because of you. Thanks for when your tools actually worked. I wrote up bugs in your CN repo over a year ago that you've never implemented, like allowing Inpainting with any other model. You ought to give this and your other repos to people who will ACTUALLY WORK on them. You'd make a great contributor, with occasional pushes, but you can't manage all the work as the sole dev. Not when you show up once every few months. Advice for anyone on Stable Forge: Switch back to A1111. They've probably implemented most or all of the good code from this midden heap. Goodbye Illyasviel and Generative Art. |
Beta Was this translation helpful? Give feedback.
-
It seems most of the people who commented here do not know what open-source development is... |
Beta Was this translation helpful? Give feedback.
-
controlnet is not supported by xyz plot, when will it be? |
Beta Was this translation helpful? Give feedback.
-
F***, we spend months to learn the forge backend in order to port our extension to forge. Now you say it “likely to break almost all extensions”. This is really making us 🤡 |
Beta Was this translation helpful? Give feedback.
-
I think people here should chill the f out with their entitlement, it's irritating to say the least.
|
Beta Was this translation helpful? Give feedback.
-
Hi Forge Users, Here are some updates regarding the recent announcement:
We recommend users to back up their files because the code base may undergo major changes in a few weeks. Right now, users do not need to do anything. If you are a professional user in a production environment, after the update happens (which will be in several weeks later), we recommend using version 29be1da (which will soon be available on a “download previous version” page) or using the upstream webui if necessary. There is also a possibility that our updates will be seamless, with no noticeable errors, but this chance is relatively small. Finally, please note that the repository is not being "re-oriented." The original purpose of Forge is to "make development easier, optimize resource management, speed up inference, and study experimental features." This announcement will soon bring Gradio4 and a newer memory management system, which aligns with the original purpose of Forge. Forge |
Beta Was this translation helpful? Give feedback.
-
I'm wondering if it's possible to set a scheduler selection like this on Forge |
Beta Was this translation helpful? Give feedback.
-
If it's about money, let me know what it would cost to fix the issue, I can surely donate |
Beta Was this translation helpful? Give feedback.
-
this is the reason we have been waiting for! Personally, I feel that Forge is more suitable for me compared to A1111. |
Beta Was this translation helpful? Give feedback.
-
Forge is fast, whatever magic you did in the inference pipeline is brilliant. I can run SDXL on my 1070ti. The fastest GPU I can foresee being able to get my hands on in the next few years is an 11gb 2080ti so... ultimately, a tool like Forge will still be needed for lots of people. 11GB isn't enough for SDXL on A1111. I appreciate whatever changes and work you did to this project. I'm still using Forge. I still get good inference speed with SDXL and up to 2 LORAs. I hope your changes get merged into A1111, I don't want to have to learn Comfy. It reminds me way too much of the Unreal4 Shader Editor lmao. |
Beta Was this translation helpful? Give feedback.
-
Is there a way I can switch Forge to ReForge? or do I have to install ReForge from the beginning? |
Beta Was this translation helpful? Give feedback.
-
Update July 21: Hi Forge Users, Here are some updates regarding the recent announcement:
Forge |
Beta Was this translation helpful? Give feedback.
-
Hi forge users,
Today the dev branch of upstream sd-webui has updated many progress about performance. Many previous bottlenecks should be resolved. As discussed here, we recommend a majority of users to change back to upstream webui (directly use webui dev branch or wait for the dev branch to be merged to main).
At the same time, many features of forge (like unet-patcher and modern memory management) are considered to be too costly to be implemented in the current webui’s ecosystem.
Forge will then be turned into an experimental repo to mainly test features that are costly to integrate. We will experiment with Gradio 4 and add our implementation of a local GPU version of huggingface space’ zero GPU memory management based on LRU process scheduling and pickle-based process communication in the next version of forge. This will lead to a new Tab in forge called “Forge Space” (based on Gradio 4 SDK
@spaces.GPU
namespace) and another Tab titled “LLM”.These updates are likely to break almost all extensions, and we recommend all users in production environments to change back to upstream webui for daily use.
We invite a small group of users to stay here to test Gradio 4, since feedback and extensions for Gradio 4 are also necessary for upstream’s considerations or adaptations, with regard to gradio’s recent advancement in LLM interface and streaming system, image editors and displays, and Gradio sdk’s seamless integration of zero-gpu computation management system.
Finally, we recommend forge users to backup your files right now (or just change back to upstream webui if possible). If you mistakenly updated forge without being aware of this announcement, the last commit before this announcement is 29be1da
Update June 27:
Hi Forge Users,
Here are some updates regarding the recent announcement:
There are no code changes between June 8 and today (June 27). If something is broken, it is likely due to other reasons, not this announcement.
We will provide a “download previous version” page similar to most other desktop software. If you are not an advanced Git user, please do not add, modify, or delete program files.
The “break extensions” refers to the extensions’ Gradio version. This mainly affects compatibility with A1111 extensions. For newer Forge extensions, upgrading will only require a few lines of modifications related to Gradio calls. The logical patching API will not change.
We understand your concerns and hear your feedback, but please do not misinterpret our announcements as an implication to eliminate the repository (which is false).
We recommend users to back up their files because the code base may undergo major changes in a few weeks. Right now, users do not need to do anything. If you are a professional user in a production environment, after the update happens (which will be in several weeks later), we recommend using version 29be1da (which will soon be available on a “download previous version” page) or using the upstream webui if necessary. There is also a possibility that our updates will be seamless, with no noticeable errors, but this chance is relatively small.
Finally, please note that the repository is not being "re-oriented." The original purpose of Forge is to "make development easier, optimize resource management, speed up inference, and study experimental features." This announcement will soon bring Gradio4 and a newer memory management system, which aligns with the original purpose of Forge.
Forge
Update July 21:
Hi Forge Users,
Here are some updates regarding the recent announcement:
Forge
Beta Was this translation helpful? Give feedback.
All reactions