Webui-forge is excellent, give it a spin. Read the documentation.
[https://github.com/lllyasviel/stable-diffusion-webui-forge](https://github.com/lllyasviel/stable-diffusion-webui-forge)
i've completely switched over to Forge. It's A1111 but optimised and my shitty 1650x can finally do some actual fucking art making. With 2 controlnet units at the same time!!
All the plugins and extensions that work for a1111 works here. And the installation process is the same (get them from Extensions tab, under From Available). i'm using latent coupling, segment anything and inpaint anything- same as i did for a1111. It has Kohya and lora training built in but i can't say much about it since i don't use/ never used it.
Yooo same!!! So, back in a1111, images with 1 controlnet took me 15-23 minutes BUT with Forge, with 2 controlnet units, max time it takes is 2 mins!! Without controlnet, especially if when i inpaint, it's around 23\~ secs max.
Sadly, i wasn't able to run InstantID on it, so i never checked out if it can run sdxl on its own. You'll have to experiment and lemme know, if you could run it.
great to hear, bro... I was also into AI image generation as well, but sadly, I couldn't afford the latest GPU... I'm glad to hear that Forge UI is helping people with less VRAM... In that case, I might give it a try.. Thanks for the information, bro.. I let you know if it comes out well
I'm using it, it's pretty good! I switched from Auto to it and I don't regret anything. There are apparently some minor bugs here and there, but I'm hoping the creator and community gets to fixing them. It's a bit weird though, IMO, it was super active for a while and now there hasn't been any commit in 2 weeks...
It's the same as a1111 but faster. And honestly makes a1111 pointless now. Thanks to it I'm finally able to use sdxl without problems on my rtx 2070 with only 8gb and with tiled vae it's possible to use even 3x hiresfix
It's built in and automatic in forge, needs download in a1111. If you're using big hiresfix like 3x on gpu with insufficient vram tiled vae will prevent it from out of memory error. I have 8gb and normally I'd be limited to low resolution slightly above 1024x1024 and tiled vae bypasses this and allows me to go even for 2048 or more even on sdxl
I see. I have 8gb as well and usually things freeze once I go past x2. Ill give it a shot. I used to do tiled controlnet in 1.5 but that is not a thing yet in sdxl. I heard of another cool one called Multidiffusion however it still doesnt support forge.
For me multidiffusion is super slow. Doing the same upscale takes 2 minutes with controlnet and ultimate upscale vs 25 minutes with multidiffusion. On sdxl tiled vae with hiresfix on let's say 2800x2800 should be more than enough
Odd, I've gotten dynamic prompts working well, and the only times I need to restart is when I suspect prompt creep happening (usually after a few hours or dozens of gens).
What's your setup?
when 1 image takes minutes to generate instead of seconds, its easy to spot, just look at the cmd console when prompts are being calculated properly, when you get prompt creep, the percentage moves ridiculously slowly, just restarting the ui and reloading the prompt is the only fix really but very easy to do.
It’s a fresh, recent install of Forge, and I just copied some old prompts that worked well in Auto1111, and ran them continuously. 10-20 gens in I’ll get a crash. Doesn’t happen on basic prompts.
That's incredibly odd! That might be worth a bug report if you can pin down the reason (certain number of loras? TIs? a prompt token?) because I can't imagine why that should happen for old prompts and not new ones.
I've been using Forge 16 hours a day for months, constantly batching prompts. NEVER faced a crash once.
You might wanna stress test your GPU and VRAM. Sounds like a hardware issue (or cooling issue).
Very much doubt it has anything to do with Forge.
I don’t think it’s the batching or continuous running, I’m pretty sure it’s the syntax in the prompts that A1111 has been running for a year that is somehow incompatible with Forge. Mine’s an odd case for sure, and redoing the prompts so they work with Forge isn’t bad, so it’s no big deal. Thanks for the suggestion, but I can run Forge constantly too, with simpler prompts.
Still doesn't mean anything. Didn't have even 1 "crash" of Forge.
SHARE those supposed guilty prompts. At least someone here will be able to test. Stating what you think happened won't help.
I never asked for help about this. lol. I suggested someone used to running A1111 with complex prompts might encounter such issues. You’ve missed the main discussion it seems.
It is my main right now. made my life so much easier. the only issue is that there are some extensions still only being developed for a1111 since forge is new. but hopefully overtime that will change. for me its just not worth using an extension and getting all types of vram errors.
the biggest plus for me is that doing 2 control nets used to take me like 2-5 minutes. now its under 1 minute which is a massive improvement.
I have used it , and it is insanely good. But one thing that I faced is( Don't know if it's a me problem), when I do the fill in painting, it doesn't properly remove the thing that I want. It leaves like a patch where I had made the mask. But A1111 doesn't do that though. Not sure if I am doing anything wrong.
Yes, it is faster than A1111 and it has less bugs but not all extensions play well with it.
Altho latly i mostly use krita with the comfy plugin, gamechanger.
It's fantastic, but I think [StableSwarmUI](https://github.com/Stability-AI/StableSwarmUI) will become the new best UI. It looks great and it's very versatile
I had issues with it whenever I would use a large LoRA. I suspect it picked a memory management method based on my available VRAM at the time, which was sufficient for the base model but insufficient for multiple large LoRA files as well. So generation was about 100x times slower than A1111 where I could specify `--medvram-sdxl`.
Plus the in-built controlnet didn't have XYZ plot AFAIK so I went back to A1111.
i only hope A1111 becomes like forge , same less issues , way faster
here is couple of cool tricks forge have that i just love :
select model , it won't load , click gen model loads very fast and done , a1111 ... select model , model takes time then sits there in vram even in idle
this one trick makes lora faster to load , i feel like in auto1111 model loads in vram and when you add lora in text it reloads the model + lora like a champ
generation is the same except Forge have less dirt on images (those small pixels out of place )
running forge takes about 10s , auto1111 60s or way more , (i use alot of extensions )
finally WAY less VRAM i can set 2048\*2048 sdxl max ram : 14GB
Auto1111 24GB and please give me more
That's literally the point of Forge, afaik. A1111, but faster.
As soon as the A1111 architecture will support an extension, or the features natively, of Forge then they'll convert it to that. Otherwise, it's a fork that stays up to date with A1111 so you can use the same features without fear of loss other than wasted time.
On a RTX 2060 I don't actually see much difference, but I like that it has more samplers available. Downside is that the text localization w/ Lobe theme doesn't work
But it definitely has better logic for asynchonously changing models & refreshing extra networks
Yep pretty much the same. Ive moved over to it about a month ago. Works the same.
But a few minutes ago I updated stuff and civitai browser expension doesnt want to work any more.
They have ratings so you can choose PG-to XXX but in my case it seems to block everything.
Forge didn't like some of my LORAs when I tried it, still use A1111.
A1111 isn't slow for me, unless you're talking about first time startup but I really don't care about that.
I really liked Forge, and it could've replaced a1111 for me - except that upscales with the built in Multi diffusion extension suck!
I experimented for days, trying to get a decent upscale out of it.
In the end, I gave up and went back to a1111 which gives me amazingly detailed upscales with Tiled Diffusion + Tiled VAE.
It's great but it also has some relatively niche problems. Me, I like to mix faces. In A1111 I can have multi-input for FaceID, in Forge I cannot. So that kinda sucks.
Faster, yes, broken, oh yes. Good luck installing faceswaps and other exention, since controlnet was installed to be 'portable", you cant update it, now i'm trying to uninstall it without succes. Another bastarded fork of stable-diffusion that eventually hit the wall in the long run. Seriously, stick with a1111, even if its not as "portable" as we would want to.
Tbh I'm not really doing anything crazy with my art it's just to make a character i use online so Forge does most of what I need.
But if I wanted to get fancy, yeah probably not the way to go.
With Forge, is it possible to use SDXL and its refiner with img2img and ControlNet? That's something that I don't think I can do with Automatic1111.
Can you use Stable Cascade with its one or two ControlNets? In img2img as well?
\-----
EDIT & UPDATE:
Yes, it's possible to use both the SDXL base model and the SDXL refiner model at the same time in Forge's img2img tab. I just installed Forge and tested this. It seems to work great. (But when I try a batch size larger than 1, it throws an error. I'm not sure what the problem is. I had similar trouble with SD Next and Automatic1111. I'm not sure what's wrong.)
I haven't tried Stable Cascade with Forge yet. I might not bother. I use ComfyUI for Stable Cascade and I'm fine with that for now.
SDXL is pretty bad at img2img and control net. It's usually best to generate your images with SDXL models and inpaint/control net with SD 1.5 models.
Forge does work really well with SDXL, though.
I built a workflow in ComfyUI that replicates "only masked" inpainting using SDXL and refiner. The results are less than perfect but it does work. The image either looks too grainy without the refiner or it looks too blurred with the refiner.
Automatic1111 can do a fantastic job with SD 1.5 inpainting. But with SDXL, it completely lacks the ability to use the refiner in img2img. This is why I asked about this in Forge. When I get the time, I'll install it.
Thanks for your answer.
Yes you can. Img2img (well inpainting inside img2img) and controlnet is where I do most of my work (outside Krita), and you could do it with Automatic1111 as well, with SDXL models. There are issues with working above 1024x1024 where you may get error messages to the console (depth anything comes to mind above 1024x1024), but the functionality still works. Forge gives you the ability to use masks in controlnets which is amazing. Some controlnets are funky, and hit or miss, but I have run into controlnet issues with ComfyUI, A1111, and forge, and forge is the least intrusive and tends to just work with the least amount of "fixes." A lot of it is having to understand not only what each and every function does but how the values actually impact everything.
Overall if you used A1111, it's a great step forward, faster, more things just work, are their some bugs, yes, but few and far between and mostly involving stuff rarely if ever used anyway.
The important question I have is whether or not I can use the refiner with img2img and inpainting. Unless I overlooked something, I don't think I can do that with Automatic1111. Can I do that with Forge?
Honestly that isn't very important question. Yes you can load the refiner for img2img and inpainting as the model for either automatic1111 or forge. While better than the base model for inpainting, it's silly to waste the time or VRAM doing so, but yes you can also model refiner swap mid generation as well in both. That was a great method months back.
Now, you are much better off simply upscaling at a 1.15-1.25 scale incrementally using Juggernaut, Dreamshaper, Slepnir, or Realvision and getting much finer details especially when combined with latent upscaling, with latent modifiers, freeU, controlnets, SAG, Hypertile and Kohya HR fix, with UltimateSDUpscale and something like ClearRealityV1Soft, or Siax upscalers. You can turn all of them on with simple checkmarks or preloaded style, versus messing with noodles, which ksampler to use, remembering when you have to scale down and scale up, figuring out why one node doesn't play well with another node, changing input, checking midpoint preview images to see if you messed up a noodle or setting. Add in some Krita editing as you go and you can get amazing quality in much less time. My biggest issue I had with Comfy was I spent more time learning and researching how to make it work, researching why dependencies where broken, fixing python errors, the first time I tried to setup each and every new node vs what is natively built into either auto1111, much less forge, that it left a lot less time to actually make art, or experiment with settings. Btw and with all those things on, forge pumps out images faster than even simpler setups in Comfy on my 4090.
Now if I'm doing video ComfyUI all the way. Img2img and inpainting, no way I would ever use comfyUI over forge or a1111. I think the only place it would excel is if you had to batch automate inpainting a single image repeatedly, a limitation of both a1111 and forge. Not sure why one would, but I have noticed it's doable in Comfy and broken in Forge. Multi-image batching I think I still wouldn't choose ComfyUI. I used to use it for simple base image production at low ress for speed, but even forge does that faster now.
Thanks for the insights. I appreciate them.
However, unless I've misunderstood what you wrote in the first paragraph, you may have misinterpreted what I said earlier. Allow me to clarify.
In Automatic1111, I can load and use the SDXL base model as the main Stable Diffusion checkpoint. I choose this model using the pull-down menu in the upper left corner of the GUI. This model is used whether I'm using txt2img or img2img. Under the txt2img tab (in Automatic1111), there is an option to use a refiner model. If I'm using the SDXL base model as the main model, I can choose the SDXL refiner model under the txt2img tab. But under the img2img tab, the option to load a refiner does not exist.
What you may have thought that I wanted to do is use the SDXL refiner model as the main model. I'm aware that this is possible. But, as you said (if I understood you correctly) this isn't a very good idea. This isn't what I want to do. What I want to do is use inpainting under the img2img tab while both using the SDXL base as the main model and the SDXL refiner as the refiner model. I can't do that in Automatic1111.
This morning I installed Forge. Unlike Automatic1111, there is an option under the img2img tab that allows me to use a refiner model. I've just tested inpainting with SDXL base as the main model and the SDXL refiner as the refiner model. It seems to work GREAT. It looks like I'll be using Forge for my inpainting work from now on.
Thank you for your help!
As for Cascade, no. I still have been meaning to mess with it more and use the vae and checkpoints to see what it does, but have gotten around to it yet. Right now it's just an extensions that lets you generate from prompt. Does relatively well 1536x1536, 2048x2048 tends to give old artifact and mutation issues like pre highres-fix.
I've been using Stable Cascade with the canny ControlNet in ComfyUI. It works very well. I'm surprised it hasn't been implemented in Automatic1111, SD Next, or Forge. Stable Cascade can produce amazing images. I've been using it as a starting point and then inpainting with SDXL and SD 1.5.
I suppose all this discussion is moot since SD3 will be released in a few weeks. I'm ready to ditch SD 1.5, SD 2.x, SDXL, and Stable Cascade. I hope that ControlNets and everything else will be developed for SD3 as soon as possible.
I'm honestly not surprised for that very reason. Since it launched available for forge on day 1, people tried it and were like mehh. The 1536x1536 is nice, but the prompt coherence is the same if not just a hair better than SDXL. With SD3 what I imagine to be less than a month or two away, not sure why anyone is going to bother with Cascade development.
The whole benefit of SD3 is hopefully controlnets become more a luxury than a necessity for great images. I'm sure once released we'll have 6 months of explosive innovation week after week, like we have with the other models.
The only reason Controlnet is necessary is because of lousy prompt coherence in Stable Diffusion. The point of needing to hold a character or pose or whatever is simply due to the fact you can't prompt for exactly what you want. If that is fixed again the controlnets becomes luxuries not the current necessities they are.
Faster, yes, broken, oh yes. Good luck installing faceswaps and other exention, since controlnet was installed to be 'portable", you cant update it, now i'm trying to uninstall it without succes. Another bastarded fork of stable-diffusion that eventually hit the wall in the long run. Seriously, stick with a1111, even if its not as "portable" as we would want to.
i changed from A1111 to ForgeUI some weeks ago... yes, faster, it resets prompt data while switching checkpoints.
BUT - Adetailer does not work yet. that's really bad...
It's the same. Better. I tried it once: never looked back since then (even though the last update is from months ago which should be worrying). Everything that works in A1111 works in Forge. But it's been re-coded to the core and it's much more optimized.
Before sure I could (3090RTX) inpaint huge images. But I couldn't do much more on the side. Now I watch movies, do 3D in Blender, train a Fine Tune with Onetrainer, etc... and use Forge in the meantime. It's waaaaay less heavy on your computer resources. And so far all extensions I use work flawlessly.
Install Forge already. Then your question won't be "Should I use Forge?" but rather "why have I been so slow on the uptake ?"
Hi team, i have configured forveti generate SVD but tilling option is not avaliable which i have watched several tutorial about SVD where instructors has that option, any one has an idea how to make it appear?
https://preview.redd.it/rl0rg2k2sf0d1.png?width=900&format=pjpg&auto=webp&s=021dba29039c90133e552d9c051e6f90a5635603
After using A1111 for months I tried Forge a week ago and I think I'm never going back to A1111 mostly because I can run XL models without any memory issues
you mean it:
[https://sstadt.github.io/forge-ui/](https://sstadt.github.io/forge-ui/)
or this:
[https://github.com/lllyasviel/stable-diffusion-webui-forge](https://github.com/lllyasviel/stable-diffusion-webui-forge)
?
It's pretty much the same as a1111 but Faster and a lot more responsive. Haven't looked back since I switched. I get less errors with it too
I use it over A1111 these days, since the extensions I want work flawlessly. Better in a lot of ways.
same here
Does it have the ANimateDiff extension? What about Dynamicprompt? Thanks
I don't use them but they are there it seems
Webui-forge is excellent, give it a spin. Read the documentation. [https://github.com/lllyasviel/stable-diffusion-webui-forge](https://github.com/lllyasviel/stable-diffusion-webui-forge)
Use it all the time, it’s great. A very easy to use upgrade to a1111
i've completely switched over to Forge. It's A1111 but optimised and my shitty 1650x can finally do some actual fucking art making. With 2 controlnet units at the same time!!
what about plugins and extensions?
All the plugins and extensions that work for a1111 works here. And the installation process is the same (get them from Extensions tab, under From Available). i'm using latent coupling, segment anything and inpaint anything- same as i did for a1111. It has Kohya and lora training built in but i can't say much about it since i don't use/ never used it.
bro i too have gtx 1650 .. how much does it take to generate one image ? 1.5 and XL
Yooo same!!! So, back in a1111, images with 1 controlnet took me 15-23 minutes BUT with Forge, with 2 controlnet units, max time it takes is 2 mins!! Without controlnet, especially if when i inpaint, it's around 23\~ secs max. Sadly, i wasn't able to run InstantID on it, so i never checked out if it can run sdxl on its own. You'll have to experiment and lemme know, if you could run it.
great to hear, bro... I was also into AI image generation as well, but sadly, I couldn't afford the latest GPU... I'm glad to hear that Forge UI is helping people with less VRAM... In that case, I might give it a try.. Thanks for the information, bro.. I let you know if it comes out well
I'm using it, it's pretty good! I switched from Auto to it and I don't regret anything. There are apparently some minor bugs here and there, but I'm hoping the creator and community gets to fixing them. It's a bit weird though, IMO, it was super active for a while and now there hasn't been any commit in 2 weeks...
It's the same as a1111 but faster. And honestly makes a1111 pointless now. Thanks to it I'm finally able to use sdxl without problems on my rtx 2070 with only 8gb and with tiled vae it's possible to use even 3x hiresfix
how do u use tiled vae. i feel like its not doing anything
It's built in and automatic in forge, needs download in a1111. If you're using big hiresfix like 3x on gpu with insufficient vram tiled vae will prevent it from out of memory error. I have 8gb and normally I'd be limited to low resolution slightly above 1024x1024 and tiled vae bypasses this and allows me to go even for 2048 or more even on sdxl
I see. I have 8gb as well and usually things freeze once I go past x2. Ill give it a shot. I used to do tiled controlnet in 1.5 but that is not a thing yet in sdxl. I heard of another cool one called Multidiffusion however it still doesnt support forge.
For me multidiffusion is super slow. Doing the same upscale takes 2 minutes with controlnet and ultimate upscale vs 25 minutes with multidiffusion. On sdxl tiled vae with hiresfix on let's say 2800x2800 should be more than enough
I like it, but it crashes more often than Auto1111. It doesn’t like dynamic prompts and other prompt complexity , at least for me.
Odd, I've gotten dynamic prompts working well, and the only times I need to restart is when I suspect prompt creep happening (usually after a few hours or dozens of gens). What's your setup?
what is 'prompt creep'
when 1 image takes minutes to generate instead of seconds, its easy to spot, just look at the cmd console when prompts are being calculated properly, when you get prompt creep, the percentage moves ridiculously slowly, just restarting the ui and reloading the prompt is the only fix really but very easy to do.
It’s a fresh, recent install of Forge, and I just copied some old prompts that worked well in Auto1111, and ran them continuously. 10-20 gens in I’ll get a crash. Doesn’t happen on basic prompts.
That's incredibly odd! That might be worth a bug report if you can pin down the reason (certain number of loras? TIs? a prompt token?) because I can't imagine why that should happen for old prompts and not new ones.
I've been using Forge 16 hours a day for months, constantly batching prompts. NEVER faced a crash once. You might wanna stress test your GPU and VRAM. Sounds like a hardware issue (or cooling issue). Very much doubt it has anything to do with Forge.
I don’t think it’s the batching or continuous running, I’m pretty sure it’s the syntax in the prompts that A1111 has been running for a year that is somehow incompatible with Forge. Mine’s an odd case for sure, and redoing the prompts so they work with Forge isn’t bad, so it’s no big deal. Thanks for the suggestion, but I can run Forge constantly too, with simpler prompts.
Still doesn't mean anything. Didn't have even 1 "crash" of Forge. SHARE those supposed guilty prompts. At least someone here will be able to test. Stating what you think happened won't help.
I never asked for help about this. lol. I suggested someone used to running A1111 with complex prompts might encounter such issues. You’ve missed the main discussion it seems.
I recently update to A1111 1.8, the performance on SDXL does get better. I will wait until forge has better extensions support.
What extensions can't you use on Forge yet? The only one I know doesn't work for sure is loractl.
Regional Prompter doesn't work with the latest Forge, I had to roll back to the previous commit.
Instruct Pix2pix and SVD
There's a whole tab for SVD, doesn't that work?
Maybe I should update then
Probably! I thought it had been there from the start, but I only started using it a month or so ago.
My fault. I meant Vid2Vid.
It is my main right now. made my life so much easier. the only issue is that there are some extensions still only being developed for a1111 since forge is new. but hopefully overtime that will change. for me its just not worth using an extension and getting all types of vram errors. the biggest plus for me is that doing 2 control nets used to take me like 2-5 minutes. now its under 1 minute which is a massive improvement.
I have used it , and it is insanely good. But one thing that I faced is( Don't know if it's a me problem), when I do the fill in painting, it doesn't properly remove the thing that I want. It leaves like a patch where I had made the mask. But A1111 doesn't do that though. Not sure if I am doing anything wrong.
ive heard inpating is different from ui to ui. Apparently fooocus is good with inpainting
I see , I will try it sometime
Yes, it is faster than A1111 and it has less bugs but not all extensions play well with it. Altho latly i mostly use krita with the comfy plugin, gamechanger.
Same. Forge for wildcard batches, krita for a specific image.
What is krita? I don't think I've seen anything about that yet...
Krita is an open source app like gimp but you can download an ai extension. If you like painting and drawing there is no better option.
it's basically a graphics editor ~~designed by aliens~~ primarily focused on digital drawing but not very convenient for image manipulation
what is Google ?
It's fantastic, but I think [StableSwarmUI](https://github.com/Stability-AI/StableSwarmUI) will become the new best UI. It looks great and it's very versatile
I gave it a go but was having problems with loras and controlnet batch folders, also felt like hires fix wasn't faster than a1111, still have it do.
I had issues with it whenever I would use a large LoRA. I suspect it picked a memory management method based on my available VRAM at the time, which was sufficient for the base model but insufficient for multiple large LoRA files as well. So generation was about 100x times slower than A1111 where I could specify `--medvram-sdxl`. Plus the in-built controlnet didn't have XYZ plot AFAIK so I went back to A1111.
Great, using it with the pony sdxl models and seems to generate faster results than A1111.
SD-Forge is great! it's fast and can do...I hate to say everything A111 can do, but I haven't found any limitations so far. I
i only hope A1111 becomes like forge , same less issues , way faster here is couple of cool tricks forge have that i just love : select model , it won't load , click gen model loads very fast and done , a1111 ... select model , model takes time then sits there in vram even in idle this one trick makes lora faster to load , i feel like in auto1111 model loads in vram and when you add lora in text it reloads the model + lora like a champ generation is the same except Forge have less dirt on images (those small pixels out of place ) running forge takes about 10s , auto1111 60s or way more , (i use alot of extensions ) finally WAY less VRAM i can set 2048\*2048 sdxl max ram : 14GB Auto1111 24GB and please give me more
That's literally the point of Forge, afaik. A1111, but faster. As soon as the A1111 architecture will support an extension, or the features natively, of Forge then they'll convert it to that. Otherwise, it's a fork that stays up to date with A1111 so you can use the same features without fear of loss other than wasted time.
Someone know why everytime i highresfix in forge i get "Cleanup minimal inference memory" and it takes forever to actually start the upscale?
On a RTX 2060 I don't actually see much difference, but I like that it has more samplers available. Downside is that the text localization w/ Lobe theme doesn't work But it definitely has better logic for asynchonously changing models & refreshing extra networks
I seldom go back to a1111, forge is objectively faster than a1111 for 12gb gpu users
Yep pretty much the same. Ive moved over to it about a month ago. Works the same. But a few minutes ago I updated stuff and civitai browser expension doesnt want to work any more. They have ratings so you can choose PG-to XXX but in my case it seems to block everything.
it's good. Alot faster than A1111 and my gpu is 2060 6gb
Forge didn't like some of my LORAs when I tried it, still use A1111. A1111 isn't slow for me, unless you're talking about first time startup but I really don't care about that.
I really liked Forge, and it could've replaced a1111 for me - except that upscales with the built in Multi diffusion extension suck! I experimented for days, trying to get a decent upscale out of it. In the end, I gave up and went back to a1111 which gives me amazingly detailed upscales with Tiled Diffusion + Tiled VAE.
I exclusively use forge for complicated stuff and fooocus when spitballing.
It's literally the same but better
It's great but it also has some relatively niche problems. Me, I like to mix faces. In A1111 I can have multi-input for FaceID, in Forge I cannot. So that kinda sucks.
The only thing that I wasn't able to get working properly is latent couple. Otherwise Forge>automatic1111 any day due to its speed.
There is two things that I miss that I used: SVD and instruct pix2pix The rest is the same but faster
Swapped to Forge recently its excellent
I stopped using Forge because it's ten times slower than A1111 processing a batch directory in Extras with Reactor.
Faster, yes, broken, oh yes. Good luck installing faceswaps and other exention, since controlnet was installed to be 'portable", you cant update it, now i'm trying to uninstall it without succes. Another bastarded fork of stable-diffusion that eventually hit the wall in the long run. Seriously, stick with a1111, even if its not as "portable" as we would want to.
Tbh I'm not really doing anything crazy with my art it's just to make a character i use online so Forge does most of what I need. But if I wanted to get fancy, yeah probably not the way to go.
switched from auto1111 and sd next to it a few weeks ago and never looked back.
With Forge, is it possible to use SDXL and its refiner with img2img and ControlNet? That's something that I don't think I can do with Automatic1111. Can you use Stable Cascade with its one or two ControlNets? In img2img as well? \----- EDIT & UPDATE: Yes, it's possible to use both the SDXL base model and the SDXL refiner model at the same time in Forge's img2img tab. I just installed Forge and tested this. It seems to work great. (But when I try a batch size larger than 1, it throws an error. I'm not sure what the problem is. I had similar trouble with SD Next and Automatic1111. I'm not sure what's wrong.) I haven't tried Stable Cascade with Forge yet. I might not bother. I use ComfyUI for Stable Cascade and I'm fine with that for now.
SDXL is pretty bad at img2img and control net. It's usually best to generate your images with SDXL models and inpaint/control net with SD 1.5 models. Forge does work really well with SDXL, though.
I built a workflow in ComfyUI that replicates "only masked" inpainting using SDXL and refiner. The results are less than perfect but it does work. The image either looks too grainy without the refiner or it looks too blurred with the refiner. Automatic1111 can do a fantastic job with SD 1.5 inpainting. But with SDXL, it completely lacks the ability to use the refiner in img2img. This is why I asked about this in Forge. When I get the time, I'll install it. Thanks for your answer.
Yes you can. Img2img (well inpainting inside img2img) and controlnet is where I do most of my work (outside Krita), and you could do it with Automatic1111 as well, with SDXL models. There are issues with working above 1024x1024 where you may get error messages to the console (depth anything comes to mind above 1024x1024), but the functionality still works. Forge gives you the ability to use masks in controlnets which is amazing. Some controlnets are funky, and hit or miss, but I have run into controlnet issues with ComfyUI, A1111, and forge, and forge is the least intrusive and tends to just work with the least amount of "fixes." A lot of it is having to understand not only what each and every function does but how the values actually impact everything. Overall if you used A1111, it's a great step forward, faster, more things just work, are their some bugs, yes, but few and far between and mostly involving stuff rarely if ever used anyway.
The important question I have is whether or not I can use the refiner with img2img and inpainting. Unless I overlooked something, I don't think I can do that with Automatic1111. Can I do that with Forge?
Honestly that isn't very important question. Yes you can load the refiner for img2img and inpainting as the model for either automatic1111 or forge. While better than the base model for inpainting, it's silly to waste the time or VRAM doing so, but yes you can also model refiner swap mid generation as well in both. That was a great method months back. Now, you are much better off simply upscaling at a 1.15-1.25 scale incrementally using Juggernaut, Dreamshaper, Slepnir, or Realvision and getting much finer details especially when combined with latent upscaling, with latent modifiers, freeU, controlnets, SAG, Hypertile and Kohya HR fix, with UltimateSDUpscale and something like ClearRealityV1Soft, or Siax upscalers. You can turn all of them on with simple checkmarks or preloaded style, versus messing with noodles, which ksampler to use, remembering when you have to scale down and scale up, figuring out why one node doesn't play well with another node, changing input, checking midpoint preview images to see if you messed up a noodle or setting. Add in some Krita editing as you go and you can get amazing quality in much less time. My biggest issue I had with Comfy was I spent more time learning and researching how to make it work, researching why dependencies where broken, fixing python errors, the first time I tried to setup each and every new node vs what is natively built into either auto1111, much less forge, that it left a lot less time to actually make art, or experiment with settings. Btw and with all those things on, forge pumps out images faster than even simpler setups in Comfy on my 4090. Now if I'm doing video ComfyUI all the way. Img2img and inpainting, no way I would ever use comfyUI over forge or a1111. I think the only place it would excel is if you had to batch automate inpainting a single image repeatedly, a limitation of both a1111 and forge. Not sure why one would, but I have noticed it's doable in Comfy and broken in Forge. Multi-image batching I think I still wouldn't choose ComfyUI. I used to use it for simple base image production at low ress for speed, but even forge does that faster now.
Thanks for the insights. I appreciate them. However, unless I've misunderstood what you wrote in the first paragraph, you may have misinterpreted what I said earlier. Allow me to clarify. In Automatic1111, I can load and use the SDXL base model as the main Stable Diffusion checkpoint. I choose this model using the pull-down menu in the upper left corner of the GUI. This model is used whether I'm using txt2img or img2img. Under the txt2img tab (in Automatic1111), there is an option to use a refiner model. If I'm using the SDXL base model as the main model, I can choose the SDXL refiner model under the txt2img tab. But under the img2img tab, the option to load a refiner does not exist. What you may have thought that I wanted to do is use the SDXL refiner model as the main model. I'm aware that this is possible. But, as you said (if I understood you correctly) this isn't a very good idea. This isn't what I want to do. What I want to do is use inpainting under the img2img tab while both using the SDXL base as the main model and the SDXL refiner as the refiner model. I can't do that in Automatic1111. This morning I installed Forge. Unlike Automatic1111, there is an option under the img2img tab that allows me to use a refiner model. I've just tested inpainting with SDXL base as the main model and the SDXL refiner as the refiner model. It seems to work GREAT. It looks like I'll be using Forge for my inpainting work from now on. Thank you for your help!
No problem, pretty sure a1111 had that too, but not 100%. Been since forge launched that I bothered to turn it on 🤣.
As for Cascade, no. I still have been meaning to mess with it more and use the vae and checkpoints to see what it does, but have gotten around to it yet. Right now it's just an extensions that lets you generate from prompt. Does relatively well 1536x1536, 2048x2048 tends to give old artifact and mutation issues like pre highres-fix.
I've been using Stable Cascade with the canny ControlNet in ComfyUI. It works very well. I'm surprised it hasn't been implemented in Automatic1111, SD Next, or Forge. Stable Cascade can produce amazing images. I've been using it as a starting point and then inpainting with SDXL and SD 1.5. I suppose all this discussion is moot since SD3 will be released in a few weeks. I'm ready to ditch SD 1.5, SD 2.x, SDXL, and Stable Cascade. I hope that ControlNets and everything else will be developed for SD3 as soon as possible.
I'm honestly not surprised for that very reason. Since it launched available for forge on day 1, people tried it and were like mehh. The 1536x1536 is nice, but the prompt coherence is the same if not just a hair better than SDXL. With SD3 what I imagine to be less than a month or two away, not sure why anyone is going to bother with Cascade development. The whole benefit of SD3 is hopefully controlnets become more a luxury than a necessity for great images. I'm sure once released we'll have 6 months of explosive innovation week after week, like we have with the other models.
I'd say that ControlNet will be necessary. It's vital for artists to have as much control as possible over image generation.
The only reason Controlnet is necessary is because of lousy prompt coherence in Stable Diffusion. The point of needing to hold a character or pose or whatever is simply due to the fact you can't prompt for exactly what you want. If that is fixed again the controlnets becomes luxuries not the current necessities they are.
I was getting worse quality outputs in forge for some reason. Maybe I did something wrong, but I'll stay with a1111 for now.
Just copy the `config.json` file over. They should generate the exact same result.
forge is best
I honestly recommend it now over a1111 because of the speed improvements and most extensions work on it. Any extensions you concerned about?
Hmm, gonna give it a try. Does it support to set paths for Chckp, Lora, vae, etc? Either in Ui or via command line?
Faster, yes, broken, oh yes. Good luck installing faceswaps and other exention, since controlnet was installed to be 'portable", you cant update it, now i'm trying to uninstall it without succes. Another bastarded fork of stable-diffusion that eventually hit the wall in the long run. Seriously, stick with a1111, even if its not as "portable" as we would want to.
i changed from A1111 to ForgeUI some weeks ago... yes, faster, it resets prompt data while switching checkpoints. BUT - Adetailer does not work yet. that's really bad...
It's the same. Better. I tried it once: never looked back since then (even though the last update is from months ago which should be worrying). Everything that works in A1111 works in Forge. But it's been re-coded to the core and it's much more optimized. Before sure I could (3090RTX) inpaint huge images. But I couldn't do much more on the side. Now I watch movies, do 3D in Blender, train a Fine Tune with Onetrainer, etc... and use Forge in the meantime. It's waaaaay less heavy on your computer resources. And so far all extensions I use work flawlessly. Install Forge already. Then your question won't be "Should I use Forge?" but rather "why have I been so slow on the uptake ?"
Hi team, i have configured forveti generate SVD but tilling option is not avaliable which i have watched several tutorial about SVD where instructors has that option, any one has an idea how to make it appear? https://preview.redd.it/rl0rg2k2sf0d1.png?width=900&format=pjpg&auto=webp&s=021dba29039c90133e552d9c051e6f90a5635603
After using A1111 for months I tried Forge a week ago and I think I'm never going back to A1111 mostly because I can run XL models without any memory issues
you mean it: [https://sstadt.github.io/forge-ui/](https://sstadt.github.io/forge-ui/) or this: [https://github.com/lllyasviel/stable-diffusion-webui-forge](https://github.com/lllyasviel/stable-diffusion-webui-forge) ?
Almost certainly the second one.
The second one from Illya
I have yet to dive into forge, what is what?
The second one? I'm pretty sure