Lisias

[>= 1.4] TweakScale - Under Lisias' Management - 2.4.3.4 - 2019-0903

Recommended Posts

I'm getting the Houston error also. Here is my log. And thank you for going through and checking everyone's issues. 

KSP.log

Share this post


Link to post
Share on other sites
17 hours ago, AmpCat said:

It's that TweakscaleMakingHistoryConfigs again . Delete GameData/TweakscaleMakingHistoryConfigs and everything will be fine. The last fellow Kerbonaut that had this issue told me that deleting this didn't caused any side effect.

I still don't know what this thing is. Well, I think I do - it appears to be patches for Making History parts. The part count fits, at least. I just don't know from where. :)

Okay, I uninstalled the TweakscaleMakingHistory mod, and no longer getting the 51 Houston errors. It still found 9 Show Stoppers, I think? Some error box that vanished before I had a chance to copy the message. I'll let you know how it behaves.

Share this post


Link to post
Share on other sites
Posted (edited)
18 hours ago, BigPapaGD said:

I'm getting the Houston error also. Here is my log. And thank you for going through and checking everyone's issues. 

KSP.log

Yep. 8 Show Stoppers.

[LOG 16:26:32.606] [TweakScale] WARNING: **FATAL** Found a showstopper problem on M2X.Endcap (Mk2 Airlock Adapter Endcap).
[LOG 16:26:32.607] [TweakScale] ERROR: **FATAL** Part M2X.Endcap (Mk2 Airlock Adapter Endcap) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.705] [TweakScale] WARNING: **FATAL** Found a showstopper problem on MEMLander (Munar Excursion Module (M.E.M.)).
[LOG 16:26:32.705] [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 16:26:32.714] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTInlineAirIntake (XM-600 1.25m Air Intake).
[LOG 16:26:32.714] [TweakScale] ERROR: **FATAL** Part SXTInlineAirIntake (XM-600 1.25m Air Intake) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.714] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTWingSmall (Mk0B Small Modular Wing).
[LOG 16:26:32.714] [TweakScale] ERROR: **FATAL** Part SXTWingSmall (Mk0B Small Modular Wing) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.714] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTWingLarge (FAT-460 Super-Lift Aeroplane Main Wing).
[LOG 16:26:32.714] [TweakScale] ERROR: **FATAL** Part SXTWingLarge (FAT-460 Super-Lift Aeroplane Main Wing) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.719] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTOsaulNoseCockpitAn225 (Kn-225 "Osaul Payload" Cockpit).
[LOG 16:26:32.719] [TweakScale] ERROR: **FATAL** Part SXTOsaulNoseCockpitAn225 (Kn-225 "Osaul Payload" Cockpit) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.720] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTOsualRadCockpit (Mk.P-Yavka Radial Cockpit).
[LOG 16:26:32.720] [TweakScale] ERROR: **FATAL** Part SXTOsualRadCockpit (Mk.P-Yavka Radial Cockpit) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 16:26:32.733] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTtruckbox (Truck Box).
[LOG 16:26:32.733] [TweakScale] ERROR: **FATAL** Part SXTtruckbox (Truck Box) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).

This appears to be something, these parts didn't got Fatalities around here yet. Let's check them:

The M2X_EndCap TweakScale patches are being applied twice:

[LOG 16:19:23.035] Config(@PART[M2X_Endcap]:NEEDS[TweakScale]) Mk2Expansion/Patches/M2X_Tweakscale/@PART[M2X_Endcap]:NEEDS[TweakScale]
[LOG 16:19:23.036] Config(@PART[M2X_Endcap]:NEEDS[TweakScale]) Mk2Expansion/Patches/M2X_Tweakscale/@PART[M2X_Endcap]:NEEDS[TweakScale]

I initially though it was a wildcard problem, let's see the patch:

<line 155>
@PART[M2X_Endcap]:NEEDS[TweakScale]
{
    %MODULE[TweakScale]
    {
        type = stack
        defaultScale = 1.25
    }
}
...
...
...
<494>
@PART[M2X_Endcap]:NEEDS[TweakScale]
{
    %MODULE[TweakScale]
    {
        type = stack
        defaultScale = 1.25
    }
}
  

But I was wrong. The patching is being applied two times.

Well, the fix is obvious: delete de second patch. :)  I applied a pull request to the Maintainer with the fix, and until a new release is issued, you can download the fixed file here (click "Raw") and replace the current file in GameData/Mk2Expansion/Mk2Expansion/GameData/Mk2Expansion/Patches/M2X_Tweakscale.cfg . [and told the Maintainer this time! :P ]

 

This fix one problem. There're 7 more to go. The next problem is MEMLander (Munar Excursion Module (M.E.M.)) :

Spoiler

[LOG 16:19:23.015] Config(@PART[MEMLander]:NEEDS[SquadExpansion]) IndicatorLights/Parts/crewable/memLander/@PART[MEMLander]:NEEDS[SquadExpansion]
[LOG 16:19:23.074] Config(@PART[MEMLander]:FOR[RealPlume]:NEEDS[SmokeScreen]) RealPlume-Stock/SXT Continued/MEMLander/@PART[MEMLander]:FOR[RealPlume]:NEEDS[SmokeScreen]
[LOG 16:19:23.100] Config(PART) SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander/MEMLander
[LOG 16:19:23.111] Config(PART) SXT/Parts/Rocketry/Command/MEM/part/MEMLanderSXT
[LOG 16:19:23.113] Config(@PART[MEMLander]:NEEDS[TweakScale]) SXT/Patches/ModCompatibility/SXT_TweakScale/@PART[MEMLander]:NEEDS[TweakScale]
[LOG 16:19:23.117] Config(@PART[MEMLander]:NEEDS[ConnectedLivingSpace]) SXT/Patches/ModCompatibility/CLS/CLS_StationsBases/@PART[MEMLander]:NEEDS[ConnectedLivingSpace]
[LOG 16:19:23.149] Config(@PART[MEMLander]) TweakScale/patches/SquadExpansion/MakingHistory/Pods/@PART[MEMLander]
[LOG 2019-08-03 16:14:12.076] Deleting root node in file SXT/Patches/ModCompatibility/CLS/CLS_StationsBases node: @PART[MEMLander]:NEEDS[ConnectedLivingSpace] as it can't satisfy its NEEDS
[LOG 2019-08-03 16:14:33.746] Applying update IndicatorLights/Parts/crewable/memLander/@PART[MEMLander]:NEEDS[SquadExpansion] to SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander.cfg/PART
[LOG 2019-08-03 16:14:46.814] Applying update SXT/Patches/ModCompatibility/SXT_TweakScale/@PART[MEMLander]:NEEDS[TweakScale] to SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander.cfg/PART
[LOG 2019-08-03 16:15:31.132] Applying update TweakScale/patches/SquadExpansion/MakingHistory/Pods/@PART[MEMLander] to SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander.cfg/PART
[LOG 2019-08-03 16:15:53.345] Applying update RealPlume-Stock/SXT Continued/MEMLander/@PART[MEMLander]:FOR[RealPlume]:NEEDS[SmokeScreen] to SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander.cfg/PART
[LOG 16:22:58.261] PartLoader: Compiling Part 'SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander/MEMLander'
[LOG 16:22:58.416] PartLoader: Part 'SquadExpansion/MakingHistory/Parts/Pods/Size1_5_Lander/MEMLander' has no database record. Creating.
[LOG 16:22:58.434] DragCubeSystem: Creating drag cubes for part 'MEMLander'
[LOG 16:23:28.187] PartLoader: Compiling Part 'SXT/Parts/Rocketry/Command/MEM/part/MEMLanderSXT'
[LOG 16:23:28.321] PartLoader: Part 'SXT/Parts/Rocketry/Command/MEM/part/MEMLanderSXT' has no database record. Creating.
[LOG 16:23:28.332] DragCubeSystem: Creating drag cubes for part 'MEMLanderSXT'
[LOG 16:24:34.535] [Part:MEMLander (id=C4293743836)#Module:29] Dynamically create pod inventory at seat: 0
[LOG 16:24:34.536] [Part:MEMLander (id=C4293743836)#Module:30] Dynamically create pod inventory at seat: 1
[LOG 16:24:34.675] [Part:MEMLanderSXT (id=C4293623826)#Module:13] Dynamically create pod inventory at seat: 0
[LOG 16:24:34.676] [Part:MEMLanderSXT (id=C4293623826)#Module:14] Dynamically create pod inventory at seat: 1
[WRN 16:26:30.740] Internal space config for MEMLander is at URL SquadExpansion/MakingHistory/Spaces/MEM/MEM_IVA/MEM_IVA, filename G:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\SquadExpansion\MakingHistory\Spaces\MEM\MEM_IVA.cfg
[WRN 16:26:30.787] Internal space config for MEMLanderSXT is at URL SXT/Spaces/MEMInternals/internal/MEMInternals, filename G:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\SXT\Spaces\MEMInternals\internal.cfg
[LOG 16:26:32.705] [TweakScale] WARNING: **FATAL** Found a showstopper problem on MEMLander (Munar Excursion Module (M.E.M.)).
[LOG 16:26:32.705] [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 ).

Initially I was confused because I didn't found how SXT patches would double patch the Stock's MEMLander from Making History. But then I realized than one month ago the Maintainers fixed a problem on the SXT's MEMLander to rename it to MEMLanderSXT and things made sense. From your log I learnt that you are using SXT Continued 0.3.23.7, while the SXT Release is the 0.3.28.2 .

I suggest you to update SXT. I think this will fix all the other errors, as they are all related to SXT and the latests release has fixes for TweakScale. :)

15 hours ago, AmpCat said:

Okay, I uninstalled the TweakscaleMakingHistory mod, and no longer getting the 51 Houston errors. It still found 9 Show Stoppers, I think? Some error box that vanished before I had a chance to copy the message. I'll let you know how it behaves.

Please publish the new KSP.log , so I can hunt them down. :)

Edited by Lisias
I tole the Maintainer about the Pull Request this time! :)

Share this post


Link to post
Share on other sites

Yep. Getting that ''Houston, we have a problem" error too! Playing RP-1/RO. Let me know if there's anything I can supply that would help. 

Share this post


Link to post
Share on other sites
44 minutes ago, Calvin_Maclure said:

Yep. Getting that ''Houston, we have a problem" error too! Playing RP-1/RO. Let me know if there's anything I can supply that would help. 

Full KSP.log and ModuleManager.ConfigCache when available.

Share this post


Link to post
Share on other sites

so I removed the conteras mod and deleted GameData/TweakScale/patches/NFT_TweakScale.cfg and it appeared to work without a hitch... then today I get a tweakscale warning saying found 74 parts that failed sanity checks

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, sierralpha said:

so I removed the conteras mod and deleted GameData/TweakScale/patches/NFT_TweakScale.cfg and it appeared to work without a hitch... then today I get a tweakscale warning saying found 74 parts that failed sanity checks

Failing a Sanity Check means a known issue that was mitigated to avoid problems. It's a nuisance, because that parts can't be scaled for now. But they were never scaled before because they are being quarantined for a long time, and before that your game would be crashing when using them.

But send me this new KSP.log anyway, so I can try to priorize the tasks I need to do to get rid of those quarantines (it usually involves writing code to support new things).

 

16 hours ago, AmpCat said:

Okay, I uninstalled the TweakscaleMakingHistory mod, and no longer getting the 51 Houston errors. It still found 9 Show Stoppers, I think? Some error box that vanished before I had a chance to copy the message. I'll let you know how it behaves.

If the window vanished after 30 seconds, it was not a Show Stopper. It was a warning or am advising, otherwise it would be bugging your screen, getting on the way and preventing you to even start a game without you actively closing it.

The countdown stops by clicking on the window. Then the window will stay there until you close it or until you start a new game, switching scenarios.

By the figure you gave, 9, it should be the Stock parts I do not support yet because they use a thing called MODULEVARIANTPART that has mass, and TweakScale doesn't know yet how to scale these parts. These will be tacked down on TweakScale 2.4.4.x series. (There's one more 2.4.3.x release planned with some more weird but happily rare situations handled, and then I will work on the 2.4.4.x series).

 

— — — addendum — — — 

1 hour ago, Calvin_Maclure said:

Got it.

[LOG 22:28:18.501] [TweakScale] INFO: TweakScale::WriteDryCost: Concluded : 0 checks failed ; 0 parts with issues overruled ; 7 Show Stoppers found; 50 Sanity Check failed;

Let's see that 7 Show Stoppers first:

[LOG 22:28:18.481] [TweakScale] WARNING: **FATAL** Found a showstopper problem on batteryBankMini (Z-200 Rechargeable Battery Bank).
[LOG 22:28:18.481] [TweakScale] ERROR: **FATAL** Part batteryBankMini (Z-200 Rechargeable Battery Bank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.492] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTInlineAirIntake (XM-600 1.25m Air Intake).
[LOG 22:28:18.492] [TweakScale] ERROR: **FATAL** Part SXTInlineAirIntake (XM-600 1.25m Air Intake) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.492] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTWingSmall (non RO (RP-0 yes) - Mk0B Small Modular Wing).
[LOG 22:28:18.492] [TweakScale] ERROR: **FATAL** Part SXTWingSmall (non RO (RP-0 yes) - Mk0B Small Modular Wing) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.492] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTWingLarge (non RP-0 - FAT-460 Super-Lift Aeroplane Main Wing).
[LOG 22:28:18.492] [TweakScale] ERROR: **FATAL** Part SXTWingLarge (non RP-0 - FAT-460 Super-Lift Aeroplane Main Wing) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.494] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTOsaulNoseCockpitAn225 (An-124 Cockpit).
[LOG 22:28:18.494] [TweakScale] ERROR: **FATAL** Part SXTOsaulNoseCockpitAn225 (An-124 Cockpit) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.494] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTOsualRadCockpit (An-124 Cockpit Radial).
[LOG 22:28:18.494] [TweakScale] ERROR: **FATAL** Part SXTOsualRadCockpit (An-124 Cockpit Radial) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).
[LOG 22:28:18.499] [TweakScale] WARNING: **FATAL** Found a showstopper problem on SXTtruckbox (non RP-0 - Truck Box).
[LOG 22:28:18.499] [TweakScale] ERROR: **FATAL** Part SXTtruckbox (non RP-0 - Truck Box) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).

The "good news" is that these are already diagnosed. The batteryBankMini is borking due a patch on ROs, see this post about how to fix. There's a lot of potential problems on the RO's patch, and unfortunately I lack the time to proper support TweakScale and also propose fixes for RO's patches, so I kindly ask you to reach RO's maintainers about the issue, pinpointing this post as a source of information.

The remaining ones are SXT, and they were also diagnosed and I think it's all fixed too. Download the latest SXT (currently 0.3.28.2), and if anything are still broken, kick me here and I will check it for you.

That 50 Sanity Checks are more than an annoyance, however. I'm sorry for that. Some parts are in need of proper TweakScale support, what will happen in the next 2.4.4.x releases. But most of them, however, are happening due having a deadly mix of Fuel Switches on the same part. It's not exactly a defect on the Fuel Switches, but a fail on living together - what's not exactly a fail after all, as the part should have only one Fuel Switch applied to it! So, really, it's a problem of patches being applied without regards of already existing patches.

I talked about it here, for reference.

Unfortunately, my best and only advise is to choose a Fuel Switch and stick with it, and uninstall the others. Firespitter appears to be the One those everybody knows how to deactivate or coexist with, so this one you can leave alone. But from all the others, the easy way out for now is to choose only one of them and uninstall the others.

You could have all of them installed if patches didn't try to apply all of them on the same part - this is the problem (patches that add more than one Fuel Switch to a part), but the easiest way out of the mess is to not have more than one installed, so even if a rogue patch apply them, it will not be effective and the problem will not happen.

Kick me here if something else happens.

Edited by Lisias
addendum

Share this post


Link to post
Share on other sites

Okay, I coulda swore I posted my new log. Looks like I forgot to hit submit. But sounds like you figured it out. Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)

Announce.

Minor Release 2.4.3.2 is on the wild. Just some typos fixed and added support for the new Cryo Engines from Nertea's.

  • 2019-0804: 2.4.3.2 (Lisias) for KSP >= 1.4.1
    • This is an Emergencial Release due an Emergencial Release due an Emergencial Release. I love recursion, don’t you? :P
    • Closing or reworking the following issues:
      • #65 Support for new Nertea’s Cryo Engines
      • Fixing some tyops :P on Logging and Dialog Boxes.

Links on the OP.  

Edited by Lisias
Publishing schedule

Share this post


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

The "good news" is that these are already diagnosed. The batteryBankMini is borking due a patch on ROs, see this post about how to fix. There's a lot of potential problems on the RO's patch, and unfortunately I lack the time to proper support TweakScale and also propose fixes for RO's patches, so I kindly ask you to reach RO's maintainers about the issue, pinpointing this post as a source of information.

The remaining ones are SXT, and they were also diagnosed and I think it's all fixed too. Download the latest SXT (currently 0.3.28.2), and if anything are still broken, kick me here and I will check it for you.

That 50 Sanity Checks are more than an annoyance, however. I'm sorry for that. Some parts are in need of proper TweakScale support, what will happen in the next 2.4.4.x releases. But most of them, however, are happening due having a deadly mix of Fuel Switches on the same part. It's not exactly a defect on the Fuel Switches, but a fail on living together - what's not exactly a fail after all, as the part should have only one Fuel Switch applied to it! So, really, it's a problem of patches being applied without regards of already existing patches.

I talked about it here, for reference.

Unfortunately, my best and only advise is to choose a Fuel Switch and stick with it, and uninstall the others. Firespitter appears to be the One those everybody knows how to deactivate or coexist with, so this one you can leave alone. But from all the others, the easy way out for now is to choose only one of them and uninstall the others.

You could have all of them installed if patches didn't try to apply all of them on the same part - this is the problem (patches that add more than one Fuel Switch to a part), but the easiest way out of the mess is to not have more than one installed, so even if a rogue patch apply them, it will not be effective and the problem will not happen.

Kick me here if something else happens.

Thanks for this very complete answer, I really do appreciate it, and your efforts to solve this issue. Modders don't get enough recognition. 

- Got the SXT link, downloaded and installed. Thanks.

- RO -> so... for now, manually applying the ''%'' to all 300-and-change is the way to go? *sigh*! Ok! lol... 

- Regarding Fuel Switching, I'll keep FireSpitter as you suggested... but I have no idea what the other ones are that I should remove... (and I'm assuming I'll also have to get rid of the mods for whom those other Fuel Switch are dependencies?)

Thanks, 

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, Calvin_Maclure said:

- Regarding Fuel Switching, I'll keep FireSpitter as you suggested... but I have no idea what the other ones are that I should remove... (and I'm assuming I'll also have to get rid of the mods for whom those other Fuel Switch are dependencies?)

Thinking is a very healthy habit, I think :P I should do that more times. :D 

There's another option that I totally missed. A OVERRULE patch. It's kinda of brute-forcing our way out of the mess, and this may make Add'Os' Authors less than happy (as we would deactivating things they intended to be active), but it's a way out nevertheless. This will surely void your warranty :sticktongue: .

Update your TweakScale to 2.4.3.2, where I fixed a dumb mistake on the Log, generate another Log and post it with the ModuleManager.ConfigCache. Then tell me what is your favorite Fuel Switch. I will cook a OVERRULE patch that will delete all the others FuelSwitches but the one you want when more than one FuelSwitch is on a part.

It's not perfect as it can be overruled² by a smarter patch, may break if you install another Fuel Switch, but it may work for now. And if that thing really works, I can consider adding it to Extras folder of the next TweakScale version!

Edited by Lisias
Some comments added

Share this post


Link to post
Share on other sites

I confirmed my errors are just 9 parts failing sanity checks. Should I dig up the list, or do you already have it?

Also, why can't we scale the stock science experiment storage unit? For rovers, probes and small landers, it's just massive! I've not found any mods that have smaller ones.

Share this post


Link to post
Share on other sites
3 minutes ago, AmpCat said:

I confirmed my errors are just 9 parts failing sanity checks. Should I dig up the list, or do you already have it?

I already know that. Thanks.

 

4 minutes ago, AmpCat said:

Also, why can't we scale the stock science experiment storage unit? For rovers, probes and small landers, it's just massive! I've not found any mods that have smaller ones.

Because nobody wrote the patches. :) It's an interesting feature for the 2.4.4.x series.

Share this post


Link to post
Share on other sites

Hm. How hard is writing patches? Not that I want to sign up for another hobby, but this might be worth the effort. ;)

Share this post


Link to post
Share on other sites
23 minutes ago, AmpCat said:

Hm. How hard is writing patches? Not that I want to sign up for another hobby, but this might be worth the effort. ;)

fairly easy, once you learn the basic syntax. However, it can get complicated and involved once you go past the simple and straightforward. TweakScale patches are relatively easy, as long as you remember to have ReScale.dll installed. :o

There are several interesting MM patches that clone (+PART) stock inventory containers, one by @4x4cheesecake (iirc) for the landercan is rather fun. One bit of note: I believe (from testing) that the max number of slots is limited by the PAW GUI to something like 30 slots.

Share this post


Link to post
Share on other sites

I meant the Tweakscale patches in particular. I've done other several other patches. Would just like to be able to get a smaller experiment storage unit. :p Or somehow add that functionality to any command module would be nice too. I suppose I could dig up the container type from the stock one and look up the patch scripting to put it on any command module.

Share this post


Link to post
Share on other sites
Posted (edited)
42 minutes ago, AmpCat said:

I meant the Tweakscale patches in particular. I've done other several other patches. Would just like to be able to get a smaller experiment storage unit. :p Or somehow add that functionality to any command module would be nice too. I suppose I could dig up the container type from the stock one and look up the patch scripting to put it on any command module.

 

this might work:

Spoiler

@PART[*]:HAS[@CrewCapacity[>0]&@MODULE[!ModuleScienceContainer]&@MODULE[!KerbalEVA]&@MODULE[!KerbalSeat]]:FOR[zzzMe]
{
	MODULE
	{
		name = ModuleScienceContainer
		reviewActionName = Review Experiment Data
		storeActionName = Store Experiment Data
		evaOnlyStorage = True
		storageRange = 3
		collectActionName = Take Experiment Data
		allowRepeatedSubjects = True
		canBeTransferredToInVessel = True
		canTransferInVessel = True
		showStatus = True
	}
}

// zer0Kerbal

or


// ============================================================
// === Science Container
// ===
@PART[*]:HAS[@MODULE[ModuleCommand]]:FINAL
{
	@MODULE[ModuleScienceContainer] //%
	{
		%reviewActionName = Review Experiment Data
		%storeActionName = Store Experiments
		%collectActionName = Take Experiment Data
		%evaOnlyStorage = False
		%storageRange = 3
		%allowRepeatedSubjects = True
		%canBeTransferredToInVessel = True
		%canTransferInVessel = True
		%showStatus = True
	}
}

// zer0Kerbal

 

and this is a simple scale patch for that part: (untested) I had fun writing this patch - added a new 'sanitykeeping' feature - the :HAS[MODULE[!TweakScale]] so no duplicate patches! (*knocking on wood*). Also note - smaller = lighter and costlier. Larger = heavier and uncostlier (ok, not a word).

Spoiler

// Squad
// TweakScale - v 1.0
// created: 06 Aug 19
// updated: 06 Aug 19

@PART[ScienceBox]:HAS[@MODULE[!TweakScale]]:NEEDS[TweakScale]:FINAL
{
	MODULE
	{
		%name = TweakScale
		%type = free
		&defaultScale = 0.625
		&scaleFactors   = 0.078125, 0.15625, 0.3125, 0.625, 1.25, 2.5, 3.75, 5.0, 6.25, 7.5, 10, 15, 20
	}
}
// zer0Kerbal
// CC-BY-NC-SA-4.0 

 

 

Edited by zer0Kerbal

Share this post


Link to post
Share on other sites
On 8/4/2019 at 11:21 PM, Lisias said:

Thinking is a very healthy habit, I think :P I should do that more times. :D 

There's another option that I totally missed. A OVERRULE patch. It's kinda of brute-forcing our way out of the mess, and this may make Add'Os' Authors less than happy (as we would deactivating things they intended to be active), but it's a way out nevertheless. This will surely void your warranty :sticktongue: .

Update your TweakScale to 2.4.3.2, where I fixed a dumb mistake on the Log, generate another Log and post it with the ModuleManager.ConfigCache. Then tell me what is your favorite Fuel Switch. I will cook a OVERRULE patch that will delete all the others FuelSwitches but the one you want when more than one FuelSwitch is on a part.

It's not perfect as it can be overruled² by a smarter patch, may break if you install another Fuel Switch, but it may work for now. And if that thing really works, I can consider adding it to Extras folder of the next TweakScale version!

I was just... thinking ;) if I'm on KSP 1.6.1, wouldn't the TS version 2.4.0.7 work? The subsequent versions seem to be the ones where this Kraken issue began, no?

Share this post


Link to post
Share on other sites
15 minutes ago, Calvin_Maclure said:

I was just... thinking ;) if I'm on KSP 1.6.1, wouldn't the TS version 2.4.0.7 work? The subsequent versions seem to be the ones where this Kraken issue began, no?

Nops. These things are happening since 1.4.1 at least (I got my first serious crashes and savegames corruptions on 1.4.3, last year). You should use the latest TweakScale on any KSP >= 1.4.1, as all of them suffer from the problem TS detects.

You may have some reluctrance to get older Add'On versions fixed for older KSP versions, but that is the main reason I cooked the OVERRULES patches. The worst happens, we handcraft a patch for you to keep your game running on a safe, besides far from ideal, way.

Share this post


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

Nops. These things are happening since 1.4.1 at least (I got my first serious crashes and savegames corruptions on 1.4.3, last year). You should use the latest TweakScale on any KSP >= 1.4.1, as all of them suffer from the problem TS detects.

You may have some reluctrance to get older Add'On versions fixed for older KSP versions, but that is the main reason I cooked the OVERRULES patches. The worst happens, we handcraft a patch for you to keep your game running on a safe, besides far from ideal, way.

Huh, ok. My only concern is your previous (if it still applies) comment regarding the Fuel Switching. Since I play RO/RSS/RP-1, I use Real Fuels (which uses SolverEngines which I believe is a Fuel Switching mod??). FireSpitter I know is used by several mods (though I could not tell you which ones...), so my main and only concern really is, if I can only use one Fuel Switching and not the others, then I have to get rid of several mods (potentially) and I don't know which ones use what... Makes sense?? Don't know what, if anything, can be done about this.

Thanks so much for all your help and efforts. 

Share this post


Link to post
Share on other sites
5 minutes ago, Calvin_Maclure said:

if I can only use one Fuel Switching and not the others, then I have to get rid of several mods (potentially) and I don't know which ones use what... Makes sense?? Don't know what, if anything, can be done about this.

Or you can apply a OVERRULE patch to get rid of the "extra" Fuel Switch on the parts that have more than one. :) 

You can have more than one Fuel Switch installed on the GameData, things goes through the tubes when people install more than one Fuel Switch on a part. The easiest way of avoid the mess is to do no install more than one Fuel Switch on your KSP - so patches just can't shove more than one on a part even if they try (and some will).

But easiest is not always best. For your case, the OVERRULE patch is the solution.

Share this post


Link to post
Share on other sites

I received a warning that 9 parts failed a sanity check.  I've reviewed the log and can see what they are (mostly engine plates).  Can I ignore this warning and still use the engine plates (and be careful to not tweak them), or will issues arise?  Thanks!

Share this post


Link to post
Share on other sites
3 minutes ago, ble210 said:

I received a warning that 9 parts failed a sanity check.  I've reviewed the log and can see what they are (mostly engine plates).  Can I ignore this warning and still use the engine plates (and be careful to not tweak them), or will issues arise?  Thanks!

You can use them without worries. TweakScale is telling you that these parts cannot be scaled by lack of proper support, but they are alright to be used.

Warnings and advises are just informative. These are yellow or white, and means that things are not perfect (yet), but are not bad either.

The nasty things are informed in red, and these gets in the way preventing you to proceed until you dismiss them.

About that 9 parts, version 2.4.4 will have them supported. 

Share this post


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.