Update Multistage2015 Update to OpenOrbiter2024

[jacquesmomo]

Thanks to everyone for your patience.

Thanks to you for your work!

 

[Matias Saibene]

Ok, I'm done initializing the variables, now I'm going to compile and see what happens.

computer explodes

 

[Matias Saibene]

I'm making some small progress now, I commented out the DelThrusterGroups line in the Jettison function of Multistage2015.cpp and now the SRB rockets are properly separated.

I need to find out more exactly what is going on with that line that crashes Orbiter. However the payload issue is still a problem as well.

Can anyone try this "temporary update"?

I also asked @fred18 for permission to upload the code to GitHub to make the changes more public, but I haven't received a reply, so for now I keep a local Git repository.

Also, since I'm not familiar with Multistage, I don't know why the SLS is floating in the air, there should be something below supporting it?

 

[Buck Rogers]

Really glad to see you working on this. Testing so far Multistage looks like it is the only major extension not working in Orb2014, and this one is essential (IMO).
Will test- Good Luck

 

[Buck Rogers]

Tested MS SLS test .scn: booster sep. good
Payload sep: CTD
Step by step getting there

 

[CurlSnout]

I can confirm that SRB separation, staging, and payload deployment all work fine, using the temporary update that you posted above. I have only tested the scenarios included in the Multistage2015 package. Congratulations on vanquishing the CTD that was occurring after SRB separation. I can also confirm that the Pad/Crawler assembly does not appear beneath the SLS sitting in the Hangar - but I am also unsure of the reason why this is so.

Thanks for working on this and sharing your progress.








Hi-Ho,

cs

 

[jacquesmomo]

I'm sorry because I can't test your work : I'm in Philippina for scuba diving until march the 4th....

 

[gattispilot]

I tested with my SLS and still it sets on the pad.

 

[Urwumpe]

I tested with my SLS and still it sets on the pad.

Just as suggestion: What about implementing the bare use cases of Multistage.dll as one or more Lua modules instead, that just makes it easier to code a LuaVessel for such launchers? Like you just need to import "something" at the start of the Lua script and can than just pass the configuration of the stages as a list of objects, while the Lua module handles the behaviour...

Yes, you can't just reuse the ini files then.
But translating the ini files to Lua would be a very simple recipe that everybody can learn, while only the development of the imported Lua module(s) would be difficult.

 

[gattispilot]

Just as suggestion: What about implementing the bare use cases of Multistage.dll as one or more Lua modules instead, that just makes it easier to code a LuaVessel for such launchers? Like you just need to import "something" at the start of the Lua script and can than just pass the configuration of the stages as a list of objects, while the Lua module handles the behaviour...

Yes, you can't just reuse the ini files then.
But translating the ini files to Lua would be a very simple recipe that everybody can learn, while only the development of the imported Lua module(s) would be difficult.

Oh. I would not know how to convert the ms2015 sls.ini to lua.

 

[Urwumpe]

Oh. I would not know how to convert the ms2015 sls.ini to lua.

I don't know myself yet and I am not really a Lua crack, its been a while since I did serious stuff with it.

Just converting the .ini to Lua now would result in lots of code having to be written, that we would need to copy into every vessel converted that way. But we should be able to do everything in Lua, that multistage can do, and we should be able to move the reuseable part of the code into a module that we can import. And the advantage would be that the new MS would be platform independent and likely runnable for some years and Orbiter versions. Maybe its the future.

 

[CurlSnout]

Also, since I'm not familiar with Multistage, I don't know why the SLS is floating in the air, there should be something below supporting it?

When I load the Multistage2015 'SH_SLS - Hangar and Crawler TEST' scenario it opens like this in Orbiter 2016:



In Orbiter 2024 (using the temporary update provided above) it looks like this:



In Orbiter 2024 the pad/crawler assembly is missing.

 

[Matias Saibene]

When I load the Multistage2015 'SH_SLS - Hangar and Crawler TEST' scenario it opens like this in Orbiter 2016:

View attachment 42407

In Orbiter 2024 (using the temporary update provided above) it looks like this:

View attachment 42408

In Orbiter 2024 the pad/crawler assembly is missing.

Thanks, I'll check why the pad mesh isn't loading.

 

[gattispilot]

Yes. it is missing. Nothing in the log like missing a mesh. I ran it in default graphics and the same result.

And it looks like the floor may need to be raised?

 

[Buck Rogers]

@gattispilot, I think I know why your SLS won't launch properly:
IIRC in MS you can define boosters as one unit with individual meshes, or define each booster individually (MS SLS demo has only one(?)).
I have individual boosters defined and only the first one is firing, hence lack of thrust and crash. Can you check boosters in the MS MFD.

@Matias Saibene, The MS MFD shows no fuel consumption for booster 2, Orbiter log says both boosters ignited!
Boosters did not seperate, fairings jettisoned successfully, second stage did not sep. or ignite.
Also Complex flight explosion causes a CTD

 

[Matias Saibene]

@gattispilot, I think I know why your SLS won't launch properly:
IIRC in MS you can define boosters as one unit with individual meshes, or define each booster individually (MS SLS demo has only one(?)).
I have individual boosters defined and only the first one is firing, hence lack of thrust and crash. Can you check boosters in the MS MFD.

@Matias Saibene, The MS MFD shows no fuel consumption for booster 2, Orbiter log says both boosters ignited!
Boosters did not seperate, fairings jettisoned successfully, second stage did not sep. or ignite.
Also Complex flight explosion causes a CTD

Thank you, I'll keep that in mind.
It's going to take more work than I thought, but it's a very interesting learning process.

 

[gattispilot]

I ran my SLS in 2016 and 2024.
my SLS has 6 boosters really 1 and 2 are active. the rest are dummy.

 

[Matias Saibene]

Here's another small progress:

The Crawler is now fixed. And I also fixed one of the scenarios where the Crawler was not working properly (it was upside down).

Mysteriously the entire Crawler code had disappeared so that was the error why it was not showing up in the scenario. Now it has its source code fixed and it works (as far as I know) as it should.

 

[Buck Rogers]

I ran my SLS in 2016 and 2024.
my SLS has 6 boosters really 1 and 2 are active. the rest are dummy.

Some of the boosters are effects?
In the Orb2024 screenshot defineately only one booster has ignited (G6)

 

[gattispilot]

yes
[BOOSTER_1]
N=1
MeshName=SLS_2016\SLSSRBNOCHECKERBOARD
Height=53.900
Diameter=3.710
EmptyMass=3.600
FuelMass=622727.300
Thrust=16363630.640

[BOOSTER_2]
N=1
Angle=0.000
Meshname=SLS_2016\SLSSRB_1NOCHECKERBOARD
Off=(-6.300,0.000,-0.300)
Height=53.900
Diameter=3.710
Thrust=16363630.640
EmptyMass=3.600
FuelMass=622727.300

[BOOSTER_3]
N=2
Angle=0.000
Meshname=SLS_2016\dummy
Off=(6.300,0.000,0.000)
Height=0.001
Diameter=0.001
Thrust=0.001

[BOOSTER_4]
N=3
Angle=90.000
Meshname=SLS_2016\dummy
Off=(2.200,0.000,25.000)
Height=0.001
Diameter=0.001
Thrust=0.001
EmptyMass=0.100
FuelMass=0.100

[BOOSTER_5]
N=1
Angle=0.000
Meshname=SLS_2016\dummy
Off=(0.000,0.000,0.000)
Height=0.001
Diameter=0.001
Thrust=0.001
EmptyMass=0.100

[BOOSTER_6]
N=1
Angle=0.000
Meshname=SLS_2016\dummy
Off=(0.000,0.000,0.000)
Height=0.001
Diameter=0.001
Thrust=0.001
EmptyMass=0.100