Skip to content

Releases: KSP2Community/LFO

v1.0.0

20 Nov 00:27
Compare
Choose a tag to compare

After a lot of refactoring, rewriting, and upgrading of the base systems of both the LFO runtime mod and the editor package, and adding many new features to the editor package, LFO is finally dropping the 0.x version number and getting its first stable 1.0 release.

Notable changes:

  • Added support for the loading of assets from addressables. Your mod can now add custom meshes and textures for use with LFO plumes using this system.
  • Added support for the loading of plume JSON configs from addressables. This means plumes can now be patched using Patch Manager. Plumes made with previous versions will be registered as addressable assets at runtime, meaning that even plumes made in pre-1.0 versions can be patched.
  • Many changes to the LFO Unity editor package, which can be installed in the Unity Package Manager from Git URL: https://github.com/KSP2Community/LFO.Editor.git

Known issues:

  • Using the SORRY engines "M-35 Pursina", "Kheip-0" and "Reiptor-12" currently breaks the plumes of all other running engines. This does not seem to be an issue with LFO itself, because no other tested engines or mods trigger this bug. It is recommended to avoid using these three engines until SORRY is updated.

Full Changelog: v0.10.0...v1.0.0

0.10.0

05 Nov 02:21
b918686
Compare
Choose a tag to compare

First release for KSP2 0.1.5.

Known issues:

  • Shader for additive mesh-based plumes is currently not working as expected (affects most chemical modded engines, plume shape will look wrong)
    Edit: This doesn't seem to be an issue with the shader as much as the shader has just been reworked, so existing plumes have to be remade. There is an actual bug with a few SORRY engines that seems to be only specific to that mod.