Jump to content

[1.4.4 <= KSP <= 1.11.2] TweakScale - Under Lisias' Management - 2.4.5.0 - 2021-0410


Recommended Posts

hey, lisias? the scale factor sill didn't work with the typos cleared out

here's the code:

Quote

@PART[virgo_fuel_tank_s1_2]:NEEDS[Tantares,TweakScale] // Tantares Size 0.5 to Size 0 Adapter
{   %MODULE[TweakScale]
    {
        type = stack
        defaultScale = 1.25
        scaleFactors   = 0.1,  0.3,0.625,0.9375,1.25,1.5,1.875, 2.5,3.125,3.75, 5.0,10,20
        incrementSlide = 0.01, 0.05, 0.05, 0.05,  0.05, 0.05, 0.05,  0.05, 0.5, 0.05
    }
}

 

Link to post
Share on other sites
5 hours ago, moguy16 said:

hey, lisias? the scale factor sill didn't work with the typos cleared out

here's the code:

Well... apparently it worked...

[LOG 16:58:42.418] [ModuleManager] INFO: Applying update __LOCAL/TweakScale/Tantares/virgo_fuel_tank_s1_2/@PART[virgo_fuel_tank_s1_2]:NEEDS[Tantares,Tw
eakScale] to Tantares/Parts/LOK/_virgo_fuel_tank_s1_2/PART

And there's no error after.

Follows an excerpt from the ModuleManager.ConfigCache:

UrlConfig
{
	name = virgo_fuel_tank_s1_2
	type = PART
	parentUrl = Tantares/Parts/LOK/_virgo_fuel_tank_s1_2
	PART
	{
		name = virgo_fuel_tank_s1_2
		module = Part
		author = Tantares

		yada yada yada

		MODULE
		{
			name = TweakScale
			type = stack
			defaultScale = 1.25
			scaleFactors = 0.1,  0.3,  0.625, 0.9375, 1.25, 1.5,  1.875, 2.5,  3.125, 3.75, 5, 10, 20
			incrementSlide = 0.01, 0.05, 0.05,  0.05,   0.05, 0.05, 0.05,  0.05, 0.5,   0.05
		}
	}
}

So things apparently are working.

And... It works for me!

pxfVS79.png

Follows a exact copy & paste from my config file:

@PART[virgo_fuel_tank_s1_2]:NEEDS[Tantares,TweakScale] // Tantares Size 0.5 to Size 0 Adapter
{
	%MODULE[TweakScale]
	{
		type = stack
		defaultScale = 1.25
		scaleFactors   = 0.1,  0.3,  0.625, 0.9375, 1.25, 1.5,  1.875, 2.5,  3.125, 3.75, 5, 10, 20
		incrementSlide = 0.01, 0.05, 0.05,  0.05,   0.05, 0.05, 0.05,  0.05, 0.5,   0.05
	}
}

It's exactly as yours , only better whitespaced.

Check if you installed TweakScale, or if there's something missing on it. I just borked the first try because I forgot to install 999_Scale_Redist.dll on a clean KSP 1.9.1 :P  (yeah, it happens even to me!)

 

Edited by Lisias
Tyops, as usulla...
Link to post
Share on other sites
Just now, Lisias said:

Well... apparently it worked...

[LOG 16:58:42.418] [ModuleManager] INFO: Applying update __LOCAL/TweakScale/Tantares/virgo_fuel_tank_s1_2/@PART[virgo_fuel_tank_s1_2]:NEEDS[Tantares,Tw
eakScale] to Tantares/Parts/LOK/_virgo_fuel_tank_s1_2/PART

And there's no error after.

Follows an excerpt from the ModuleManager.ConfigCache:

UrlConfig
{
	name = virgo_fuel_tank_s1_2
	type = PART
	parentUrl = Tantares/Parts/LOK/_virgo_fuel_tank_s1_2
	PART
	{
		name = virgo_fuel_tank_s1_2
		module = Part
		author = Tantares

		yada yada yada

		MODULE
		{
			name = TweakScale
			type = stack
			defaultScale = 1.25
			scaleFactors = 0.1,  0.3,  0.625, 0.9375, 1.25, 1.5,  1.875, 2.5,  3.125, 3.75, 5, 10, 20
			incrementSlide = 0.01, 0.05, 0.05,  0.05,   0.05, 0.05, 0.05,  0.05, 0.5,   0.05
		}
	}
}

So things apparently is working.

And... It works for me!

pxfVS79.png

Follows a exact copy & past from my config file:

@PART[virgo_fuel_tank_s1_2]:NEEDS[Tantares,TweakScale] // Tantares Size 0.5 to Size 0 Adapter
{
	%MODULE[TweakScale]
	{
		type = stack
		defaultScale = 1.25
		scaleFactors   = 0.1,  0.3,  0.625, 0.9375, 1.25, 1.5,  1.875, 2.5,  3.125, 3.75, 5, 10, 20
		incrementSlide = 0.01, 0.05, 0.05,  0.05,   0.05, 0.05, 0.05,  0.05, 0.5,   0.05
	}
}

It's exactly as yours , only better whitespaced.

Check if you installed TweakScale, or if there's something missing on it. I just borked the first try because I forgot to install 999_Scale_Redist.dll on a clean KSP 1.9.1 :P  (yeah, it happens even to me!)

 

i will try again thanks :)

Link to post
Share on other sites

I just set up a new 1.81 install, pretty heavily modded. I am getting the issue #34 problem on 36 parts, all of them (I think) from Contares sub-mods (mostly the Chinese vehicle parts). 

Is my only option to uninstall these? I'd really rather not, I like my standard library of Contares parts. @hraban since these seem to be his parts, or at least I think so. Your log doesn't show the parts' paths so it's harder to figure out who owns them. Hint hint please add the path: **FATAL** Part <path>/XXXX.

[LOG 16:08:19.532] [TweakScale] WARNING: **FATAL** Found a showstopper problem on KSRO-SITVC-RCS (KSRO SITVC-RCS).
[LOG 16:08:19.532] [TweakScale] ERROR: **FATAL** Part KSRO-SITVC-RCS (KSRO SITVC-RCS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.532] [TweakScale] WARNING: **FATAL** Found a showstopper problem on KhiSP.SZ (KhiSP-SZ).
[LOG 16:08:19.532] [TweakScale] ERROR: **FATAL** Part KhiSP.SZ (KhiSP-SZ) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.532] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Parabol.KhiNa (Communication Dish).
[LOG 16:08:19.532] [TweakScale] ERROR: **FATAL** Part Parabol.KhiNa (Communication Dish) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.532] [TweakScale] WARNING: **FATAL** Found a showstopper problem on A1-44.FIN (A1-44 VS).
[LOG 16:08:19.532] [TweakScale] ERROR: **FATAL** Part A1-44.FIN (A1-44 VS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.533] [TweakScale] WARNING: **FATAL** Found a showstopper problem on REX.FLAP (REX-FLAP).
[LOG 16:08:19.533] [TweakScale] ERROR: **FATAL** Part REX.FLAP (REX-FLAP) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.533] [TweakScale] WARNING: **FATAL** Found a showstopper problem on CEMP187 (Engine Mounting Plate).
[LOG 16:08:19.533] [TweakScale] ERROR: **FATAL** Part CEMP187 (Engine Mounting Plate) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.534] [TweakScale] WARNING: **FATAL** Found a showstopper problem on FalkeX-Nosecone (FalkeX Aerodynamic Nosecone).
[LOG 16:08:19.534] [TweakScale] ERROR: **FATAL** Part FalkeX-Nosecone (FalkeX Aerodynamic Nosecone) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.534] [TweakScale] WARNING: **FATAL** Found a showstopper problem on U.Bremse (UL BRAKE).
[LOG 16:08:19.534] [TweakScale] ERROR: **FATAL** Part U.Bremse (UL BRAKE) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.535] [TweakScale] WARNING: **FATAL** Found a showstopper problem on C.BUS.KOFFER (GEO-Bus).
[LOG 16:08:19.535] [TweakScale] ERROR: **FATAL** Part C.BUS.KOFFER (GEO-Bus) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.535] [TweakScale] WARNING: **FATAL** Found a showstopper problem on BBBP-001 (BBBP-001).
[LOG 16:08:19.535] [TweakScale] ERROR: **FATAL** Part BBBP-001 (BBBP-001) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.535] [TweakScale] WARNING: **FATAL** Found a showstopper problem on BBBP-002 (BBBP-002).
[LOG 16:08:19.535] [TweakScale] ERROR: **FATAL** Part BBBP-002 (BBBP-002) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.536] [TweakScale] WARNING: **FATAL** Found a showstopper problem on DT-004 (DT-004).
[LOG 16:08:19.536] [TweakScale] ERROR: **FATAL** Part DT-004 (DT-004) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.536] [TweakScale] WARNING: **FATAL** Found a showstopper problem on KERBUS1000 (KERBUS-1000).
[LOG 16:08:19.536] [TweakScale] ERROR: **FATAL** Part KERBUS1000 (KERBUS-1000) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.536] [TweakScale] WARNING: **FATAL** Found a showstopper problem on BBBPrTANK (TKS MP-Tank light).
[LOG 16:08:19.536] [TweakScale] ERROR: **FATAL** Part BBBPrTANK (TKS MP-Tank light) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.536] [TweakScale] WARNING: **FATAL** Found a showstopper problem on BBBPrTANKx2 (TKS MP-Tank light x2).
[LOG 16:08:19.536] [TweakScale] ERROR: **FATAL** Part BBBPrTANKx2 (TKS MP-Tank light x2) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.538] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Fin.RIVER (Fin RIVER).
[LOG 16:08:19.538] [TweakScale] ERROR: **FATAL** Part Fin.RIVER (Fin RIVER) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.539] [TweakScale] WARNING: **FATAL** Found a showstopper problem on RK-Z-0110 (RK-Z-0110).
[LOG 16:08:19.539] [TweakScale] ERROR: **FATAL** Part RK-Z-0110 (RK-Z-0110) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 16:08:19.539] [TweakScale] WARNING: **FATAL** Found a showstopper problem on TLV.FIN.C (UNION II TLV-VS).
[LOG 16:08:19.539] [TweakScale] ERROR: **FATAL** Part TLV.FIN.C (UNION II TLV-VS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0

 

Link to post
Share on other sites
14 minutes ago, vossiewulf said:

I just set up a new 1.81 install, pretty heavily modded. I am getting the issue #34 problem on 36 parts, all of them (I think) from Contares sub-mods (mostly the Chinese vehicle parts). 

Is my only option to uninstall these? I'd really rather not, I like my standard library of Contares parts. @hraban since these seem to be his parts, or at least I think so. Your log doesn't show the parts' paths so it's harder to figure out who owns them. Hint hint please add the path: **FATAL** Part <path>/XXXX.

 

Please publish on DropBox, Google Drive or something the full KSP.log, otherwise I can't help you. Don't use pastebin, gist or similar as they truncate the file, rendering it useless.

See the OP (on the Support spoiler) for instructions about how to proceed.

Link to post
Share on other sites
4 hours ago, Lisias said:

Please publish on DropBox, Google Drive or something the full KSP.log, otherwise I can't help you. Don't use pastebin, gist or similar as they truncate the file, rendering it useless.

See the OP (on the Support spoiler) for instructions about how to proceed.

This problem seems very well-known (I read most of the GH issue), I thought the cause(s) would be as well.

KSP.log

Output_txt.log

Thanks for looking into it. I'm getting these as soon as I load the game, along with a warning that every atom in my body will explode at the speed of light if I don't fix them. The count is 36 and I was wrong, only half are Contares. The other half are Nertea's NF Construction, mostly the octo-girder parts.

When I set up this game I pulled almost everything from CKAN, and only added a couple new items from those of the last game (1.71) that was working. But I guess new versions of mods mean new conflicts.

Edited by vossiewulf
Link to post
Share on other sites
2 hours ago, vossiewulf said:

This problem seems very well-known (I read most of the GH issue), I thought the cause(s) would be as well.

KSP.log

Output_txt.log

Got it.

[LOG 20:02:45.189] [TweakScale] INFO: WriteDryCost Concluded : 4836 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 36 Show Stoppers found; 68 Sanity Check failed; 2620 unscalable parts.

Well, pretty decent instalment. 4836 parts, being 2620 parts that will not scale due lack of patch (or a problem detected, see the 36 and 68 ones, they are on this basket).

That 68 parts are parts that TweakScale needs to implement proper support, most of the time. Trying to scale them now would lead to problems, so TweakScale withdraws itself from that parts. Some os that parts are already fixed on TweakScaleCompanion for Firespitter (roll that wall of text until you see it) if you are interested.

The problematic parts are that 36 ones, with FATALities:

Spoiler

 

[LOG 20:02:44.821] [TweakScale] ERROR: **FATAL** Part KSRO-SITVC-RCS (KSRO SITVC-RCS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.822] [TweakScale] ERROR: **FATAL** Part KhiSP.SZ (KhiSP-SZ) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.822] [TweakScale] ERROR: **FATAL** Part Parabol.KhiNa (Communication Dish) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.822] [TweakScale] ERROR: **FATAL** Part A1-44.FIN (A1-44 VS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.823] [TweakScale] ERROR: **FATAL** Part REX.FLAP (REX-FLAP) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.823] [TweakScale] ERROR: **FATAL** Part CEMP187 (Engine Mounting Plate) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.823] [TweakScale] ERROR: **FATAL** Part FalkeX-Nosecone (FalkeX Aerodynamic Nosecone) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.824] [TweakScale] ERROR: **FATAL** Part U.Bremse (UL BRAKE) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.825] [TweakScale] ERROR: **FATAL** Part C.BUS.KOFFER (GEO-Bus) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.825] [TweakScale] ERROR: **FATAL** Part BBBP-001 (BBBP-001) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.825] [TweakScale] ERROR: **FATAL** Part BBBP-002 (BBBP-002) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.825] [TweakScale] ERROR: **FATAL** Part DT-004 (DT-004) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.826] [TweakScale] ERROR: **FATAL** Part KERBUS1000 (KERBUS-1000) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.826] [TweakScale] ERROR: **FATAL** Part BBBPrTANK (TKS MP-Tank light) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.826] [TweakScale] ERROR: **FATAL** Part BBBPrTANKx2 (TKS MP-Tank light x2) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.827] [TweakScale] ERROR: **FATAL** Part Fin.RIVER (Fin RIVER) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.829] [TweakScale] ERROR: **FATAL** Part RK-Z-0110 (RK-Z-0110) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.829] [TweakScale] ERROR: **FATAL** Part TLV.FIN.C (UNION II TLV-VS) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.902] [TweakScale] ERROR: **FATAL** Part truss-octo-01 (Octo-Girder Modular Truss XL) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.903] [TweakScale] ERROR: **FATAL** Part truss-octo-02 (Octo-Girder Modular Truss) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.903] [TweakScale] ERROR: **FATAL** Part truss-octo-03 (Octo-Girder Modular Truss Mini) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.903] [TweakScale] ERROR: **FATAL** Part truss-octo-04 (Octo-Girder Modular Truss Micro) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.903] [TweakScale] ERROR: **FATAL** Part truss-octo-adapter-01 (Octo-Girder Modular Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.903] [TweakScale] ERROR: **FATAL** Part truss-octo-adapter-crew-01 (Octo-Girder Pressurized Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.904] [TweakScale] ERROR: **FATAL** Part truss-octo-angled-01 (Octo-Girder Modular Angular Connector) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.904] [TweakScale] ERROR: **FATAL** Part truss-octo-angled-crew-01 (Octo-Girder Pressurized Angular Connector) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.904] [TweakScale] ERROR: **FATAL** Part truss-octo-attach-01 (Octo-Girder Radial Attach Node) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.904] [TweakScale] ERROR: **FATAL** Part truss-octo-crew-01 (Octo-Girder Pressurized Truss XL) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.904] [TweakScale] ERROR: **FATAL** Part truss-octo-crew-02 (Octo-Girder Pressurized Truss) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-crew-03 (Octo-Girder Pressurized Truss Mini) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-docking-125 (Octo-Girder Docking Connector) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-docking-25 (Octo-Girder Heavy Docking Connector) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-docking-octo (Octo-Girder Octagonal Docking Connector) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-drone-01 (Octo-Girder Guidance Unit) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.905] [TweakScale] ERROR: **FATAL** Part truss-octo-hub-01 (Octo-Girder Modular Hub) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0
[LOG 20:02:44.906] [TweakScale] ERROR: **FATAL** Part truss-octo-hub-crew-01 (Octo-Girder Pressurized Hub) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0

 

 

