Jump to content

[1.8-1.11] KSPBurst - Burst compiler for Kerbal Space Program

dkavolis

By dkavolis
in KSP1 Mod Development

 Share

Recommended Posts

dkavolis

dkavolis

Posted
Posted (edited)

KSPBurst

Burst compiler for Kerbal Space Program

KSPBurst by itself will not provide any performance benefits. Mods will need to use Unity job system and decorate the jobs with [BurstCompile] to get any improvements.

The Burst compiler is archived to prevent KSP from trying to load its dynamic libraries. The archive is extracted the first time the mod runs to <path to KSP>/PluginData/KSPBurst@<mod version>-<archive name>. Burst standard outputs can be found in <path to KSP>/Logs/KSPBurst/ and KSP.log.

Repository: https://github.com/KSPModdingLibs/KSPBurst/

Installation

Download the latest release from the GitHub releases and extract the archive into your KSP directory. plugins_only version does not contain the compiler, use it only if KSPBurst is a hard dependency and download size is an issue.

Alternatively, KSPBurst can be installed from CKAN using KSPBurst identifier. plugins_only version is indexed as KSPBurst-Lite.

Compiler version requires Mono, you can download it from here.

Burst compiler version can be changed by replacing existing com.unity.burst@<version>.zip archive with a different one. The mod expects the archive to follow <package name>@<package version>.<extension> naming scheme, where <package name> contains burst. If a matching archive was not found, KSPBurst will default to using a compiler matching <path to KSP>/PluginData/*burst*/package/.Runtime/bcl.exe with the greatest package version.

Burst packages can be found here.

Modders

KSPBurst can be bundled with other mods. Bundling plugins_only version will keep the file size down but users will need to download the compiler version for Burst benefits.

Burst compatible Unity plugins and their dependencies are also bundled:

Configuration Options

All configuration options present in KSPBurst.cfg map directly to bcl.exe command line options. If ModuleManager is present, patched options will be used.

Spoiler 



Usage: bcl.exe [options]
       bcl.exe --platform=<platform> --assembly=<PathToAssembly.dll_or_exe> --type=<TypeName>
       bcl.exe --platform=<platform> --assembly-folder=<path1;path2> --method=<FullMethodName[--MethodHash];method2>
       bcl.exe --validate-external-tool-chain --platform=<platform>
      --platform=VALUE       Target Platform <Windows|macOS|Linux|Android|iOS|
                               PS4|XboxOne|Wasm|UWP|Lumin|Switch|Stadia|tvOS>.
                               Default: Windows
      --backend=VALUE        The backend name. Default: `burst-llvm-11`
      --safety-checks        Enable safety checks. Default for safety checks:
                               Disabled
      --disable-safety-checks
                             Disable safety checks. Default for safety checks:
                               Disabled
      --disable-opt          Disable `ir-opt` and `cpu-opt` optimizations
      --fastmath             Enable fast math optimizations
      --target=VALUE         Target CPU <Auto|X86_SSE2|X86_SSE4|X64_SSE2|X64_
                               SSE4|AVX|AVX2|WASM32|ARMV7A_NEON32|ARMV8A_
                               AARCH64|THUMB2_NEON32|ARMV8A_AARCH64_HALFFP>.
                               Can be specified multiple times for enabling
                               more than one target. Default: Auto
      --opt-level=VALUE      Optimization level. Default: 3
      --opt-for-size         Optimizes for size instead of performance. Default:
                                False
      --float-precision=VALUE
                             Precision CPU <Standard|High|Medium|Low> Default:
                               Standard
      --float-mode=VALUE     Math options <Default|Strict|Deterministic|Fast>
                               Default: Default
      --dump=VALUE           Dump flags <None|IL|Backend|IR|IROptimized|Asm|
                               Function|Analysis|IRPassAnalysis|ILPre|All>
                               Default: Function
      --format=VALUE         Object format <Elf|Coff|MachO|Wasm> Default: Elf
      --debugtrap            Inserts a debug trap on the first instruction of
                               the entry point function. Default: False
      --disable-vectors      Disable SIMD Vector types special codegen (float4,
                               float2...). Default: False
      --debug=VALUE          Enables generation of debug info <None|Full|
                               LineOnly> - PDB, DWARF -. Default: None
      --debugMode            Enables debuggability for code generation using a
                               native debugger. Default: False
      --generate-static-linkage-methods
                             Enables the generation of static linkage methods.
                               Default: False
      --generate-job-marshalling-methods
                             Enables the generation of job marshalling methods.
                               Default: False
      --temp-folder=VALUE    The temporary directory to use. Defaults to C:\
                               Users\Username\AppData\Local\Temp\
      --disable-warnings=VALUE
                             Warnings to disable (separated by ;)  e.g. BC1370;
                               BC1322
      --compilation-defines=VALUE
                             Compilation defines to use for building (seperated
                               by ;)  e.g. UNITY_2020_1;NET_2_0
      --linker-options=VALUE Additional settings to be consumed by the native
                               linkers (seperated by ;)
      --enable-direct-external-linking
                             Link external calls directly instead of using
                               burst.initialize. Default: False
      --use-platform-sdk-linkers
                             Use platform compiler tool chains for building
                               desktop platforms (requires MSVC/XCode/Gcc/Clang)
                               , also has no cross platform support : Default:
                               false
      --output=VALUE         Output path for the generated shared library.
                               Default: lib_burst_generated
      --keep-intermediate-files
                             Keep intermediate files along the shared library
                               generated final file. Default: False
      --nolink               Don't link the final object file to a shared
                               library but let the object file to be the output.
                                Default: false
      --no-native-toolchain  Don't look for a native toolchain. Useful if you
                               want to provide your own.
      --emit-llvm-objects    Forces output of object files to be LLVM bitcode
                               rather than native objects.
      --key-folder=VALUE     Key file folder location - required for some
                               platforms. Default:
      --decode-folder=VALUE  Decode folder location - required for some
                               platforms. Default: C:\burst
      --threads=VALUE        Number of compiler threads working concurrently.
                               Default is 13
      --assembly-folder=VALUE
                             Assembly folders (separated by ; or multiple
                               options)
      --method=VALUE         Full methodname with optional hash (separated by --
                               )
      --type=VALUE           A type to decompile all static public methods from.
                                A hash will be generated for each method
      --assembly=VALUE       An assembly path to look for the type
      --group                Start a new group of methods
      --verbose              Display methods being compiled. Default: false
      --root-assembly=VALUE  Root assembly for finding compile target methods
      --include-root-assembly-references=VALUE
                             Recursively scan root assembly references for
                               target methods. If this is false, only target
                               methods from the root assembly will be compiled.
                               Default is True
      --validate-external-tool-chain
                             Don't attempt to build anything, just check that
                               the current target and host are correctly
                               configured for linking
      --patch-assemblies-into=VALUE
                             Produce patched managed assemblies and put them in
                               this folder
      --pinvoke-name=VALUE   Patch assemblies with pinvokes to this name
      --only-static-methods  Compile only static methods and not Execute
                               methods of job producer interfaces
      --method-prefix=VALUE  Add a prefix to the names of generated methods
      --chunk-size=VALUE     Number of methods to compile per threads working
                               concurrently. Default is 3
      --log-timings          Log timings. Default False
      --enable-guard         Enable guard asserts. Default False
      --execute-method-name=VALUE
                             Name of Execute method. Used in DOTS Runtime,
                               where an extra wrapper Execute method is
                               generated.
      --print-monopinvokecallbackmissing-message
                             Print a warning if a compiled function pointer is
                               missing MonoPInvokeCallbackAttribute (needed for
                               IL2CPP). Default: false
      --output-mode=VALUE    Output mode <SingleLibrary|LibraryPerJob> Default:
                               SingleLibrary
      --always-create-output=VALUE
                             Always create output library. If this is false and
                               no target methods are found, no output library
                               will be created. Default True
      --cache-directory=VALUE
                             Cache directory. Default
      --only-list-methods    Only list the methods to compile. Outputs like '
                               assembly.dll, method'. Default False
      --pdb-search-paths=VALUE
                             A semicolon seperated list of paths to search for
                               pdbs, in addition to the same folder as the
                               assembly.
      --warmup               Run a warmup pass of the compile to amortize the
                               cost of the JIT Compile. Default False
      --help                 Show Help

 

Building

Prerequisites

  1. KSP installation
  2. python
  3. Unity Editor 2019.2.2f1 (if building Unity packages)

Configuration

Tools read mod configuration options from config.json, users should create config.json.user and override the values there:

Option Description
unityBuildDir relative path to unity project build directory
kspMin minimum compatible KSP version
kspMax maximum compatible KSP version
version KSPBurst version
versionTemplate relative path to version template file
unityPackages list of bundled unity packages
unityDependencies list of managed plugins that unity packages depend on

Tools

tools contains python scripts:

Script Description
post_build.py copy libraries to the mod directory, archive the Burst package if it exists and copy the mod to KSP installation
version.py update version information in source files and ReadMe
package.py package mod into an archive at archives/, outputs 2 versions, one with and one without the Burst compiler

Building the Mod

  1. Clone KSPBurst

  2. Create Directory.Build.props.user in the root directory with 

    <Project>
  <PropertyGroup>
    <KSP_DIR>path to KSP</KSP_DIR>
  </PropertyGroup>
</Project>

    Depending on the platform you may also need to set DATA_DIRNAME to match your installation.

  3. If not building Unity packages, go to to step 7

  4. Open Unity project at Unity/KSPBurst in Unity Editor

  5. Build the Unity project and note the build directory

  6. Create config.json.user in root directory with 

    {
  "unityBuildDir": "<relative path to unity build directory in step 5>"
}

     

  7. Build KSPBurst with your IDE or from command line, the mod will be copied your KSP installation. If the burst package is present in Unity directory, it may take a while to archive it the first time.

License

Unity plugins are licensed under under the Unity Companion License for Unity-dependent projects--see Unity Companion License.
KSPBurst is licensed under the MIT license

Notes

System.IO.Compression and System.IO.Compression.FileSystem plugins are used for archive decompression and are bundled with Unity Editor.
NuGet package Microsoft.Extensions.FileSystemGlobbing is used for glob pattern matching.

Edited by dkavolis
Link to comment
Share on other sites
  • 2 months later...
  • 3 months later...
  • 2 months later...
linuxgurugamer

linuxgurugamer

Posted
Posted

If you took a minute to look at the log file, you would have found this:

Spoiler 
[KSPBurst]: Burst stdout:
Options processed in:                44ms
UpdateObjectFormatFromPlatform:       1ms
new BclApp:                         110ms
Backend Reload:                       0ms
Methods to compile:                 990ms
    Create Threads:                               3ms
    Schedule Compilations:                        0ms
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

[KSPBurst]: Burst stderr:
Error while executing command: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp"
Unhandled Exception: Burst.Compiler.IL.Aot.AotLinkerException: The native link step failed Error while executing command: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp". Check previous exception in the log - linker command line : "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp""
   at Burst.Compiler.IL.Aot.AotNativeLinkBase.RunNativeLinkerTool(String command, String arguments, String errorMessage, String commandType, String workingDirectory, Boolean muteOutputs)
   at Burst.Compiler.IL.Aot.AotNativeLinkLLVMWindows.Link(TargetCpu targetCpu, List`1 inputFiles, String outputFile, Boolean enableDebugInfo)
   at Burst.Compiler.IL.Aot.AotCompiler.Link(List`1 groups, String nameSuffix, AotCompilerOptions compilerOptions, TextWriter consoleOut, TextWriter consoleError)
   at Burst.Bcl.BclApp.LibraryThread.Process(LibraryCompilationRequest libraryRequest)
   at Burst.Bcl.BclApp.LibraryThread.Run()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

 

