Once you are in the proper directory on the command line, use of the Texture Optimizer is as follows:

textureoptimizer <source folder> <image resolution> 

A complete command line example:

textureoptimizer "D:/MSFS/Community/fsltl-beta-airplanes" 2048 

https://izn-flightsim.s3.amazonaws.com/textureoptimizer.html

Edited October 15, 20223 yr by toby23

19 minutes ago, derex17 said:

@toby23

As you can see in the picture, I get an error message after pressing the enter key.
Incorrect spelling or path not found.
Can you help me with this problem?

 

https://drive.google.com/file/d/1sbZ7YtBKpjyVgF3VwK22Sl9Ujk8nuWXV/view?usp=sharing

https://drive.google.com/file/d/1hCz14Ebh_9Zak9tw0kV6AYOCKHIpJ14H/view?usp=sharing

Check your UserCfg.opt file for the correct community folder path. Open the file with notepad and check the last line. I don't think you are inserting the correct path.

Also, as toby23 said, you need to put textureoptimizer before the path.

@toby23 and Alvega

Thank you to you two. With your help it worked now. @Alvega, they were right of course, the correct path must start with C:/Users...

Unfortunately, my English isn't the best either,

and I'm thankful that this is tolerated by most members in the forum.

Many Thanks

Wish there was a video on how to use this. There are some gray areas that need more explanation. Command lines can be tricky and if your not used to using them, daunting. 

Hi All,

I've just published a new version (1.3) of my Texture Optimizer tool.  This version addresses several issues in 1.2 and adds a bunch of new optional parameters that allow you to fine-tune how you want optimized textures generated.

This new version requires the DirectX tool TexConv, which is linked in the updated installation guide.  Also, the command line parameters have changed slightly to allow for named parameters, which helps support further customization of the tool.  Installation and User Guide updated to include information on both of these items.

Available at: https://izn-flightsim.s3.amazonaws.com/textureoptimizer.html

Change Log:

• New Features:
  • New optional parameters for mipmaps, DXT mode generation, and debugging info
  • Resolution settings expanded to 256
  • Named command line attributes and better help
  • Approx. 4x improvement in texture generation speed
• Bug Fixes:
  • Mipmaps not being generated on optimized textures
  • Possible corruption of alpha channels on BC7, ATSC, and ATI* compressed DDS textures
  • Improved support for various formats that would cause unloadable texture warnings

I still have some work to do on improving the texture exporting to support more advanced and higher quality texture compression formats, but 1.3 is a big improvement in speed and features.

10 minutes ago, MammyJammy said:

Hi AllI've just published a new version (1.3) of my Texture Optimizer tool. 

I'm aware of the opinions on mipping Normal maps but does this version now add them, seeing as how it can repair/correct them ? Also, does it correct incorrect texture sizing like Ordenador does?

Really appreciate you updating and sharing this tool. Saves me a lot of time, headaches, random crashes and HDD space.. Thank you 

Edited October 17, 20223 yr by toby23

3 minutes ago, toby23 said:

I'm aware of the opinions on mipping Normal maps but does this version now add them, seeing as how it can repair/correct them ? Also, does it correct incorrect texture sizing like Ordenador does?

Yes, it adds them.  In the user guide you will see new parameters to force mipmaps on or off, or use the auto setting which will intelligently create them based on a number of input texture and output resolution criteria.  Give the User Guide a read to get the deets. 

As for resizing, it will correctly size based on the output size you supply if the input image is larger.  I have on my list an item to handle the correct power-of-two issue, however I haven't hit a texture in the FSLTL package I've been testing that is problematic on that front.

28 minutes ago, MammyJammy said:

Yes, it adds them. 

As for resizing..

Great news, thank you. It's not so much the FSLTL textures, as I fixed those with your tool and Ordenador, more the 4k and 8k freeware and payware addon textures, that don't follow the official guidelines and that, as a result, can cause random crashes that I'm more concerned about. Ordenador fixes the scaling issues but it would be great to have it all in one tool.

Regarding the improved speed, I had thought that you were somehow restricting the processing speed to remove the margin for unexpected errors?

Thank you 

Edited October 17, 20223 yr by toby23

25 minutes ago, MammyJammy said:

In the user guide

HUGE speed improvement, much appreciated MammyJammy

13 minutes ago, toby23 said:

HUGE speed improvement, much appreciated MammyJammy

Did you use mipmap auto or on?

9 minutes ago, Alvega said:

Did you use mipmap auto or on?

I didn't change any of the default settings. Mipping set to auto by default I believe.

1 minute ago, toby23 said:

I didn't change any of the default settings. Mipping set to auto by default I believe.

Are you sure it does the mipmaps if we don't use -mipmaps auto or on? I'm not sure, so I'm going to use -mipmaps auto.

52 minutes ago, MammyJammy said:

Yes, it adds them.  In the user guide you will see new parameters to force mipmaps on or off, or use the auto setting which will intelligently create them based on a number of input texture and output resolution criteria.  Give the User Guide a read to get the deets. 

As for resizing, it will correctly size based on the output size you supply if the input image is larger.  I have on my list an item to handle the correct power-of-two issue, however I haven't hit a texture in the FSLTL package I've been testing that is problematic on that front.

Thank you for sharing this,

I just had my first CTD with resized textures in FSLTL. I will give this a go once I am back on the ground 🙂 

1 minute ago, Alvega said:

Are you sure it does the mipmaps if we don't use -mipmaps auto or on? I'm not sure, so I'm going to use -mipmaps auto.

Only -source and -resolution are required.  All other have defaults that are listed in the User guide.  Also, If you want to see the default options from the command line, just type:

textureoptimizer -h

It will spit out the following:

usage: TextureOptimizer [-h] -resolution {4096,2048,1024,512,256}
                        -source SOURCE [-mipmaps {auto,on,off}]
                        [-dxt {auto,DXT1,DXT3,DXT5}]
                        [-debuginput {true,false}]
                        [-debugoutput {true,false}] [-global GLOBAL]

Texture Optimizer for MSFS and Prepar3D (ideal for AI aircraft)

named arguments:
  -h, --help             show this help message and exit
  -resolution {4096,2048,1024,512,256}
                         The desired resolution of the output texture files
  -source SOURCE         Directory   containing   source    texture   files
                         (includes sub-directories)
  -mipmaps {auto,on,off}
                         Mipmaps generation - On  or  off forces choice for
                         ALL textures (default: auto)
  -dxt {auto,DXT1,DXT3,DXT5}
                         DXT/DDS Output - Non auto  options force output to
                         selected DDS format (default: auto)
  -debuginput {true,false}
                         Write debug information  for  each  source file to
                         the console (default: false)
  -debugoutput {true,false}
                         Write debug information  for  each  output file to
                         the console (default: false)
  -global GLOBAL         CURRENTLY EXPERIMENTAL - DO  NOT  USE YET.  Global
                         texture  directory,  if  one  exists  (will  avoid
                         generation of textures identical  to those located
                         in this directory)

 

5 minutes ago, Alvega said:

Are you sure it does the mipmaps if we don't use -mipmaps auto or on? I'm not sure, so I'm going to use -mipmaps auto.

Yes I am sure that it adds them. You can always check or look at the filesize. See my older mipmapping guide for more information.

Edited October 17, 20223 yr by toby23