2025-07-19: reForge development will continue (for now). #377
Replies: 25 comments 35 replies
|
For now I have done the backend changes to upstream from Comfy. Please report if you find new issues, and is highly factible with 150+ commits. |
|
Thank you for your work on reForge! It is my favorite UI for t2i work and I'm so glad to see you continuing to develop it. |
|
Seriously, thank you for your work. I feel not comfortable with ComfyUI (hah...) and your continued development of the WebUI client is such a blessing. |
|
Impresionante!! Gracias por tu enorme trabajo!! |
|
Welcome back! Still actively using reForge - it's still the best for SDXL! It allows wild combinations to produce original work - e.g. a combination of CFG++ sampler, BETA scheduler and RAUNet, or a combination of DPM++ 3M DY BETA with RAUNet and Smoothed Energy Guidance - none of these can be easily used in any other tool. |
|
Hi, I don't suppose I can get a more detailed explanation on how to update reForge? I see the command to use on the main page but I have no idea where to execute it, where to execute it, if I need to type anything else, etc. I wanna be able to update reForge without having to redownload the whole thing and I'm not experienced enough with Git or Python or even the CMD to know exactly what to do when I see it. Appreciate any help! |
|
Awesome! great to have you back |
|
Glad you are back. reForge was always one of my favourite. |
|
Yeah i understand it must be hard. Thanks for your work on reForge so far. Hope newer models like cosmos gets support sooner or later. |
|
Great to have you back. |
|
Glad to have you back! I tried to move to Comfy UI but it doesn't have an easy way to do batch count (not batch size) when dealing with scheduled tasks. It's super annoying that it doesn't even exist if you wanted to have a few separate image generation setups and you want each one to be run in order and have different image counts (again, not batch size in the empty latent image node, that generates multiple at the same time). |
|
I'm so glad you're back! First, I apologize for my poor English skills. English is not my first language. I wanted to let you know that your masterpiece has made my work much easier. I’m writing a web novel and needed illustrations, but my ability to create them myself was very limited, so reForge was a huge help in creating the initial drafts. :) My graphics card isn’t very powerful, so I didn’t have any other alternatives. Due to the lack of graphic resources, Forge also didn’t run properly. Thank you again. I found a few bugs while using it. In particular, I tried everything to fix the openpose issue in ControlNet, but nothing worked. I will post a detailed issue report about the relevant bugs soon! I'm really glad you're resuming this work. I'll keep cheering you on. |
|
Welcome back! |
|
First of all, welcome back @Panchovix and thanks for your hard work thus far (and in the future). reForge has been my go to for a while but I'm worried it's grown a bit too bloated (which could increase the difficulty in updating and the risk of breaking it) and in that sense I like what Classic is trying to do so I'm wondering if it wouldnt be better to build from Classic rather than Forge Gradio4 (Gradio4 is overrated). |
|
Maybe we could take a look at this project. The author seems to have put in a lot of effort, and I look forward to having the opportunity to collaborate. https://github.com/DenOfEquity/ersatzForge.git |
|
Hello guys, hope you're good. I will, maybe, now focus on newforge_newmain branch, which is based forge2 (gradio4, flux, etc) rather than the branches that are based on comfy backend (main, dev, dev2, experimental, gradio4-main). This is because after 1 week trying to implement new models, I think these branches have no really a way to do it without breaking other models and/or other features. So, preliminary, those branches (main, dev, dev2, experimental, gradio4-main) will have only bug fixes and not new features, while for that branch based on forge2, I will try first to port some things (like CFG++ samplers, schedulers, etc) and then some models, which looks way more feasible. For now it has added python 3.12 support, sageattention 2, sageattention 3 and flash attention. If someone is interested in forge2 but based on gradio3, I may give it a go but not sure how factible it is. Hope I explained myself correctly and sorry as well, as I think latest weeks some changes have had some issues when updating comfy to upstream. If you guys have too much issues, I can return main branch as how it was on April of this year. Any question is welcome, hope you have a good day. |
|
Welcome back, Panchovix! Thank you for your hard work and for keeping us updated. |
|
So which branch, newforge_dendev or newmain_newforge, will get the latest updates? And which one should I switch to if I want to experiment? |
|
Hi, Pancho! Is it possible to transfer "separate Text Encoder loading" to newmain_newforge branch? Also do you think --persistent-patches from forge-classic would work on your branches? Haoming02#64 Haoming02#116 and lora speedup? Haoming02#120 |
|
Does ReForge support the Qwen model? |
|
Will there be keyboard shortcuts for the gradio 4 version? The canvas in regular forge doesn't support resizing the brush with anything but the slider, which is pretty tedious |
|
Thank you for all your work. |
|
U are amazing :)!!!!! |
|
are the two branches getting merged anytime? seems frustrating having to maintain two branches. |
|
Sorry for being away guys, but I think I can't manage the time to develop on the repo as I want, I'm in a bad place (mentally) so I will un-archive it as people that want to do discussions and PRs, I will still take a look. For now newmain_newforge at least has CFG++ and the samplers of reForge, which can be used to play. Again, I'm very sorry for this and raising so much expectations, I tried not to. |
Uh oh!
There was an error while loading. Please reload this page.
Hi there guys, long time no see.
I have, for now, decided to retake reForge a little, first trying to upstream the changes of the last months up to upstream.
Then, I will try, without promises to be fair, add some features.
At the same time I will try to tackle some bugs if I can.
This probably will take a while, and maybe pushing the changes mostly to the dev branch. Just don't get too hopeful as I have to refresh a bit of my coding.
Thanks!
All reactions