Custom Texture Tool PS v50.1

[Matrix2525]

Nice work Bighead! Just did a bit of quick testing and so far, everything looks good to me.

[Bighead]

@Vlad1vostok: This should allow what you want. In the options menu is now an "Exclusions" tab. Just uncheck whatever you don't want to process.
http://www.mediafire.com/file/8q88m0ywtig1opb/Custom+Texture+Tool+PS+v40.0.b16.zip

Spoiler: (Show Spoiler)

Fortunately I already do all these checks when the texture is intialized so it was really easy to implement. There is currently no protection in place (nothing will stop you from disabling both "no alpha" and "has alpha" which disables every texture), but I'm done for the night.

[Vlad1vostok]

@Bighead Thank you so much! The fastest response from the developer ever. ) You have made it very easy to work with texture mods for everyone.

[Bighead]

I added "Transparency" to the mix of exclusions since it's not the same as "alpha channel". This may actually be what you want, since an opaque image can have an alpha channel.
http://www.mediafire.com/file/77aaxlcuy2l5zy0/Custom+Texture+Tool+PS+v40.0.b17.zip
http://www.mediafire.com/file/gpwxq51u3y4owh5/Custom+Texture+Tool+PS+v40.0.b18.zip

Spoiler: (Show Spoiler)

I made the option into a groupbox rather than checkboxes since I wanted to somehow show that changing it will make the script slower overall. An alpha channel check is fast, it's as simple as does it exist (true/false). Checking for transparency requires looping through every pixel to see if the alpha byte is less than 255, which is rather slow (especially on larger images).

The "best" (which translates into fastest) course of action is to ensure that no opaque textures have an alpha channel when doing these kinds of tasks. The operation Remove Alpha Channel From Opaque Textures can do just that, that way the "Alpha Channel" checks can be used and not have to rely on the "Transparency" checks.

Since the transparency check is slow, I made it so it's only done once per texture. This check was already done when using ESRGAN/SFGTAN, so the result will be saved if the option is toggled, and won't have to be done twice.

Edit: Because "go big or go home". Now textures can be excluded by names or phrases. Each search string should be entered onto a new line. The entire path to the file is checked, and if it contains one of these entries, it will be excluded. This allows excluding specific textures by dimensions, even more specific can include the hash, and can mimic the above checkboxes and skip mipmaps by entering "_m_" or a file extension ".dds". An entire folder can be skipped by entering the folder name.

I was torn between separating entries with a comma or using a new line, and I decided a new line would be the way to go to keep the list readable and neat. An issue with commas is that if an entry exceeds the line, it continues onto the next line which causes a visible break in the entry. So with that said, using commas will not work. Each entry must be on a new line.

Spoiler: (Show Spoiler)

[Bighead]

This should hopefully be the final beta before release.
http://www.mediafire.com/file/o92mag6a83eapc6/Custom+Texture+Tool+PS+v40.0.b19.zip

I changed the options menu a bit. I didn't like the "Operations" tab so I scrapped it. It felt really bloated to me compared to my other menus, displaying a bunch of unrelated options all at once. But I did want a way to configure that stuff from the "Options" menu, plus have a place for the ESRGAN/SFTGAN auto-install, so I created the "Misc" tab (which may have a name change I just can't think of what to call it).

Spoiler: (Show Spoiler)

BEFORE / AFTER

Compared to the previous "Operations" tab, it still provides access to all the same things except more elegantly. And there is space for whatever else ends up there eventually. The buttons will open the same menus that the associated "Operation" opens.

Spoiler: (Show Spoiler)

There probably won't be any more significant changes, all I have left is to finish up some info in the Help menu. But I figured it might be a good idea to do one final "beta" and wait a few days to see if any fun and interesting bugs pop up that I may have missed.

[ewzzy]

Trying out the latest version and I can't get the ESRGAN/SFTGAN auto-install to work. When it downloads the models from github afterward there isn't a C:\Superscalers folder. I tried creating one manually and rerunning but it didn't do anything.

[Bighead]

I figured I broke something somewhere, thank you for finding something so quickly.
http://www.mediafire.com/file/8xbbh7wrl8ho1ff/Custom+Texture+Tool+PS+v40.0.b20.zip
http://www.mediafire.com/file/cz5og2o9u5fzsfl/Custom+Texture+Tool+PS+v40.0.b21.zip

Edit: Since I seem to have this issue with not testing my changes well enough, I spent the past few hours testing everything possible and found all kinds of serious issues. As far as I can tell, everything should be fixed now.

[ewzzy]

It finished perfectly this time and now my computer is burning through a whole mess of textures. Thank you so much!

[e2zippo]

Woot, ESRGAN support, this is awesome! I'm been looking forward to try to do some texture packs with upscaling! I've been dumping some textures from Star Fox 64 to see how they look upscaled. Your tool is making this process soooo much easier! Many thanks Bighead! Since I'm a complete noob at this I'll probably be back with a load of questions though

I've been looking into N64 textures as well, and I've been dumping some textures to .png files with Rices video plugin. Could I use this tool on those textures as well?

Cheers!

Edit: Tried the latest beta and started the auto configuration for ESRGAN, but I fail when trying to install Nvidia CUDA (failed to connect to Nvidia). Are there any prerequisites before installning CUDA (I saw the installer mentioned Visual Studio)?

[Bighead]

It can be used with N64 textures, set the CTT-PS Mode to "Expert Mode" and it will work with all PNG, DDS, and JPG images.

You need to have a nvidia GPU to install CUDA. You should still be able to use ERSGAN using CPU (find the option "Disable GPU" in the script), but it will be much slower and I've never actually tried it without CUDA.