New Release Interplanetary Modular Spacecraft RC9

cosmonaut2040 · Sep 8, 2012

Grover said:
isnt that what the ASTG module does? as far as i can tell, it makes its power from SOMETHING onboard (i can only assume that its fuel)

I don't know, I assumed that ASTG is Advanced Stirling Generator - a type of radio-isotopic generator, converting plutonium decay into heat and electricity. I didn't try it yet so I don't know if it consumes fuel.

But talking about consuming fuel - I noticed that my LH2 is slowly dissapearing somewhere even when the engine is not in use. Does IMS simulate boil-off? Otherwise I have no idea what might be consuming it.

Grover · Sep 8, 2012

well its not RCS fuel... perhaps there are some modules other than engines that consume liquid hydrogen? are you sure you havent made a hydrogen fuel cell for IMS? :lol:

ive finished the "planning" stage of my guide, next ill explain how the functions work and get it up here for you peeps

cosmonaut2040 · Sep 9, 2012

I have another problem, probably a bug:
this happens only with a finalised ship taking it's settings from a config file (doesn't happen when the settings are loaded from the scenario file):
activating the antenna module leads always to a CTD in the moment when the antenna finishes deployment. If the antenna was deployed before finalising, then it loads in deployed state and CTD's when I select the antenna in the engineering panel.

PeterRoss · Sep 9, 2012

cosmonaut2040 said:
- the NERVA engines in IMS produce way too much heat. As far as I understand their operation, NTR's cool themselves very efficiently

We're planning to increase efficiency of NTRs to 99.999 with the RC3. Maybe we should increase NERVA's efficiency as well, thanks for your suggestion.

cosmonaut2040 said:
- it would be nice to have a power cell as a another power generator option: consuming LOx+LH2 and producing power+H20

To be dicided, thanks.

cosmonaut2040 said:
- it seems that batteries are not charged from external supply. I made a vessel powered only by batteries and when docked to another IMS ship, the docked vessel supplied just the exact power required to run the internal systems, but not to charge the batteries.

THis seems to be an oversight. Thanks again

Grover said:
isnt that what the ASTG module does? as far as i can tell, it makes its power from SOMETHING onboard (i can only assume that its fuel)

Cosmonaut2040 is right - Advanced Stirling Generator doesn't consume fuel or anything else.

cosmonaut2040 said:
But talking about consuming fuel - I noticed that my LH2 is slowly dissapearing somewhere even when the engine is not in use. Does IMS simulate boil-off? Otherwise I have no idea what might be consuming it.

The main reason for constant fuel leakage is chemical engine heating being on when it's unneded. The problem is that LH2 isn't being used by any chemical engine. It may be caused by wrong engine type specification in its config. What engines do you use?

cosmonaut2040 said:
I have another problem, probably a bug:
this happens only with a finalised ship taking it's settings from a config file (doesn't happen when the settings are loaded from the scenario file):
activating the antenna module leads always to a CTD in the moment when the antenna finishes deployment. If the antenna was deployed before finalising, then it loads in deployed state and CTD's when I select the antenna in the engineering panel.

Seem's like a bug, thanks.

cosmonaut2040 · Sep 9, 2012

PeterRoss said:
The main reason for constant fuel leakage is chemical engine heating being on when it's unneded. The problem is that LH2 isn't being used by any chemical engine. It may be caused by wrong engine type specification in its config. What engines do you use?

I use the NERVA, and indeed the fuel loss stops when I turn off the heating, thanks :thumbup:

Good to know that on longer trips I should keep the heating off, otherwise I would get to Mars with empty tanks :lol:

---------- Post added at 10:58 AM ---------- Previous post was at 10:52 AM ----------

PeterRoss said:
We're planning to increase efficiency of NTRs to 99.999 with the RC3. Maybe we should increase NERVA's efficiency as well, thanks for your suggestion.

probably it should be the same for chemical engines too - they have the same method of cooling by ejecting the hot exhaust

jedidia · Sep 9, 2012

- the NERVA engines in IMS produce way too much heat.

known, we're only now getting around to do some real research on some stuf. RC3 will have overhauled, more realistic configs.

- it would be nice to have a power cell as a another power generator option: consuming LOx+LH2 and producing power+H20

It would be nice to have a lot of things... I'll note it for the future.

- it seems that batteries are not charged from external supply.

oops.

But talking about consuming fuel - I noticed that my LH2 is slowly dissapearing somewhere even when the engine is not in use. Does IMS simulate boil-off? Otherwise I have no idea what might be consuming it.

More oops. Config error...

activating the antenna module leads always to a CTD in the moment when the antenna finishes deployment.

big oops. Will be fixed. RC3 will probably tke a while to get on the road, very busy ife currently, but I'm working on it on and off.

PeterRoss · Sep 9, 2012

cosmonaut2040 said:
I use the NERVA, and indeed the fuel loss stops when I turn off the heating, thanks :thumbup:

Some obsolete config parameter. Just change string

Code:

EngineType = Thermal

into

Code:

Type = Thermal

and you won't need to bother about controlling heating once it's on - this is what's good about thermal engines :lol:
Configs will be updated with RC3 anyway.

Grover · Sep 9, 2012

to elaborate on my UCD bug:

the modules are attached properly in the scenario, but when the scenario is loaded again, the attachment is not made, so they drop to the ground below where they were

the scenario file doesn't show anything dramatic, perhaps there's a subtle error with the attachment lines?

Code:

BEGIN_DESC
XR5 loaded
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51982.4183614005
END_ENVIRONMENT

BEGIN_FOCUS
  Ship _URMS
END_FOCUS

BEGIN_CAMERA
  TARGET _URMS
  MODE Extern
  POS 2.33 -100.94 -8.88
  TRACKMODE TargetRelative
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 5460384.72 -3932714.08 -86565.50
  RVEL -4199.853 -5888.998 2627.631
  AROT -124.91 -9.28 -4.19
  VROT 0.10 0.05 -0.07
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
  O2_TANK 100.00
  FOOD_TANK 100.00
  CFG_MONTH_O2 6.00
  CFG_MONTH_FOOD 6.00
  UCGO @@0,1,0,0,@@1,1,0,0,@@2,1,0,0,@@3,1,0,0,@@4,1,0,0,@@5,1,0,0,@@6,1,0,0,@@7,1,0,0,
