You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and checked the recent builds/commits
What would your feature do ?
Regarding built-in plugins within Forge, such as Controlnet and multidiffusion, they do not offer the complete set of functionalities I require (for instance, in Forge's Controlnet, third-party preprocessors that have already been adapted for the original webui would need to be re-adapted specifically for Forge, which is quite challenging for those without programming skills). When I attempt to install these separately, my self-installed versions are consistently disabled. The suggestion is to refrain from disabling self-installed plugins that also happen to be part of the built-in ones, so that users like myself can freely switch between the built-in and self-installed versions to utilize complementary features each may lack.
Proposed workflow
None
Additional information
No response
The text was updated successfully, but these errors were encountered:
They are disabled because they are incompatible due to the modified UNet patcher. They're impossible to use with Forge, so forcefully disabling them is the only logical option.
Separate issue(s) should be opened for functionality that is missing. There are a few already tracking some.
Is there an existing issue for this?
What would your feature do ?
Regarding built-in plugins within Forge, such as Controlnet and multidiffusion, they do not offer the complete set of functionalities I require (for instance, in Forge's Controlnet, third-party preprocessors that have already been adapted for the original webui would need to be re-adapted specifically for Forge, which is quite challenging for those without programming skills). When I attempt to install these separately, my self-installed versions are consistently disabled. The suggestion is to refrain from disabling self-installed plugins that also happen to be part of the built-in ones, so that users like myself can freely switch between the built-in and self-installed versions to utilize complementary features each may lack.
Proposed workflow
None
Additional information
No response
The text was updated successfully, but these errors were encountered: