Closed ElMickuy closed 9 months ago
your terminal window is wai too small, the erorr message is truncated and I can't know exactly what's wrong. Make the window very large so that we can read the full message.
But before you do that: the script out of the box is not configured to work with Buran, did you create custom configs or are you using the default configs for my fork of SSS? Because if it's the latter, then the script will never work without those custom configs, the README does say it
OK, This is the message that appears in the kOS terminal. I used your fork and don't change anything
Do you use Atmospheric Autopilot? Other people had your same error and we traced it down to an incompatibility with that mod
Emm no Witch mods are incompatible?
So far I'm only aware of Atmospheric Autopilot, but there can always be more.
I need more information, so please try this:
execute the following command: print ship:partsdubbed("ShuttleTailControl")[0]:modules. and post a second screenshot with the output.
make sure the terminal is quite large as the command output can be loengthy
1st scrensshot: 2nd screenshot:
The second screenshot shows the problem: The part is supposed ot have two ModuleControlSurface but yours only has one for some reason.
Please verify that ijndeed you installed the latest SpaceShuttleSuystem from my fork. Please also verify that you have re-assembled the Orbiter ship from scratch after updating as stated in the SpaceShuttleSystem README.
After you have done both, please re-do this test. If it still doesn't work, we'll have to try a clean KSP install
The "run deorbit" script works normally, the problem occurs when I place the "run entry" script in kOS, what is in the image appears. Why does this happen? What it says about BURAN/ENERGIA was the name I gave to the aircraft