Custom Texture Tool PS v50.1

[SecretCircle]

(03-31-2019, 11:18 AM)Bighead Wrote: @SecretCircle: The start button should only be grayed out on startup if the script doesn't find ImageMagick. It's the only "required" program, much of the script relies on it in some way.
http://www.imagemagick.org/script/download.php#windows

Ah yes, that was exactly it. Thanks. 

Just another question, is it normal for the upscale factor to be locked at 4 with ESRGAN and capped at 4 with SFTGAN?

[Bighead]

Yes. Although the ESRGAN python script has a value for "upscale", changing it just breaks things. If I try 2x-3x, it shows an error. Attempting 5x-6x works as in ESRGAN spits out an image, but it doesn't do anything (the image still comes out at 4x). I tried the simple GUI here by dsluo who has implemented an upscale factor. It behaves exactly in the same way. So I just locked it at 4x.

For SFTGAN, the upscale factor affects the image that is upscaled with nearest neighbor before upscaling with SFTGAN. Although the limit is artificial (you could do 16x no problem), the quality is awful. Even a bump to 5x pretty much kills all the quality that can be gained. It did however look pretty good at lower values, which is why I allow 2x and 3x. It may be better to just run the image through it twice if you wanted a larger image. Such as, if you wanted 8x, do a 4x SFTGAN run then a 2x run.

[Bighead]

This should hopefully speed things up a bit:
http://www.mediafire.com/file/op2olu9x1z439y9/Custom+Texture+Tool+PS+v40.0.b10.zip
http://www.mediafire.com/file/txqf629emoroxfg/Custom+Texture+Tool+PS+v40.0.b11.zip

- Alpha channel will now only be kept if an image actually contains transparent pixels. Slightly slower, moderately slower on enormous images.
- Seamless pixels are now extracted and applied, rather than tile an image 9x and crop the center, should provide small-moderate speed-up.
- Segment size can now be doubled (max of 544x544 vs. original of 288x288). Requires more VRAM, should provide moderate speed-up. Disable if images fail.
- Upscaling image before running SFTGAN can now be disabled, useful maybe if you want to run ESRGAN and SFTGAN after.

Spoiler: (Show Spoiler)

Some options are now hidden behind the auto-setup, so I added an arrow button to hide/unhide it. Also, from my testing, 20 seamless pixels may be sufficient over 24. The less needed here the better.

Edit: Updated to beta 11. Replaced the doubled segment size option with a multiplier. This allows even larger segments if you have the VRAM for it.

Spoiler: (Show Spoiler)

There are 3 possible settings:

0 = 288x288
2 = 544x544
4 = 1056x1056

I didn't add 8 or above because I don't think any GPU can upscale a 2080x2080 image directly. The setting "4" will require lots of VRAM, but if your GPU can support input images with ESRGAN or SFTGAN at this size, it should be very fast.

I also made it so if an image or segment fails to be created, and the cause is lack of VRAM, the message will now show "out of VRAM" specifically.



As long as nobody encounters any bugs, I think ESRGAN/SFTGAN support is nearly complete.

[Bighead]

This should most likely be the last beta before release:
http://www.mediafire.com/file/pck5aip9tig8uh3/Custom+Texture+Tool+PS+v40.0.b12.zip
http://www.mediafire.com/file/ldloy127p5ux9hc/Custom+Texture+Tool+PS+v40.0.b13.zip

Everything I wanted to finish is done, I just wanted to release it as it is now to hopefully get some testing and feedback. Once I make an official release I'll cover all the changes more thoroughly, but for now I want to focus on the last of the ESRGAN/SFTGAN updates.

Spoiler: (Show Spoiler)

Edit: The second image is now how the GUI appears since b13.

Rather than use a "segment multiplier", I changed it so it's possible to just pick the maximum segment size in dimensions. The option functions identically to before, but I think this name makes it a little more obvious on what it does.

A new option has been added named Pixel Buffer Type (was Pixel Border Type in b12). It's a little hard to explain, so I'll provide some examples. When creating a segmented image, a border of pixels is added around the image. This makes it very easy to create all segments the same size. By default, I created the borders in a fashion that makes the image seamless. This is perfect for the inner pixels, but can have problems around the edges if the image was not seamless to begin with. Some of the pixels from the border can bleed over into the main image when it is upscaled. This option should help rectify that problem for non-seamless textures.

---

Pixel Buffer Type: Standard

Base Image / With Border / Results Zoomed




The first image is not seamless, so this method is the best. This method mirrors the edges of the image onto the border. If looking at the corner of the upscale result, the colors are what would be expected. The second image however is a seamless image, and looking at where the image tiles after upscaling, there are noticeable seams where they meet.

---

Pixel Buffer Type: Seamless

Base Image / With Border / Results Zoomed




Here we see this method is not so kind to the first image, as the result has pixels that bled over from the extra pixels. This method tiles the image onto the border, as if the image were in a 3x3 grid. When looking at the results of the seamless image, it no longer has seams in the result where the images come together.

---

Unfortunately there is no way to automate this process, as far as I know it's impossible to know whether or not an image is supposed to be seamless.

Edit: OCD gets the best of me again. Made a quick update because I wasn't happy with the ESRGAN/SFTGAN options.
http://www.mediafire.com/file/ldloy127p5ux9hc/Custom+Texture+Tool+PS+v40.0.b13.zip

Spoiler: (Show Spoiler)

The naming is now more consistent and I made use of all the possible space and managed to squeeze everything in. The auto-setup now fits with everything else, and can still be hidden with the button. Rather than call the temporary pixels a "Border" which sounds more permanent, I went with "Buffer" which sounds more temporary. Also rearranged the Waifu2x options to fall more in line with the ESRGAN/SFTGAN options.

The "Pre-Upcale SFTGAN" option was removed. To get the same effect as unchecking it, the "Upscale Factor" can now be set to 1x for SFTGAN. This seems more intuitive anyway, and removes an unnecessary option.

[Matrix2525]

So, I just grabbed v40.0.b13 to check it out, and textures with transparency are now failing to upscale with ESRGAN. I went back to the last version I was using, b11, and everything works fine. Otherwise, all of the other features seem to be working alright.

[Bighead]

And here I was hoping my next post would be a final release.

Does the image fail completely? Meaning, do you not get any output at all, or is it just losing transparency? I just tested b13 and had no issues upscaling an image with transparency with either ESRGAN or SFTGAN.

I made a lot of changes the past few days, so hopefully it resolved itself.
http://www.mediafire.com/file/dqcn6pmdfk213w3/Custom+Texture+Tool+PS+v40.0.b14.zip

[Matrix2525]

Downloaded b14 to test and unfortunately, the image still fails completely with no output.  I even went through the setup again and re-downloaded ESRGAN etc, just to make sure, but nada.  If I go back to b11, the upscale works properly and I get an upscaled image with transparency.  Also, I haven't really been using SFTGAN, but  I tried it just to test in both versions, b11 and b14. In both cases, it produced an upscaled image with a black background instead of transparency.  And the result is the same for every transparent image in a group I tried upscaling, mixed with standard opaque textures.  Textures with no transparency worked, and with transparency failed.  I also tried to upscale them one at a time, too.  So, I have no idea what changed from b11 to b13+.  I'll attach one of the images that failed for me and you can take a look if you like.

   

[Bighead]

Thank you for the info. That texture does not work for me either. It seems only segmented upscales are working correctly when alpha is involved, non-segment upscales (smaller images) take a different path which isn't working correctly. I'll have a fix soon.

[Vlad1vostok]

Nice work. Could you add a function (checkbox) to process only images that have (not) transparency or skip such, please. This will make it very easy to use different models for them.

[Bighead]

Heeeeeeeeere we go! Issues should be resolved, and resource packs can now be compressed (thanks to spycrab as this has bugged me for awhile and I couldn't get it working).
http://www.mediafire.com/file/6bfcac4ue8s5yec/Custom+Texture+Tool+PS+v40.0.b15.zip

Spoiler: (Show Spoiler)

@Matrix2525: The issue should be resolved now. Figuring out the problem was a bit annoying, especially since I did it to myself. I have a small function to test if the upscale was created, and somewhere along the lines I inverted the output in one of my refactors, so it was thinking that it was never created. This was accounted for in segmented upscales, but not straight forward upscales.

@Vlad1vostok: I'll consider it. What you are asking for is simple enough, but it does go against my design philosophy a bit. This checkbox would be a very specific filter on a very specific operation. I do try to avoid implementing "operation specific options" like this, as there is a lot of things that an option like this could be applied to.

It does give me a more large-scale idea. I could add a new tab to the options menu, one that has some kind of "filtering" to choose which kinds of textures are processed. Although at the moment I can't think of too many filter types off the top of my head. (Has alpha, has mipmaps, min dimensions, max dimensions, that kind of stuff). That could give complete control over what textures the script processes, and would be applied to all operations and not just upscaling options.

Edit: A quick peek at what I have in mind. Creating the dialog like this is the easy part. Hooking it all up will be the fun part.

Spoiler: (Show Spoiler)