# New ReleaseInterplanetary Modular Spacecraft RC9

#### Tacolev

##### New member
Yes sorry. Here's a before and after with a different vessel. The example I used was present-to-hand but I didn't have any scenarios with it where it still had its radiators:

#### PeterRoss

##### Warranty man
Could you post a scenario with rads wiped out and the one before it (autosave?)?

#### jedidia

##### shoemaker without legs
ok, major wtf. Never seen anything like it. Could you try to describe exactly when it happens? That is, the actions you do that lead to it happening, every mouseclick, keyboard entry, whatever. And I'll need the exact scenario you do the tests with.

#### Tacolev

##### New member
Ok I will honor Peter's request for the before and after .scn because in doing so I discovered something I wasn't by just looking at the autosaves that might have localized how the issue came about:

Before, autosave:
Code:
BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 54147.0281861477
END_ENVIRONMENT

BEGIN_FOCUS
Ship HDPE
END_FOCUS

BEGIN_CAMERA
TARGET HDPE
MODE Extern
POS 1.83 33.95 -24.53
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
HDPE:IMS\finished vessels\HDPE-01C
STATUS Orbiting Earth
RPOS 6902314.24 0.00 1213126.78
RVEL -1305.488 -0.000 7427.819
AROT 0.00 -0.00 0.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000 4:1.000000
NAVFREQ 0 0
COMMAND 0 0
MODULES 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
PROP LOX_LH2 11360
PROP LH2 312156
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ANIM 56 SBB41B\BCCH_Container_Holder 0 0
CONSUMABLES 0.00010.00010.0001
TEMPERATURES -1:298.00:297.35 1:298.00:297.35 14:999.91:301.04 15:999.91:301.04 16:999.91:288.23 17:999.91:288.23 30:1300.46:297.35 31:1300.46:286.21 34:1300.47:297.35 35:1300.47:264.42 43:999.91:301.04 44:999.91:288.23 45:1300.46:297.35 46:1300.46:264.42
RADIATOR 18 287.101 0 1 0 30 31 34 35 14 15 16 17 43 44 45 46
RADIATOR 19 243.829 0 1 0 30 31 34 35 14 15 16 17 43 44 45 46
RADIATOR 20 241.456 0 1 0 14 15 17 16 30 31 34 35
RADIATOR 21 242.928 0 1 0 14 15 16 17 30 31 34 35 43 44 45 46
RADIATOR 22 242.703 0 1 0 30 31 34 35 14 15 16 17 43 44 45 46
RADIATOR 23 244.2 0 1 0 30 31 34 35 14 15 16 17 43 44 45 46
RADIATOR 24 242.625 0 1 0 14 15 16 17 30 31 34 35 43 44 45 46
RADIATOR 25 242.724 0 1 0 30 31 34 35 15 16 17 43 44 45 46
RADIATOR 26 242.724 0 1 0 30 31 34 35 14 15 16 17 43 44 45 46
RADIATOR 27 242.724 0 1 0 30 31 34 35 14 15 16 17 45 46 43 44
RADIATOR 37 288.976 0 1 0 -1
RADIATOR 38 288.558 0 -1 0 1
RADIATOR 39 284.93 -1 0 0 -1 1
RADIATOR 40 284.929 1 0 0 -1 1
HEATING -1
THGROUPLEVELS 0 0 0 0
CREW 0 0
ENERGY 0.000000
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

And... here check this out. After clicking "save current" this is what is produced:
Code:
BEGIN_DESC

END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 54147.0281861477
END_ENVIRONMENT

BEGIN_FOCUS
Ship HDPE
END_FOCUS

BEGIN_CAMERA
TARGET HDPE
MODE Extern
POS 1.83 33.95 -24.53
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
HDPE:IMS\finished vessels\HDPE-01C
STATUS Orbiting Earth
RPOS 6902314.24 0.00 1213126.78
RVEL -1305.488 -0.000 7427.819
AROT 0.00 -0.00 0.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000 4:1.000000
NAVFREQ 0 0
COMMAND 0 0
MODULES 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
PROP LOX_LH2 11360
PROP LH2 312156
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ENGINE 0 -1
ANIM 56 SBB41B\BCCH_Container_Holder 0 0
CONSUMABLES 0.00010.00010.0001

Neatly truncating right before the radiators.

Of note is that this vessel is loading from a "finalized" configuration. Since I had been re-using so many of the same names I didn't realize that this only occurs when a vessel loads from a "finalized" config:

So to get this error:
1. Instantiate vehicle from finalized config.
2. Autosave
3. "Save current..." autosave.

Give me a moment and I will add some stereotyped examples using a radiator taped to a control unit.

---------- Post added at 06:43 AM ---------- Previous post was at 06:25 AM ----------

Hrmm... Okay I officially have no idea what's going on here anymore. I wiped all the previously-generated config files and scenarios and went to document my constructed test case and now it seems that instantiating ANY vessel from a finalized config file does this even without the save thing. It is nearly 3AM where I am at so I will save any more rigorous debugging and documentation stuff til tomorrow.

#### jedidia

##### shoemaker without legs
Should be enough information to figure it out, I'm on it. Thanks!

EDIT: Reproduced and nailed. The problem is glaringly obvious, the radiators simply aren't written to the config file. Looks like this has never been really tested beyond just loading a finalised vessel, looking at it from outside and thinking "yap, works". I know I never tested this feature beyond that...

On another funny note, I tried something out before releasing RC1 to see if it might reduce the ctd-probability. I was pretty astonished to see that it did, only to find out now that the reason it did was because it didn't work, and didn't delete all the docking ports it should. Now that it actually does what I wanted it to do, ctds are more frequent again. Oh well...

Last edited:

#### Tacolev

##### New member
Aha. Well it works pretty drat well otherwise, all things considered, if that's all the checking you did on it. :lol:

---------- Post added at 04:30 PM ---------- Previous post was at 04:08 PM ----------

OK, I'll prod you one more time on something else. Probably in a manner that doesn't have the potential to cause existential terror:

Is there a clean way, either within a module config file or in the scenario file, to offset the z axis of a control module/ims vessel besides screwing with its size parameters in the config file? Specifically I'm thinking of the "Control AI" cargo box which has a tendency to make things tumble under thrust for this reason.

A flat out "no" is a perfectly acceptable answer if it would throw priorities off.

#### jedidia

##### shoemaker without legs
Is there a clean way, either within a module config file or in the scenario file, to offset the z axis of a control module/ims vessel besides screwing with its size parameters in the config file?

Not sure what you mean by "offset the Z axis". I assume you talk about center of gravity. You have to pay attention to build symmetricaly, that's the easiest way to avoid the problem. I once had a CoG-shift MFC in the plan, but after reworking the whole CoG calculation it became so stable that there are no issues as long as you watch what you're building. I might still pick up the idea again if it's called for, but it won't be too soon.

Currently, the CoG is calculated from scratch depending on the modules, module positions and modules load (propellant and consumables), so there is no way to alter the CoG without editing the mass of the modules in their configs.

Last edited:

#### Tacolev

##### New member
Maybe I'm misinterpreting what's happening here but it seemed to me like control module's z-axis is taking precedence with the COG calculations.

Consider this vessel, perfectly balanced about the Z axis, with the control module attached to the nadir construction port and an equivalent mass battery on top:

When I fire both engines it "tumbles" as though the COG were through the control module, even though the mass on the whole is balanced.

Last edited:

#### jedidia

##### shoemaker without legs
When I fire both engines it "tumbles" as though the COG were through the control module, even though the mass on the whole is balanced.

Should not happen! please post the scenario.

#### Tacolev

##### New member
Here we are:

Code:
BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 54147.0298814113
END_ENVIRONMENT

BEGIN_FOCUS
Ship HDPE-00C
END_FOCUS

