Update Multistage2026 - Development thread

[jacquesmomo]

Hi Matias

Here are the results of my initial tests:

• I installed the new MultiStage 2026 modules and used your two patch files, A64.ini and A64.cfg, which I renamed to A64_TEST.ini and A64_TEST.cfg.
• I used a copy of the Ariane 6.4 (Generic).scn scenario, just modifying A64 to A64_TEST.

Sorry for that, but I haven't had time to test the boosters yet; currently, so the rocket only has [STAGES_n] and not yey [BOOSTER_n]

Here are my observations:

1) - At launch, pressing the P key displays the MET (at the bottom left of the screen), but it starts at "0" instead of -20.
- And .... this guidance file doesn't works : the rocket remains stationary (no sounds, no commands from the guidance file)

I'm just reminding you of the beginning of my guidance file:

-20=orbit(300,300,50)
-19=PlaySound(Sounds\Multistage\Communs\Sound_Bip.wav)
-16=PlaySound(Sounds\Multistage\A6_262\05_Decompte_final.wav)
-11=PlaySound(Sounds\Multistage\A6_262\06_CountDown.wav)
-3.5=engine(0,20,2)
-1=engine(20,80,1)
0=engine(80,100,1)
25=PlaySound(Sounds\Multistage\A6_262\07_Nominale.wav)

etc...

2) There is no visible EXAUST texture for the engines of any stage
(the [PARTICLESTREAM_n] are working correctly)

3) The position of the onboard payload is incorrect (I haven't changed the XYZ values in the ini file).



4) Every time I exit Orbiter during flight then restart it with the "(Current state).scn", I got a CTD.



I need to continue my tests (for the boosters), but this is what I've observed so far.

 

[Matias Saibene]

Hi Matias

Here are the results of my initial tests:

• I installed the new MultiStage 2026 modules and used your two patch files, A64.ini and A64.cfg, which I renamed to A64_TEST.ini and A64_TEST.cfg.
• I used a copy of the Ariane 6.4 (Generic).scn scenario, just modifying A64 to A64_TEST.

Sorry for that, but I haven't had time to test the boosters yet; currently, so the rocket only has [STAGES_n] and not yey [BOOSTER_n]

Here are my observations:

1) - At launch, pressing the P key displays the MET (at the bottom left of the screen), but it starts at "0" instead of -20.
- And .... this guidance file doesn't works : the rocket remains stationary (no sounds, no commands from the guidance file)


etc...

2) There is no visible EXAUST texture for the engines of any stage
(the [PARTICLESTREAM_n] are working correctly)

3) The position of the onboard payload is incorrect (I haven't changed the XYZ values in the ini file).

View attachment 46572

4) Every time I exit Orbiter during flight then restart it with the "(Current state).scn", I got a CTD.

View attachment 46573

I need to continue my tests (for the boosters), but this is what I've observed so far.

Thank you, thank you very much. That information is valuable to me.

I need to study and fix the Guidance, and I also need to implement the sound playback issue... I forgot to mention that it's completely disabled because it was causing code to run that invoked OrbiterSound. But I'll work on implementing XRSound at the end, when everything is up and running.

From what I can see, there is an error in the function responsible for the payloads. Specifically the offset. There is also an error in the code responsible for adding the exhausts.

The CTD happens because Orbiter tries to save a variable but is unable to and crashes. I need to find out which variable it is.

I'm going to make changes today and I'll post them here in this thread with the results. Yesterday I forgot to update the GitHub repository.

 

[Matias Saibene]

I am running the ms2015 in Orbiter 2016 and then the MS2026 in 2024.
On the SLS launch I get a CTD with this in the log:
000023.697: Post Creation Started
000023.697: SLS: Gravity Turn Initial Pitch by user: 89.500 Calculated:83.350
000023.697: Creating Launchpad

the crawler one seems to work. I haven't figured out how to attach the rocket in ms2015 and ms2026

My apologies, I hadn't seen your post!

So @gattispilot and @jacquesmomo could you try this new test release?

I think I've fixed the payload issue...

 

[gattispilot]

I still get a CTD on the SLS launch

000030.333: Finished initialising status
000030.333: Finished initialising camera
000030.386: Finished setting up render state
000030.386: D3D9: [Scene Initialized]
000030.386: Post Creation Started
000030.387: SLS: Gravity Turn Initial Pitch by user: 89.500 Calculated:83.350
000030.387: Creating Launchpad

scn
BEGIN_SHIPS
SLS:Multistage2026
STATUS Landed Earth
POS -80.6208600 28.6271940
HEADING 0.00
FUEL 1.000
CONFIG_FILE Config\Multistage2026\SLS.ini
GUIDANCE_FILE Config\Multistage2026\Guidance\SLS_57302.65_GNC.txt
TELEMETRY_FILE Config\Multistage2026\Telemetry\SLS_57310.61_TLM.txt
CONFIGURATION 0
CURRENT_BOOSTER 1
CURRENT_STAGE 1
CURRENT_PAYLOAD 1
FAIRING 1
COMPLEX
FAILURE_PROB 0
GROWING_PARTICLES
CAMERA
END

 

