Custom Texture Tool PS v50.1

[Bighead]

(05-06-2019, 09:15 AM)Malkierian Wrote: I have many files that are conglomerates of small bits of textures, and are not tagged for mipmaps.  Is the mipmap generation applied to these non-mipmapped textures, as well?

Mipmap generation is only automatic for Dolphin textures that have "tex1" prefix and also have the mipmap flag when in "Dolphin Mode". For all other images, mipmaps have to be force created in various ways, usually in "Expert Mode".

- Check "Force Create Mipmaps" in Expert Mode which creates mipmaps for all images.
- Include a single dummy mipmap with the image "texture_mip1.png".
- A flag in the name can be used to force a certain number of mipmaps "texture_mm3.png" (always on for PNG, needs "Search Flags" for DDS Format when converting to DDS).

To disable the automatic mipmap generation for Dolphin textures, either check "Disable Mipmap Generation" or set "Max Mipmap Levels" to 0.

(05-06-2019, 09:15 AM)Malkierian Wrote: Also, when trying to run this with the latest CompressonatorCLI, it keeps telling me "Invalid Command Line" over and over again, and if I don't run Powershell as an administrator beforehand, it keeps asking for elevation every time it runs Compressonator.

I'll have to look into this one more. I haven't updated Compressonator in awhile so maybe newer versions are causing issues, but I doubt that is the case. Running PowerShell as administrator I think changes up some things and might bug some stuff out (at least, that is the case with some batch scripts and CMD.exe, they don't work the same or at all when running as an administrator). It sounds like a permissions issue, as anything in "C:\Windows" and anything installed in "C:\Program Files" or "C:\Program Files x86" has this additional, yet annoying layer of protection since I think Windows 8. If your windows user account is not an administrator account I can see this being a problem. An alternative might be to install Compressonator somewhere else, such as the base of "C:\".

Edit: I forgot to add, did you try the included batch script to change the PS Execution Policy to "Unrestricted"? I don't think its as necessary on Windows 10 as some of the older versions (it just asks if you want to temporarily change it), and I don't think it will help with your issue, but it might be worth a try.

[MamiyaOtaru]

It's not possible to use Waifu2x without losing transparency on PNGs

(03-31-2019, 07:39 PM)Bighead Wrote: 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.

Not sure if this precise change has anything to do with it, but with beta 9 I can use waifu2x and keep png transparency. With the release version anything that was transparent comes out just black.

EDIT
release version: Seamless Mode all, Noise_Scale: png loses transparency. Seamless Mode off, Noise_Scale: png retains transparency. Seamless Mode all, Noise: png loses transparency. Seamless Mode off, Noise: image fails to save
beta 9: Seamless Mode all, Noise_Scale: png retains transparency. Seamless Mode off, Noise_Scale: png retains transparency. Seamless Mode all, Noise: image fails to save. Seamless Mode off, Noise: image fails to save

So going from beta 9 to release, waifu2x Seamless Mode Noise_Scale pngs lost their transparency. OTOH we gained the ability to save pngs with Seamless Mode all, Noise (but they still lose transparency) and in neither instance can we get anything from Seamless Mode off, Noise.

[Malkierian]

(05-07-2019, 04:50 AM)Bighead Wrote: I'll have to look into this one more. I haven't updated Compressonator in awhile so maybe newer versions are causing issues, but I doubt that is the case. Running PowerShell as administrator I think changes up some things and might bug some stuff out (at least, that is the case with some batch scripts and CMD.exe, they don't work the same or at all when running as an administrator). It sounds like a permissions issue, as anything in "C:\Windows" and anything installed in "C:\Program Files" or "C:\Program Files x86" has this additional, yet annoying layer of protection since I think Windows 8. If your windows user account is not an administrator account I can see this being a problem. An alternative might be to install Compressonator somewhere else, such as the base of "C:\".

Edit: I forgot to add, did you try the included batch script to change the PS Execution Policy to "Unrestricted"? I don't think its as necessary on Windows 10 as some of the older versions (it just asks if you want to temporarily change it), and I don't think it will help with your issue, but it might be worth a try.

I did run that batch script first thing.  Turns out, it looks like the Compressonator exe is set up to require admin permissions by itself.  Has nothing to do with PS script permissions or folder permissions.  And I don't think I can disable that, it's a flag in the executable itself that is automatically read by Windows.  I honestly don't know why it even needs admin permissions, but perhaps you would be so kind as to look into setting up the script to work in elevated permissions?  In the meantime, I'll try downloading a few older versions to see if they also require admin rights, and how far back this went.

[Malkierian]

Well, nevermind setting it up to work with admin rights, I just tried running their GUI's "Export to batch" output in both a command prompt and a powershell window (with and without admin rights), and get the same thing, so I made an issue on their tracker about it.

[Bighead]

As far as I can tell, the script already works if running as administrator. This version will automatically attempt to run the script as administrator on launch:
http://www.mediafire.com/file/aijtjb451p7rsqk/Custom+Texture+Tool+PS+v40.0-admin.zip

THIS IS NOT AN UPDATE! For everyone else, I do not suggest using it over the normal version as I noticed it does break drag and drop operations and I don't know why. But other than that, everything else seems to work. I was able to scan for issues, convert textures, etc. If for some reason that doesn't work, I think it is possible to run the normal script as admin in this way using the long command below:

Spoiler: (Show Spoiler)

The path to the script would need to be modified in the command. If this fixes your issues, I'll see if I can add an option internally to force running the script as admin. I suppose it will only be possible if the modified script I posted above successfully launches the script as admin as the manual method won't be too helpful in automating the process.

EDIT: Bleh, looks like I missed your post by maybe minutes. Alright then keep me posted on what you find out!

[Bighead]

(05-08-2019, 05:23 AM)MamiyaOtaru Wrote: It's not possible to use Waifu2x without losing transparency on PNGs


Not sure if this precise change has anything to do with it, but with beta 9 I can use waifu2x and keep png transparency. With the release version anything that was transparent comes out just black.

EDIT
release version: Seamless Mode all, Noise_Scale: png loses transparency. Seamless Mode off, Noise_Scale: png retains transparency. Seamless Mode all, Noise: png loses transparency. Seamless Mode off, Noise: image fails to save
beta 9: Seamless Mode all, Noise_Scale: png retains transparency. Seamless Mode off, Noise_Scale: png retains transparency. Seamless Mode all, Noise: image fails to save. Seamless Mode off, Noise: image fails to save

So going from beta 9 to release, waifu2x Seamless Mode Noise_Scale pngs lost their transparency. OTOH we gained the ability to save pngs with Seamless Mode all, Noise (but they still lose transparency) and in neither instance can we get anything from Seamless Mode off, Noise.

I almost missed this post, thank you for the info. This is a bug that has been here before, was fixed (v29.4), was back again, was fixed again (v32.0), and is back again. I was afraid something like this would happen when I made the changes to the seamless method. The upscaling code in its current state has always been very touchy to changes, and the only way to "fix" it properly is to rewrite some of it. Right now the PNG type generated is attempting to be universal, and the best route is probably to make special cases. Since it worked for awhile now, I never bothered to do this. I think that time has come so this issue doesn't keep popping back up.

[Malkierian]

Hey, so there's one thing I've run across, because of the way I structure my folders, could you make it optional whether the image path gathering is recursive? I have to separate images that I've already done, because I want to do them a bit at a time instead of all at once (that way I can enjoy some of the upscaled textures while I play through for the dumps), and I like to keep the "done" folder nested under the folder I select as the texture path, but that will currently be included in the conversions because it's always recursive.

Also, I've noticed another thing. When in Expert Mode, the file list headers are fine, but when you hit start, they revert to what they would be for Dolphin Mode, while still listing the info that would otherwise be there. Screenshot for clarity:
https://i.imgur.com/J7vx2Qv.png

[Bighead]

I really do appreciate the feedback and bug reports! The script has become very complex, my code is awful (but is always improving somewhat), and it is nearly impossible for me to test every single situation when I make changes. So its really easy to miss stuff.

(05-08-2019, 04:29 PM)Malkierian Wrote: Hey, so there's one thing I've run across, because of the way I structure my folders, could you make it optional whether the image path gathering is recursive? I have to separate images that I've already done, because I want to do them a bit at a time instead of all at once (that way I can enjoy some of the upscaled textures while I play through for the dumps), and I like to keep the "done" folder nested under the folder I select as the texture path, but that will currently be included in the conversions because it's always recursive.

I'm a bit cluttered for additional options, so I'm not so sure about disabling directory recursion as it would have limited use. There are other ways to accomplish what you want though.

You can skip processing a directory simply by adding a tilde ~ character anywhere, as long as its in the path to the texture. This is why the tilde is mandatory for the Output Path ~CTT_Generated as it may actually be contained in the "Texture Path", plus it keeps it at the top of the directory. So you could temporarily name your folder "~Done" or "Done~" and the script will never touch anything inside it. Dolphin does not ignore the tilde, so it is okay to keep it that way when loading textures.

If you only want to process a few textures at a time, you can also try the [!] button next to Start. This is called "Process Selected", where you can select or drag and drop textures to process separately from everything else. Although I do think in your case it would be easier to just use a tilde character on your "Done" folder.

(05-08-2019, 04:29 PM)Malkierian Wrote: Also, I've noticed another thing.  When in Expert Mode, the file list headers are fine, but when you hit start, they revert to what they would be for Dolphin Mode, while still listing the info that would otherwise be there.  Screenshot for clarity:
https://i.imgur.com/J7vx2Qv.png

Thanks! I didn't notice this was happening. The new header for "Expert Mode" was completely untested, and I have no idea why it is changing on start, but looks like I'll have to figure it out.

[Malkierian]

(05-09-2019, 02:33 AM)Bighead Wrote: You can skip processing a directory simply by adding a tilde ~ character anywhere, as long as its in the path to the texture

Oooooh, that's good to know.  I can live with that.

[Malkierian]

Ah, here's another one for you: there's actually no way to make a custom output folder name.  You can't pick the folder "~CTT_Generated" goes in, let alone change the name of that folder or the subfolder ("DDS_BC3").  Any changes I make in "Output Folder" text box just revert to the default within the texture folder parent.  Is there any, safe, way you could allow those changes?  Like, right now, I'm experimenting with different mipmap depths, so it'd be nice to be able to rename something to include the number of mipmap levels generated.  If not, that's fine, I'll do it manually, just one of those "would-be-nice" things.