Problem Fairing sep causes CTD

[n122vu]

So I've been working on my fairing for my Falcon 9 project, and in testing the mesh in Orbiter I noticed that when the fairing jettisoned in flight, Orbiter immediately CTDs. Anyone know what would cause this? I did notice a couple of missing meshes in the log, but i'm not sure they have anything to do with the fairing...

Orbiter.log:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI MOBILITY RADEON 7500  )
==> Direct3D T&L HAL (ATI MOBILITY RADEON 7500  )
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module ScnEditor.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module ExtMFD.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module Rcontrol.dll [API v.050206]
Module InterMFD421.dll [API v.050206]
Module InterMFD53.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Stencil buffer: 8 bit
Render device: Fullscreen 1024 x 768
Device has hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
Module Multistage2.dll [API v.050206]
Module Spacecraft3.dll [API v.050206]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\KSC_6.msh
**** WARNING: Mesh not found: .\Meshes\.msh

 

[Lucy]

This, I'm assuming (Given that you have multistage2 and spacecraft3 in the list) is a multistage / SC3 ship?

Since when you stage a vessel, what actually happens is a new vessel is spawned with the requisite mesh to "pretend" to be the discarded stage, things which can cause CTD which wouldn't leave a trace in the .log include duplicating the name of the vessel and misdefinition of the mesh required for the new vessel.

I've never developed with multistage2 nor SC3, however I have written a staging vessel with a .dll module for control, so I understand the process itself if not the manipulation of those generic dlls to achieve the result.

Generally speaking, however, it's usually a good idea to double check everything twice. I'm amazed how often I miss simple spelling or coding errors because my eyes skip past them and my brain fills in what I expect to see there, rather than what is. CTDs of this nature are most likely due to an oversight, as far as I know.

 

[eveningsky339]

Could use some input on what tools you are using for the staging of the vehicle. Spacecraft3? Multistage2? CVE-lite? Or custom .dll?

 

[n122vu]

I was launching it atop glider's Falcon 9, which is a multistage2 craft, for testing. I made my own copies of the scenario, config, and ini files and edited them accordingly so I would have the originals to go by. In both the meshes and config folders, I created a folder called MyFalcon9 at the same level as the SpaceX folders. I kept the original file names the same and placed my copies in these folders. The only thing I edited were the folder names in the scenario and the ini files, and the name of the fairing to use my own fairings. I know it sounds like a mess by the way I've explained it, but I took every step to ensure everything matched the original and changed only what was necessary to use my fairing.

**EDIT**
Attached is an image of the fairing in place atop glider's Falcon 9.

 

[n122vu]

I've discovered it only occurs if I manually jettison the fairing before either/both the 1st stage or the "pseudo-booster" glider uses on his Falcon 9 are jettisoned.

Again, this is glider's ini file and I am using it for testing purposes only. I simply changed the directory of the fairing mesh location to match where I had put my mesh.

INI file:

[MISC]
cog=3
Telemetry=0

[TEXTURE_LIST]
TEX_1=Merlin-1C_exhaust
TEX_2=Kestrel_exhaust

[PARTICLESTREAM_1]
NAME=stg1_contrail
SRCSIZE=6.
SRCRATE=200
V0=150.0
SRCSPREAD=0.1
LIFETIME=6.
GROWTHRATE=2.5
ATMSLOWDOWN=0.5
LTYPE=DIFFUSE
LEVELMAP=LVL_PSQRT
LMIN=0.85
LMAX=1.
ATMSMAP=ATM_PLOG
AMIN=0.015
AMAX=0.6
TEX=Contrail_01

[PARTICLESTREAM_2]
NAME=1st_stg_flame
SRCSIZE=1.47
SRCRATE=1000
V0=300.0
SRCSPREAD=0.01
LIFETIME=0.15
GROWTHRATE=-2.5
ATMSLOWDOWN=2.0
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=0.1
ATMSMAP=ATM_PLIN
AMIN=-2
AMAX=1
TEX=Contrail_02

[PARTICLESTREAM_3]
NAME=2nd_stg_flame
SRCSIZE=1.17
SRCRATE=3500
V0=500.0
SRCSPREAD=0.01
LIFETIME=0.01
GROWTHRATE=-3
ATMSLOWDOWN=2.0
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=1
ATMSMAP=ATM_PLIN
AMIN=-2
AMAX=1
TEX=contrail3

[BOOSTER_1]
N=1
BurnDelay=0
MeshName="SpaceX\tr_box"
off=(0.,0.,0.)
ANGLE=0.
Height=34.72
Diameter=3.6
BurnTime=103
EmptyMass=1.
FuelMass=1.
Thrust=662579.
ENG_TEX=Merlin-1C_exhaust
eng_1=(0.,0.,-18.0)
eng_diameter=0.81
ENG_PSTREAM1=1st_stg_flame
CURVE_1=(0,28.)
CURVE_2=(30,76.)
CURVE_3=(50,100.)
CURVE_4=(110,100.)
Module="SpaceX\pseudo_booster"
speed=(0.,0.,-2.)
rot_speed=(0.,0.,0.0)

[BOOSTER_2]
N=1
BurnDelay=0
MeshName="SpaceX\tr_box"
off=(0.,0.,0.)
ANGLE=0.
Height=34.72
Diameter=3.6
BurnTime=107
EmptyMass=1.
FuelMass=1.
Thrust=662579.
eng_1=(0.,0.,-40.)
eng_diameter=0.01
ENG_PSTREAM1=stg1_contrail
CURVE_1=(0,28.)
CURVE_2=(30,76.)
CURVE_3=(50,100.)
CURVE_4=(115,100.)
Module="SpaceX\pseudo_booster"
speed=(0.,0.,-2.)
rot_speed=(0.,0.,0.0)

[STAGE_1]
Height=34.72
Diameter=2.
EmptyMass=14601.
FuelMass=246780.
Thrust=4638053.
BurnTime=125
off=(0.,0.,0.)
MeshName="SpaceX\Falcon-9_1st_stg"
eng_1=(-1.,1.,-18.)
eng_2=(0.,1.,-18.)
eng_3=(1.,1.,-18.)
eng_4=(-1.,0,-18.)
eng_5=(1.,0,-18.)
eng_6=(-1.,-1.,-18.)
eng_7=(0.,-1.,-18.)
eng_8=(1.,-1.,-18.)
ENG_TEX=Merlin-1C_exhaust
eng_diameter=0.81
ENG_PSTREAM1=1st_stg_flame
speed=(0.,0.,-4.)
rot_speed=(0.,0.,0.0)
Module="SpaceX\Falcon-9_1st_stg"

[STAGE_2]
MeshName="SpaceX\Falcon-9_2nd_stg"
IGNITE_DELAY=3.
Diameter=2.
Height=8.68
EmptyMass=4897
FuelMass=76728.0
Thrust=741042.
BurnTime=345
off=(0.,0.,19.)
eng_1=(0.,0,-6.6)
ENG_TEX=Kestrel_exhaust
eng_diameter=1.16
ENG_PSTREAM1=2nd_stg_flame
PITCHTHRUST=200000

[FAIRING]
N=2
MeshName="MyFalcon9\Falcon9Fairing"
Diameter=5.2
Height=13.9
angle=90.
off=(0.,0.,31.5)

[PAYLOAD_1]
off=(0.,0.,32.5)
speed=(0.,0.,0.5)
rot_speed=(0.,0.,0.)
MeshName="SpaceX\Falcon-9_payload"
Module="SpaceX/Falcon-9_LEO_satellite"
name="PAYLOAD"
Diameter=4.8
Height=4.
Mass=11290.
render=0

 

[PhantomCruiser]

I'm working a multistage project now myself, and had similar issues. If there is a problem with the payload, then I'd get a CTD right at fairing sep.
To see if you are having the same trouble, make a test run after changing the CURRENT_PAYLOAD 1 in the scenario file to a 0, and editing out the payload in your config file. Then see if she flies right after the fairing sep.
Just a thought...

 

[n122vu]

I'm working a multistage project now myself, and had similar issues. If there is a problem with the payload, then I'd get a CTD right at fairing sep.
To see if you are having the same trouble, make a test run after changing the CURRENT_PAYLOAD 1 in the scenario file to a 0, and editing out the payload in your config file. Then see if she flies right after the fairing sep.
Just a thought...

I'll give that a try tonight.

I'd honestly rather give it a try now than be in the day-long meetings I've been in, but gotta pay the bills somehow I guess LOL.

Thanks,
n122vu