You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files "SpaceplanePlus_TweakScale.cfg" and " Squad_TweakScale.cfg" contain duplicate entry for
part "IntakeRadialLong" found under name "Structural Intake" in VAB/SPH parts list page "Aerodynamics".
This causes a scaling bug manifested when craft is created in flight scene. The part is left unchanged at 100% scale. In SPH/VAB editor, part is properly scaled from menu and after loading craft from disk.
Debug log shows following :
[Warning]: [TweakScale Warning] Duplicate TweakScale module on part [IntakeRadialLong] Structural Intake
TweakScale.Tools:LogWf(String, Object[])
TweakScale.TweakScale:CheckForDuplicateTweakScale()
TweakScale.TweakScale:Update()
Most likely the merger of SPP into KSP caused unintended duplication under both Squad and SPP parts packs. If SPP is now part of KSP, all TS cfg entries for SPP should be merged into Squad parts TS list.
The text was updated successfully, but these errors were encountered:
Files "SpaceplanePlus_TweakScale.cfg" and " Squad_TweakScale.cfg" contain duplicate entry for
part "IntakeRadialLong" found under name "Structural Intake" in VAB/SPH parts list page "Aerodynamics".
This causes a scaling bug manifested when craft is created in flight scene. The part is left unchanged at 100% scale. In SPH/VAB editor, part is properly scaled from menu and after loading craft from disk.
Debug log shows following :
[Warning]: [TweakScale Warning] Duplicate TweakScale module on part [IntakeRadialLong] Structural Intake
TweakScale.Tools:LogWf(String, Object[])
TweakScale.TweakScale:CheckForDuplicateTweakScale()
TweakScale.TweakScale:Update()
Most likely the merger of SPP into KSP caused unintended duplication under both Squad and SPP parts packs. If SPP is now part of KSP, all TS cfg entries for SPP should be merged into Squad parts TS list.
The text was updated successfully, but these errors were encountered: