Thermal Control System extending before it should

[maddog59]

After I loaded KSPIE I found that the Thermal Control Systems are extending as soon as the vehicle is launched. If they're inside a protective shell, the vehicle gets up to orbit but when I try to deploy the shell, it's a crap shoot as to whether or not the TCS is broken. For instance, I have an ISRU rover with 4 TCS ... each time I launch it, at least one of the TCS' is broken, and usually two or three. Is there any way to fix this so that the TCS will extend when I want them to and not before? 

[jimmymcgoochie]

I think this has come up before; there might be a setting for KSPIE to disable automatic TCS deployment but I can’t remember the solution that was posted before.

[Guest]

I ran into the same issues when doing PEAR. It is possible to code it so the game checks if something is inside a fairing/cargo bay and not deploy if so, as well as setting triggers for arming systems when you get to a certain altitude. 

Therefore, I’d put forward the issue in the mod thread and maybe open an issue on  GitHub as that’s a dev issue from what you’ve described in my opinion.

PS I have no experience of the mod in question so don’t know how it’s supposed to work etc, just going on the description in the OP.

[maddog59]

5 hours ago, FruitGoose said:

Therefore, I’d put forward the issue in the mod thread and maybe open an issue on  GitHub as that’s a dev issue from what you’ve described in my opinion.

I agree, seems like a bug to me; I was kinda hoping there'd be a place in the ship file that I could hack to keep it closed. I'm not familiar with GitHub, but will see if I can figure out how to open an issue.

I've tried posting for help on the Interstellar Extended thread on other topics (remember my missteps in posting about 'No lights in the Command Dome' topic? ) and haven't gotten a response.

[Guest]

36 minutes ago, maddog59 said:

I agree, seems like a bug to me; I was kinda hoping there'd be a place in the ship file that I could hack to keep it closed. I'm not familiar with GitHub, but will see if I can figure out how to open an issue.

I've tried posting for help on the Interstellar Extended thread on other topics (remember my missteps in posting about 'No lights in the Command Dome' topic? ) and haven't gotten a response.

Ah yes I remember! It may be possible to disable the extending part using a MM patch as a temp fix (to make them like the flat ones). Not ideal but would stop them breaking at least.

[maddog59]

10 minutes ago, FruitGoose said:

Ah yes I remember! It may be possible to disable the extending part using a MM patch as a temp fix (to make them like the flat ones). Not ideal but would stop them breaking at least.

"MM Patch" ??? Whazat??

[Guest]

4 minutes ago, maddog59 said:

"MM Patch" ??? Whazat??

ModuleManager 

[maddog59]

1 hour ago, FruitGoose said:

ModuleManager 

Oy!!!! I should've known. Thanks!!! 

[maddog59]

19 hours ago, FruitGoose said:

It may be possible to disable the extending part using a MM patch as a temp fix (to make them like the flat ones). Not ideal but would stop them breaking at least.

I don't know how one would apply a MM patch, but I suspect it's way beyond me ... I'm a tool-user kinda guy ... just want to use the tools other brilliant people make. 

I tried turning off all of the 'auto-deploy' switches I could find in MJ2 but it had no effect: when the fairing deployed 3 of the 4 TCS' on the ship were destroyed.  And I can't seem to find anything to control any KSPIE settings.  This is really putting a crimp in my ability to run missions, if I can't get an ISRU unit somewhere with intact TCS components.

<next day>

I opened an issue on Github  and as usual I now have egg on my face. I received a response to look for an 'Auto deploy' switch for the TCS. In my case the switch is labeled "Automated" and it was hidden in the action window by being inside the "Radiator" drop down section, and I somehow missed it. I tried it and it works as expected. I suggested to them that, since it's similar to a solar panel, that it the default value be 'off' rather than 'on.'

My thanks to both you and @jimmymcgoochiefor taking the time to work with me.

Edited May 8, 2021 by maddog59
added results of opening an issue with Github