BEGIN_CAMERA
TARGET HDPE-00C
MODE Extern
POS 548373.57 55.61 -26.57
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
HDPE-00C:IMS\SBB41B\BG203_CONTROL_AI_SContainer
STATUS Orbiting Earth
RPOS 7007559.16 0.03 87382.36
RVEL -94.035 0.002 7541.104
AROT 0.00 -0.00 90.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000
NAVFREQ 0 0
COMMAND 0 1
MODULE SBB41B\BT101_Truss 0,2.3571,0 0,0,1 -1,0,0 0
MODULE SBB41B\BG201_Battery_SContainer 0,4.7143,0 0,0,1 0,-1,0 0
MODULE SBB41B\BRCS2_ReactionControlSystem_Engine 0,2.3571,-5.623 0,0,-1 0,1,0 0
MODULE SBB41B\BTank202_LOX_LH2_SFuelTank 0,2.3571,6.1839 0,0,-1 1,0,0 0
MODULE SBB41B\BR010_Radiator 0,2.3571,7.2917 0,0,1 -1,0,0 0
MODULE SBB41B\BHVE_Sidemount_Rocket_Engine -2.0767,2.3571,-0.788 0,0,1 1,0,0 0
MODULE SBB41B\BHVE_Sidemount_Rocket_Engine 2.0767,2.3571,-0.788 0,0,1 -1,0,0 0
DELETEPOINT 1
ATTPOINT IM 0,5.9827,0 0,1,0 0,0,1
DELETEPORT 0
CONSTRUCTIONPORT 0,1.2684,0 0,-1,0 0,0,1
CONSTRUCTIONPORT 0,3.4459,0 0,-1,0 0,0,1
CONSTRUCTIONPORT 0,5.9827,0 0,1,0 0,0,1
CONSTRUCTIONPORT 0,2.3571,-5.076 0,0,1 0,1,0
CONSTRUCTIONPORT 0,2.3571,5.076 0,0,-1 0,1,0
CONSTRUCTIONPORT 0,2.3571,7.2917 0,0,-1 0,1,0
CONSTRUCTIONPORT -1.0887,2.3571,0 1,0,0 0,0,1
CONSTRUCTIONPORT 1.0887,2.3571,0 -1,0,0 0,0,1
EMPTYMASS 7500.000000
MASSCENTER 0.000000 0.000000 0.000000
PMI 17.060000 17.410000 6.860000
PROP LOX_LH2 5680 5680
ENGINE 5 0 -1
ENGINE 6 0 -1
RCSBLOCK 4 4000 4099 0,2.3571,-5.623 5 0,1,0 -1,0,0 0,-1,0 1,0,0 0,0,1 0
CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
TEMPERATURES -1:298.00:273.04 1:298.00:298.01 5:700.00:699.72 6:700.00:699.72
RADIATOR 4 200 0 0 1
HEATING -1
THGROUPLEVELS 0 0 0 0
CREW 0 0
ENERGY 396000000.000000
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

Not enough fuel for the problem to really show with the main engines but try the linear RCS forward.

#### jedidia

##### shoemaker without legs
I have to crunch timeaccel to 100x while firing the RCS to expierience any real tumbling here. This slight error is most probably due to a double inprecision somewhere in the fractions of a milimeter when calculating the position of the thruster relative to the CoG (as all positions are stored relative to the origin, that is, the position of the command module, and then recalculated). Is it really that much of a problem?

Anyways, not having the CM aligned with x zero/y zero does lead to more inprecisions than having it aligned, as then the center of mass will be a pure result of addition and subtraction, which, as mentioned, always leads to slight errors. If the CM is at X0/Y0 the symmetry recognition takes care of that, but if the CM is not in the center there is no symmetry to recognise without prior knowledge of where the CoG is supposed to be (which, of course, would make the whole calculation superfluous...)

Last edited:

#### Tacolev

##### New member
I'm very sorry for sending you on another wild goose chase but looking at the scenario files the problem seems to be related to something entirely different: the uneven drawdown of propellant.

As it turns out, I was only using the offset control module in setups with multiple fuel resources that would become unbalanced if drawn down one at a time instead of all at once. If I stack the tanks so that they are in line with the cog this problem doesn't present.

This is very noticable with electric engines at mild time accelerations but with the chemical engines it was caused by the RCS drawing from the same reservoir as the main engines and partially emptying one tank thus unbalancing the whole thing.

Is this expected behavior for the propellant draw-down?

#### jedidia

##### shoemaker without legs
Is this expected behavior for the propellant draw-down?

It would be if the tanks had different propellant stored... Draw from propellant tanks of the same type should be identical, but it's possible there's a bug in the calculation...

#### Tacolev

##### New member
These were the same type, BTA101 LH2 tanks.

I made a scenario to demonstrate this, putting two on either side of a truss, stuck a single engine on the back, zapped it out to sun-earth L2. I loaded it up, fired the engines, and it drew from only one of the tanks. I was going to post the scenario file here. But to make sure to myself of what was going on I loaded the same scenario file, tried it again, and it didn't happen.

I am metrically confused about what is going on. Sorry to open another widening gyre.

---------- Post added at 06:37 PM ---------- Previous post was at 06:33 PM ----------

I'll post it anyway in case you are curious.

Code:
BEGIN_DESC
Orbiter saved state at T = 210
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 54147.0284890354
END_ENVIRONMENT

BEGIN_FOCUS
Ship A
END_FOCUS

BEGIN_CAMERA
TARGET A
MODE Extern
POS 4.53 -34.20 -52.21
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
A:IMS\SBB41B\BM002_CONTROL_AI
STATUS Orbiting Sun
RPOS -302382021453.28 9603341145.29 -683413635279.40
RVEL 11009.937 -228.255 -4363.798
AROT 0.00 0.00 -90.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000
NAVFREQ 0 0
COMMAND 1 0
MODULE SBB41B\BT101_Truss 0,0,7.4516 0,0,1 0,1,0 0
MODULE SBB41B\BTank101_LH2_LFuelTank 3.3293,0,7.4516 0,0,1 0,-1,0 0
MODULE SBB41B\BTank101_LH2_LFuelTank -3.3293,0,7.4516 0,0,1 0,1,0 0
MODULE VASIMR_10MW 0,0,-6.8756 0,0,1 1,0,0 0
DELETEPOINT 2
DELETEPOINT 1
ATTPOINT IM 0,1.0887,7.4516 0,1,0 0,0,1
ATTPOINT IM 0,-1.0887,7.4516 0,-1,0 0,0,1
ATTPOINT IM 0,0,12.5277 0,0,1 1,0,0
ATTPOINT IM 5.5698,0,7.4516 1,0,0 0,0,1
ATTPOINT IM 3.3293,-2.2405,7.4516 0,-1,0 0,0,1
ATTPOINT IM 3.3293,2.2405,7.4516 0,1,0 0,0,1
ATTPOINT IM -5.5698,0,7.4516 -1,0,0 0,0,1
ATTPOINT IM -3.3293,2.2405,7.4516 0,1,0 0,0,1
ATTPOINT IM -3.3293,-2.2405,7.4516 0,-1,0 0,0,1
DELETEPORT 1
DELETEPORT 0
CONSTRUCTIONPORT 0,1.0887,7.4516 0,1,0 0,0,1
CONSTRUCTIONPORT 0,-1.0887,7.4516 0,-1,0 0,0,1
CONSTRUCTIONPORT 0,0,12.5277 0,0,1 1,0,0
CONSTRUCTIONPORT 0,0,2.3756 0,0,-1 1,0,0
CONSTRUCTIONPORT 1.0887,0,7.4516 -1,0,0 0,0,1
CONSTRUCTIONPORT 5.5698,0,7.4516 1,0,0 0,0,1
CONSTRUCTIONPORT 3.3293,-2.2405,7.4516 0,-1,0 0,0,1
CONSTRUCTIONPORT 3.3293,2.2405,7.4516 0,1,0 0,0,1
CONSTRUCTIONPORT -1.0887,0,7.4516 1,0,0 0,0,1
CONSTRUCTIONPORT -5.5698,0,7.4516 -1,0,0 0,0,1
CONSTRUCTIONPORT -3.3293,2.2405,7.4516 0,1,0 0,0,1
CONSTRUCTIONPORT -3.3293,-2.2405,7.4516 0,-1,0 0,0,1
CONSTRUCTIONPORT 0,0,-2.3756 0,0,1 1,0,0
EMPTYMASS 18500.000000
MASSCENTER 0.000000 0.000000 0.000000
PMI 29.060000 29.060000 8.610000
PROP LH2 18984 18984
ENGINE 3 0 0
CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
TEMPERATURES -1:298.01:279.78 3:999.59:333.39
HEATING -1
THGROUPLEVELS 0 0 0 0
CREW 0 0
ENERGY 197963577.013983
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