Let's check one of them, KSRO-SITVC-RCS:

[LOG 19:52:03.350] Applying update Contares/Patches/CONTARES_TweakScale/@PART[KSRO-SITVC-RCS] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:03.588] Applying update Contares_IND/Patches/Contares_IND_TweakScale/@PART[KSRO-SITVC-RCS] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:06.856] Applying update ModularFuelTanks/Propellants/@PART[*]:HAS[@MODULE[ModuleEnginesFX]] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:16.375] Applying update StationScience/MKSEffects/@PART:NEEDS[MKS] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:28.696] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:30.493] Applying update WildBlueIndustries/Pathfinder/ModuleManagerPatches/MM_Skills/@PART[*]:NEEDS[Pathfinder]:HAS[!MODULE[KerbalEVA],!MODULE[ModuleAsteroid]] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:32.552] Applying update AtmosphereAutopilot/csurf_sync/@PART[*]:HAS[@MODULE[ModuleGimbal]]:FOR[AtmosphereAutopilot] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:42.109] Applying update Contares_IND/Patches/Contares_IND_plume/@PART[KSRO-SITVC-RCS]:FOR[RealPlume]:NEEDS[SmokeScreen] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:45.114] Applying update RealPlume/000_Generic_Plumes/000_EFFECTS_Remover/@PART[*]:HAS[@PLUME[*]]:AFTER[RealPlume]:NEEDS[SmokeScreen] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:45.264] Applying update RealPlume/000_Generic_Plumes/000_EFFECTS_Remover/@PART[*]:HAS[@PLUME[*],@MODULE[ModuleEngines*],!MODULE[ModuleRCSFX]]:AFTER[RealPlume]:NEEDS[SmokeScreen] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:52.126] Applying update RealPlume/000_Generic_Plumes/000_zRealPlume/@PART[*]:HAS[@PLUME[*]]:FOR[zRealPlume]:NEEDS[SmokeScreen] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:52:57.013] Applying update RealPlume/000_Generic_Plumes/Deprecated/Hypergolic-Upper/@PART[*]:HAS[@PLUME[Hypergolic-Upper]:HAS[~processed[*]]]:AFTER[zRealPlume]:NEEDS[SmokeScreen] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]
[LOG 19:53:00.744] Applying update RealPlume-Stock/Global Patches/@PART[*]:HAS[@PLUME[*],@MODULE[ModuleEngines*]]:FOR[zzzRealPlumeStock] to Contares_IND/Parts/KSRO/KSRO-SITVC-RCS.cfg/PART[KSRO-SITVC-RCS]

Interesting. The first two patches appears to reveal the problem, Contares and Contares_IMD are patching it.

So I checked another part (only the first two updates):

[LOG 19:52:03.392] Applying update Contares/Patches/CONTARES_TweakScale/@PART[KhiSP_SZ] to Contares_KHI/Parts/KhiNa/KhiSP_SZ.cfg/PART[KhiSP_SZ]
[LOG 19:52:03.604] Applying update Contares_KHI/Patches/CONTARES_KHI_TweakScale/@PART[KhiSP_SZ] to Contares_KHI/Parts/KhiNa/KhiSP_SZ.cfg/PART[KhiSP_SZ]

Now we have a double patching from Contares and from Contares_KHI.

So I checked another one, RK-Z-0110 :

[LOG 19:52:03.460] Applying update Contares/Patches/CONTARES_TweakScale/@PART[RK-Z-0110] to Contares_RUS/Parts/UNION-2/RK-Z-0110.cfg/PART[RK-Z-0110]
[LOG 19:52:03.848] Applying update Contares_RUS/Patches/Contares_RUS_TweakScale/@PART[RK-Z-0110] to Contares_RUS/Parts/UNION-2/RK-Z-0110.cfg/PART[RK-Z-0110]

Now we have a double patching from Contares and from Contares_RUS.

Well, we have a pattern. Let's go for the trusses (truss-octo-01) and see what we get:

[LOG 19:52:03.575] Applying update Contares/Patches/CONTARES_TweakScale/@PART[truss-octo-*] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:09.738] Applying update NearFutureConstruction/Patches/NFConstructionCRPTrusses/@PART[truss-octo-01]:NEEDS[CommunityResourcePack&CryoTanks] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:16.469] Applying update StationScience/MKSEffects/@PART:NEEDS[MKS] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:23.169] Applying update TweakScale/patches/NF/NFC_TweakScale/@PART[truss-octo-01] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:28.782] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:30.602] Applying update WildBlueIndustries/Pathfinder/ModuleManagerPatches/MM_Skills/@PART[*]:NEEDS[Pathfinder]:HAS[!MODULE[KerbalEVA],!MODULE[ModuleAsteroid]] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:52:37.978] Applying update NearFutureConstruction/Patches/NFConstructionCRPTrusses/@PART[truss-octo-01]:NEEDS[CommunityResourcePack]:FOR[NearFutureConstruction] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]
[LOG 19:53:01.025] Applying update B9PartSwitch/PartInfo/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]]:FOR[zzzzzz-B9PartSwitch] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-01.cfg/PART[truss-octo-01]

And again, Contares. (sigh)

I think you should file a bug report on Contares, as I did here. But until (or if) they fix it, delete Contares/Patches/CONTARES_TweakScale.cfg . This file is double patching everything, including TweakScale's default patches. It's the same problem I diagnosed previously, but with steroids.

 

2 hours ago, vossiewulf said:

Thanks for looking into it. I'm getting these as soon as I load the game, along with a warning that every atom in my body will explode at the speed of light if I don't fix them. The count is 36 and I was wrong, only half are Contares. The other half are Nertea's NF Construction, mostly the octo-girder parts.

Welcome.

