Open dot3x3q opened 7 months ago
Reverting the two changes I made back in config.json to how they were originally, did not fix the boot errors , so that was clearly not the issue.
UPDATE:
I've found the source of the problem, at least in my case. In comparing my config.json to a default one, adding postprocessing_enable_in_main_ui
to extra_options_txt2img
causes boot to fail.
Full snippet:
"extra_options_txt2img": [ "postprocessing_enable_in_main_ui" ],
Does anyone have any idea why this might have caused errors on startup?
Checklist
What happened?
Been using this install of A1111 for weeks now without much issue. The issues I have had I've been able to resolve by searching the issues on this repo (it's been very helpful). I did a search for this particular one, however, but was unable to find anything before writing this up.
Basically, I changed a few settings and webui.bat no longer successfully boots at all.
The errors go on and on; see console logs for full errors in the cmd terminal.
Steps to reproduce the problem
UPDATE: See my comment below. These settings changes appear to not be what caused the issue. Errors persist.
If I can recall specifically, I changed:
I may have changed a few more settings in the UI before applying a reload, but I just can't remember.
What should have happened?
Running webui.bat should boot as it always normally has.
What browsers do you use to access the UI ?
Brave
Sysinfo
sysinfo-2024-02-11-07-32.json
Console logs
Additional information
No response