Tell us what is missing in ControlNet Integrated

[lllyasviel]

The integrated ControlNet is not updated for a while, and we are going to make it a bit more up-to-date.

However that will happen after some other newer experiments. Old features are relatively lower priority - so that we can experiment with more new ideas first.

I personally know some models like uni-controlnet (or called promax by some non-research people) and some preprocessors like DSINE/DepthAnything/etc. Those are very easy to add – after I get other things done, those only need me 1 or 2 hours to add them all.

However I will not add the below things:

1. webui's IPA multi-inputs implementation. The reason is that I find them misleading and technically wrong. One can just use multiple ControlNet Units to have similar logic. The “multi-inputs” implies some feature mixture techniques when it is not. So it is wrong and I cannot add it. (but will consider some technically correct multiple IP mixture later if flexible
2. Automatic model filtering and ipadapter preprocessor recognizing. I find those things very annoying since model filtering is somewhat bind to model load and is very laggy. Also I cannot not know from UI what are the underlying rules and how those automatic recognizing works (and if they worked after all) when I click generate.
3. All things that I find hard to understand – if I cannot quickly understand what it is then most people will not understand it.

By the way, several experiments will be implemented in a “Forge Space” (that I will add later, similar to some local HuggingFace Spaces) rather than that ControlNet extension. So many functionalities will happen elsewhere.

This post is only for controlnets. Experiments with other newer diffusion models will happen before controlnets.

Please tell us what is missing in ControlNet Integrated. Please do not talk about things that are already mentioned in this post – I will take a look several days later when I finish some other things.

---

Update Sep 1:

The rewrite of ControlNet Intergrated will start at about Sep 29 (delayed) start at about Oct 15 (delayed) start at about Oct 30 (delayed) start at about Nov 20. (When this note is announced, the main targets include some diffusers formatted Flux ControlNets and some community implementation of Union ControlNets. However, this may be extended if stronger models come out after this note.)

---

About IPAdapter:

Note that the CLIP Vision names of sd-webui-controlnet are non-standard. Forge uses correct names:

SD v.	IPadapter	Img encoder
v1.5	ip-adapter_sd15	ViT-H
v1.5	ip-adapter_sd15_light	ViT-H
v1.5	ip-adapter-plus_sd15	ViT-H
v1.5	ip-adapter-plus-face_sd15	ViT-H
v1.5	ip-adapter-full-face_sd15	ViT-H
v1.5	ip-adapter_sd15_vit-G	ViT-bigG
SDXL	ip-adapter_sdxl	ViT-bigG
SDXL	ip-adapter_sdxl_vit-h	ViT-H
SDXL	ip-adapter-plus_sdxl_vit-h	ViT-H
SDXL	ip-adapter-plus-face_sdxl_vit-h	ViT-H
v1.5	FaceID	InsightFace+CLIP-H
v1.5	FaceID Plus	InsightFace+CLIP-H
v1.5	FaceID Plus v2	InsightFace+CLIP-H
v1.5	FaceID Portrait	InsightFace+CLIP-H
SDXL	FaceID	InsightFace+CLIP-H
SDXL	FaceID Plus v2	ViT-H

[sdbds]

There are 3 new controlnet-based architectures to try:

Update in Oct 15

ctrlora
Base ControlNet along with condition-specific LoRAs on base conditions with a large-scale dataset. Then, our Base ControlNet can be efficiently adapted to novel conditions by new LoRAs with as few as 1,000 images and less than 1 hour on a single GPU.

only SD1.5 for now.

AnyControl

One input with multiple preprocessor inputs

ControlNeXt

Modified variants of some blocks that seem to perform well on SVD and SDXL.

[sdbds]

update for ctrlora

[toyxyz]

Some Ctrlora training test!

Ctrlora actually works very well with small datasets.

[reaperhammer]

Did you train new models from Ctrlora base? This looks cool if I can sketch to image with stick people!

[BNP1111]

instant id+inpaint PLZ

[LeDXIII]

First of all I want to say - thanks for the Great tool. That the previous version was very good, that the new version looks very promising (judging by commits).

Regarding controlnet.

1. Already realized implementations. I'll just walk through them briefly to avoid forgetting anything.

