[SD.Next] 'txt2img_enable_hr' could not be processed. about config-presets

[Zyin055]

@steto123 @brknsoul
This should hopefully be resolved now after merging PR #55 . If it is let me know and I'll close this issue.

[brknsoul]

Workaround #52

[Zyin055]

As I said in the other thread, I do not guarantee compatibility with Vlad's SD.Next because I do not use it. Sounds like Vlad removed the Hires fix checkbox (or renamed the ID), possibly due to trying to support SDXL's refiner model?

If someone wants to submit a PR to either give support for this somehow, or figure out a way to ignore fields that Config Presets cannot find (I couldn't figure out an easy way to do it when I made the extension months ago) then feel free.

[brknsoul]

I've popped an Extension Issue up on SD.Next's github, however Vlad's on a vacation for a month from the 27th or 28th of July. He'll still have his laptop and internet access, but that's only for emergencies.

The work-around I linked to above probably could be rolled into a pull request, detecting if one is using SD.Next (rather than A1111) and reference the element IDs correctly, but I'm not a dev, so I'm not sure how to do that.

[Symbiomatrix]

@Zyin055 I'm just starting to make sense of vlad's latest, but it seems that at least in principle, it should be possible to make certain components optional, so that if they don't exist in some particular version (ie component is null) then they're simply dropped before the ui build. The PR I've sent seems to be functional both on my old may and latest august versions of vlad's. Could use much more testing however.
If this works, theoretically might also be able to map the same id to multiple components at runtime (depending on which one exists), instead of for example the text replacement for controlnet's mod_radio -> mode_radio correction (backwards compatibility and whatnot).
What do you think?

[brknsoul]

Works perfectly! Thank you for working on this.