Version 2.10.0

Added support for providing custom mip images to override the default generated mipmaps with -m/--mipmap. This can be done either with providing the -M/--custom-mip command-line argument one or more times or by passing a text file with --custom-mip-list with one entry per line. Each custom mip has the following parameters provided:

• Mip level to replace. (required)
• Depth to replace. (optional, defaults to 0) When used with a 3D texture, all depths for a given level must be replaced, while array textures can have individual depths replaced or left as default.
• Cube face to replace as +/-xyz. (optional, defaults to +x) When used with a non-cubemap texture, only +x is valid to use.
• How to use the image for subsequent mip levels for the same depth and cube face. May be either once to switch back to the previous image or continue to keep using the new image. (optional, defaults to continue)
• Path to the image to use. (required)

The images for custom mips will go through the same transformation steps (e.g. swizzle, flip, rotate, normalmap generation, etc.) as the main input images and resized to the appropriate size for the mip.

Windows builds can now load Unicode file paths, utilizing the UTF-8 codepage. This provides parity with the macOS and Linux builds, where the systems already used UTF-8 for Unicode support.

No longer prints full help output when an invalid option is provided. Full help output is still provided when no options are given.

Updated GLM to the latest version.

Binaries are provided for the following platforms:

• Linux (glibc 2.35 or later) (x86-64) (e.g. Ubuntu 22.04)
• macOS 10.14 or later (x86-64/arm64 universal binary)
• Windows (VS 2017 runtime) (x86 and x86_64) Each has two separate artifacts:
  • "full" release, which includes the debug and release libraries that may be linked to by other applications. This will require the Visual Studio redistributable to be installed.
  • "tool" release, which includes only the tool. It is statically linked and uses the static runtime, which means it will run without the Visual Studio redistributable installed.

Note: When using the pre-built binaries on Mac you may need to allow execution of the executable and libraries under the "Security & Privacy" control panel. You may also add specific apps (such as Terminal) to the "Developer Tools" option in the "Privacy" section to allow running unsigned code without prompts.