I see there are some TweakScale modules in the part cfgs missing :NEEDS[TweakScale]:
KerblingOrbiter
OrbiterBasket
If most of the HL parts require TweakScale, maybe it would be better to make TS a hard dependency, and then change the patches in the cfgs from:
@PART[<x>]:NEEDS[TweakScale], to put the NEEDS at the top of the cfg, right in the PART def, so the parts wont load at all if TweakScale is not present?... then of course, add the TS module right into the PART{} node itself..
Example:
PART:NEEDS[TweakScale]
{
// --- general parameters ---
name = ZepTailCone
module = Part
author = Spanner
// --- asset parameters ---
mesh = ZepTailcone.mu
MODEL
{
model = HLAirships/Parts/Aero/ZepKit/ZepTailcone
scale = 1.0, 1.0, 1.0
}
....etc
Also related, the TS definition in TweakScale.cfg should really have a :NEEDS[TweakScale] added to it.
Also, there are missing models for all but one of the ZepKit parts. Might be good to change the file extension for the .cfgs, to disable them from loading, until models for them are available?... .txt would work... vOv
Also, KIS & KAS modules missing NEEDS on AirEnabledKASBoatAnchorIV.cfg
I see there are some TweakScale modules in the part cfgs missing
:NEEDS[TweakScale]:KerblingOrbiter
OrbiterBasket
If most of the HL parts require TweakScale, maybe it would be better to make TS a hard dependency, and then change the patches in the cfgs from:
@PART[<x>]:NEEDS[TweakScale], to put the NEEDS at the top of the cfg, right in the PART def, so the parts wont load at all if TweakScale is not present?... then of course, add the TS module right into the PART{} node itself..Example:
Also related, the TS definition in TweakScale.cfg should really have a :NEEDS[TweakScale] added to it.
Also, there are missing models for all but one of the ZepKit parts. Might be good to change the file extension for the .cfgs, to disable them from loading, until models for them are available?... .txt would work... vOv
Also, KIS & KAS modules missing NEEDS on AirEnabledKASBoatAnchorIV.cfg