Skip to content
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]: Repeated Upscaler Entries #313

Open
4 of 6 tasks
Haoming02 opened this issue Feb 18, 2024 · 6 comments
Open
4 of 6 tasks

[Bug]: Repeated Upscaler Entries #313

Haoming02 opened this issue Feb 18, 2024 · 6 comments
Labels
bug Confirmed report of something that isn't working pending upstream This item is awaiting an existing resolution in an upstream repo in order to be resolved.

Comments

@Haoming02
Copy link

Checklist

  • The issue exists after disabling all extensions
  • The issue exists on a clean installation of webui
  • The issue is caused by an extension, but I believe it is caused by a bug in the webui
  • The issue exists in the current version of the webui
  • The issue has not been reported before recently
  • The issue has been reported before but has not been fixed yet

What happened?

In the Extras tab, the upscalers in the ESRGAN folder now show up twice in the dropdown.

Steps to reproduce the problem

  1. Pull the latest commit (43c9e3b)
  2. Launch the Webui
  3. Go to Extras tab
  4. Click on the Upscalers dropdown

What should have happened?

Each file only shows up once

What browsers do you use to access the UI ?

Microsoft Edge

Sysinfo

N/A

Console logs

N/A

Additional information

N/A

@jipsita
Copy link

jipsita commented Feb 23, 2024

I have the same problem, any workaround? it's just aesthetically annoying but still :/

@catboxanon
Copy link
Collaborator

I can't reproduce this as it doesn't occur for me with a fresh install.

@catboxanon
Copy link
Collaborator

This seems to be coming from upstream, but as I mentioned above this isn't something I'm able to reproduce on a clean install after adding a few models to the ESRGAN folder.

@catboxanon catboxanon added the upstream Should be resolved in the AUTOMATIC1111/ComfyUI repo or upstream elsewhere. label Feb 26, 2024
@Haoming02
Copy link
Author

Right now, my Forge installation uses a symlink for the entire models folder, instead of using the set A1111_HOME thingy in the .bat.
Maybe this is the cause?

I added a print(file) at this line, and I got:

C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui\models\ESRGAN\2x-AnimeClassics-UltraLite.pth
C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui\models\ESRGAN\4x-UltraSharp.pth
C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui\models\ESRGAN\4xLSDIRplusC.pth
C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui-forge\models\ESRGAN\2x-AnimeClassics-UltraLite.pth
C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui-forge\models\ESRGAN\4x-UltraSharp.pth
C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui-forge\models\ESRGAN\4xLSDIRplusC.pth

Meaning, it somehow loads the files twice.

Funnily, I also put another model here:

C:\Users\Michael.C\Documents\GitHub\stable-diffusion-webui-forge\models\DAT\4xNomos8kDAT.pth

But this one doesn't show up twice.

@catboxanon catboxanon added the bug Confirmed report of something that isn't working label Feb 26, 2024
@catboxanon
Copy link
Collaborator

catboxanon commented Feb 26, 2024

Thanks! I'm able to reproduce now after symlinking the entire models folder as you mentioned.

@catboxanon
Copy link
Collaborator

AUTOMATIC1111/stable-diffusion-webui#15035 will close this, and likely some other issues as well such as #282.

@catboxanon catboxanon added pending upstream This item is awaiting an existing resolution in an upstream repo in order to be resolved. and removed upstream Should be resolved in the AUTOMATIC1111/ComfyUI repo or upstream elsewhere. labels Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed report of something that isn't working pending upstream This item is awaiting an existing resolution in an upstream repo in order to be resolved.
Projects
None yet
Development

No branches or pull requests

3 participants