-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Re: some parameters in "config.txt" ignored on Fooocus startup in V2.3.0 #2566 #2609
Comments
This is not necessarily a bug but an intended feature, at least it was until preset selection has been made available in the UI. When starting the presets with console arg, this parameter is set as default. |
One addition: as metadata import, history log import and preset switch use the same functionality this adjustment would have a bigger impact than the one described in this issue. I'd see it rather as a won't fix. |
@DavidDragonsage fixed & implemented |
Wonderful! I just started Fooocus and noticed it working as expected. I've been doing a lot of model testing lately using preset switching and prompt arrays requiring a size of 2. That resetting to 1 problem was driving me crazy! Yes, it wouldn't have been a problem until the ability to switch presets within Fooocus was introduced in version 2.3. Thanks so much! |
Checklist
What happened?
Following the update to 2.3.0, the only fault remaining for me is that "default_image_number" resets to 1 every time I change presets. My setting in config.txt is "default_image_number": 5,
I tried adding "default_image_number": 5, to my custom presets but that did not help.
For trouble-shooting purposes, I just did a clean installation of Fooocus, so the Image Number started at 2. But whenever I change to another preset, the Image Number resets to 1. The problem remains the same.
Steps to reproduce the problem
What should have happened?
The image number should stay the same, no matter which preset you use.
What browsers do you use to access Fooocus?
Mozilla Firefox
Where are you running Fooocus?
Locally
What operating system are you using?
Windows 10
Console logs
Additional information
I think this one just got overlooked in the thread:
#2566
The text was updated successfully, but these errors were encountered: