Does anyone have a recommendation for the settings other than the resolution.
I mean the setting that should bring the most stable result when editing the textures with the Texture Optimizer.

Just use the default settings 

@MammyJammy Hoping you are still around.. I'm trying to add mips with your tool to a bunch of unoptimised textures but the tool keeps resizing all of the textures below the specified size (4096). i.e. It is resizing all of the textures in the folder to 4096x4096. 

I thought it was supposed to ignore anything smaller than the specified size?

Original files

Edited Files

Edited August 24, 20232 yr by toby23

@MammyJammy Are you still around?

I stopped compressing the files as you'll come across a ton of errors while downsizing (97 compression errors to be exact).

I didn't notice any issues in game, but I'd rather just leave the files alone as space and performance is no longer an issue for me.

Edited September 6, 20232 yr by blueshark747

4 hours ago, blueshark747 said:

I stopped compressing the files as you'll come across a ton of errors while downsizing (97 compression errors to be exact).

I didn't notice any issues in game, but I'd rather just leave the files alone as space and performance is no longer an issue for me.

I'm still doing it following @MammyJammy's instructions and don't get any errors.

On 8/24/2023 at 5:38 AM, toby23 said:

Hoping you are still around.. I'm trying to add mips with your tool to a bunch of unoptimised textures but the tool keeps resizing all of the textures below the specified size (4096). i.e. It is resizing all of the textures in the folder to 4096x4096. 

I thought it was supposed to ignore anything smaller than the specified size?

It appears there's a small bug in how image metadata is being captured prior to processing - Likely emerged when I changed the processor architecture to speed it up a few revisions ago.  It's not a terribly difficult fix and I'll get to it when I have some time over the next few weeks.  I'll add a new switch to the config to allow for forcing all vs. skipping smaller as well.

On 9/6/2023 at 2:11 PM, blueshark747 said:

I stopped compressing the files as you'll come across a ton of errors while downsizing (97 compression errors to be exact).

What were the errors captured in the error log?  They would be helpful in identifying any improvements to the compression algorithms being used.

19 hours ago, MammyJammy said:

It appears there's a small bug in how image metadata is being captured prior to processing - Likely emerged when I changed the processor architecture to speed it up a few revisions ago.  It's not a terribly difficult fix and I'll get to it when I have some time over the next few weeks.  I'll add a new switch to the config to allow for forcing all vs. skipping smaller as well.

 

That would be nice. Apart from that, your optimizer works great. Thanks for your work!

Hi All,

I've just published a new version (1.4) of my Texture Optimizer tool.  This version fixes the processor architecture issue that was causing smaller images to be incorrectly processed.

Requires uninstall/reinstall of the Texture Optimizer.  The directions are available at: https://izn-flightsim.s3.amazonaws.com/textureoptimizer.html.  NOTE:  If you have Compressonator and TexConv already installed, you do not need to reinstall them.

Change Log:

• New Features:
  • New optional parameters for resizesmaller and reformatsmaller that allows for custom control of how smaller images are handled.
  • Continued performance enhancements
• Bug Fixes:
  • Architecture fixes to support proper handling of images smaller than the target resolution that is specified.

Please read the linked guide for information on how the tool works, including the new optional parameters.  By default, images smaller than the target resolution specified will not be resized, however they will be reformatted according to the processing specified when it is run.  If -dxt is set to "auto" (or left to default...It's a purely optional parameter), smaller images will be reformatted and mipmaps added as determined by the algorithm.  Said another way, -resizesmaller defaults to false, -reformatsmaller defaults to true.  I would highly recommend leaving these as they are.

I haven't tested this heavily...I don't have time.  I ran it against an FSLTL package and it seemed to work fine.  YMMV.

Thank you for fixing the utility @MammyJammy

Edited September 30, 20232 yr by toby23

please delete

Edited October 1, 20232 yr by toby23

Hi @MammyJammy,

After using Texture Optimizer to resize the FSLTL textures again today after the new FSLTL model update (which got my folder from 37,9GB to 13,9GB 😉) I got this on the log after converting:

Quote

END FILE WARNINGS #################################################################################
BC2
BC1
BC3
BC5
BC7
BC5_S

 

Do you know what this is?

Thanks.

 

 

Edited December 9, 20232 yr by Alvega

Thanks for this tool, currently doing it with FSLTL as I strive for more FPS, selected 1024 for size so that should help somewhat.

13 minutes ago, MarcG said:

Thanks for this tool, currently doing it with FSLTL as I strive for more FPS, selected 1024 for size so that should help somewhat.

Can't understand why the FSLTL devs insist on just providing 4K textures (some are even 8K) for AI traffic. It's ridiculous, not everyone has a 16GB or 24GB GPU, many still use 6GB or 8GB.

3 minutes ago, Alvega said:

Can't understand why the FSLTL devs insist on just providing 4K textures (some are even 8K) for AI traffic. It's ridiculous, not everyone has a 16GB or 24GB GPU, many still use 6GB or 8GB.

Yeah a choice of Download size would be nice, I went too low with 1024 so redoing them at 2048!