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
A user may have already set up their webUI with their favorite sampler, desired number of steps, CFG scale, among other settings. After successfully installing the plugin, the user may notice that none of their settings carried over from the webUI, so they have to set everything up again.
The solution is simple: make the plugin automatically mirror the webUI's relevant settings i.e. the settings exposed to the plugin.
I for instance have tried clicking on the "Configure all settings in webUI" option, change some setings (namely enabling color correction for img2img), apply them, then go back to Krita to click on "Auto-Refresh Options Now" thinking that the settings changed would update in the plugin UI, only to find out that it did absolutely nothing and that color correction was still disabled within the plugin UI, despite being enabled in the webUI.
The text was updated successfully, but these errors were encountered:
A user may have already set up their webUI with their favorite sampler, desired number of steps, CFG scale, among other settings. After successfully installing the plugin, the user may notice that none of their settings carried over from the webUI, so they have to set everything up again.
The solution is simple: make the plugin automatically mirror the webUI's relevant settings i.e. the settings exposed to the plugin.
I for instance have tried clicking on the "Configure all settings in webUI" option, change some setings (namely enabling color correction for img2img), apply them, then go back to Krita to click on "Auto-Refresh Options Now" thinking that the settings changed would update in the plugin UI, only to find out that it did absolutely nothing and that color correction was still disabled within the plugin UI, despite being enabled in the webUI.
The text was updated successfully, but these errors were encountered: