0.3.0.3 (LisiasT) for KSP >= 1.4.1

• Updating the Sanity Check to prevent an annoying "Proceed with caution" warning.

0.3.0.2 (LisiasT) for KSP >= 1.4.1

• After some weeks of denying, it was finally realised that AttachedOnEditor is needed downoto KSP 1.4.3 - on the very first ModulePartVariant implementation.
  • What a crap of a code they published, damn!
• Fixes a small brain fart of mine on the INSTALL.md file.
• Updates KSPe.Light to the latest release (2.4.2.1 at this time)
• Closes issues:
  • #55 The KSP Editor is screwing things since 1.4.3
  • #50 Not sure how to install 0.3.0.0
    • Thanks to @tomtheisen for the heads up!

0.3.0.1 (LisiasT) for KSP >= 1.4.1

• Fixes a huge brain fart of mine from 0.2.2.4 #facePalm
• Closes issues:
  • #52 REPORT: Diagnosing the GoAHead Issue
  • #49 ArgumentOutOfRangeException causes saving to break and makes my save file unplayable

Your attention please!

As a workaround for upgrading the existent SubAssemblies, use Craft Manager!

Load the SubAssembly as it would a Craft, then drag'n'drop the whole shebang back to a new SubAssembly!!

0.3.0.0 (LisiasT) for KSP >= 1.4.1

• Prevents a race condition with Making History on Main Menu on heavily loaded rigs.
• Updates ModuleManagerWatchDog to 1.1.0.1
• Updates KSPe.Light.Recall to 2.4.1.16 due the Proton fix.
• Closes issues:
  • #45 Move the Sanity Checks) out of the Main Menu startup

Your attention please!

As a workaround for upgrading the existent SubAssemblies, use Craft Manager!

Load the SubAssembly as it would a Craft, then drag'n'drop the whole shebang back to a new SubAssembly!!

0.2.2.4 (LisiasT) for KSP >= 1.4.1

• Closes issues:
  • #41 Investigate a possible (bad) iteraction with Procedural Parts (RO) V2.3.0
  • #40 Unhappy interaction with Deep Freeze?
  • #37 Check about a missing use-case on AttachedOnEditor
  • #21 Update KSPe.Light for KSPe

Your Attention Please

If you use KSP/Windows under Linux using Proton, you need to install the HOTFIX01 below. Just unzip the thing replacing the older DLL.

0.2.2.3 (LisiasT) for KSP >= 1.4.1

• Allows patching AttachedOnEditor on every compatible part, no matter it has TweakScale installed or not.
  • Needed because a TweakScaled part borks when attached to another without it.

Your attention please!

As a workaround for upgrading the existent SubAssemblies, use Craft Manager!

Load the SubAssembly as it would a Craft, then drag'n'drop the whole shebang back to a new SubAssembly!!

0.2.2.2 (LisiasT) for KSP >= 1.4.1

• Reworks:
  • #35 AttachedOnEditor is not working for SubAssemblies.

0.2.2.1 (LisiasT) for KSP >= 1.4.1

• Formally closes issues:
  • #35 AttachedOnEditor is not working for SubAssemblies.
  • #34 NEW Misbehaviour on KSP introduced by AttachedOnEditor

Your attention please:

A new problem was found, affecting Editor since KSP 1.9, where some parts are triggering a strange misbehaviour when you Alt+Click a part for a duplicate, when Loading a craft for Merge or when loading a SubAssembly.

It was determined that when Parts without ModulePartVariant is the root of the SubAssembly, the parts attached to it must have the ModulePartVariant otherwise the problem will be triggered.

• I realised that the problem is that the Positions on the Attachment Nodes are not being initialised by the vanilla Parts - apparently the initialisation was moved to the ModulePartVariant module.
  • This may be the reason Squad choose to shove prefab back into the craft when loading it from the Editor, as apparently they didn't were able to pinpoint the cause of the misbehaviour...

Problem: I solved the problem for SubAssemblies and Craft files saved after installing the newest Release of KSP-Recall, but didn't managed to cook a way to salvage the pre-existent ones.
- Currently, there's no other alternative but to redo your SubAssemblies. I failed to find a viable automated process for salvaging them.

For more information:
- Got a bug with a subassembly here on Forum
- Issue #34 on GitHub

See KNOWN ISSUES file for more information.

0.2.2.0 (LisiasT) for KSP >= 1.4.1 PRE-RELEASE

• Implements another missing use case, handled on #34
• Works the issues:
  • #34 NEW Misbehaviour on KSP introduced by AttachedOnEditor

Your Attention Please

This release is BETA, not to be widely consumed. It's intended to be used by early adopters willing to help me out with the issue.

Apparently I fixed the problem with SubAssemblies, but it only works with SubAssemblies created with this new release.

SubAssemblies created with previous releases of KSP-Recall will not work, because they lack the needed data - and I didn't managed to cook a way to salvage them yet.

0.2.1.4 (LisiasT) for KSP >= 1.4.1

• Implements a missing use case, handled on #34
• Works the issues:
  • #34 NEW Misbehaviour on KSP introduced by AttachedOnEditor

Your Attention Please

A bug on KSP was discovered, affecting the Editor since KSP 1.9, where some parts trigger a weird misbehaviour when set as the root of a SubAssembly.

This misbehaviour happens when loading a Craft for Merge, when loading a SubAssembly from the SubAssembly palette, and when copying subtrees of a craft using Alt+Click.

The current workaround is to avoid the situation where these parts end up being the root of the SubAssembly. See the KNOWN ISSUES file for details, or the following links:

• Got a bug with a subassembly here on Forum
• Issue #34 on GitHub