Yeah, the warning is really meant to me scary - a fellow Kerbonaut recently lost a 2.5 years savegame recently due a mishap while trying to fix his rig. Things can go down through the tubes pretty fast, as an inconsistent GameDatabase will corrupt the savegame on loading, and once it's loaded and corrupted, it's doomed as it will be saved over the previous one. It's the reason I push S.A.V.E. for everybody.

The scary part is that TweakScale only tries to avoid the problems that affect it. Any other Add'On are susceptible to this problem, as Fuel Switches. KSP overwrites the Module data with a corrupted copy on every part on every craft on a savegame, how you will restore it? Some savegames has hundreds or thousands on parts on the Universe...

 

2 hours ago, vossiewulf said:

When I set up this game I pulled almost everything from CKAN, and only added a couple new items from those of the last game (1.71) that was working. But I guess new versions of mods mean new conflicts.

And unfixed older versions of Add'Ons means old conflicts. Now we mix them, and we have a whole new set of conflicts to handle. :)

Patching in the old days was a mess, I detected parts with 3, 4 copies of the patching data and if you install or deinstall something, the data changes and then everything that use that part goes kaput on the next load.

Link to post
Share on other sites
16 minutes ago, Lisias said:

Got it.

[LOG 20:02:45.189] [TweakScale] INFO: WriteDryCost Concluded : 4836 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 36 Show Stoppers found; 68 Sanity Check failed; 2620 unscalable parts.

Well, pretty decent instalment. 4836 parts, being 2620 parts that will not scale due lack of patch (or a problem detected, see the 36 and 68 ones, they are on this basket).

That 68 parts are parts that TweakScale needs to implement proper support, most of the time. Trying to scale them now would lead to problems, so TweakScale withdraws itself from that parts. Some os that parts are already fixed on TweakScaleCompanion for Firespitter (roll that wall of text until you see it) if you are interested.

Ok. so nothing I can do but uninstall Contares, sigh. I appreciate you doing the log-reading to confirm what is going on, hopefully he can release a fix soon.]

I had grabbed the TweakScale Companion from CKAN, and have it installed. So if it's supposed to be doing something about some of these parts then something is wonky there as well.

25 minutes ago, Lisias said:

Yeah, the warning is really meant to me scary - a fellow Kerbonaut recently lost a 2.5 years savegame recently due a mishap while trying to fix his rig. Things can go down through the tubes pretty fast, as an inconsistent GameDatabase will corrupt the savegame on loading, and once it's loaded and corrupted, it's doomed as it will be saved over the previous one. It's the reason I push S.A.V.E. for everybody.

Wow, that's a megalithic bummer. I understand why, but at the end of that warning I was doing Ghostbusters... dogs and cats living together,  MASS HYSTERIA :)

 

Link to post
Share on other sites
4 minutes ago, vossiewulf said:

Ok. so nothing I can do but uninstall Contares, sigh. I appreciate you doing the log-reading to confirm what is going on, hopefully he can release a fix soon

Just delete that file first. Contares is a hell of a nice Add'On, I think it worths the trouble of trying to fix it first. :)

 

4 minutes ago, vossiewulf said:

I had grabbed the TweakScale Companion from CKAN, and have it installed. So if it's supposed to be doing something about some of these parts then something is wonky there as well.

