Jump to content

[KSP >= 1.3.0] TweakScale - Under Lisias' Management - 2.4.7.6 - 2024-0322


Lisias

Recommended Posts

@LisiasI made A Config File for all the ReStock+ parts. Could you insert that into your mod?
Config file: https://cdn.discordapp.com/attachments/295199794102796288/621422952134737922/ReStockPlus_Tweakscale.cfg

I haven't tested this yet, Please correct me if you find anything wrong. I am quite new to this.

Link to comment
Share on other sites

1 hour ago, IronKerbal said:

@LisiasI made A Config File for all the ReStock+ parts. Could you insert that into your mod?
Config file: https://cdn.discordapp.com/attachments/295199794102796288/621422952134737922/ReStockPlus_Tweakscale.cfg

I haven't tested this yet, Please correct me if you find anything wrong. I am quite new to this.

Yeah, I can add it to the Experimental fork, and after validating it publish it on the incoming 2.4.4.x series.

But… Did you considered alternatives? ReStock guys wouldn't want to adopt the patches themselves? I think that the Add'On maintainer is the preferable way for publishing these things, as it prevents Updating Fest when an Add'On change something - only the changed Add'On needs to be republished, and not everybody else.

Another possibility is you publishing yourself the Add'On, with both ReStock and TweakScale as dependencies. Something as "TweakScale_ReStock_Plugin", and I will help you in any way you need (including on how not to build a netkan file - :sticktongue:).

The nice thing of this last option is that I'm going to do exactly that for the upcoming 2.5 TweakScale series - everything non Stock/Vanilla will be split into "Plugins" (or handed over to the Add'On maintainers willing to take care of it) and be maintained separately, and what would be the best time to start it but now? :) 

What do you think? No wrong answers here. :) 

 

Link to comment
Share on other sites

45 minutes ago, Lisias said:

Yeah, I can add it to the Experimental fork, and after validating it publish it on the incoming 2.4.4.x series.

But… Did you considered alternatives? ReStock guys wouldn't want to adopt the patches themselves? I think that the Add'On maintainer is the preferable way for publishing these things, as it prevents Updating Fest when an Add'On change something - only the changed Add'On needs to be republished, and not everybody else.

Another possibility is you publishing yourself the Add'On, with both ReStock and TweakScale as dependencies. Something as "TweakScale_ReStock_Plugin", and I will help you in any way you need (including on how not to build a netkan file - :sticktongue:).

The nice thing of this last option is that I'm going to do exactly that for the upcoming 2.5 TweakScale series - everything non Stock/Vanilla will be split into "Plugins" (or handed over to the Add'On maintainers willing to take care of it) and be maintained separately, and what would be the best time to start it but now? :) 

What do you think? No wrong answers here. :) 

 

Ok sounds Good, I will try Making it my own mod.

Link to comment
Share on other sites

Will all the configs stay within tweakscale or will  I have to go and get the configs from other people because that would be a huge pain in the butt,  being an end user all you want to do is download install and play not search for the configs you need for the 100 plus mods you may have. Or have i got this completely wrong 

Link to comment
Share on other sites

What follows is a open brainstorming about the problems I see, not about your arguing. I'm not "fighting" you, I'm exposing problems that are happening (or I think it will) , and how to cope with them.

Of course, by solving "my' problems, we end up creating some others. This exchange of ideas is how we can try to reach a balance on the issue!

Fell free to mercilessly bash anything you think it's wrong on the argument. :)

 

1 hour ago, Virtualgenius said:

Will all the configs stay within tweakscale or will  I have to go and get the configs from other people because that would be a huge pain in the butt,  being an end user all you want to do is download install and play not search for the configs you need for the 100 plus mods you may have. Or have i got this completely wrong 

The patches are rarely updated, so you will not have to download everything every time. You will download only what's changed.

Downloading everything in a single ZIP is also a pain in the butt - every time a single file changes, you need to download the whole shebang. KAX had added a new part? You need to Download TweakScale again. NFA added a new part? You need to download TweakScale again. You don't use NFA or KAX? Too bad, you will have to download it nevertheless. 

But if the patches are bundled with the Add'On, things are solved by themselves : you download the newest version for the Add'Ons you use, and you are set.