I have no idea what KSPBurst is, and am not about to do any more research into this.  

I suggest you do the following:

Backup your entire game directory.  This can be done easily by opening up the directory:

C:\Program Files (x86)\Steam\steamapps\common

and moving the Kerbal Space Program directory onto your desktop

Then, use Steam to reinstall it.

Finally, use CKAN to install your mods, a few at a a time, and testing after each install.

Assuming that you manage to get all the mods installed via CKAN that are available via CKAN, make a full backup/copy of the enter game.

Then, install the mods which aren't available, one at a time, and test after each install

If it fails at any of the times you try starting the game, you should have a good idea of the problem.

 

This is NOT a problem with this contract pack, I'm going to ask the moderators to move this into a new thread.

 

Link to comment
Share on other sites
Angelo Kerman

Angelo Kerman

Posted
Posted
9 hours ago, MirrorsareHard154 said:

https://we.tl/t-d4w3v6CTc1

Nevermind it still brokey, pressing any button, at least once I get to the main menu, KSP never likes inputs when its loading in the first place, still crashes

 

8 hours ago, linuxgurugamer said:

If you took a minute to look at the log file, you would have found this:

  Reveal hidden contents 
[KSPBurst]: Burst stdout:
Options processed in:                44ms
UpdateObjectFormatFromPlatform:       1ms
new BclApp:                         110ms
Backend Reload:                       0ms
Methods to compile:                 990ms
    Create Threads:                               3ms
    Schedule Compilations:                        0ms
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

[KSPBurst]: Burst stderr:
Error while executing command: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp"
Unhandled Exception: Burst.Compiler.IL.Aot.AotLinkerException: The native link step failed Error while executing command: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp". Check previous exception in the log - linker command line : "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\PluginData\[email protected]@1.5.5\package\.Runtime\hostwin\lld -flavor link "@C:\Users\Alan Mcghie\AppData\Local\Temp\tmp3396.tmp""
   at Burst.Compiler.IL.Aot.AotNativeLinkBase.RunNativeLinkerTool(String command, String arguments, String errorMessage, String commandType, String workingDirectory, Boolean muteOutputs)
   at Burst.Compiler.IL.Aot.AotNativeLinkLLVMWindows.Link(TargetCpu targetCpu, List`1 inputFiles, String outputFile, Boolean enableDebugInfo)
   at Burst.Compiler.IL.Aot.AotCompiler.Link(List`1 groups, String nameSuffix, AotCompilerOptions compilerOptions, TextWriter consoleOut, TextWriter consoleError)
   at Burst.Bcl.BclApp.LibraryThread.Process(LibraryCompilationRequest libraryRequest)
   at Burst.Bcl.BclApp.LibraryThread.Run()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

 

I have no idea what KSPBurst is, and am not about to do any more research into this.  

I suggest you do the following:

Backup your entire game directory.  This can be done easily by opening up the directory:

C:\Program Files (x86)\Steam\steamapps\common

and moving the Kerbal Space Program directory onto your desktop

Then, use Steam to reinstall it.

Finally, use CKAN to install your mods, a few at a a time, and testing after each install.

Assuming that you manage to get all the mods installed via CKAN that are available via CKAN, make a full backup/copy of the enter game.

Then, install the mods which aren't available, one at a time, and test after each install

If it fails at any of the times you try starting the game, you should have a good idea of the problem.

 

This is NOT a problem with this contract pack, I'm going to ask the moderators to move this into a new thread.

 

Hey folks, I've moved your posts over to this thread, which appears to be for KSPBurst.

Link to comment
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...