Known Issues

• Attachment nodes are being reset when changing Variant on a scaled part. Please change the Variant before scaling the part as a temporary workaround.
  • See issues #307 and #314 for the gory details.
• There's a long standing issue on TweakScale about scaling ModuleEnginesFX's plumes - some engines' plumes is just not scaled, while others scaled pretty badly. It's something that never worked right on TweakScale, and it will only be really fixed on TweakScale 2.5 (when this thing goes gold)
  • The best workaround (and also the reason I'm dragging my feet on this) is to use SmokeScreen or Waterfall.
    • For SmokeScreen (works on all KSP versions), you need:
      • SmokeScreen itself.
      • Real Plumes (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes.
    • For Waterfall, you need:
      • Waterfall itself.
      • StockWaterfallEffects (to enable Waterfall on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on StockWaterfallEffects.
  • https://github.com/TweakScale/TweakScale/issues/27

Known Issues

• Attachment nodes are being reset when changing Variant on a scaled part. Please change the Variant before scaling the part as a temporary workaround.
  • See issues #307 and #314 for the gory details.
• There's a long standing issue on TweakScale about scaling ModuleEnginesFX's plumes - some engines' plumes is just not scaled, while others scaled pretty badly. It's something that never worked right on TweakScale, and it will only be really fixed on TweakScale 2.5 (when this thing goes gold)
  • The best workaround (and also the reason I'm dragging my feet on this) is to use SmokeScreen or Waterfall.
    • For SmokeScreen (works on all KSP versions), you need:
      • SmokeScreen itself.
      • Real Plumes (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes.
    • For Waterfall, you need:
      • Waterfall itself.
      • StockWaterfallEffects (to enable Waterfall on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on StockWaterfallEffects.
  • https://github.com/TweakScale/TweakScale/issues/27

This release is borked. Please use 2.7.4.2 until I release a new one!

See Forum for the gory details!

My apologies.

• Backport the Unity's Update Life Cycle fix from Aviation Lights #4
  • Hopefully preventing some shitstorm on users running KSP on Hybrid CPUs (P-Cores, E-Cores, that crap).
• Closes Issues:
  • #308 Insidious NRE on changing scenes
  • #307 Attachment Points are not being scaled (or being reset) after changing the Variant

Known Issues

DO NOT use this release.

Your Attention Please

Due a major screw up of mine (hate you, Windows!!), you will need to manually remove the following file before updating - unless you install things manually, when you will overwrite them anyway!

• <KSP_ROOT>/GameData/666_ModuleManagerWatchDog.dll

Your Attention Please

If installing from here, you will need to manually update the [TweakScale Companion Überpaket too](https://spacedock.info/mod/3202/TweakScale%20Companion%20(the%20%22UberPaket%22)!

This is ~probably~ hopefully the last time this will happen.

Your Attention Please.

A new bug on KSP's Editor, detected to be happening since KSP 1.11.x, was discovered: scaling parts using Symmetry Counter Parts (i.e., radial attachment with symmetries) is leading to misbehaviours on the Part's resources. It was proven that this is not TS fault, and the reason TS was working previous to 2.4.6.20 is a "mystery" at this moment.

See #283 for the gory details.

The workaround is simple: save and load the craft while editing it. No other Scene is affected by this misbehaviour.

NOTICE

Users of KSP 1.9.x need to install [KSP Recall](https://forum.kerbalspaceprogram.com/index.php?/topic/192048-*]

NOTICE

Users of KSP 1.9.x need to install [KSP Recall](https://forum.kerbalspaceprogram.com/index.php?/topic/192048-*]

• This Release locks TweakScale to run only on KSP versions greater or equal 1.4.1 and less then 1.8 .
• Updated KSPe Light for TweakScale:
  • Checking against incompatible Unity Versions
  • And this thing worked fine on Unity 2019.2 ! :)
• Closing or reworking the following issues:
  • #79 Prevent TweakScale from running on Incompatible Unity versions

Warning

This release breaks the TweakScale's long tradition of being compatible with multiple KSP versions. This release will work only for KSP releases before 1.8.

This is not critical or mandatory if you are not planning to migrate your savegames to KSP 1.8, but newer installations should download this version and I need to prevent TweakScale from running on Unity 2019 for now.

KSP 1.8 compatibility is already Work In Progress - but it will give me a bit more work than I though. It was confirmed that it's a bug on KSP on a very base feature used on UI, and some Add'Ons (TweakScale included) were relying on it. It's uncertain at this point if the best line of action if to wait for KSP 1.8.1 or just rework the UI.

Release 2.4.3.3 is available for downloading, with the following changes:

• Added support for hot-fixes - handcrafted patches to brute force a correct path when the normal way is not possible - as when an unmaintained ARR Add'On is involved on the mess.
  • New hot fix for CxAerospace:Station Parts breaking Bluedog_DB.

Highlights

Hot Fixes

TweakScale know recognizes and keep track of HOT FIXES.

A Hot Fix is a hand crafted patch that fixes by brute force patching problems, forcing the original intended result for a given KSP installment. The difference from an overrule is that Hot Fixes don't break compatibility with sane installments, so you can start new savegames and share your crafts without worries.

However, a Hot Fix is highly specialized to a given situation, and thiere're no guarantees that it will behave correctly as the affected Add'Ons are updated by the maintainers. So, a pesky Advise will popup when Hot Fixes are detected to prevent you from forgetting a old Hot Fix on your installments.

In an ideal World, Overrules and HotFixes would not be necessary. These are temporary workaround to keep KSP installments sane enough to keep going.

Apply Hot-Fixes or Overrules only when recommended by me, LisiasT. It's ok to reach me asking about if you think it will help you, but please confirm with me first. These things can cause as much damage as it can fix them.

Each Hot Fix will have an URL associated pinpoint to the Post where the problem were detected and fixed for traceability.

New Scaling Behaviour

A new TWEAKSCALEBEHAVIOUR, ModuleGeneratorExtended , is available for parts using ModuleGenerator that wants to scale the INPUT_RESOURCES too. This feature wasn't introduced directly into the ModuleGenerator's TWEAKSCALEEXPONENTS to prevent damage on Add'Ons (and savegames) that rely on the current behaviour (scaling only the output), as suddenly the resource consumption would increase on already stablished bases and crafts.

Just add the lines as the example below (the output resources scaling is still inherited from the default patch!).

@PART[my_resource_converter]:NEEDS[TweakScale]
{
    #@TWEAKSCALEBEHAVIOR[ModuleGeneratorExtended]/MODULE[TweakScale] { }
    %MODULE[TweakScale]
    {
        type = free
    }
}

WARNINGS

The last detected Unholy interaction between modules (Kraken Food), when rogue patches apply twice the same property on a part, are still detected on the Sanity Checks and a (now) proper (scaring) warning is being shown. Unfortunately, this issue is a serious Show Stopper, potentially (and silently) ruining your savegames. This is not TweakScale fault, but yet it's up to it to detect the problem and warn you about it. If this happens with you, call for help. Now a "Cancel" button is available for the brave Kerbonauts willing to fly unsafe.

TweakScale strongly recommends using S.A.V.E..

Special procedures for recovering mangled installments once the TweakScale are installed (triggering the MM cache rebuilding) are possible, but keep your savegames backed up. And DON`T SAVE your crafts once you detect the problem. Reach me on Forum for help.

TweakScale stills "mangles further" affected crafts and savegames with some badly (but recoverable) patched parts so when things are fixed, your crafts preserve the TweakScale settings without harm. THIS DOES NOT FIX THE PROBLEM, as this is beyond the reach of TweakScale - but it at least prevents you from losing your crafts and savegames once the problem happens and then is later fixed.

As usual, this version still drops support in runtime for some problematic parts. Any savegame with such problematic parts scaled will have them "descaled". This is not a really big problem as your game was going to crash sooner or later anyway - but if you plan to return to such savegame later when TweakScale will fully support that parts again, it's better to backup your savegames!

Keep an eye on the Known Issues file.

• This is an emergencial Release due a Emergencial Release. :P
• Adding KSPe Light facilites:
  • Logging
• Closing or reworking the following issues:
  • #31 Preventing being ran over by other mods
    • A misbehaviour on detecting the misbehaviour :) was fixed.
  • #47 Count failed Sanity Checks as a potential problem. Warn user.
  • #48 Backport the Heterodox Logging system into Orthodox (using KSPe.Light)
  • #49 Check the Default patches for problems due wildcard!
  • #50 Check the patches for currently supported Add'Ons
    • ModuleGeneratorExtended Behaviour
  • #51 Implement a "Cancel" button when Actions are given to MessageBox
    • Yeah. Doing it right this time.
  • #54 [ERR FATAL link provided in KSP.log links to 404
    • "Typo maldito, typo maldito - tralálálálálálá"
  • #56 "Breaking Parts" patches
  • #57 Implement Warning Dialogs
    • Warnings about Overrules, parts that couldn't be checked and parts with TweakScale support withdrawn.
    • Doing it right this time!
  • #58 Mk4 System Patch (addendum)

Highlights

A new TWEAKSCALEBEHAVIOUR, ModuleGeneratorExtended , is available for parts using ModuleGenerator that wants to scale the INPUT_RESOURCES too. This feature wasn't introduced directly into the ModuleGenerator's TWEAKSCALEEXPONENTS to prevent damage on Add'Ons (and savegames) that rely on the current behaviour (scaling only the output), as suddenly the resource consumption would increase on already stablished bases and crafts.

Just add the lines as the example below (the output resources scaling is still inherited from the default patch!).

@PART[my_resource_converter]:NEEDS[TweakScale]
{
    #@TWEAKSCALEBEHAVIOR[ModuleGeneratorExtended]/MODULE[TweakScale] { }
    %MODULE[TweakScale]
    {
        type = free
    }
}

WARNINGS

The last detected Unholy interaction between modules (Kraken Food), when rogue patches apply twice the same property on a part, are still detected on the Sanity Checks and a (now) proper (scaring) warning is being shown. Unfortunately, this issue is a serious Show Stopper, potentially (and silently) ruining your savegames. This is not TweakScale fault, but yet it's up to it to detect the problem and warn you about it. If this happens with you, call for help. Now a "Cancel" button is available for the brave Kerbonauts willing to fly unsafe.

TweakScale strongly recommends using S.A.V.E..

Special procedures for recovering mangled installments once the TweakScale are installed (triggering the MM cache rebuilding) are possible, but keep your savegames backed up. And DON`T SAVE your crafts once you detect the problem. Reach me on Forum for help.

TweakScale stills "mangles further" affected crafts and savegames with some badly (but recoverable) patched parts so when things are fixed, your crafts preserve the TweakScale settings without harm. THIS DOES NOT FIX THE PROBLEM, as this is beyond the reach of TweakScale - but it at least prevents you from losing your crafts and savegames once the problem happens and then is later fixed.

As usual, this version still drops support in runtime for some problematic parts. Any savegame with such problematic parts scaled will have them "descaled". This is not a really big problem as your game was going to crash sooner or later anyway - but if you plan to return to such savegame later when TweakScale will fully support that parts again, it's better to backup your savegames!

Keep an eye on the Known Issues file.

WARNINGS

And yet another Unholy interaction between modules (Kraken Food) was detected when rogue patches apply twice the same property on a part. Unfortunately, one of that rogue patches were being delivered on the TweakScale Releases. We apologize for that.

Be advised that a new situation was detected that demanded withdrawing support from some parts at runtime due rogue patching. No breakage is expected this time as such parts are rendered useless and you could not use them anyway, but take precautions on installing Add'Ons on your installment as some older ones are prone to induce this misbehaviour.

Issues that would mangle your savegames and crafts still persists. Things still work until the problem is fixed (by installing, deleting or updating an add'on!) when then your KSP installment will be sane but all your savegames and crafts with TweakScale parts will get reset to defaults - yeah, you can't fix the problem or things get worse. This version of TweakScale "mangles further" the affected crafts and savegames so when things are fixed, your crafts preserve the TweakScale settings without harm. THIS DOES NOT FIX THE PROBLEM, as this is beyond the reach of TweakScale - but it at least prevents you from losing your crafts and savegames once the problem happens and then is later fixed.

Special procedures for recovering mangled installments once the TweakScale are installed (triggering the MM cache rebuilding) are possible, but keep your savegames backed up. And DON`T SAVE your crafts once you detect the problem. Reach me on Forum for help.

As usual, this version still drops support in runtime for some problematic parts. Any savegame with such problematic parts scaled will have them "descaled". This is not a really big problem as your game was going to crash sooner or later anyway - but if you plan to return to such savegame later when TweakScale will fully support that parts again, it's better to backup your savegames!

Keep an eye on the Known Issues file.

WARNINGS

Another Unholy interaction between modules (Kraken Food) was detected that would mangle your savegames and crafts. Things still work until the problem is fixed (by installing, deleting or updating an add'on!) when then your KSP installment will be sane but all your savegames and crafts with TweakScale parts will get reset to defaults - yeah, you can't fix the problem or things get worse. This version of TweakScale "mangles further" the affected crafts and savegames so when things are fixed, your crafts preserve the TweakScale settings without harm. THIS DOES NOT FIX THE PROBLEM, as this is beyond the reach of TweakScale - but it at least prevents you from losing your crafts and savegames once the problem happens and then is later fixed.

Special procedures for recovering mangled installments once the TweakScale are installed (triggering the MM cache rebuilding) are possible, but keep your savegames backed up. And DON`T SAVE your crafts once you detect the problem. Reach me on Forum for help.

On the other hand, however, this version still drops support in runtime for some problematic parts. Any savegame with such problematic parts scaled will have them "descaled". This is not a really big problem as your game was going to crash sooner or later anyway - but if you plan to return to such savegame later when TweakScale will fully support that parts again, it's better to backup your savegames!

Keep an eye on the Known Issues file.

BACKUP YOUR SAVEGAMES . Some parts will loose TweakScale support, and if such parts are being used your crafts will have problems. Support for these parts will be restored in the future, but until there you will need to play without TweakScaling them.

Known issues:

the new stock texture switch messes up attachment nodes on scaled parts
(first switching and then scaling seems to work)