Another potential source of trouble are embedding deprecated versions of dependencies on the bundle. So if you have FuzzyTools, and bundle it to FancyAddOn and NiceAddOn, and then update FuzzyTools and release a new version for FancyAddOn, all the users need to be cautious to do not overwrite FuzzyTools when they download NiceAddOn - at least until the maintainer updates it. And now and then this doesn't happens.

How many 100 megabytes sized AddOns are "updated" when only the dependencies change? I just spend a good part of my night downloading 250 Megabytes from the exact same binary files under a new zip filenames (about 4 of them) because *one* dependency changed *15* files, I think a total of 350Kbytes of really new files. Had that Add'Ons not embedded all that dependencies, I would need to update only one with a couple megabytes only,

It's nuts, this is almost suicidal: old and deprecated Add"Ons (or dependencies) are the main source of crashes - and this long and troublesome series of posts on this thread from the last months shows it clearly.

So by going on the "everything and the kitchen's sink" bundle, you will be downloading things every time the same way. The only difference is the size of the downloading bundle, and how many times you will have to download the same thing again and again. And I'm not even talking about the hassle to keep updating everything from the maintainer's side of the things.

Alternatively, and this is indeed the best way of keeping your installment updated, use an Update Tool. KSP-AVC is a very handy tool, and CKAN besides some problems, do the job for a large portion of the userbase. I agree that they are far from perfection, but broken things can be fixed - how about to help these Add'On maintainers to perfect the tools by beta testing, bug reporting and helping on writing documentation and configuration files for Add'On maintainers? On Linux distros like Debian, packaging is a role by itself.

The convenience you think you have by having everything packed into a same file is minor. The burden you have by the need of downloading again everything, every time a single file changes - not to mention the risk of overwriting dependencies with older versions on the way - is far greater.

But most people don't see this burden, as they use a Update Tool to automate the thing. But if most people use an automated tool to update things, why we are still shoving everything on a single file as default?

That said, the project being split in different packages doesn't means that one cannot shove all the dependencies into a custom bundle and publish it. As long the guy takes the responsibility to update the bundle and to properly support the thing, as I'm doing here, it's all clear. And yeah, it's something that I will probably have to do myself on TweakScale. :)

This is what I'm planning to do with the "TweakScale" entry on CKAN - using it as a meta-package, so the transition will be seamless to people that already use TweakScale nowadays:

  • TweakScale
    • TweakScale-Core
    • TweakScale-<AddOn-0>-Plugin
      • Depends TweakScale-Core
      • Depends <AddOn-0>
    • TweakScale-<AddOn-1>-Plugin
      • Depends TweakScale-Core
      • Depends <AddOn-1>
    • TweakScale-<AddOn-n>-Plugin
      • Depends TweakScale-Core
      • Depends <AddOn-n>

Of course, I need to study netkan files a lot in order to accomplish this thing. And how to handle SpaceDock and CurseForge is something I still need to figure out.

Link to comment
Share on other sites

4 hours ago, Lisias said:

his is what I'm planning to do with the "TweakScale" entry on CKAN - using it as a meta-package, so the transition will be seamless to people that already use TweakScale nowadays:

Did the same with the release of On Demand Fuel Cells (ODFC) - put the core in one and then the two packages of patches (not mutually exclusive) in another. Seems to be working very well.

I like and support this idea. Install the core plus none or one or more of the patch files.

seems to me the biggest pain is maintaining all the individual version / readme files - other than that - and a whole lot more initial setup work - all is well.

 

just for all that is nuclear - no miniavc.... have enough of those buggers floating around.

Edited by zer0Kerbal
Link to comment
Share on other sites

On 9/12/2019 at 5:11 PM, qromodynmc said:

is there a way to disable fatal error warning at start, i know im in trouble, i just enjoy it.

Well.. Yep.

On 9/12/2019 at 5:41 PM, zer0Kerbal said:

delete the parts it yells about? :P

This one is the one I recommend. But you don't need to manually delete the patch, you can hack your way into it.

On somewhere in the GameData (I like GameData/__LOCAL/TweakScale/hacks), put a file like this:

@PART[victim1,victim2,etc]:FINAL
{
	-MODULE[TweakScale],* { }
}

This will get rid of the TweakScale modules and keep your gaming safe. But then any savegame using that parts would suffer.

There's another option, if you know the problem is the benign kind (or are willing to take your chances). Use a OVERRULE.

Be advise that overrules… overrules TweakScale sanity checks. You will be at your own on this - but, hey, now you know it. :)

@PART[victim1,victim2,etc]:NEEDS[TweakScale]:FINAL
{
	@MODULE[TweakScale]
	{
		ISSUE_OVERRULE = "#72"
	}
}

 

On 9/12/2019 at 6:16 PM, TheKSPBeginner said:

Using BDB dev branch makes fatal error pls help

I need your KSP.log and ModuleManager.ConfigCache . Publish it on a dropbox, google drive or something and link them here!

Edited by Lisias
Forgot a :FINAL on a patch
Link to comment
Share on other sites

Hi, I am also having an issue with a part. I tried to create a .cfg (this is what you meant by a file?) in Tweakscale/hacks to disable tweakscale for the 1 object having an issue but it did not seem to work. logs and my failed hack are in the drive below.

https://drive.google.com/drive/folders/1CdEwBcCxCDEEI5XiATYGkzmbK2TZ0x_a?usp=sharing

Link to comment
Share on other sites

9 hours ago, TheKSPBeginner said:

Wow! 69 FATALities. Almost as bad as one installment of mine, that got 172. :)

[LOG 09:10:25.892] [TweakScale] INFO: WriteDryCost Concluded : 2443 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 69 Show Stoppers found; 9 Sanity Check failed; 1065 unscalable parts.

On the bright side, you have only 9 Sanity fails, and these 9 are due lack of proper support - no worries, these will be tacked down soon.

That 1065 unscalable parts are parts without TweakScale (including that 9), from a pool of 2443 parts on the GameDatabase. This is just informational, so you know that about 43% of your inventory is not scalable.

Nows, let's check that 69 victims:

[LOG 09:10:25.752] [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 ).
[LOG 09:10:25.752] [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 ).
[LOG 09:10:25.753] [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 ).
[LOG 09:10:25.753] [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 ).
[LOG 09:10:25.753] [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 ).
[LOG 09:10:25.753] [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 ).
[LOG 09:10:25.754] [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 ).
[LOG 09:10:25.754] [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 ).
[LOG 09:10:25.754] [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 ).
[LOG 09:10:25.755] [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 ).
[LOG 09:10:25.755] [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 ).
[LOG 09:10:25.756] [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 ).
[LOG 09:10:25.756] [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 ).
[LOG 09:10:25.756] [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 ).
[LOG 09:10:25.757] [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 ).
[LOG 09:10:25.757] [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 ).
[LOG 09:10:25.758] [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 ).
[LOG 09:10:25.758] [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 ).
[LOG 09:10:25.849] [TweakScale] ERROR: **FATAL** Part Decoupler.1p5 (TD-18 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.849] [TweakScale] ERROR: **FATAL** Part Decoupler.4 (TD-50 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.850] [TweakScale] ERROR: **FATAL** Part Separator.1p5 (TS-18 Stack Separator) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.850] [TweakScale] ERROR: **FATAL** Part Separator.4 (TS-50 Stack Separator) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.851] [TweakScale] ERROR: **FATAL** Part Size1p5.Strut.Decoupler (Size 1.5 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.852] [TweakScale] ERROR: **FATAL** Part LiquidEngineKE-1 (Kerbodyne KE-1 "Mastodon" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.852] [TweakScale] ERROR: **FATAL** Part LiquidEngineLV-T91 (LV-T91 "Cheetah" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.853] [TweakScale] ERROR: **FATAL** Part LiquidEngineLV-TX87 (LV-TX87 "Bobcat" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.854] [TweakScale] ERROR: **FATAL** Part LiquidEngineRE-I2 (RE-I2 "Skiff" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.855] [TweakScale] ERROR: **FATAL** Part LiquidEngineRE-J10 (RE-J10 "Wolfhound" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.856] [TweakScale] ERROR: **FATAL** Part LiquidEngineRK-7 (RK-7 "Kodiak" Liquid Fueled Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.857] [TweakScale] ERROR: **FATAL** Part LiquidEngineRV-1 (RV-1 "Cub" Vernier Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.857] [TweakScale] ERROR: **FATAL** Part monopropMiniSphere (Stratus-V Minified Monopropellant Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.857] [TweakScale] ERROR: **FATAL** Part Size1p5.Monoprop (FL-R5 RCS Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.857] [TweakScale] ERROR: **FATAL** Part Size1p5.Size0.Adapter.01 (FL-A150 Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.858] [TweakScale] ERROR: **FATAL** Part Size1p5.Size1.Adapter.01 (FL-A151L Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.858] [TweakScale] ERROR: **FATAL** Part Size1p5.Size1.Adapter.02 (FL-A151S Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.858] [TweakScale] ERROR: **FATAL** Part Size1p5.Size2.Adapter.01 (FL-A215 Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.858] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.01 (FL-TX220 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.859] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.02 (FL-TX440 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.859] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.03 (FL-TX900 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.859] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.04 (FL-TX1800 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.860] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.05 (FL-C1000 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.860] [TweakScale] ERROR: **FATAL** Part Size3.Size4.Adapter.01 (Kerbodyne S3-S4 Adapter Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.860] [TweakScale] ERROR: **FATAL** Part Size4.EngineAdapter.01 (Kerbodyne Engine Cluster Adapter Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.860] [TweakScale] ERROR: **FATAL** Part Size4.Tank.01 (Kerbodyne S4-64 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.860] [TweakScale] ERROR: **FATAL** Part Size4.Tank.02 (Kerbodyne S4-128 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.861] [TweakScale] ERROR: **FATAL** Part Size4.Tank.03 (Kerbodyne S4-256 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.861] [TweakScale] ERROR: **FATAL** Part Size4.Tank.04 (Kerbodyne S4-512 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.861] [TweakScale] ERROR: **FATAL** Part roverWheelM1-F (RoveMax M1-F Rover Wheel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.861] [TweakScale] ERROR: **FATAL** Part Size1to0ServiceModule (SM-6A Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.862] [TweakScale] ERROR: **FATAL** Part ServiceModule18 (SM-18 Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.862] [TweakScale] ERROR: **FATAL** Part ServiceModule25 (SM-25 Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.862] [TweakScale] ERROR: **FATAL** Part kv1Pod (KV-1 'Onion' Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.863] [TweakScale] ERROR: **FATAL** Part kv2Pod (KV-2 ‘Pea’ Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.864] [TweakScale] ERROR: **FATAL** Part kv3Pod (KV-3 'Pomegranate' Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.864] [TweakScale] ERROR: **FATAL** Part Mk2Pod (Mk2 Command Pod) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.865] [TweakScale] ERROR: **FATAL** Part MEMLander (Munar Excursion Module (M.E.M.)) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.865] [TweakScale] ERROR: **FATAL** Part EquiTriangle0 (SP-T06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.866] [TweakScale] ERROR: **FATAL** Part EquiTriangle1 (SP-T12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.866] [TweakScale] ERROR: **FATAL** Part EquiTriangle1p5 (SP-T18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.866] [TweakScale] ERROR: **FATAL** Part EquiTriangle2 (SP-T25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.866] [TweakScale] ERROR: **FATAL** Part Panel0 (SP-S06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.867] [TweakScale] ERROR: **FATAL** Part Panel1 (SP-S12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.867] [TweakScale] ERROR: **FATAL** Part Panel1p5 (SP-S18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.867] [TweakScale] ERROR: **FATAL** Part Panel2 (SP-S25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.867] [TweakScale] ERROR: **FATAL** Part Triangle0 (SP-R06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.868] [TweakScale] ERROR: **FATAL** Part Triangle1 (SP-R12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.868] [TweakScale] ERROR: **FATAL** Part Triangle1p5 (SP-R18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.868] [TweakScale] ERROR: **FATAL** Part Triangle2 (SP-R25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 09:10:25.869] [TweakScale] ERROR: **FATAL** Part HeatShield1p5 (Heat Shield (1.875m)) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).

All that "truss" problems are old news. It's Contares.

[LOG 08:52:37.306] Applying update Contares/Patches/CONTARES_TweakScale/@PART[truss-octo-*] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-03.cfg/PART[truss-octo-03]
[LOG 08:53:12.070] Applying update TweakScale/patches/NFT_TweakScale/@PART[truss-octo-03] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-03.cfg/PART[truss-octo-03]
[LOG 08:54:34.286] Applying update B9PartSwitch/PartInfo/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]]:FOR[zzzzzz-B9PartSwitch] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-03.cfg/PART[truss-octo-03]
[LOG 08:54:35.569] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-03.cfg/PART[truss-octo-03]

This was already detected and fixed here. And the latest TweakScale has already the HotFix on the distribution file.

TL;DR: Contares problems can be fixed are follows:

  • Download (click on the Raw button) or extract from the distribution file the TweakScale/Extras/TweakScale/HotFixes/Contares--TweakScale.cfg file.
  • Move it into some place on your KSP installment. Be sure to remember where, as you would want to delete it once the Add'Ons maintainers fix the problem.
    • I suggest to use GameData/__LOCAL/TweakScale/HotFixes/
  • Every time you update Contares, you will need to check if this HotFix is still needed. HotFixes brute force their way into the GameDatabase, and if Contares make any fix on it patches, they will be trashed in favor of the HotFix.

Well, this solves 18 issues at once. Now let's check the others. Let's check Decoupler_1p5.

[LOG 08:53:42.020] Applying update TweakScale/patches/SquadExpansion/MakingHistory/Coupling/@PART[Decoupler_1p5] to SquadExpansion/MakingHistory/Parts/Coupling/Decoupler_1p5.cfg/PART[Decoupler_1p5]
[LOG 08:53:43.334] Applying update TweakscaleMakingHistoryConfigs/Coupling/@PART[Decoupler_1p5] to SquadExpansion/MakingHistory/Parts/Coupling/Decoupler_1p5.cfg/PART[Decoupler_1p5]
[LOG 08:53:51.497] Applying update EngineLight/decoupler-configs/@PART[*]:HAS[@MODULE[Module*Decouple*]]:FOR[EngineLight] to SquadExpansion/MakingHistory/Parts/Coupling/Decoupler_1p5.cfg/PART[Decoupler_1p5]
[LOG 08:54:36.089] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to SquadExpansion/MakingHistory/Parts/Coupling/Decoupler_1p5.cfg/PART[Decoupler_1p5]

Well… There's a lot of people patching Decoupler_1p5. This i not necessarily bad, as only double patching TweakScale is surely known to lead to problems. So we have to inspect every patch, what is a but worksome. I will try to cut some work by inspecting the ConfigCache instead, with luck I can trace the source of the double patching inspecting the part directly:

UrlConfig
{
        parentUrl = SquadExpansion/MakingHistory/Parts/Coupling/Decoupler_1p5.cfg
        PART
        {
                name = Decoupler_1p5
        <CUT>
                MODULE
                {
                        name = TweakScale
                        type = stack
                        defaultScale = 1.875
                        scaleFactors = 0.1,  0.3,   0.625, 1.25,  1.875, 2.5,  3.75, 5.0, 7.5, 10, 20
                        incrementSlide = 0.01, 0.025, 0.025, 0.025, 0.025, 0.05, 0.05, 0.1, 0.1, 0.2
                        type = stack
                        defaultScale = 1.875
                        scaleFactors = 0.1,  0.3,   0.625, 1.25,  1.875, 2.5,  3.75, 5.0, 7.5, 10, 20
                        incrementSlide = 0.01, 0.025, 0.025, 0.025, 0.025, 0.05, 0.05, 0.1, 0.1, 0.2
                        TWEAKSCALEEXPONENTS
                        {
                                name = TweakScale
                                DryCost = 0.5
                                mass = 2
                        }
                }
                MODULE
                {
                        name = TweakScale
                        TWEAKSCALEEXPONENTS
                        {
                                name = TweakScale
                                DryCost = 0.5
                                mass = 2
                        }
                }

MY GOD!! It's full of double patches!!!!

Well… Congrats. This is the worst patching I ever saw. :P There's at least THREE guys shoving patches into this part, one of them is TweakScale default patches. On the bright side, this is one of the benign kind of rogue patching - everybody is shoving the same data into the part, so don't reaaly matter what the datum being used. At least that.

The first and obvious one is TweakscaleMakingHistoryConfigs (and yeah, an illustrious unknown). Delete GameDatabase/TweakscaleMakingHistoryConfigs . I Don't know what is it, and who is still recommending to use it, and frankly, by this time, I strongly recommend to avoid using anything from someone that still tells you to use this thing for the following reasons:

  • It's not available anywhere, I can't find a source for downloading it.
    • So I can't inspect it. I don't have a clue about what is this stunt!
    • So it doesn`t complies with Forum Rules for Add`Ons
  • It's almost a year that TweakScale actively supports Making History from the default installation files.
    • It's long the time this thing were necessary.
    • I once found a download link from Spacedock, but that entry was deleted from the site. Don't have a clue when.

I'm pretty sure there was a time that this patch was needed. But it's way long in the past already. :)

We found one, two more to go.

Let's check EngineLight. Simple mod (nice one!!!), and its patches doesn't touches TweakScale. INNOCENT #ghostRiderFeelings. :sticktongue:

Now let's see Kopernicus. I failed to understand why this is patching a Decoupler, but since this doesn't touch TweakScale neither, it's not the problem.

Well, I ran out of suspects. Only TweakscaleMakingHistoryConfigs appears to be playing a role on this. Since I counted 60 entries on the FATALities mentioning it, I'm pretty sure that by bluntly deleting GameData/TweakscaleMakingHistoryConfigs your installment should be fine. 

If anything bad still remains, publish the new KSP.log and ModuleManager.ConfigCache here and I will look on it.!

Scale Safe! ;)

2 hours ago, Strait_Raider said:

Hi, I am also having an issue with a part. I tried to create a .cfg (this is what you meant by a file?) in Tweakscale/hacks to disable tweakscale for the 1 object having an issue but it did not seem to work. logs and my failed hack are in the drive below.

https://drive.google.com/drive/folders/1CdEwBcCxCDEEI5XiATYGkzmbK2TZ0x_a?usp=sharing

Uh… I think I didn't explained correctly how to write the patch. Sorry. :)

@PART[S2Structural]:FINAL
{
	-MODULE[TweakScale],* { }
}

Get rid of the < and > . It was meant to denote something not literal - but sometimes I forget most people here are not techie guys, and from the ones that are, most of them are not die hard UNIX freaks as me (where I got used to this notation). I will fix the original post too.

UUGH… I also forgot an opening brace!! (the first one below :FINAL). Sorry! :P

Edited by Lisias
UGH =P
Link to comment
Share on other sites

38 minutes ago, DoritoPanda1423 said:

the warning told me to put this here so here it is:

Tweakscale Version: 2.4.3.3

KSP version:1.4.1

I almost certainly forgot something so let me know what I need to add

Thanks in advance

KSP.log and ModuleManager.ConfigCache, please! :) 

Link to comment
Share on other sites

4 minutes ago, DoritoPanda1423 said:

Do i attach them or paste them in as text?

Publish them on DropBox, GoogleDrive or some other file sharing service. A full explanation on the matter can be found here:

 

Link to comment
Share on other sites

On 9/14/2019 at 9:08 PM, DoritoPanda1423 said:

E lavamos nozes! ("And we wash walnuts" - a joke with "E lá vamos nós", that sounds like "e lavamos nozes", that translated goes to "and we wash walnuts" - yeah. late night already).

Spoiler

FlakySeveralAfricangroundhornbill-size_r

And away we go!

Ugh!!!! :o

[LOG 17:39:52.559] [TweakScale] INFO: WriteDryCost Concluded : 708 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 371 Show Stoppers found; 0 Sanity Check failed; 317 unscalable parts.

Dude, we have a winner. Half the parts on your installment has a FATALity. Worst, the DryCostWriter is failing a lot too:

[LOG 17:39:52.605] [TweakScale] ERROR: part=parachuteRadial (Mk2-R Radial-Mount Parachute) Exception on Sanity Checks
: System.NullReferenceException: Object reference not set to an instance of an object
  at TweakScale.PrefabDryCostWriter.checkForSanity (.Part p) [0x00000] in <filename unknown>:0
  at TweakScale.PrefabDryCostWriter+<WriteDryCost>d__3.MoveNext () [0x00000] in <filename unknown>:0

However, this is going to be easier than I had feared! Relax, the fix is simple. There're more than one copy of TweakScale on your GameData.  That enormous amount of Exceptions are due a Toe Stomping Fest between TweakScale 2.4.3.4 and this evil older brother, TweakScale 2.4.3.3. :sticktongue:

Scale v2.4.3.4
Scale_Redist v1.0.0.0 / v2.4.3.4
RasterPropMonitor v0.30.6.14937
KerbetrotterTools v1.2.10.0
Stock assembly: KSPSteamCtrlr v0.0.1.35
TimeControl v2.9.6.0
KSPe.Light.TweakScale v2.1.0.13
Scale v2.4.3.3
Scale_Redist v1.0.0.0 / v2.4.3.4

By accident, something had extracted a copy of TweakScale on the wrong place:

[LOG 17:34:49.082] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\TweakScale\Plugins\KSPe.Light.TweakScale.dll
[LOG 17:34:49.114] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\TweakScale\Plugins\Scale.dll
[LOG 17:34:50.364] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\KSPe.Light.TweakScale.dll
[LOG 17:34:50.378] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\Scale.dll

Delete D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData and everything will be alright!!

Edited by Lisias
Fixing the animated gif
Link to comment
Share on other sites

1 minute ago, Lisias said:

E lavamos nozes! ("And we wash walnuts" - a joke with "E lá vamos nós", that sounds like "e lavamos nozes", that translated goes to "and we wash walnuts" - yeah. late night already).

  Reveal hidden contents

FlakySeveralAfricangroundhornbill-mobile

Ugh!!!! :o


[LOG 17:39:52.559] [TweakScale] INFO: WriteDryCost Concluded : 708 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 371 Show Stoppers found; 0 Sanity Check failed; 317 unscalable parts.

Dude, we have a winner. Half the parts on your installment has a FATALity. Worst, the DryCostWriter is failing a lot too:


[LOG 17:39:52.605] [TweakScale] ERROR: part=parachuteRadial (Mk2-R Radial-Mount Parachute) Exception on Sanity Checks
: System.NullReferenceException: Object reference not set to an instance of an object
  at TweakScale.PrefabDryCostWriter.checkForSanity (.Part p) [0x00000] in <filename unknown>:0
  at TweakScale.PrefabDryCostWriter+<WriteDryCost>d__3.MoveNext () [0x00000] in <filename unknown>:0

However, this is going to be easier than I had feared! Relax, the fix is simple. There're more than one copy of TweakScale on your GameData.  That enormous amount of Exceptions are due a Toe Stomping Fest between TweakScale 2.4.3.4 and this evil older brother, TweakScale 2.4.3.3. :sticktongue:


Scale v2.4.3.4
Scale_Redist v1.0.0.0 / v2.4.3.4
RasterPropMonitor v0.30.6.14937
KerbetrotterTools v1.2.10.0
Stock assembly: KSPSteamCtrlr v0.0.1.35
TimeControl v2.9.6.0
KSPe.Light.TweakScale v2.1.0.13
Scale v2.4.3.3
Scale_Redist v1.0.0.0 / v2.4.3.4

By accident, something had extracted a copy of TweakScale on the wrong place:


[LOG 17:34:49.082] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\TweakScale\Plugins\KSPe.Light.TweakScale.dll
[LOG 17:34:49.114] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\TweakScale\Plugins\Scale.dll
[LOG 17:34:50.364] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\KSPe.Light.TweakScale.dll
[LOG 17:34:50.378] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\Scale.dll

Delete D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData and everything will be alright!!

I'll Try it out now

Link to comment
Share on other sites

On 9/15/2019 at 1:46 AM, Lisias said:

The first and obvious one is TweakscaleMakingHistoryConfigs (and yeah, an illustrious unknown). Delete GameDatabase/TweakscaleMakingHistoryConfigs . I Don't know what is it, and who is still recommending to use it, and frankly, by this time, I strongly recommend to avoid using anything from someone that still tells you to use this thing for the following reasons:

I think the problem is that it comes up in CKAN when you type Tweakscale. A lot of people might assume when they see it, that TMHC exists because Tweakscale natively doesnt support MH. I also thought this and briefly had it installed at some point before realizing MH was already covered. I think having TMHC marked as incompatible with tweakscale in the your netkan might help with this issue.

TMHC is marked as max KSP version of 1.4 but a lot of people enable older versions to access mods which arent explicitly updated for the current version. Not 100% sure if this is the source but at lease if you can shut it down this way it will reduce it somewhat.

Edited by Zorg
Link to comment
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...