All upscaler images fail

[eaglenv]

Hello, every time I use any upscale method (other than HiRes)...I get this image:

I have tried every upscaler option with multiple different settings...there are no errors in the cmd window or in the UI. It generates images just fine, but this is the result of upscale generation. Shows 100% complete every time.

i7 8700k - GTX 1080ti - 32GB Ram...I have no idea what to try next...please advise. Thanks in advance.

[MisterChief95]

Is this happening in the img2img tab, extras, or somewhere else? Do non-upscaled generations show fine?

[eaglenv]

Is this happening in the img2img tab, extras, or somewhere else? Do non-upscaled generations show fine?

That is correct...only in img2img and extras tab...the non-upscaled images generate perfectly without issues.

I did a fresh install today...generated a fresh image and tried to upscale it...same result 😒

[MisterChief95]

Can you do try this:
Add --loglevel DEBUG to your command line args in the launch script, then do following:

1. generate an image
2. generate an image with hires fix using an upscaler (or quick upscale the previous image)
3. Upscale any image in the extras tab

Please copy the console output to a text file and attach it here. I would like to ensure that there are no underlying issues that are not being captured at the standard log level. The only other potential cause I can think of is that the upscale models may be corrupt. However, this seems unlikely given that you have tried multiple models. Considering it occurs on a fresh installation, there may be some dependency issues but that also seems unlikely.

[eaglenv]

Can you do try this: Add --loglevel DEBUG to your command line args in the launch script, then do following:

1. generate an image

2. generate an image with hires fix using an upscaler (or quick upscale the previous image)

3. Upscale any image in the extras tab

Please copy the console output to a text file and attach it here. I would like to ensure that there are no underlying issues that are not being captured at the standard log level. The only other potential cause I can think of is that the upscale models may be corrupt. However, this seems unlikely given that you have tried multiple models. Considering it occurs on a fresh installation, there may be some dependency issues but that also seems unlikely.

Here it is.
Python 3.10.6 (tagsv3.10.69c7b4bd,.txt

The HiRes image generation upscaled perfectly...

This is the image from the img2img upscale:

[MisterChief95]

Nothing seems out of the ordinary, and nothing really seems off in the PNG info for your latest image. Couple more questions:

1. When you say you tried every upscaler, did you try None or Lanczos? Those options don't use any AI model so it would be bizarre if those did something weird as well
2. I see you are trying this with a Flux model, does the same thing happen with an SDXL or SD 1.5 model?

It's important to note, too, that HiRes Fix is img2img, just run immediately after txt2img. If you take an image, and run it through img2img without any upscaling at a denoise of 0.1-0.3 does it still produce banded images like those? I want to see if we can isolate it to something wrong with img2img or the upscalers.

[eaglenv]

Indeed I have tried "None and Lanczos"...None produced the image with just lines...Lanczos produced this awkward image different than the others but still failed.

This is with SD 1.5 - ERGAN_4x....still failed but closer to the image than any others.

SDXL - ERGAN_4x...failed but there is something there.

img2img without upscaling and denoise at 0.1 it produces the same image as the first one I posted with the lines.

Note *** I have used SuperImage Pro, Upscayl and a different Web UI to test other upscaling options...all have worked without issue.

[MisterChief95]

#2404 is the only issue that resembles what's going on here, but even their SDXL/SD1.5 checkpoints worked fine.

I can't reproduce on my end either, so the only thing left to ask is what OS/NVidia Driver are you using?

[eaglenv]

#2404 is the only issue that resembles what's going on here, but even their SDXL/SD1.5 checkpoints worked fine.

I can't reproduce on my end either, so the only thing left to ask is what OS/NVidia Driver are you using?

11 Pro 23h2

566.36...I will try a different driver and report...Is there a driver you recommend or should I just wing it?

[MisterChief95]

It should work with that setup - it's what I use. I'm running out of troubleshooting ideas though.

Since nothing else seems to be giving us a sign as to what's wrong, a reinstall may be your best bet if you haven't tried it. What you can try before a full reinstall is renaming ui-config.json and config.json to ui-config.json.old and config.json.old respectively, and let Forge regenerate your settings. If it starts working after that, you had a misconfigured/corrupted setting somewhere. If that doesn't work, then try the reinstall.

[eaglenv]

It should work with that setup - it's what I use. I'm running out of troubleshooting ideas though.

Since nothing else seems to be giving us a sign as to what's wrong, a reinstall may be your best bet if you haven't tried it. What you can try before a full reinstall is renaming ui-config.json and config.json to ui-config.json.old and config.json.old respectively, and let Forge regenerate your settings. If it starts working after that, you had a misconfigured/corrupted setting somewhere. If that doesn't work, then try the reinstall.

I tried 3 different drivers....fresh install 2 times...although #2404 is similar, his worked with different checkpoints and mine just fails with them all. I will continue to monitor and hopefully a update will tackle the issue...fingers crossed.

MisterChief95...ty for your assistance and time...i appreciate it...please keep me advised if you find out anything on the subject.