BrianJ
Addon Developer
Yes. Enter the required inclination as negative, it should use the southerly launch azimuth.
Brian
-
ORBITER-FORUM will be temporarily closed at 2026-07-23 18:00 UTC while we complete some OF maintenance tasks. The amount of downtime is expected to take up to one hour, but probably less.
OHM Falcon9 for Orbiter2016
- Thread starter OrbitHangar
- Start date
Brian
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
I did a fresh install of Orbiter 2016, and I'm attempting to run a scenario of Falcon 9 launching from SLC-40 with Zuma. It appears to be loading well, but then the program closes automatically with no error message. What is the problem?
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
However, a different scenario of Falcon 9 launching Inmarsat-5 F4 from LC-39A works perfectly.
To be clear, all launch scenarios from 39A work while SLC-40 scenarios just close before the actual game begins.
To be clear, all launch scenarios from 39A work while SLC-40 scenarios just close before the actual game begins.
francisdrake
Addon Developer
- Joined
- Mar 23, 2008
- Messages
- 1,326
- Reaction score
- 1,656
- Points
- 128
- Website
- francisdrakex.deviantart.com
What payload pack / mission package are you using?
I found the Zuma in "SpaceX Mission Package" but
- This is for the older Block4 -
Zuma:Falcon9_BLOCK4/Payloads/Zuma
- It is only the scenario file. A cfg file for the Zuma is also required.
I found the Zuma in "SpaceX Mission Package" but
- This is for the older Block4 -
Zuma:Falcon9_BLOCK4/Payloads/Zuma
- It is only the scenario file. A cfg file for the Zuma is also required.
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
I duplicated a TestSat config file (i.e. 6300_sat) in the vanilla Falcon 9 v1.2 addon pack, renamed it to Zuma (which is in the "Payloads" folder I created), and changed the mass to just over 1,100 kilograms.
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
I personally think it has to do with the SLC-40 config in the scenario file because if I changed the launch pad to 39A, the scenario runs great.
francisdrake
Addon Developer
- Joined
- Mar 23, 2008
- Messages
- 1,326
- Reaction score
- 1,656
- Points
- 128
- Website
- francisdrakex.deviantart.com
I made a Zuma sat, as you described, in a 'Payloads' folder.
Attached is the scenario. Runs without problems here.
Attached is the scenario. Runs without problems here.
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
The scenario you attached still isn't working.
However, I forgot to mention that I have the Falcon Heavy addon and I swapped the SLC-40 pad from the Falcon 9R V1.2 addon with the pad from the Falcon Heavy addon. It works great with the Falcon Heavy SLC-40 pad.
To reiterate, I think something is wrong with the Falcon 9R V1.2 addon's SLC-40 pad. Can't tell if it's the new crew tower or some other miniscule detail. But the Falcon Heavy addon's SLC-40 pad works as a substitute.
However, I forgot to mention that I have the Falcon Heavy addon and I swapped the SLC-40 pad from the Falcon 9R V1.2 addon with the pad from the Falcon Heavy addon. It works great with the Falcon Heavy SLC-40 pad.
To reiterate, I think something is wrong with the Falcon 9R V1.2 addon's SLC-40 pad. Can't tell if it's the new crew tower or some other miniscule detail. But the Falcon Heavy addon's SLC-40 pad works as a substitute.
Last edited:
BrianJ
Addon Developer
Hi,
EDIT **************************************************************
Oh...wait a moment....there might be a mesh error on the new "crew tower" at SLC40.
"Isolated vertices" in the mesh can cause random problems.
It might be that. Back soon.
EDIT2
Had a check on the mesh - no isolated vertices but something is not quite right with one of the mesh groups, not sure what it is. In the meantime you might try my suggestions below.
**********************************************************************
I'd suggest:
1) Try one of the "Test" SLC40 scenarios that are included with the Falcon9 add-on.
2) Copy your "Zuma" scenario, remove the payload from the scenario, see if scenario works.
My first guess is its a payload attachment point definition problem.
If either test gives CTD, post scenario and orbiter.log
Cheers,
BrianJ
SLC40 is working as usual for me.
EDIT **************************************************************
Oh...wait a moment....there might be a mesh error on the new "crew tower" at SLC40.
"Isolated vertices" in the mesh can cause random problems.
It might be that. Back soon.
EDIT2
Had a check on the mesh - no isolated vertices but something is not quite right with one of the mesh groups, not sure what it is. In the meantime you might try my suggestions below.
**********************************************************************
I'd suggest:
1) Try one of the "Test" SLC40 scenarios that are included with the Falcon9 add-on.
2) Copy your "Zuma" scenario, remove the payload from the scenario, see if scenario works.
My first guess is its a payload attachment point definition problem.
If either test gives CTD, post scenario and orbiter.log
Cheers,
BrianJ
Last edited:
I also confirm that all Falcon9 scenarios using pad SLC40 produce CTD (but only during nighttime launch!). If I change the MJD date to daytime then all scenarios do work. I attach my Orbiter_NG.cfg file for reference. No errors are recorded in Orbiter.log file. Hope my comment is useful for debugging the problem.
BrianJ
Addon Developer
Hi,
hmmm, another slightly strange bug. The only difference between day/night launches is the "local light" sources illuminating the launch pad. I don't know if that would cause problems on certain set ups?
Anyway, it all works OK for me, running Windows8.1 on an ancient PC with built-in graphics chip.
The only thing that I could find that might be causing problems was the SLC40 Crew Tower mesh.
So, I have updated the add-on with a new Crew Tower mesh (double checked and about 4000 less polys!).
Update 240521
Give that a try, if the problem persists, post your orbiter.log after the CTD (it can give information even if there are no explicit errors listed).
Cheers,
Brian
After a quick test with the updated "slc40r_crew_tower.msh" file ... CTD again. I attach log file after trying to load "OG2 launch(SLC40 LZ1 flyback)" scenario.
I also disabled local light sources, but no effect.
I also disabled local light sources, but no effect.
With default Orbiter graphics I get exactly same behaviour.
My D3D9 version is R4.26.
I put the crew tower mesh file in a base config file and loaded with no problems. My guess the bug is at the interface between slc40r.dll and slc40r_crew_tower.msh .
My D3D9 version is R4.26.
I put the crew tower mesh file in a base config file and loaded with no problems. My guess the bug is at the interface between slc40r.dll and slc40r_crew_tower.msh .
BrianJ
Addon Developer
Hmmm. OK, thanks for testing.
There is a little bit of code that relates to making the Crew Access Arm windows light up at night (mesh material changes) - this is the only thing I can think might be causing the problem.
Attached below is a new slc40r.dll module, without the mesh material change code.
See if it works for you.
If "No" then the only option is to revert to an older version with no Crew Access tower.
Thanks,
Brian
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 136
- Reaction score
- 14
- Points
- 33
- Location
- Argyle
- Website
- www.zachsellinger.com
Your patch worked.
BrianJ
Addon Developer
Thanks.
Below is attached another slc40r.dll module patch.
Mesh material change code has been replaced and revised slightly.
@ZacharyS41 and @sberinde if you have the time to test it, let me know if works.
Many thanks,
Brian
BrianJ
Addon Developer
OK, thanks
I have one last idea what might be the problem.
Another version of slc40r.dll is attached below - give it a try.
If it does not work, I am interested to know if the Crew Dragon works for you (it uses the same method to change mesh material). In any scenario, go to the Virtual Cockpit view [F8] and switch cabin lights on/off [ Ctrl ] + [ 8 ]. Does it work?
Thanks,
Brian