So you grabbed the Companion for ReStock+, currently is the only one published there (there's a huge lot coming on, but I will keep them in Alpha or Beta for while, as I settle up things).

These patches (the Companion ones) are meticulously curated by myself. Of course a bork leaks now and then, but they are rapidly detected and fixed. And since these patches are curated by the TweakScale maintainer (yours truly), I have the policy to consider them canon (unless the Add'On author decides to provide support for TweakScale him/herself - where then I will withdraw the Companion), so I handle them as they were part of TweakScale itself - they were split to reduce the TweakScale surface of exposition, as 90% of the problems are now on patching and this was giving TweakScale a hell of a bad reputation.

 

12 minutes ago, vossiewulf said:

Wow, that's a megalithic bummer. I understand why, but at the end of that warning I was doing Ghostbusters... dogs and cats living together,  MASS HYSTERIA :)

Dude, I lost the count of people that had their long time running savegames corrupted and lost by bad patching. I managed to salvage some of them, but since the days KSP started to overwrite good, healthy savegames with bad data from a corrupted GameDatabase, this task became too much for a single dude - once the good data is overwritten, I would need to manually inspect part by part to check the context and infer what I should put there back.

As much as it appears overkill for someone that plays KSP occasionally, there are die hard KSP fans here playing the same savegames for years (my own savegames are from the 1.4.1 era, when I detected the problem, fixed it for me, and then ended up here doing the same for everybody), and for these guys this is almost the end of the World...

Link to post
Share on other sites
12 hours ago, Lisias said:

Just delete that file first. Contares is a hell of a nice Add'On, I think it worths the trouble of trying to fix it first. :)

Looks like Hraban already fixed it, thanks for the help there. I'm going to try the new versions now.

12 hours ago, Lisias said:

These patches (the Companion ones) are meticulously curated by myself.

I'm going to try those as well, thanks.

12 hours ago, Lisias said:

Dude, I lost the count of people that had their long time running savegames corrupted and lost by bad patching.

This is why I have a policy of not changing mods once a game starts. I have several career saves, each with the exact same set of mods that the game started with, so I can go back to them without issues. It's very tempting to add mods, but there are only two or maybe three mod developers who are sufficiently meticulous that I'd even consider adding one of their mods to a game, and even then so far I've resisted. I think it's the only way to keep a game safe.

Thanks again for helping getting this fixed!

Edited by vossiewulf
Link to post
Share on other sites
On 6/12/2020 at 7:45 AM, Lisias said:

And.... yes, this is not exactly off-topic. As TweakScale scales these Modules, it may potentialise the effect. I was wise on keeping the Wheels scaling only on TweakScale Beta, as something appears to had gone backwards on KSP 1.9 (or perhaps 1.8 - I'm really not playing these new versions, I just testing on it). On KSP 1.7 I don't remember seeing something like this.

I'm glad I didn't derail things by accident. Though I've noticed that the World Stabilizer mod helps with that low scale trembling.

Now I don't know if Tweak Scale makes it worse, or makes it better, but I took a reaction wheel, made it stronger for larger craft, and added TS support. Even unscaled, on an impact, boom. Yet scale it up .... I need to try that out. 

Link to post
Share on other sites

Scaling up a SAS won't impact the death spin. I can make it happen with stock, mods, and my moded mods. So TS doesn't seam like its a culprit unless the sized up parts are a problem.

EDIT:

So after posting this, the craft did stop spinning! An other edit once I investigate.

EDIT 2:

What looks like happened is that once the stand alone SAS got destroyed, the spinning stopped. The command pod still had a working SAS.

I'm not sure if this helps prove that TS isn't creating the problem, or that its not making it worse

Edited by Azic Minar
Well now pt 2
Link to post
Share on other sites
10 hours ago, Azic Minar said:

What looks like happened is that once the stand alone SAS got destroyed, the spinning stopped. The command pod still had a working SAS.

I'm not sure if this helps prove that TS isn't creating the problem, or that its not making it worse

Could you send me the craft you used? I tried something with this stunt below, scaling up a SAS and scaling down intakes, fuel tanks and engines, and everything is alright.

I made this test, with the front SAS active, and the Cabin and rear SAS active only by pilot, and everything happened as expected.

So, no, TweakScale is not the one causing the problems, I would had something on this test if it were.

But it may the one triggering the problem somewhere else (a Screaming Victim). TweakScale does scale things, and these things includes torque and explosion potential. A Part partially bad configured (as some parts in the past, inducing TweakScale to render a zero or negative mass on the part), and perhaps a torque would ended up with INF or NaN, what is a plausible explanation for what you describes.

Since you managed to reproduce the behaviour and I'm not, the answer should be on the craft you are using.

eUd2hLk.png

HTOuRfo.png

7JeJ1cx.png

OnmOzAo.png

IROUv2H.png

gRgQK6h.png

eo3F6sX.png

jX7loSI.png

Edited by Lisias
reordering screenshots
Link to post
Share on other sites

While I've recreated this without landing legs, in a small craft I needed landing legs and wings. The interesting thing is that as soon as  half to all but one of the SAS explodes, the craft stops spinning.

https://www.audunis.com/wp-content/uploads/2020/06/DeathspinTest.zip

Let me know if that download doesn't work. 

Interesting thing is, I can't get it to recreate on a small scale without using some mods. I'm not sure if its because the SAS is high powered in the BlueTie SAS or if it has something to do with the OPT wings or KF Lannding legs. 

Just launch, start spinning using q or e, angle to one side slightly and cut throttle. When you hit the ground, you'll see the spin until mostly SASless. Now I need to open up my huge rover and see if keeping only one SAS will prevent DS.

EDIT:

So for those who are just reading this, my stating about holding the q and e was to increase the likely hood of the death spin from happening. After doing more testing, I'm finding that I can't recreate it as easily as I did last weekend and the weekend before. That tells me that one of the mods I just updated might have fixed things.

I do have one craft to test left

Edited by Azic Minar
For those just reading this
Link to post
Share on other sites
  • 2 weeks later...
On 6/10/2020 at 6:32 PM, Azic Minar said:

@Lisias Did you see the preview for the new parts yet? It looks like the flag has scaling built into it! I wonder if its just causing it to load different sizes, or if there is going to be some official coding for scaling built in with this update?

Hey, I think I now how Squad implemented that Scale thingy of theirs! :)

Unfortunately, it ended up biting TweakScale - not that bad, but enough to make me open an issue and work on it. (oh, well - it could be worse. :) )

Really thanks for the heads up - I would be chasing my tail right now without it! 

-- post edit --

Nope, I was completely wrong! :P But I learn something in the process, so the heads up leaded me to the right place in a way or another! :) 

------- post post edit ------

METAR

KSP 1.9 rendered the Sanity Checks inefective, the code that removed TweakScale from an insane part is not working anymore, and so some of the terrible things that used to happen in the past are, now, risking happening again.

I'm currently working on an alternative solution, in the hopes to prevent savegame breakage once the Sanity Checks works again - the whole point of the Sanity Checks is to prevent insane parts to be used to prevent breakage on living crafts on the savegame since KSP injects prefab data on them on loading the savegame.

Now I have God knows how many savegames with insane parts flying around, and fixing things on TweakScale can break them.

I'm not exaxtly happy right now.

- -- -- -- CLIMAT -- -- -- 

KSP is innocent. Regression tests downto KSP 1.4.3 revealed that the current withdrawing method is not working anymore.

My current theory is that the refactoring needed to support ModulePartVariant changing the surface attachment points broke some kind of equilibrium needed by the wirhdrawing stunt, and I did'n realised it at the time.

Edited by Lisias
CLIMAT
Link to post
Share on other sites
4 hours ago, Azic Minar said:

I wish I knew more to help. Eventually I'll know that much codding.  Could this be related to the MM no longer using the newest version when there are two or more in the install?

Not directly related (if at all).

MM problem is about changing how Assemblies are loaded into memory.

This is how a PartModule is initialized on a part.

In the past, removing the PartModule's section from the prefab on MainMenu prevented the PartModule from being initialized. Now, it is initialized nevertheless (and so TweakScale borks because there's no data available).

I'm not worried about how to deactivate the module (worst case cenario, I shove a flag on it and make the thing to ignore all unity and KSP callbacks and events).

I'm concerned on how the part is handled by the bad initialized module. This will affect the mass of the part, umbalancing the whole craft once this is fixed for starters.

Happily, only 9 parts on a vanila installment are susceptible to this problem - but add'ons are starting to make good use of ModulePartVariants on complex parts (it's how I detected the problem), and things can escalate fast.

Edited by Lisias
tyop! Surprised?
Link to post
Share on other sites

ANNOUNCE

Release 2.4.3.15 is available for downloading.

This is an VERY IMPORTANT update, fixing some lsat minute problems detected on KSP >= 1.8, as well introducing new Houstons to alert the users about problems on the instalment:

  • KSP Recall is now not only recommended, but heavily pushed on KSP >= 1.9. TweakScale will pesky you until you install it.
  • TweakScale 2.4.3 will not run on KSP >= 1.10 , and will complain it you try.
    • Only Version 2.4.4 will support KSP 1.10
    • But you can try your luck nevertheless - just be absolutely sure you installed S.A.V.E.
      • Really. Everybody should be using S.A.V.E. by now, and I holding myself to do not code a new Houston for it.

See OP for the links.

Highlights

KSP 1.10.x Support

KSP 1.10 definitively will not be supported by TweakScale without a comprehensive set of testings from my side.

Don't expect KSP 1.10 support on 2.4.3, I'm almost certain that only 2.4.4.0 will allow being run on KSP 1.10 (however, Kerbal proposes, Kraken disposes...).

But you can try your luck if you want.

KSP 1.9.x Support

VAB/SPH Editor

KSP 1.9.x Editor introduced a glitch that was rendering parts with ModulePartVariant displaced on loading. Crafts being instantiated on LaunchPad/Runway (as also living craft on the Universe) are not affected.

This is what I know until this moment:

  • KSP is shoving back prefab data into living crafts on savegames (and on loading crafts on the Editor) since 1.6 or 1.7, and recently started to obliterate the resources customisations made by Modules.
    • You already know that, KSP Recall was born due it.
  • The novelty is that, somehow, surface attachments are, now, also affected - but not exactly as the Resources, and this is what caught me with my pants down (and what made me bork the 2.4.3.13 release, already withdrawn):
    • Parts with variants are getting surface attachments mangled on Editor, but parts without variants are not!
      • Attachments points apparently are being mangled too, but I did't did a full testing on the matter - proceed with caution
        • Attachment points with parts are also reset, but are preserved on classic parts.
        • Boy, what a mess... :P 
  • This, probably, could be also solved by using the GameEvents.onEditorVariantApplied, but since KSP still mangles with TweakScale business in other situations (including on Flight Scene), I would need to split the survivorship logic in two different places now - so I opted to keep the current Event handling for while until I fully refactor (and validade) the code.
    • Surviving different KSP Version's idiosyncrasies are taxing badly the codetree
    • And I'm firm on my commitment to keep TweakScale (core) compatible with every KSP still em use - expect TweakScale 2.5 to be useable down to KSP 1.2 (KSPe already does it, by the way) - so I will be able to backport every fix and enhancements to people that choose to stay playing older KSP versions.
  • The after math is that I'm still using Unity's Update callback to handle the first Scale Back event, needed to survive KSP manglings. For some time I considered using KSP Recall to handle this situation, but since Scaling is the TweakScale's Core Business, and I don't intend to tie KSP Recall to TweakScale in any way (it must be a generic solution for everyone, not just for me), I rolled back any change on it.

Please also note that there's a lot of glitches on KSP 1.9 Editor not related to TweakScale (or any other Add'On).

Drain Valve

The FTE-1 Drain Valve is being scaled, however not properly. Mass and size scales fine, but the drain rate is not. See Issue #102 for details.

Resources

KSP 1.9.x is known to replace any Resource customisation made by custom modules with default definitions from the prefab.

This affects many Add'Ons, being TweakScale only one of them. So a new Add'On called KSP Recall was created to specifically handle KSP issues that would affect everybody.

Users of KSP 1.9.0 and 1.9.1 are urged to install KSP Recall. Future KSP releases may or may not fix the glitches KSP Recallaims to workaround - but until there, you need KSP Recall to use TweakScale on KSP 1.9.x . 

Misc

Keep an eye on the Known Issues file.

— — — — —

This Release will be published using the following Schedule:

  • GitHub, reaching first manual installers and users of KSP-AVC. Right now.
  • CurseForge, Thursday night
  • SpaceDock (and CKAN users), Friday night

The reasoning is to gradually distribute the Release to easily monitor the deployment and cope with eventual mishaps.

 

On 6/23/2020 at 3:09 AM, Azic Minar said:

Can you give an example of a part in vanilla with this problem? 

 

Check this comment on the Issue #114.

Edited by Lisias
Writting in a hurry leads to strange phrases...
Link to post
Share on other sites

Hello, I received a pop-up on game load titled "Houston, we have a problem".It told me that there are problems with certain parts and that I needed to post the log to this forum, if not, please redirect me to the proper location. I've seen this message once before, and downloaded ksp recall. This didn't work, so I deleted tweakscale, which stopped the warnings, but broke saved crafts, and caused rockets to have pink squares on them. So I reinstalled tweakscale, and am back to where I started. With a quick, uneducated look at the log, it seems that the failed sanity checks are being caused by the structural tubes and engine plates. The fatal errors are caused by parts from KIS.

Is there any way I can fix this without having to uninstall KIS, or is that the only way? 

Log

Link to post
Share on other sites
42 minutes ago, Froost said:

Hello, I received a pop-up on game load titled "Houston, we have a problem".It told me that there are problems with certain parts and that I needed to post the log to this forum, if not, please redirect me to the proper location. I've seen this message once before, and downloaded ksp recall. This didn't work, so I deleted tweakscale, which stopped the warnings, but broke saved crafts, and caused rockets to have pink squares on them.

Deinstalling TweakScale would break flying crafts that have scaled parts for sure. That's the reason I push S.A.V.E. to be used by everyone - something breaks somewhere (and not only on TweakScale), and we risk KSP shoving bad data on flying crafts.

But the pink squares is a new for me - TweakScale doesn't touches textures, it scales the mesh and let KSP handle the texturing....

 

42 minutes ago, Froost said:

So I reinstalled tweakscale, and am back to where I started. With a quick, uneducated look at the log, it seems that the failed sanity checks are being caused by the structural tubes and engine plates. The fatal errors are caused by parts from KIS.

Is there any way I can fix this without having to uninstall KIS, or is that the only way? 

Log

The Sanity Checks are about parts with known problems, and that are deactivated. TweakScale warns you about the deactivation because someone wrote a patch to it, and so it's expected that such part would be scaled. That parts you mentioned are parts with VARIANTS with mass, a known problem  still to be fixed by TweakScale - it's scheduled to be (AT LAST!) handled on TweakScale 2.4.4 series - assuming a new pandemic doesn't shove all my plans on the trash bin again....

Since these parts were never really supported in the past, this is not a FATALity (i.e., something that will break KSP). That pesky warning, FINALLY, now are only issued when Module Manager redo the patching (to tell you the true, TweakScale checks the timestamp of the MM caches and suppress Warnings and Advises if they are older than 1 hour).

Now... That Houstons you got are the real deal - Something is usually really bad (or looks like being bad - TweakScale is not really smart to tell weird things from bad weird things, so it yells on anything weird). One weirdness that can be really problematic (but not always) is double patching, i.e., when a rogue patch patches an already patched part uncontrollably. Last time this happened on KIS was due me forgetting to remove a old file from the TweakScale distribution - and, yeah, you are using TweakScale 2.4.3.11 - the one I had borked! :(

[LOG 15:53:19.127] [TweakScale] Version 2.4.3.11 /L

<yada yada yada>

[LOG 15:53:27.167] Applying update TweakScale/Deprecating/patches/KIS_TweakScale/@PART[KIS_Container1] to KIS/Parts/container1/part.cfg/PART[KIS_Container1]
[LOG 15:53:29.643] Applying update TweakScale/patches/KIS_TweakScale/@PART[KIS_Container1] to KIS/Parts/container1/part.cfg/PART[KIS_Container1]

Please use the latest TweakScale, 2.4.3.15 . It's currently only on Github, CurseForge will be updated tonight and SpaceDock (and CKAN) tomorrow night.

However, the current patches for KIS are EoL, they are old and do not scales most current KIS parts. TweakScale Companion for KIS will solve that, but currently this is still in Alpha status, so perhaps you should wait a bit as I didn't ironed out all the bugs of that thing (if any, the true is that I don't know if there're bugs on it yet!).

In time, I found a lot of MiniAVC dlls on your instalment. MiniAVC was deprecated by the maintainer, and it's known to play havoc on KSP >= 1.8, sometimes in a pretty nasty way. Please install ZeroMiniAVC - really, install it, it's a question of time until something triggers a crash.

Cheers!

Edited by Lisias
Wrong link on ZeroMiniAVC
Link to post
Share on other sites

Thank you very much! The problems are gone, no more FATAL errors. Although, the squares are still there. Not that I think has anything to do with my previous problem. Here they are on an engine, and another on a Kerbal. It's OK if you have no idea what the cause is. I think it may be an interaction with Restock, and Planetshine. I just wanted to show you if you where curious. Thank you again for your continued support towards the community.

P.S. The previous post, if you even see it, had messed up links. And I couldn't see it to edit them. (can you tell I don't know what I'm doing?) :blush:

Edited by Froost
reason for duplicate posts
Link to post
Share on other sites
8 hours ago, Froost said:

Thank you very much! The problems are gone, no more FATAL errors. Although, the squares are still there. Not that I think has anything to do with my previous problem. Here they are on an engine, and another on a Kerbal

Humm.... I checked your KSP.log again, and didn't found Scatterer, Kopernicus, EVE or anything that could be involved on this.

However... Perhaps the problem would be on the exhaust or any other kind of emission? It's a wild guess, but try to uninstall Smoke Screen to see what happens.

 

8 hours ago, Froost said:

(can you tell I don't know what I'm doing?) :blush:

Dark secret of modding KSP: most of the time, we neither. :sticktongue:

Edited by Lisias
Link to post
Share on other sites

I'm trying to fix some of the exponents used in tweakscale to be more accurate.

I've been able to fix engine thrust scaling to be accurate with actual rocket propulsion software with the following code:

//This is for engines to fix their size/scaling.
@TWEAKSCALEEXPONENTS[ModuleEngines]
{
%minFuelFlow = 2 //original was set to 2.5
%maxFuelFlow = 2 //original was set to 2.5
%maxThrust = 2 //original was set to 2.5
}

But I'm hitting a rock in trying to fix engine mass scaling:

//this fixes mass scaling for engines.
@TWEAKSCALEEXPONENTS[Part]:HAS[#category[Engine]]
{
%mass = 2 //original was set to 3
}

Doesn't work. Has anyone made a custom CFG that adjusts ONLY engine mass scaling?


EDIT: If you want liquid engines to scale correctly; you must use:

type = stack_square

This correctly scales their mass without the need for a patch

 

 

Edited by MKSheppard
Fixed my problem.
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...