#### jedidia

##### shoemaker without legs
No repro, as expected from your report.

Question: When you did it the first time, and the rotation occured, did you do the test in the same session as you did the building (I.E. did you not quit orbiter between building the vessel and doing the test)?

I don't see what it could matter currently, but it might be a possible explanation why it happened the first time ut not at subsequent attempts. If you can reproduce the bahavior again by building the vessel and doing the test immediately, and the problem vanishes after SQL, at least I'll have a point to start looking.

#### Tacolev

##### New member
Ai, I had thoughts similarly so I tried running it in the same session as building it. I was again unable to reproduce it. If the vehicle was not clearly integrated my best guess would be that I was simply being hasty and attached the last tank without integrating it, if not in this case then maybe in some of the past ones.

If I can get it to happen again I'll make sure to hang onto the .scn.

#### jedidia

##### shoemaker without legs
If the vehicle was not clearly integrated my best guess would be that I was simply being hasty and attached the last tank without integrating it

That would certainly explain it, yes.

#### Tacolev

##### New member
As this thread demonstrates my tendencies for catastrophism, jumping to conclusions and constitutional lack of rigeur are why I didn't ask to join the dev team in the first place.

So unless I find something glaring AND consistently reproducible I'll try to quit bothering you guys until the release.

#### jedidia

##### shoemaker without legs
As this thread demonstrates my tendencies for catastrophism, jumping to conclusions and constitutional lack of rigeur

...as well as melodrama and dramatic language! :lol:

#### Furet

##### Member
Just to report possible issues about the engines I tried so far (chemical Sidemount Rockets and NERVA). It's not very annoying (perhaps it's simply not implemented yet), but engines can be restarted after they reached their maximal operational heat. In the scenario below, they're about 2300K. In the "Thrust" Panel, engines are still indicated "R". By the way, clicking on the "CHR" block activates the engines heating and makes both "R" and "H" glowing simultaneously. Engines can also be operated when they are under the operational temperature.

