Skip to content

Lord-Akkrand/Skyrim-NX-Toolkit

Repository files navigation

Skyrim NX Toolkit

External Tools and Credits

There are several external tools that are used by my scripts to get things done.

There are further external tools that the toolkit will attempt to download if you don't have them in the Utilities directory, or that you must source yourself. These tools are:

  • ffmpeg.exe https://ffmpeg.zeranoe.com/builds/win64/static

  • nvddsinfo.exe https://github.com/castano/nvidia-texture-tools/releases

  • textconv.exe https://github.com/Microsoft/DirectXTex/releases

  • texdiag.exe https://github.com/Microsoft/DirectXTex/releases

  • HavocBehaviourPostProcess.exe is available from the Bethesda Creation Kit. It is necessary to convert any mod that has animations in it, and you are also required to have a 32-bit version of those animation files in order to perform that conversion. If you have the CK, you need to copy Tools\HavokBehaviorPostProcessHavocBehaviourPostProcess.exe to the Utilities directory in the Skyrim-NX-Toolkit.

    • It won’t convert skeleton and skeleton_female files. Get them from XPMS Switch version on Nexus
    • It won’t convert files in behaviors folders. Only occurrence I found in all SSE mods so far were in USSEP and FNIS. You can fish 32 bit equivalent
    • FNIS based mods can regenerate their behavior files in 32 bit by using the “Generate Behavior for Modders” tool included in FNIS oldrim

Running in Python

All my scripts were written in Python 3.x, then packaged into an exe using PyInstaller. If you have Python 3.x (and Python Launcher, or 'py') accessible from your command line, you may run the scripts directly if you like. You can get Python here:

Examples

There are Examples listed in the "Examples" directory. They are filled with dummy mod files, but you should be able to run them and they should produce the appropriate output. Most of the scripts can be used by dragging a directory onto them, but I prefer to run them from the command line in case there's an error whilst in the batch file, so you can see it before the window disappears. The examples all show proper command line usage.