• Anyline.
• A set of controlnets from Xinsir. In addition to Union (which has problems in realizing openpose in Automatic), the author has Tile, which also works in the Automatic controlnet not quite as expected.
• Ip-adapter compositions.
• I would also like to see SAM (2?), lama cleaner in controlnet in preprocessors.

2. From the new stuff.

• Photomaker 2. In the demo it shows very good results on face repeatability.
• CustomNet. Not sure how good it is.
• Controlnet of SD3 and other new models.
  Thank you.

[IPv6]

A feature request: segmentation tagging control net (not yet existing)

Inputs: character in default frontal pose (photo), a segment map where segment color defines clothing region in frontal pose, a segment map with same colors but in target pose.

Desired output: ControlNet should map clothing features from default pose into target pose using color-coded segments as strict guidance. That means - without adding features not present in segment in default pose, without symmetry breaks and so on. Probably specific color channel should hint about SYMMETRY for robustness. Target pose should not be restricted to "usual poses", theoretically upside-down poses, partially occluded poses, self occlusions can be resolved just fine by such 1-1 segmentation mapping

[ali0une]

The outpaint of xinsir union-controlnet-promax ... if i could outpaint with SDXL it would be wonderful.

Kepp up the good works ...

[dongxiat]

I hopefully update controlnet will work with 2 major extension :
segment-anything
replacer
its help my job alot...and want to use with in webui-forge

btw ur works is awsome

[andupotorac]

I would like to add to this. Don't include just SAM2, but also pair it with Florence as it makes for detecting areas much better.

1. https://huggingface.co/spaces/SkalskiP/florence-sam

[jordanjay29]

The biggest need here might simply be a document outlining how Forge's built-in CN differs in options and behavior. It's not much, but the will-not-adds and the workarounds to some of those would be useful for newcomers and converts from A1111.

[AxelFar94]

First of all, Thank you for your work lllyasviel.
I would like to point out that the tile_colorfix and tile_colorfix+sharp are making the images bleed their colors in a checkered pattern, and this happens since Forge launch, here some comparisons with Auto 1111 results using low ControlNet strength:

The checkered pattern is more noticeble in very low strength:

Would be great if you could fix it! It's a great way to make images strictly follow input image colors.
Thanks!

[GeminiSquishGames]

Well, I can't get it to work in the Photoshop Plugin/Extention... that's missing for me, but probably not something that can be helped since it's pretty much not getting updates on their end. I'd probably rather have it work faster in the UI than have a poor implementation in photoshop anyway at this point. Looking forward to seeing "The Chosen One" for character consistency soon as a CN model or extension of some kind.
https://omriavrahami.com/the-chosen-one/

[Crousere]

Fooocus sdxl inpaint. Inpaint_v26.fooocus.patch never worked as well on Forge for me as it did on Foocus.

[newxhy]

Inpaint_v26.fooocus.patch 在comfyui 上的效果也不如在 Foocus 上。
The effect of Inpaint-v26.foocus.patch on comfyui is not as good as on Foocus.

[andupotorac]

1. For Depth, I think it's best to look at https://depthfm.github.io/. Seems better than even Marigold.

2. Hand and feet fixing. For hands there are several approaches, and I believe the same algos could work on feet also. I'm not too technical to know, but I posted some of those data here: Can this be used for feet too, with datasets like FOOT3D and FIND? agnJason/XHand#2.

For hands you also have:
https://github.com/wenquanlu/HandRefiner

And this is looking interesting as well:
https://github.com/adventurer-w/ClickDiff

I've seen people add manual images to OpenPose, but ClickDiff does it automatically, and the other do too. Would be great if we can finally fix hands and feet with ControlNet.

3. There are some options you could add on the models to make them more robust:

• https://shariqfarooq123.github.io/loose-control/ (more flexibility for shapes)
• https://github.com/liuxiaoyu1104/SmartControl (takes context into account for better generations)
• https://github.com/open-mmlab/AnyControl (like multicontrol net, but better quality)

4. Would be nice to integrate LivePortrait (for humans and animals too) so we can have a ControlNet for emotions. :)

[softtaco1]

1.) SDXL / Pony inpainting would be amazing.

2.) A custom ControlNet which utilizes either photos or prompts to transfer outfits/clothing onto a generation. This could maybe be enhanced by utilizing layerdiffuse to overlay it correctly upon the subject through multiple passes. (Idea, not sure if could be implemented)

3.) I don't know if this is possible either, but instead of something like regional prompter or Forge Couple, creating a controlnet that instead recognizes separate individual characters interacting. I know there are things similar to this that exist, but they aren't quite what I'm looking for to generate multiple characters interacting easily while maintaining a level of versatility and not being constrained to one specific pose via OpenPose. If this idea is at all possible, a controlnet model could utilize a reference image to apply an interaction/action between multiple characters. Or instead of a reference image, it could utilize a syntax similar to Forge Couple's "NEWLINE" , but instead of generating in a new space of the 2d plane, applies character adherence to subject(s) in the scene. Then, an action could be specified, detailing how these characters are interacting. Basically, a prompt adherence helper for models that struggle with prompt adherence, especially as it relates to characteristics of specific individuals in a scene.

Example:
A dark cave
NEWCHAR A frightened middle-aged man, yellow poncho, soaking wet, holding a lantern
NEWCHAR An eldritch horror monster, devilish grin, glowing eyes.
ACTION Fighting

Again, not sure if this is even possible without a multimodal model, but I think it would be more useful to have something that helps ensure characters look a certain way than it is to make sure they are in a specific place/pose (most of the time.)

[pflky]

For me, what's missing is

1. Union ProMax model support
2. Dsine preprocessor support in Forge (most of the time it's better than all the other preprocessors, including depth and canny)

2a. Dsine on independent controlnet for A1111 has a bug that if you use a different resolution/ratio than the image, the preprocessor will generate zoomed into the image rather than crop or resize. Its been a bug since the release of Dsine as a preprocessor. This happens regardless of settings. You essentially have to format images to be the same exact resolution and ratio as the preprocessor settings, otherwise it zooms in, which can be a pain if you're working with images of mixed resolutions.

2b. Propose a feature based on the last problem: A new feature that allows people to use a draggable and resizable selector box over the controlnet image to determine the focus area of the preprocessor. I'd imagine this would also be useful for other controlnet preprocessors too, as you can then take any part of any image and make it the focus of the preprocessor on the fly. So for example, you drag a 1:1 ratio box overlay on the image, have it be resizable, and then it'll use the inputted resolution, even if the image itself is smaller; So you could zoom into a face on a 512x512 image and make just the face area preprocess at 1024x1024. Simple and versatile way of handling controlnet inputs of varying resolutions and aspect ratios and fills the gap that "just resize" and "crop and resize" doesn't cover.

3. Photomaker V2 support (faceid model)
4. DepthAnything V2 support (this outperforms marigold)
5. With the advent of Union models, the overhead for using multiple controlnet preprocessors should be smaller, because you should only need to load one model for multiple control units. I don't know if this is the current behavior, but if not, then if the same model is selected across different units, it should only be loaded into memory once.
6. There is a newer lineart preprocessor called "Anyline", which seems to create better preprocessing for lineart models. https://github.com/TheMistoAI/ComfyUI-Anyline
7. The ability to use extensions that rely on A1111 non-built-in controlnet (if possible). Some of these support things that Forge controlnet does not, like DepthAnything V2 for example. So, some kind of scheme that allows extensions that call on A1111 controlnet, to play nicely with Forge controlnet. It's really one of the only reasons I keep going back to main A1111. Forge has the memory management enhancements, but a lot of stuff gets made for A1111 that doesn't play well with Forge's built-in controlnet. So if it's possible to make things that call on A1111 controlnet to convert to use the built-in controlnet in Forge, that could solve a lot of problems and overhead, including having to go through the trouble of supporting certain new models.
8. "Contrast" feature for post-processing preprocessor results. For example, I often find things can get too blended with depth preprocessing images, where the white parts lose detail because of the depth estimation. The detail is technically still there, just in a very limited visual dynamic range. If you could essentially add contrast on the fly, you could change the preprocessor image to be more contrasty, allowing those details to be more visible, along with being more visible to the model itself. So for example, a simple contrast slider in controlnet that can apply an adjustment to the preprocessor image before it's plugged into the controlnet model. It can be just a little vertical bar beside the image that has like 5 stops on either end, so 0 as default and +5/-5. I think this could be useful for a variety of controlnet preprocessors, This should not apply to the base image, but the preprocessed image, so it should probably be in the preprocessor preview window, and maybe only visible if someone has the "allow preview" option activated. Users can then look at the preview to determine if they want to add or reduce contrast, and whatever setting is active when generation is started, is processed with that contrast on the fly and then sent off to the controlnet model.

[Satochiju]

Illyas, I'm very new to this and probably the most ignorant of all those involved here, but that doesn't stop me from telling you that I admire not only your great work in Forge, which by the way has been very useful for me as a graphic designer, but, above all, your selflessness. I'm sure that if there were more people like you in this world, things would be different, as we say in Chile. Thank you very much!! A big hug.

[Satochiju]

Ah! y lo nuevo de Forge funcionando muy bien en mi 3060ti, algo lento aún pero con muy buena calidad, Flux y SDXL

[qw381523977]

@lllyasviel Do you have a plan for when to start updating the flux controlnet?

[Gushousekai195]

It’s no use. He won’t answer.

[sd7821]

我感觉也是，不然大家去comfyUI吧

[Satochiju]

Totalmente de acuerdo con tu lúcido comentario. Gracias . Lamentablemente Einstein tenía razón, cuando decía: "hay dos cosas que siguen creciendo, el Universo y la estupidez humana que no sabe reconocer la inteligencia humana..." El sáb, 15 de feb de 2025, 4:59 a. m., UnconnectedBedna < ***@***.***> escribió:

…

At the end of the day. The fact that toxicity pushed away one of the best and open AI developers from this project is really really sad. I did not follow the entire situation, but when words like "copyright infringement" and such starts being thrown around, to me it seems obvious who is in the wrong. FOSS needs more cooperation and support, not toxicity and corpo bs buzzwords. Just my 2 cents, a user that was perfectly happy with forge, but now lack the ability to use Controlnet with FLUX. BS, all of it... But I stand behind lllyasviel and their decision to leave this behind, enough is sometimes enough. But it really fkn sux! — Reply to this email directly, view it on GitHub <#932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5FK6WCYPS6HYUOXWA6CKLL2P4FZDAVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRQHA2DSMA> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/12208490 @github.com>

[sd7821]

问一下Flux ControlNets 什么时间上线？有什么计划吗？

[gabrielxcom]

Are we there yet? 👀

[R2008KK]

If anyone is interested in one of the main reasons for such a long implementation of controlnet together with flux (or rather I believe that this is most likely the reason), I quote one of the users:
“stable-diffusion-webui does only support Stable Diffusion it's not designed to support any other type of AI models.
Models out there use diffusers pipeline, the webui uses Stability AI's reference implementation for SD(1/2/XL) and sortof SD3.
If you want other models use other software like Comfyui or SD.next (but remember you'll lose support for many popular extensiosn as these do only support SD pipeline).”

[tpcdaz]

If anyone is interested in one of the main reasons for such a long implementation of controlnet together with flux (or rather I believe that this is most likely the reason), I quote one of the users: “stable-diffusion-webui does only support Stable Diffusion it's not designed to support any other type of AI models. Models out there use diffusers pipeline, the webui uses Stability AI's reference implementation for SD(1/2/XL) and sortof SD3. If you want other models use other software like Comfyui or SD.next (but remember you'll lose support for many popular extensiosn as these do only support SD pipeline).”

What models doesn't forge support out of interest? Every model I know is a diffusion model. Flux is diffusion and Forge supports that. So do you have an example of a model that Forge doesn't support?

[R2008KK]

What models doesn't forge support out of interest? Every model I know is a diffusion model. Flux is diffusion and Forge supports that. So do you have an example of a model that Forge doesn't support?

I don't really know what you mean. As I understand it, stable diffusion models share a common architecture and stable diffusion webui was created (at least initially) specifically for them. Other models are created by other companies and are not related to stability.ai in any way, and the fact that they are supported by forge does not mean that all their features are implemented, and that features originally designed for sd models will work for other models.
So all extensions including controlnet were made for sd webui. The way controlnet does not cope well with retrained models like PonyDiffusion, you can understand that it will not work with other models at all, because it is not designed for them.

[R2008KK]

Well you stated that the reason you think it hasn’t been worked on is because it doesn’t support non stability models. But every model I’ve seen shows it does. It also supports control net quite happily. So I think the reason it’s not implemented yet is simply the dev lacked the drive to continue the development and not the architecture

I didn't say it's impossible to implement flux support. The controlnet nodes for comfyUI are an example. I don't know for sure if they were made based on lllyasviel`s controlnet, but anyway they evolved separately from it, specifically for comfyUI and its functions and models, different from what sd webui is designed for and therefore easier to adapt to flux.

[R2008KK]

Flux is supported in forge. I use forge over comfy for all my flux generations

the fact that they are supported by forge does not mean that all their features are implemented, and that features originally designed for sd models will work for other models.

And the additional extensions even more so.

[R2008KK]

And what features of forge aren’t implemented?

Considering I don't even use comfyUI, I can think of max_shift and base_shift which are not implemented. Some img2img functions are not implemented either. And as for the additional nodes, there are so many that not even 10% of them can be implemented in webui.

[tpcdaz]

Well you stated that the reason you think it hasn’t been worked on is because it doesn’t support non stability models. But every model I’ve seen shows it does. It also supports control net quite happily. So I think the reason it’s not implemented yet is simply the dev lacked the drive to continue the development and not the architecture

…

On Fri, 21 Feb 2025 at 18:41, R2008KK ***@***.***> wrote: What models doesn't forge support out of interest? Every model I know is a diffusion model. Flux is diffusion and Forge supports that. So do you have an example of a model that Forge doesn't support? I don't really know what you mean. As I understand it, stable diffusion models share a common architecture and stable diffusion webui was created (at least initially) specifically for them. Other models are created by other companies and are not related to stability.ai in any way, and the fact that they are supported by forge does not mean that all their features are implemented, and that features originally designed for sd models will work for other models. — Reply to this email directly, view it on GitHub <#932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2KN6EKDPYK7SCATIFA52HL2Q5XMHAVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGAZDKNA> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/12280254 @github.com>

[tpcdaz]

Flux is supported in forge. I use forge over comfy for all my flux generations

…

On Fri, 21 Feb 2025 at 19:06, R2008KK ***@***.***> wrote: Well you stated that the reason you think it hasn’t been worked on is because it doesn’t support non stability models. But every model I’ve seen shows it does. It also supports control net quite happily. So I think the reason it’s not implemented yet is simply the dev lacked the drive to continue the development and not the architecture I didn't say it's impossible to implement flux support. The controlnet nodes for comfyUI are an example. I don't know for sure if they were made based on lllyasviel`s controlnet, but anyway they evolved separately from it, specifically for comfyUI and its functions and models, different from what sd webui is designed for and therefore easier to adapt to flux. — Reply to this email directly, view it on GitHub <#932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2KN6EMU3OBPB3G5O72N4JT2Q52K7AVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGA2DSOI> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/12280499 @github.com>

[tpcdaz]

And what features of forge aren’t implemented?

…

On Fri, 21 Feb 2025 at 19:15, R2008KK ***@***.***> wrote: Flux is supported in forge. I use forge over comfy for all my flux generations the fact that they are supported by forge does not mean that all their features are implemented, and that features originally designed for sd models will work for other models. — Reply to this email directly, view it on GitHub <#932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2KN6EJ5PLQWLXMLF4UKJIL2Q53NDAVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGA2TOMQ> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/12280572 @github.com>

[tpcdaz]

Ah I see ok that’s fair enough. I can’t say I use any of those features so I’ve not noticed them not being implemented. I tend to just load up and generate.

…

On Fri, 21 Feb 2025 at 19:34, R2008KK ***@***.***> wrote: And what features of forge aren’t implemented? Considering I don't even use comfyUI, I can think of max_shift and base_shift which are not implemented. Some img2img functions are not implemented either. And as for the additional nodes, there are so many that not even 10% of them can be implemented in webui. — Reply to this email directly, view it on GitHub <#932 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2KN6ENPP4I5JCJRU4SDYVD2Q55ULAVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGA3TKOI> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/12280759 @github.com>

[Lexxxco]

@lllyasviel hi, there is already working (but not optimal) Controlnet and Flux.tools implementation in Forge by Academia SD in form of extension. Can you please include it in future update of Forge?

[UnconnectedBedna]

Warning

diffusers>=0.32.2, transformers>=4.48.3, Pillow>=9.5.0, tokenizers>=0.21, huggingface-hub>=0.28.1, controlnet-aux>=0.0.9,

Forge2 already has newer versions for all but diffusers. Be aware that updates to Forge2 may overwrite the requirements file.

Just be aware of what you are doing if you do that.

Also, the statement is not true for this repo: https://github.com/lllyasviel/stable-diffusion-webui-forge/blob/main/requirements_versions.txt
Or this branch either: https://github.com/lllyasviel/stable-diffusion-webui-forge/blob/sd35/requirements_versions.txt

The developer can post here, but I suspect might have refrained from it because it might probably breaks dependencies for other things.

[AcademiaSD]

Warning

diffusers>=0.32.2, transformers>=4.48.3, Pillow>=9.5.0, tokenizers>=0.21, huggingface-hub>=0.28.1, controlnet-aux>=0.0.9,

Forge2 already has newer versions for all but diffusers. Be aware that updates to Forge2 may overwrite the requirements file.

Just be aware of what you are doing if you do that.

Also, the statement is not true for this repo: https://github.com/lllyasviel/stable-diffusion-webui-forge/blob/main/requirements_versions.txt Or this branch either: https://github.com/lllyasviel/stable-diffusion-webui-forge/blob/sd35/requirements_versions.txt

The developer can post here, but I suspect might have refrained from it because it might probably breaks dependencies for other things.

I have not posted here because this is not integrated controlnet, it is Flux1 Tools which is similar to controlnet, indeed the necessary dependencies change, I have not detected any problem with the dependencies nor does any error appear, everything seems to continue working fine, but it is possible that some extension has problems

By the way, now the extension has support for LoRAs

[UnconnectedBedna]

For me it would guarantee to break because I have things relying on specific versions not higher than what is in forge, so I can't try if those are required dependencies for your plugin. :(

Btw, I think you can post it there if you just make a big disclaimer about the dependencies, it's a list of extensions, not specifically for controlnet stuff.
I think a lot of people would actually appreciate that, people that are NOT in the situation I am.

[Vagrin]

I made a backup of the requirements file. I put it back when I couldn't get it to work due to permission problems. Everything seemed to work fine throughout.

[yamfun]

I want those IP Adaptors "style" / "composition" sliders and presets in A1111 control net because I really want to choose "style only", thanks...

[qw381523977]

Please, are there any plans to update controlnet integrated this year？ @lllyasviel

[gabrielxcom]

At this point, I think it's kind of obvious that this project is what it is and how it is, and that's it.

[wzwow]

just use kontext to style it if you want to.

[E2GO]

I'm pretty sure that from most technical points of view to keep stuff updated and etc it's just more simple to lllyasviel team to create smth new like Forge 2 aka Fortress or smth)

[Cleroth]

this dead bros, what y'all doin' necroing this

[UnconnectedBedna]

Keep those kinds of negative comments away from a developer driven forum like github thank you.
If you nothing constructive to say, don't say anything.

This forge plugin was released 1h ago:
#1754 (comment)

[IPv6]

Using Forge weekly, still the fastest beast for SDXL (and for my workflows nothing else needed...)

[E2GO]

It doesn't at all. If you're working a LOT in production - Forge is a way to go (especially inpainting stuff not just batch generation). I'm working in mobile game industry and Forge is a standard for it. Second one is still Fooocus for SDXL also from @lllyasviel
Main downside now is a speed when users gets support for newer models. Then ComfyUI is a main choice for sure. But in working pipelines nobody switch each time when new model comes.

[SillySilk]

I think the problem is that semi crippled It's still for most of us is far more intuitive and easier to use better tool than any other, especially with in painting which is a large part of what I do

…

On Tue, Jul 1, 2025 at 8:53 AM Cleroth ***@***.***> wrote: this dead bros, what y'all doin' necroing this — Reply to this email directly, view it on GitHub <#932 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHN7U73PM4MZAG5YEVWWOS33GKVIFAVCNFSM6AAAAABMAFM6XCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRTGA3TKOI> . You are receiving this because you commented.Message ID: <lllyasviel/stable-diffusion-webui-forge/repo-discussions/932/comments/13630759 @github.com>

[Vagrin]

It also handles memory like no other option. Only with Forge can I run full Flux Dev with fp16 t5xxl.