Anyway, these are minor issues (if so, I'm not sure I did or understood everything well), and there is a lot of fun in view...:woohoo: :thumbup:

Here is a scenario with overheated engines:
Code:
BEGIN_DESC
Orbiter saved state at T = 28
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 51982.0514181220
END_ENVIRONMENT

BEGIN_FOCUS
Ship Essai
END_FOCUS

BEGIN_CAMERA
TARGET Essai
MODE Cockpit
FOV 60.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
Essai:IMS\SBB41B\BG203_CONTROL_AI_SContainer
STATUS Orbiting Earth
RPOS -3439647.12 -28.37 6227254.73
RVEL -9440.548 0.004 -3324.046
AROT 0.00 74.53 90.00
VROT 0.20 0.00 0.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:0.110766
NAVFREQ 0 0
COMMAND 1 0
MODULE SBB41B\BT101_Truss 0,-2.3571,0 0,0,1 0,1,0 0
MODULE SBB41B\BTank202_LOX_LH2_SFuelTank 2.1966,-2.3571,0 -1,0,0 0,1,0 0
MODULE SBB41B\BTank202_LOX_LH2_SFuelTank -2.1966,-2.3571,0 1,0,0 0,-1,0 0
MODULE SBB41B\BG201_Battery_SContainer 0,-4.7143,0 0,0,1 0,1,0 0
MODULE SBB41B\BT100_Truss 0,-2.3571,6.1648 1,0,0 0,1,0 0
MODULE SBB41B\BT100_Truss 0,-2.3571,-6.1648 1,0,0 0,-1,0 0
MODULE SBB41B\BR010_Radiator 0,-2.3571,7.2535 0,0,1 0,1,0 0
MODULE SolarArrayCirc_3m 0,-0.7684,6.1648 0,1,0 1,0,0 0
MODULE SolarArrayCirc_3m 0,-3.9459,6.1648 0,-1,0 1,0,0 0
MODULE SBB41B\BRCS_ReactionControlSystem_Engine 5.476,-2.3571,6.1648 1,0,0 0,0,-1 0
MODULE SBB41B\BRCS_ReactionControlSystem_Engine -5.476,-2.3571,6.1648 -1,0,0 0,0,-1 0
MODULE SBB41B\BHVE_Sidemount_Rocket_Engine 0,-4.4339,-6.9528 0,0,1 0,1,0 0
MODULE SBB41B\BHVE_Sidemount_Rocket_Engine 0,-0.2804,-6.9528 0,0,1 0,-1,0 0
MODULE SBB41B\BRCS_ReactionControlSystem_Engine 5.476,-2.3571,-6.1648 1,0,0 0,0,1 0
MODULE SBB41B\BRCS_ReactionControlSystem_Engine -5.476,-2.3571,-6.1648 -1,0,0 0,0,1 0
DELETEPOINT 2
ATTPOINT IM 3.3044,-2.3571,0 1,0,0 0,0,1
ATTPOINT IM -3.3044,-2.3571,0 -1,0,0 0,0,1
ATTPOINT IM 0,-5.9827,0 0,-1,0 0,0,1
ATTPOINT IM 0,-2.3571,-7.2535 0,0,-1 1,0,0
DELETEPORT 1
EMPTYMASS 9800.000000
MASSCENTER 0.000000 0.000000 0.000000
PMI 23.680000 28.000000 15.540000
PROP LOX_LH2 11360 1258.3
ENGINE 11 0 0
ENGINE 12 0 0
RCSBLOCK 4 1000 4099 5.476,-2.3571,6.1648 5 0,0,-1 0,-1,0 0,0,1 0,1,0 -1,0,0 1
RCSBLOCK 4 1000 4099 -5.476,-2.3571,6.1648 5 0,0,-1 0,1,0 0,0,1 0,-1,0 1,0,0 1
RCSBLOCK 4 1000 4099 5.476,-2.3571,-6.1648 5 0,0,1 0,1,0 0,0,-1 0,-1,0 -1,0,0 1
RCSBLOCK 4 1000 4099 -5.476,-2.3571,-6.1648 5 0,0,1 0,-1,0 0,0,-1 0,1,0 1,0,0 1
ANIM 7 SolarArrayCirc_3m 1 1
ANIM 8 SolarArrayCirc_3m 1 1
CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
TEMPERATURES -1:298.44:265.16 3:298.02:264.99 7:250.36:330.00 8:250.84:330.00 11:2298.60:241.19 12:2299.08:241.20
RADIATOR 6 221.821 0 0 1 -1 3 11 12
HEATING -1 3
THGROUPLEVELS 0 0 0 0
CREW 0 0
ENERGY 395354801.024007
SOLARARRAY 7 1 0 0.999977 0.999977 0.023984 0.023984
SOLARARRAY 8 1 0 0.000023 0.000023 0.023984 0.023984
FAILURES 11:0 11:2 12:0 12:2
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 0 0 0 -1 -1 -1 -1
MFC 1 0 7 0 0 0 -1
MFC 1 0 1 0 0 -1 -1
MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

BEGIN_ExtMFD
END
:thankyou: