Feature request: Presets

[Miraihi]

While I love the degree of control the plugin allows, it gets a bit tiring setting it all over again each time I open my .kra file (Especially if controlnet is involved). Can we have something kile the "Config-presets" plugin integration in the future?

[DrCyanide]

I have been working on saving some user settings (like prompts), but it definitely needs some improvements. I'll see if I can get a few more settings to save soon.

[DrCyanide]

I have far more settings being saved now - including denoise strength, color correction, basic ControlNet preferences, upscaler preferences, better control over Shared Prompts, etc. - all of which should make it easier to resume working on projects and take less setup time.

As for a full "Config-Presets" way to save a specific combination of settings with a custom name, I don't think that will be possible until the app is more mature. The easiest way to implement that is to have a bunch of different config files that get swapped in for the default user_settings.json that I build, but that config file is still being updated and changed as I add new features.

[DrCyanide]

I'm working on a big rewrite of the saved settings system, and I'm hoping I can get your opinion on something:

If each Krita document stored basically every setting, and remembered those settings when switching between modes, would you still want presets?

I personally don't feel like doing the initial setup for a project is that bad, which is what presets seem to be most useful for.
For me, most of the frustration is with fields and extensions reverting back when toggling between modes, and with prompts/models not being saved with a specific document. If I have to jump back and forth between documents it can be easy to lose prompts or settings, making it harder to be consistent.

I think I can do per-document settings, but having default settings + user general settings + presets + document settings... That's been giving me a headache trying to work out.

[Miraihi]

I think that per-document settings + some kind of autocomplete (at least for loras) would be great.

Presets are still useful, but in-pugin implementation (With no connection to the extensions) would be acceptable. I know that having the presets feature is handy because lately I've been using Acly's plugin that has this feature.