[jacquesmomo]

I think I've fixed the payload issue...

Yes, the payload issue is now fixed....

 

[Matias Saibene]

I still get a CTD on the SLS launch

000030.333: Finished initialising status
000030.333: Finished initialising camera
000030.386: Finished setting up render state
000030.386: D3D9: [Scene Initialized]
000030.386: Post Creation Started
000030.387: SLS: Gravity Turn Initial Pitch by user: 89.500 Calculated:83.350
000030.387: Creating Launchpad

scn
BEGIN_SHIPS
SLS:Multistage2026
STATUS Landed Earth
POS -80.6208600 28.6271940
HEADING 0.00
FUEL 1.000
CONFIG_FILE Config\Multistage2026\SLS.ini
GUIDANCE_FILE Config\Multistage2026\Guidance\SLS_57302.65_GNC.txt
TELEMETRY_FILE Config\Multistage2026\Telemetry\SLS_57310.61_TLM.txt
CONFIGURATION 0
CURRENT_BOOSTER 1
CURRENT_STAGE 1
CURRENT_PAYLOAD 1
FAIRING 1
[SIZE=6] COMPLEX[/SIZE]
FAILURE_PROB 0
GROWING_PARTICLES
CAMERA
END

Oh, I forgot to mention that Complex Flight isn't working again; I probably have memory corruption in some variable of that function.
Try removing the COMPLEX line from the scenario.

 

[gattispilot]

Thanks. I removed it and and still ctd.

 

[Matias Saibene]

Thanks. I removed it and and still ctd.

Interestingly, the Ariane 6 works better than the SLS, which really baffles me.

 

[gattispilot]

It seems the launchpad is missing. In the SLS crawler fixed scn the launchpad is missing. Not sure if that is part of the Complex? Did not see it in the docs for 2015

 

[Matias Saibene]

It seems the launchpad is missing. In the SLS crawler fixed scn the launchpad is missing. Not sure if that is part of the Complex? Did not see it in the docs for 2015

Thanks for letting me know, I'd forgotten that detail. Apparently, I'm still having problems with the parser.

EDIT: I just updated the GitHub repository: https://github.com/MatiasSaibene/Multistage2026_for_OpenOrbiter

 

[Buck Rogers]

Did a quick test with the N1, CTD on loading, seems to die right after booster initilisation. Log attatched.

It seems the launchpad is missing

This might be the cause?

 

[Matias Saibene]

Did a quick test with the N1, CTD on loading, seems to die right after booster initilisation. Log attatched.

This might be the cause?

I can't know yet. By the way, can I try N1? If so, I'd open it with the VS debugger.

And also:

000000.416: ============================ ERROR: ===========================
000000.416: Failed loading module Modules\Plugin\HUDDrawer.dll (code 126)
000000.416: [Orbiter::LoadModule | D:\a\orbiter\orbiter\Src\Orbiter\Orbiter.cpp | 643]
000000.416: ===============================================================

 

[Buck Rogers]

I can't know yet. By the way, can I try N1? If so, I'd open it with the VS debugger.

Yes, https://www.orbiter-forum.com/threads/n1-lunar.42242/post-630700
It's the MS vessel I'm currently most familiar with, will also test the SLS.

And also:
000000.416: ============================ ERROR: =========================== 000000.416: Failed loading module Modules\Plugin\HUDDrawer.dll (code 126) 000000.416: [Orbiter::LoadModule | D:\a\orbiter\orbiter\Src\Orbiter\Orbiter.cpp | 643] 000000.416: ===============================================================

Don't worry about that, some other things don't work in O24 too! Has nothing to do with MS.

 

[Matias Saibene]

Yes, https://www.orbiter-forum.com/threads/n1-lunar.42242/post-630700
It's the MS vessel I'm currently most familiar with, will also test the SLS.

Don't worry about that, some other things don't work in O24 too! Has nothing to do with MS.

I'll try it and let you know.

By the way, @gattispilot and @Buck Rogers : please tell me what operating systems you're using. Remember that I'm updating Multistage2026 for Orbiter 2024 on Windows 11.

 

[Buck Rogers]

Win10

 

[gattispilot]

WIN 10

 

[Matias Saibene]

Win10

WIN 10

Thanks, there shouldn't be any compatibility issues as far as I know.
I'm currently testing N1 with the VS debugger enabled.

 

[jacquesmomo]

By the way, @gattispilot and @Buck Rogers : please tell me what operating systems you're using. Remember that I'm updating Multistage2026 for Orbiter 2024 on Windows 11.

Windows 7

 

[Matias Saibene]

Here's an update on today's progress.

The Multistage codebase is highly interdependent, with many internal functions interconnected, making it very difficult to manage multiple bugs. While Multistage2026 retains 90% of the Multistage2015 codebase, adapting it, even with many fundamental changes, doesn't seem sufficient.

I'm going to prune the code even further, reducing it to its bare minimum of functionality. I don't know why I didn't do this sooner, but it is what it is.

Thank you very much for your patience.

 

[jacquesmomo]

Thank you very much for your patience.

No problem, take your time : it's already good that you're taking care of it...