Official Tools

From Space Engineers Wiki
Jump to navigation Jump to search

Included Tools

In the game's install folder there is a Tools folder that contains various things to help with modding.

  • xWMAEncode.exe - commandline program to convert .wav to .xwm or vice-versa.
  • AdpcmEncode.exe - commandline program to change a .wav from PCM to ADPCM or vice-versa.
  • DilationForm - unknown
  • Fonts - for making custom fonts, clone Options_dialog.txt and MakeFontDataDialog.bat then edit them accordingly. Or see the archived official guide.
  • Space texture converter - a quick and dirty way of converting old DX9 textures to DX11 (not recommended).
  • TexturePacking folder:
    • Tools/texconv.exe - a commandline program to convert images to .dds or vice-versa.
    • Tools/texassemble.exe - a commandline program to pack multiple .dds into one, used for skybox for example.
    • TexturePacking.exe - for packing multiple textures into one (like color and metalness into a single _cm), files or folders are fed by dragging and dropping, and files are expected to have specific suffixes mentioned in the selected profile.
  • VRageEditor folder:
    • AnimationController.bat - a visual editor for the animation controller SBC. Also hooks in the game and highlights currently playing nodes.
    • BehaviorTree.bat - a visual editor for AIBehavior.sbc.
    • ModelBuilder.bat - a GUI for the MWMBuilder listed below.
    • Plugins/ModelBuilder/MwmBuilder.exe - a commandline program to pack .fbx+.xml+.hkt into .mwm files.
    • ModelViewer.bat - a viewer for .mwm files, official guide.
    • VisualScripting.bat - a visual node editor for scenarios, see Visual Scripting Tool for more info.

Mod SDK

There's a Space Engineers - Mod SDK in your Steam library, in the Tools section.

Official info on the SDK: Modding - ModSDK

It contains:

  • Bin64_Profile - a special build of the game that enables F12 debug menu and profiling tools. Guide.
  • OriginalContent - source .fbx/.hkt/.xml files for the models, including DLC ones (read the OriginalContent/Models/readme.txt on rules about DLC content).
  • Tools - the same tools mentioned above in Included Tools.

How to use commandline programs

  1. In the folder where the program is, shift+right click (not on anything, do it as if you want to refresh).
  2. Then pick PowerShell or CommandLine or Terminal or whatever other kind of command line interface Windows has at the time.
  3. Then type the program's name followed by its arguments.

The arguments it expects depends on the program.
Usually running it without any arguments will print the help text, other programs expect a /? or --help argument.