VectorSlopeCLI.exe sits next to VectorSlope.exe and does the
same export without a window, for whole folders at a time. It uses the same code as the
window, so the maps are the same. The Command line button in the program shows
every option, with a Copy button. Run it from a terminal.
# a whole folder with a saved preset, into the game's Art folder
VectorSlopeCLI.exe --in textures --preset brick.json --maps normal,ao --yes
# one file, to a folder of your choice, with MTM2 style off
VectorSlopeCLI.exe --in brick.tga --out maps --no-mtm2 --name normal={stem}_nrm
# see what would be written, and the warnings, without writing anything
VectorSlopeCLI.exe --in textures --recursive --dry-run
| Option | What it does |
|---|---|
--in <path> | a PNG, TGA, JPG or RAW file, or a folder of them (repeatable) |
--recursive | also read the subfolders of an input folder |
--out <dir> | the output folder (needed without a game folder, or with --no-mtm2) |
--extras <dir> | the folder for _S and _D under MTM2 style |
--game <dir> | the MTM2 folder (default: the one the window uses) |
--preset <file> | generator settings saved from the window |
--maps <list> | normal, ao, spec, disp (default: normal) |
--format png|tga | the output format (default PNG) |
--mtm2 / --no-mtm2 | MTM2 style on or off |
--name <map>=<pattern> | a file name pattern with {stem}, MTM2 style off only |
--ao <file> / --ao-dir <dir> | your own AO, for one file or matched by name across a folder |
--dry-run | list the files and warnings; write nothing |
--yes | confirm writing into the game's Art folder |
--overwrite | replace existing files |
y/N; only --yes answers it for you. Existing files are skipped
unless you pass --overwrite. --dry-run writes nothing. Output
folders are created if missing, but the game's Art folder never is. If several inputs
share a name in one folder, only the one the game would load is exported (PNG, then
TGA, RAW, JPG).
Exit codes: 0 all went well; 1 to 63 the
number of files that failed (a skipped file is not a failure); 64 a usage
error, including a refused confirmation; 70 the graphics context could not
be created, or something unexpected went wrong.