END
XR5-01:XR5Vanguard
  STATUS Landed Earth
  POS -14.4319900 -7.9714200
  HEADING 118.39
  RCSMODE 0
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000
  IDS 0:197 100
  NAVFREQ 0 0 0 0
  XPDR 195
  SECONDARY_HUD 3
  LAST_ACTIVE_SECONDARY_HUD 0
  ADCTRL_MODE 0
  TAKEOFF_LANDING_CALLOUTS 0.000000 0.000000 0.000000 0.000000 0.000000
  APU_FUEL_QTY 0.992979
  LOX_QTY 0.996790
  CABIN_O2_LEVEL 0.209000
  CREW_STATE 0
  INTERNAL_SYSTEMS_FAILURE 0
  COGSHIFT_MODES 0 0 0
  MWS_ACTIVE 0
  COOLANT_TEMP 31.200000
  DMG_0 1.000000 Left Wing
  DMG_1 1.000000 Right Wing
  DMG_2 1.000000 Left Aileron
  DMG_3 1.000000 Right Aileron
  DMG_4 1.000000 Landing Gear
  DMG_5 1.000000 Docking Port
  DMG_6 1.000000 Retro Doors
  DMG_7 1.000000 Top Hatch
  DMG_8 1.000000 Radiator
  DMG_9 1.000000 Airbrake
  DMG_10 1.000000 Left Main Engine
  DMG_11 1.000000 Right Main Engine
  DMG_12 1.000000 Left SCRAM Engine
  DMG_13 1.000000 Right SCRAM Engine
  DMG_14 1.000000 Fore Hover Engine
  DMG_15 1.000000 Aft Hover Engine
  DMG_16 1.000000 Left Retro Engine
  DMG_17 1.000000 Right Retro Engine
  DMG_18 1.000000 Forward Lower RCS
  DMG_19 1.000000 Aft Upper RCS
  DMG_20 1.000000 Forward Upper RCS
  DMG_21 1.000000 Aft Lower RCS
  DMG_22 1.000000 Forward Star. RCS
  DMG_23 1.000000 Aft Port RCS
  DMG_24 1.000000 Forward Port RCS
  DMG_25 1.000000 Aft Star. RCS
  DMG_26 1.000000 Outboard Upper Port RCS
  DMG_27 1.000000 Outboard Lower Star. RCS
  DMG_28 1.000000 Outboard Upper Star. RCS
  DMG_29 1.000000 Outboard Lower Port RCS
  DMG_30 1.000000 Aft RCS
  DMG_31 1.000000 Forward RCS
  DMG_32 1.000000 Bay Doors
  DMG_33 1.000000 Elevator
  IS_CRASHED 0
  MET_STARTING_MJD -1.000000
  INTERVAL1_ELAPSED_TIME -1.000000
  INTERVAL2_ELAPSED_TIME -1.000000
  MET_RUNNING 0
  INTERVAL1_RUNNING 0
  INTERVAL2_RUNNING 0
  ACTIVE_MDM 1
  TEMP_SCALE 2
  CUSTOM_AUTOPILOT_MODE 0
  AIRSPEED_HOLD_ENGAGED 0
  SCRAM0DIR 0.000000 0.000000 1.000000
  SCRAM1DIR 0.000000 0.000000 1.000000
  HOVER_BALANCE 0.000000
  MAIN0DIR 0.000000 0.000000 1.000000
  MAIN1DIR 0.000000 0.000000 1.000000
  GIMBAL_BUTTON_STATES 0 0 0 0 0 0
  ATTITUDE_HOLD_DATA 40.000000 0.000000 0 0 0.000000
  DESCENT_HOLD_DATA 0.000000 -3.000000 0
  AIRSPEED_HOLD_DATA 0.000000
  OVERRIDE_INTERLOCKS 0 0
  TERTIARY_HUD_ON 1
  CREW_DISPLAY_INDEX 0
  GEAR 1 1.0000
  RCOVER 0 0.0000
  DOCKINGPORT 0 0.0000
  AIRLOCK 0 0.0000
  IAIRLOCK 0 0.0000
  CHAMBER 0 0.0000
  AIRBRAKE 0 0.0000
  RADIATOR 0 0.0000
  LADDER 0 0.0000
  HATCH 0 0.0000
  SCRAM_DOORS 0 0.0000
  HOVER_DOORS 0 0.0000
  BAY_DOORS 1 1.0000
  ELEVATOR 0 0.0000
  APU_STATUS 0
  EXTCOOLING_STATUS 1
  TRIM 0.000000
  LIGHTS 0 0 0
  XRUMMU_CREW_DATA_VALID 1
  UMMUCREW XI0-Michael_Samuelle-37-65-78
  UMMUCREW XI1-Nikita_Simone-29-65-54
  UMMUCREW XI2-Madeline_Dolenc-36-68-58
  UMMUCREW XI3-Seymour_Birkoff-24-71-68
  UMMUCREW XI4-Katherine_Quinn-28-67-56
  UMMUCREW XI5-Cameron_Mitchell-36-65-77
  UMMUCREW XI6-Samantha_Carter-33-66-53
  UMMUCREW XI7-Daniel_Jackson-35-68-75
  UMMUCREW XI8-Teal_c-31-64-104
  UMMUCREW XI9-Vala_Mal_Doran-30-67-53
  UMMUCREW XI10-Elizabeth_Weir-36-68-56
  UMMUCREW XI11-John_Sheppard-34-64-77
  UMMUCREW XI12-Rodney_McKay-35-72-90
  UMMUCREW XI13-Teyla_Emmagan-27-68-57
  UMMUCREW XI14-Ronon_Dex-32-63-97
  UMMUCREW XI15-Carson_Beckett-38-74-95
  UMMUCREW XI16-Lee_Adama-26-65-74
  UMMUCREW XI17-Kara_Thrace-26-67-55
  RCS_DOCKING_MODE 0
  ACTIVE_EVA_PORT 0
  PAYLOAD_SCREENS_DATA 0.2 0 1 3
  GRAPPLE_TARGET GASS
END
XR5-01_Bay:XRPayloadBay
  STATUS Landed Earth
  POS -14.4321780 -7.9713194
  HEADING 118.39
  ATTACHED 0:36,XR5-01
  AFCMODE 7
END
GASS:IMS\SBB41B\BM201_CONTROL_MODULE
  STATUS Landed Earth
  POS -14.4319772 -7.9714268
  HEADING 28.39
  ATTACHED 3:0,_UCD
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000
  NAVFREQ 0 0
  COMMAND 0 1
  EMPTYMASS 10000.000000
  MASSCENTER 0.000000 0.000000 0.000000
  PMI 8.150000 8.150000 2.300000
  CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
  TEMPERATURES -1:298.00:273.23
  HEATING -1
  THGROUPLEVELS 0 0 0 0 
  CREW 2 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
_UCD:UCargoDeck
  STATUS Landed Earth
  POS -14.4319900 -7.9714200
  HEADING 118.39
  ATTACHED 0:38,XR5-01
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
  CORE_NAME XR5-01
  JETTISONSPEED 0.00
  JETTISONINT 5.00
  ALLOW_SEND_FOCUS 0
  DEF_ATT_PARAMS 0.000 0.000 0.000 0.00000 0.00000 1.00000 0.00000 1.00000 0.00000
  PL_DESCRIPTION GASS 0.000 2.100 1.600 -1.0000 0.0000 0.0000 0.0000 1.0000 0.0000 0
  PL_DESCRIPTION Dock1 -5.100 2.100 1.600 1.0000 -0.0000 -0.0000 -0.0000 -1.0000 -0.0000 1
  PL_DESCRIPTION Node1 -4.500 2.300 -3.000 -0.0000 0.0000 -1.0000 0.0000 1.0000 0.0000 2
  PL_DESCRIPTION Node2 4.500 2.300 -3.000 -0.0000 -0.0000 -1.0000 0.0000 1.0000 -0.0000 3
  PL_DESCRIPTION Truss Anchor 0.000 2.200 -5.400 -0.0000 1.0000 -0.0000 1.0000 0.0000 0.0000 4
  PL_DESCRIPTION Solar1 0.000 2.000 -15.000 -0.0000 -1.0000 -0.0000 -1.0000 0.0000 0.0000 5
  PL_DESCRIPTION Truss1 0.000 1.100 -9.000 1.0000 -0.0000 -0.0000 -0.0000 -1.0000 -0.0000 6
  PL_DESCRIPTION Truss2 0.000 1.100 -11.400 1.0000 -0.0000 -0.0000 -0.0000 -1.0000 0.0000 7
  PL_DESCRIPTION Radiator 1 0.000 1.600 -21.100 0.0000 0.0000 -1.0000 -0.0000 1.0000 0.0000 8
  PL_DESCRIPTION RCS1 -1.500 0.500 -1.800 -0.0000 1.0000 0.0000 -0.0000 -0.0000 1.0000 9
  PL_DESCRIPTION RCS2 1.500 0.500 -1.800 0.0000 1.0000 0.0000 0.0000 -0.0000 1.0000 10
  PL_DESCRIPTION RCS3 1.500 0.500 -14.200 -0.0000 1.0000 -0.0000 0.0000 0.0000 1.0000 11
  PL_DESCRIPTION RCS4 -1.500 0.500 -14.200 0.0000 1.0000 0.0000 -0.0000 -0.0000 1.0000 12
  PL_DESCRIPTION Battery 1 0.000 1.200 -18.600 -1.0000 -0.0000 -0.0000 0.0000 1.0000 0.0000 13
  IN_JETTISON 0 0
  J_MARKER 0.00
END
Dock1:IMS\SBB41B\DADG_Docking_Adapter
  STATUS Landed Earth
  POS -14.4319552 -7.9713865
  HEADING 28.39
  ATTACHED 2:1,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Node1:IMS\SBB41B\BN200_Big_Node
  STATUS Landed Earth
  POS -14.4319945 -7.9713716
  HEADING 118.39
  ATTACHED 9:2,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Node2:IMS\SBB41B\BN200_Big_Node
  STATUS Landed Earth
  POS -14.4320334 -7.9714428
  HEADING 118.39
  ATTACHED 9:3,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Truss Anchor:IMS\SBB41B\BT201_Truss_to_Module_Adapter
  STATUS Landed Earth
  POS -14.4320331 -7.9713969
  HEADING 28.39
  ATTACHED 5:4,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Solar1:IMS\SBB41B\BP101_Solar_panel
  STATUS Landed Earth
  POS -14.4321098 -7.9713559
  HEADING 28.39
  ATTACHED 5:5,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Truss1:IMS\SBB41B\BT101_Truss
  STATUS Landed Earth
  POS -14.4320619 -7.9713815
  HEADING 28.39
  ATTACHED 9:6,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Truss2:IMS\SBB41B\BT101_Truss
  STATUS Landed Earth
  POS -14.4320811 -7.9713713
  HEADING 28.39
  ATTACHED 9:7,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Radiator 1:IMS\SBB41B\BR010_Radiator
  STATUS Landed Earth
  POS -14.4321586 -7.9713298
  HEADING 118.39
  ATTACHED 2:8,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
RCS1:IMS\SBB41B\BRCS2_ReactionControlSystem_Engine
  STATUS Landed Earth
  POS -14.4319979 -7.9714004
  HEADING 118.39
  ATTACHED 2:9,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
RCS2:IMS\SBB41B\BRCS2_ReactionControlSystem_Engine
  STATUS Landed Earth
  POS -14.4320109 -7.9714242
  HEADING 118.39
  ATTACHED 2:10,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
RCS3:IMS\SBB41B\BRCS2_ReactionControlSystem_Engine
  STATUS Landed Earth
  POS -14.4321099 -7.9713711
  HEADING 118.39
  ATTACHED 2:11,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
RCS4:IMS\SBB41B\BRCS2_ReactionControlSystem_Engine
  STATUS Landed Earth
  POS -14.4320970 -7.9713474
  HEADING 118.39
  ATTACHED 2:12,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
Battery 1:IMS\SBB41B\BG201_Battery_SContainer
  STATUS Landed Earth
  POS -14.4321386 -7.9713405
  HEADING 28.39
  ATTACHED 5:13,_UCD
  AFCMODE 7
  NAVFREQ 0 0
END
_URMS:URMS
  STATUS Landed Earth
  POS -14.4319900 -7.9714200
  HEADING 118.39
  ATTACHED 0:39,XR5-01
  AFCMODE 7
  NAVFREQ 0 0
  MAIN_STATUS 0
  JOYSTICK_STATUS 0
  JOYSTICK_CFG 1
  PLATFORM_MESH 1
  CORE_NAME XR5-01
  CORE_PARAMS 6.5000 4.0000 -2.0000 6.5000 4.0000 -14.0000 0.00000
  ORIENTATION 1.00000 -0.00000 0.00000 0.00000 0.00000 -1.00000
  CAMERA_STATUS 0
  SCALE_FACTOR 1.7000
  LIN_PARAMS 0 0.0000 0.0000
  ROOT_ROT 0 0.0000 0.0000
  SHOULDER_ROT 0 14.0000 0.0000
  ELBOW_ROT 0 0.0000 0.0000
  WRIST_ROT_H 0 104.0000 0.0000
  WRIST_ROT_V 0 104.0000 0.0000
  WRIST_ROT_R 0 0.0000 0.0000
  CARGO_PARAMS 100.00 0.00 0.00
  IK_PARAMS 1 0.00000 0.00000 0.000
END
END_SHIPS

BEGIN_ReFuelMFD
  SCENARIO_TREE 
    NAMED Computers
    END_NODE 
  END_NODE 
END

ill have a search of the forums, but i dont think ive come across this here before

thanks

---------- Post added at 07:44 PM ---------- Previous post was at 07:38 PM ----------

ah, found it!

this post, explains that its because there is a space in the names of the ones that are dropped. it seems that something in UCS or the attachment system can't handle spaces well.

i can fix this easy enough

---------- Post added at 08:03 PM ---------- Previous post was at 07:44 PM ----------

heres a suggestion, why not bring UGCO compatibility into IMS? it gives an easy way to replenish our resources (different fuel types, food and water etc) without having to edit vessel configs or add new tanks god forbid

jedidia · Sep 10, 2012

this post, explains that its because there is a space in the names of the ones that are dropped. it seems that something in UCS or the attachment system can't handle spaces well.

Ah yes... spaces in vessel names are very bad on several levels. They are not UMMU conformative, and IMS will have all kinds of its own problems with them, and even Orbiter itself doesn't seem to like them (lead to trouble with docking on reloading a scenario). To be avoided at all cost!

heres a suggestion, why not bring UGCO compatibility into IMS? it gives an easy way to replenish our resources (different fuel types, food and water etc) without having to edit vessel configs or add new tanks god forbid

UCGO is not suitable for IMS' dynamic nature due to the upper cargo limit. Some support for UCGO interaction is planned in combination with the payload system, but not UCGO support per se. As it stands, IMS comes with its own resource sharing code. You can transfer consumables and propellant from and to any docked IMS vessel (so you can build yourself a supply station), IMS storage modules, and even other vessels if you note it in their configs (only documented in config writer's guide currently, will have to change that at some poit). Beyond that, since I use actual propellant resources to manage consumables, they are accessible in the scenario editor (resources 1 to 3 are always food, water, oxygen, although I'm currently not sure about the order without looking it up). So you'll be able to make do without UCGO just fine.

PeterRoss · Sep 10, 2012

jedidia said:
Ah yes... spaces in vessel names are very bad on several levels. They are not UMMU conformative, and IMS will have all kinds of its own problems with them, and even Orbiter itself doesn't seem to like them (lead to trouble with docking on reloading a scenario). To be avoided at all cost!

Space in vessel's name again, eh? I would have used 'DON'T USE SPACES IN VESSEL'S NAME' as an official IMS slogan, but it would be unfair for all other addons suffering from it and for Orbiter itself in the first place :lol:

jedidia · Sep 10, 2012

I've updated the description in the initial post to include this piece of vital information. If we're lucky, someone will even read it :lol:

Chub777 · Sep 10, 2012

Apologies if this problem has already been posted before.
---
I've downloaded this and begun to play around with it. I must say, well done to all to helped make this addon.

However, I have experienced a problem. I was installing modules on my brand new vessel. I clicked on "attach closest module" and it worked flawlessly. After that, I clicked on "integrate" and got a CTD. This is the log:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.80208e-007 sec
Found 0 joystick(s)
Devices enumerated: 9
Devices accepted: 7
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 5400 Series   )
==> Direct3D T&L HAL (ATI Radeon HD 5400 Series   )
==> Direct3D HAL (ATI Radeon HD 5400 Series   ) #2
==> Direct3D T&L HAL (ATI Radeon HD 5400 Series   ) #2
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module EnergyConfigurator.dll  [Build ******, API 060425]
Module ProjectApolloConfigurator.dll  [Build 100907, API 100830]
Module ProjectOutpostsConfig.dll  [Build 120604, API 100830]
Module ScreenCapture.dll ..... [Build ******, API 060425]
Module NotesMFD.dll .......... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module BaseSyncMFD.dll ....... [Build 100616, API 100603]
Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
Module Load.dll .............. [Build 110906, API 100830]
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module Telescope.dll ......... [Build 110413, API 100830]
Module AttitudeMFD.dll ....... [Build ******, API 060425]
Module transx.dll ............ [Build ******, API 060425]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module LaunchMFD.dll ......... [Build 101127, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1434 x 872 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
**** WARNING: Mesh not found: .\Meshes\NanediVallis.msh
BaseObject: Parse error 1
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build ******, API 061227]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGlider.dll ....... [Build 100830, API 100830]
Module LuaInline.dll ......... [Build 100830, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
ERROR: DDraw object is still referenced: 1227
---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1034]
---------------------------------------------------------------
**** Closing simulation session

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1434 x 872 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
**** WARNING: Mesh not found: .\Meshes\NanediVallis.msh
BaseObject: Parse error 1
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build ******, API 061227]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGlider.dll ....... [Build 100830, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
Module IMS.dll ............... [Build 120902, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

I can't see anything strange about this, though. Thanks for your help. :thumbup:

Grover · Sep 10, 2012

the CTD is a small bug, something to do with docked vessels being intergrated (or docking ports being deleted)

it usually works second time, just load the presaved scenario (Scenarios/IMS/[VesselName]) and try again, it might even have been a post-integration error, so you dont even need to try again

jedidia · Sep 10, 2012

However, I have experienced a problem. I was installing modules on my brand new vessel. I clicked on "attach closest module" and it worked flawlessly. After that, I clicked on "integrate" and got a CTD. This is the log:

It can happen, and is due to an orbiter bug, so I can't fix it. See "in case of a ctd" on the first page for more information. Simply reloading the last autosave and trying again works in some cases, in others changing the integration order usually can get you around it.

Mattyv · Sep 11, 2012

First of all, I want to say that this is a beautiful addon.:thumbup:

I have learned how to use the power and thermodynamics features, but I'm have one question about life support. Most of the life support modules say that they deal with water and O2 but how exactly do these systems work? Same question for hydroponics and food.

jedidia · Sep 11, 2012

I have learned how to use the power and thermodynamics features, but I'm have one question about life support. Most of the life support modules say that they deal with water and O2 but how exactly do these systems work? Same question for hydroponics and food.

The life support section of the spacecraft design guide is in the works, as are lifesupport modules with more realistic properties. I didn't really have much time for research in that area until now. IMS internally the whole thing is a very simplified parameter that just creates the specified resource in the specified amount, if necessary out of vacuum... :shifty:

Mattyv · Sep 12, 2012

Do I need to have storage room for the produced resources?

PeterRoss · Sep 12, 2012

Yes you do, even if these resources will be consumed right after production.

Tacolev · Sep 13, 2012

So I have a question about some things not in the modder's guide thread, with regards to modelling a fusion rocket and its power turbines as separate modules. Since this concerns engines let me know if it should wait until after any changes in RC3 if they are not just to config files.

Anyway, is it kosher that I have simply add a PowerInput line to a non-electric engine module? It seems to work on its face but I'm not sure if anything wacky is going on behind the scenes with regards to heat calculations and such.

For some background on why I might want to be doing this, I am trying to model a system like this one from a public domain NASA paper:

The reason to separate the system in the first place is of course so that the generator can operate with radiators at a different temperature from the engine. The way I have it now, the engine module is a thermal type with a PowerInput for the cooling system's requirements and the generator module produces the ~30MWe at the appropriate efficiency.

jedidia · Sep 13, 2012

Anyway, is it kosher that I have simply add a PowerInput line to a non-electric engine module?

That wouldn't have any influence, but what you'd have to do is add a power output parameter. After all you want to get power out of it, not into it.
In short, it's not possible currently to have an engine that produces power, as described in the spacecraft design guide. What would be possible is to make the engine a composite module and have the generator module be a part of this composite. It won't affect the engine either, but you cannot take the other module online. For what it's worth though, I think with the code currently you can still take generators of a composite module online, but that would need a test. So it is possible that even that doesn't have an influence, but that would be very easy to fix.
So this way, you'd have the generator as a separate module that will only work if it is integrated into the fusion drive. It will still work if the drive is outside operational temperature, but that too wouldn't be difficult to rectify.

Now that I look at the schematic, though, it seems that the engine needs power for its cooling system. That could give trouble. You can of course add a PowerInput parameter to the engine, but I think the engine would consume it even if it is not thrusting. Also, the whole setup would seem to suggest that power can only be supplied while the engine is working. I'll have to run some tests, because I can't remember from the top of my head how the "active" flag is treated for engines, especially for non-electric ones, but it shouldn't be too much trouble to get this kind of setup to work (might even work already, but I doubt it):

-Drive and Generator are a composite module, that is two modules that are connected via child attachment.
-Drive will consume power set in PowerInput while thrusting. Consumption is unrelated to thrust level. (note: do not make electric engine, electric engines are hard-coded to demand their entire thrust power in electricity)
-Generator can produce power if engine is thrusting (but will not kick in automatically, and power output will not be related to thrust level).
-as a little perk, secondary engine parameters such as cooling capacity will not work if engine doesn't have power.

Is that about what you want?

New Release Interplanetary Modular Spacecraft RC9

Member

Saturn V Misfire

Member

Warranty man

Member

shoemaker without legs

Warranty man

Saturn V Misfire

shoemaker without legs

Warranty man

shoemaker without legs

New member

Saturn V Misfire

shoemaker without legs

Rocket Scientist in Training

shoemaker without legs

Rocket Scientist in Training

Warranty man

Member

shoemaker without legs

Similar threads