Custom Texture Tool PS v46.2

[Techie Android]

(02-10-2017, 05:58 AM)Bighead Wrote: Sorry I wasn't sure what you meant by "point tool" but now I understand. I still can't reproduce the issue but I think I know what's going on. Let me know if this fixes your issue:
https://mega.nz/#!e4wxXBRC!pURX4XLIwgdRuL_8t38BYTb4tSGn-JAs81tWbFjpkBM

Yeah now that I think about it I should've said the point option, which would've been more accurate since it's technically not a tool.
Unfortunately I'm in the middle of something at the moment. I'll check as soon as I get done. Thanks.

[Techie Android]

I think the bug is gone so whatever you did fixed it. Thanks a lot!

[Bighead]

So I'm up to v19.0, going the Firefox update route. Hopefully the last one for awhile:
Download - Mirror

The goal this time was to get the speed back when analyzing PNG images. Images are analyzed no matter what option is used, so this helps out everywhere. The reason I converted the batch script to PS in the first place was to create a faster script, but as time went on my prospects changed to "making better images". Now I want it all. Long ago I tested the speed of v1.0 when analyzing the HD Paper Mario:TTYD pack compared to the batch version. These days it was even slower than the batch version. So now retesting with this version compared to v18...

v1.0   - 02:18
v18.0 - 17:27  (yikes!)
v19.0 - 03:56

So v18 is almost 9x slower than v1 was, but most of that speed is back in v19. The PM:TTYD pack is also much larger now than it was then, and the script does more stuff, so it's fair to say I've almost recovered all of the lost speed. It will never be quite as fast as before because - more stuff. The main culprit was relying on ImageMagick for so many things. After several days of grueling education, I figured out ways to get the same data I need without having to rely on ImageMagick, which offered a significant performance boost. Various other little tweaks also helped to not do stuff that doesn't need doing. Working with DDS packs is still much slower, and I doubt I'll put the time into learning how to make it faster anytime soon.

Edit: Re-uploaded because by default I had "Disable Stored Options" checked. I use this option when testing stuff so Notepad++ doesn't spam me it changed.

[Techie Android]

(02-11-2017, 08:47 AM)Bighead Wrote: So v18 is almost 9x slower than v1 was, but most of that speed is back in v19. The PM:TTYD pack is also much larger now than it was then, and the script does more stuff, so it's fair to say I've almost recovered all of the lost speed. It will never be quite as fast as before because - more stuff. The main culprit was relying on ImageMagick for so many things. After several days of grueling education, I figured out ways to get the same data I need without having to rely on ImageMagick, which offered a significant performance boost. Various other little tweaks also helped to not do stuff that doesn't need doing. Working with DDS packs is still much slower, and I doubt I'll put the time into learning how to make it faster anytime soon.

That's awesome. If you ever learn Python or C++ it will probably be even faster, because in Python the interpreter doesn't need to reanalyze or reparse each source. C++ will probably be the fastest because it's a traditionally compile language. Python also has great memory management. It automatically allocates and reclaims ("garbage collects") objects when no longer used, and most grow and shrink on demand. Python will keep track of the low-level memory.

[DarthVitrial]

For some reason the GUI doesn't display for me.
Screenshot: http://imgur.com/a/wMOT1

Is it because I have a 3K monitor? DPI scaling might not be working on this tool.

[Techie Android]

(02-14-2017, 10:56 AM)DarthVitrial Wrote: For some reason the GUI doesn't display for me.
Screenshot: http://imgur.com/a/wMOT1

Is it because I have a 3K monitor? DPI scaling might not be working on this tool.

That is the GUI. And yes Windows is not scaling it properly at that resolution. As a fix some people edit the application in their registry to scale it at a different resolution.

[Bighead]

Oh neat, I didn't even know this was a thing. I think I may have read something about it somewhere at one point but I was like "who cares about this kind of stuff". Thanks for bringing it to my attention. I'll see what I can do to fix it if possible.

---

Edit: New version with a really bad workaround:
Download - Mirror

If you can make it to the options panel, there is a dropdown menu called DPI fix. If you can't make it there, edit the script with a text editor and find line 33.
$global:FontScaleLevel     = "0"

It accepts 4 possible values, what to choose depends on windows scaling:
0 - normal
1 - 125% scaling
2 - 150% scaling
3 - 175-200% scaling

There are some issues. It doesn't actually scale anything up, only down, so the window may appear very small. Group boxes get cut off, I can't figure out why. All options should at least be readable, although with the group box bug it might not be clear what some of them are. This is probably as good as it gets, I'm not talented enough to fix it without rewriting the entire GUI.

---

Meh, I wasted a few hours with my only reward being a migraine.
Download - Mirror

It's ironic that after all the time I spent trying to figure out the issue, work around it, and make this post, I figure out the source of the problem not even an hour later. It was the way I was setting the icon of all things. I learned how to create an icon from a base64 string by following a post on the web that used a "BitmapImage" type, which was the only instance of it in the entire script. Now that I know enough to do it myself in a different way, it turns out using a regular "Bitmap" does not have this problem. Maybe something to do with Windows Presentation Foundation trying to take over the layout which I know nothing about. I can only guess...

Removing that now allows the GUI to properly scale when Windows scaling is set to 150% or higher, but it will be fuzzy due to upscaling. Setting to 125% will still have issues. I found this comment on the matter:

At 150%, Windows takes over the scaling and will let your window draw itself into a bitmap. It then renders that bitmap to the screen, rescaling it to make it bigger. Yes, that looks fuzzy, you have to declare yourself dpiAware to stop that.

After looking more into it, to make this script "DPI Aware" is currently way beyond me, nor does it feel worth the effort just to have a clearer looking window. Plus I don't even know if it's possible using Powershell, I'd most likely have to learn something better. So this is now as good as it gets which is way beyond the previous junk. It's probably possible to tweak some stuff for 125%, that much I will try to do something about.

[Bighead]

Something I added in v20.0 (because I always wanted it) but forgot to mention because I became sidetracked with those scaling issues is the ability to process manually selected textures. This can be done by highlighting the "Standard Option" you wish to use, holding Control, and pressing the "Start" button. A menu like this should come up.



It's possible to just drag and drop textures into the window from anywhere or click to manually add them to the array. They don't even need to be in the same folder, and it will work for PNG, DDS, or JPG textures. Any number of textures can be added, and a number is displayed showing how many have been added. It's also possible to use the arrow buttons to look through them for whatever reason before processing. 



There is no way to remove textures from the array other than pressing X and starting over. Mostly because I'm too lazy, as this was originally designed to do a single texture but a "bug" allowed me to keep adding them and process as many as I added. So, I decided to roll with it and made it somewhat fancier. The output path can also be changed here, but this is only temporary as it just affects this single run. After the textures are processed or the "X" button is clicked, the output path will once again be whatever is selected as the "Output Path" on the main window.

That's it for now, hopefully for a long while anyway.

EDIT: Process Selected has had a huge upgrade since.

[BennyAlex98]

When setting material map format from iirushka to dolphin, following error occurs:

Get-Variable : Es kann keine Variable mit dem Namen "Dolphin" gefunden werden. (eng: theres no variable with name 'Dolphin')
In D:\Bildbearbeitung\Custom Texture Tool PS v21.0\Custom Texture Tool PS v21.0.ps1:6090 Zeichen:19
+ $NewValue = Get-Variable -Name $this.SelectedItem -ValueOnly
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Dolphin:String) [Get-Variable], ItemNotFoundException
+ FullyQualifiedErrorId : VariableNotFound,Microsoft.PowerShell.Commands.GetVariableCommand

[Bighead]

Wow I'm a noob, I don't even know how that got by me for so long. Thanks for pointing it out, it only hasn't worked since v12. It's a niche option that broke when changing it to have "Format" in the name, since I use a generic check for all combo boxes to change between PNG, DDS, JPG, and null. And since this option has none of these in the list, that error comes up and says hi.

Edit: While working on fixing some stuff in the Xenoblade pack, I discovered I created a horrible bug with the last "fix". Images would come out as "tex1_yadayada_4PNG" instead of "tex1_yadayada_4.png" when changing the output format. Ugh, hopefully this is it for awhile....

v21.2
Download - Mirror