Project Multistage2015 - Development Thread

[gattispilot]

Thanks. ! removed the booster and since only 1 thruster.

ARIES:Multistage2015
  STATUS Landed Earth
  POS -80.6758960 28.5227640
  HEADING 359.97
  ATTACHED 0:0,MS_LaunchPad_SATURN5
  AFCMODE 7
  PRPLEVEL 0:1.000000 
  NAVFREQ 0 0 0 0
  XPDR 0
  CONFIG_FILE Config\Multistage2015\ARIETALON.ini
  GUIDANCE_FILE Config\Multistage2015\Guidance\Saturn5_GNC.txt
  CONFIGURATION 0
  MET -10
  BATTERY 5024.907129
  GROWING_PARTICLES 
  STAGE_IGNITION_TIME 486.624532
  STAGE_STATE 1
  TELEMETRY_FILE Config\Multistage2015\Telemetry\SLS_EM1_Orion_GNC.
  ALT_STEPS 100.0,350.0,1400.0,35000.0
  PEG_PITCH_LIMIT 35.000
  PEG_MC_INTERVAL 0.100
  RAMP 
END

still ctd

000000.000: Module Multistage2015.dll .... [Build 161006, API 160828]
000000.000: Multistage Version: 161006
000000.000: Load State Started
000000.000: ARIES: Guidance File present: Config\Multistage2015\Guidance\Saturn5_GNC.txt
000000.000: ARIES: Orbit Call Found! Targets: Apogee:185000.0 Perigee:185000.0 Inclination:0.0 Mode:1.0 GT initial Pitch: 0.0 Abside:185000.0
000000.000: ARIES: Config File: C:\Orbiter2016\Config\Multistage2015\ARIETALON.ini
000000.000: ARIES: Number of stages in the ini file: 1
000000.000: ARIES: Number of boosters group in the ini file: 0
000000.000: ARIES: Number of Payloads in the ini file: 0
000000.000: ARIES: Texture n.1 Loaded Exhaust_atsme
000000.000: ARIES: Texture n.2 Loaded SLS_2016\SSME_Exhaust
000000.000: ARIES: Stage n. 1 Tank Added: 646735.176 kg
000000.000: ARIES: Stage n.1 Engine Exhaust Stream Added:  to engine n.1
000000.000: ARIES: Stage n.1 Engine Exhaust Stream Added:  to engine n.1
000000.000: ARIES: Stage n. 1 Engines Exhaust Added--> number of engines: 1 , diameter: 2.400, position x: 0.000 y: 0.000 z: -28.900
000000.000: ARIES: Stage n.1 Mesh Preloaded: constellation\aresi_s1
000000.000: ARIES: Stage n.1 Mesh Added Mesh: constellation\aresi_s1 @ x:-0.000 y:0.000 z:0.000
000000.000: Load State Terminated
000000.000: Module EmptyModule.dll ....... [Build 161006, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: Post Creation Started
000000.000: ARIES: Gravity Turn Initial Pitch by user: 0.000 Calculated:89.000

 

[fred18]

can you please put just this:

ARIES:Multistage2015
  STATUS Landed Earth
  POS -80.6758960 28.5227640
  HEADING 359.97
  AFCMODE 7
  PRPLEVEL 0:1.000000 
  NAVFREQ 0 0 0 0
  XPDR 0
  CONFIG_FILE Config\Multistage2015\ARIETALON.ini
  GUIDANCE_FILE Config\Multistage2015\Guidance\Saturn5_GNC.txt
  CONFIGURATION 0
  MET -10
  GROWING_PARTICLES 
END

 

[gattispilot]

Thanks. Launched

---------- Post added 05-06-17 at 07:38 AM ---------- Previous post was 05-05-17 at 05:46 PM ----------

Not sure if I have the .ini correct. Stage 1 launchs slowly but never gets orbit.

[MISC]
cog=25.000
GNC_Debug=0
Telemetry=0
Focus=1
Thrust_real_pos=0
Vertical_Angle=0.000

[TEXTURE_LIST]
TEX_1=Exhaust_atsme
TEX_2=SLS_2016\SSME_Exhaust

[STAGE_1]
Height=63.720
Diameter=8.400
EmptyMass=111735.1763
FuelMass=646735.1763
Thrust=7440000.375
BurnTime=476.000
off=(-0.000,0.000,4.700)
MeshName=constellation\aresi_s1
eng_1=(0,0,-28.9)
eng_diameter=2.400
PITCHTHRUST=14193633.100 
YAWTHRUST=14193633.100 
speed=(0.000,0.000,-10.000)
ENG_PSTREAM1=
battery=1.500
Reignitable=1
Eng_tex=SLS_2016\SSME_Exhaust
Eng_pstream2=
Eng_dir=(0.000,0.000,1.000)
Module=Stage
Rot_speed=(0.000,0.000,0.000)

and the guidance;

Multistage 2015 Automatically Generated Guidance File
Vehicle: ARIES
-10=Orbit(185,185)
-3=engine(0,100,3.0)

SCN:
BEGIN_SHIPS
ARIES:Multistage2015
STATUS Landed Earth
POS -80.6758960 28.5227640
HEADING 359.97
AFCMODE 7
PRPLEVEL 0:1.000000
NAVFREQ 0 0 0 0
XPDR 0
CONFIG_FILE Config\Multistage2015\ARIETALON2.ini
GUIDANCE_FILE Config\Multistage2015\Guidance\ARIES_GNC.txt
CONFIGURATION 0
MET -10
GROWING_PARTICLES
END
MS_LaunchPad_SATURN5:EmptyModule
STATUS Landed Earth
POS -80.6758960 28.5227640
HEADING 359.97
AFCMODE 7
NAVFREQ 0 0
END
END_SHIPS

 

[fred18]

Maybe not enough dv. I don't know, it's a matter of rocket design, not of the multistage module

 

[Marg]

Thanks to Fred18, sound files work like a charm. I just recorded STS-7 launch (on youtube) TV sounds and commentary through Audacity, saved as STS-7_launch.wav, put in guidance file - and voila! Unique sound and commentary for each shuttle flight is possible now. :thumbup:
Even more - as OrbiteSound did not produce sound effect, if not focused on vehicle (shortcoming for OrbiterSound), here it works very well even in this case (controlling and viewing from MS_Camera, for example)! Amazing...

 

[fred18]

Updated both versions on OH:

- Added sound support (for the playsound command in the guidance file) independent from Orbiter Sound
- Raised hangar, crawler and pad a couple of inches from the ground as requested by interceptor
- added stage.dll that was missing
- documentation update

2010P1 Version:
[ame="http://www.orbithangar.com/searchid.php?ID=6838"]http://www.orbithangar.com/searchid.php?ID=6838[/ame]

2016 Version:
[ame="http://www.orbithangar.com/searchid.php?ID=7010"]http://www.orbithangar.com/searchid.php?ID=7010[/ame]



Fred

 

[boogabooga]

Can't believe it's been almost two years since first betas.

Perhaps call this Multistage2017?

 

[fred18]

Can't believe it's been almost two years since first betas.

Definitely! Seems yesterday that this project started...

Perhaps call this Multistage2017?

I gave it a thought but it could become a mess to rename everything... If I find a smart and easy solution for this I'll apply to the future releases with major changes.

There is actually one major feature that keeps going around in my mind and I keep printing the code to start to plan the relevant modifications but then it's always too messy and I leave it there... which is to have separate vehicles docked as stages... now in orbiter 2016 is possible, it could be really nice... would it be nicer? I really can't figure out

---------- Post added 8th May 2017 at 21:22 ---------- Previous post was 7th May 2017 at 22:27 ----------

speaking of major changes, I'd like to do a small poll:

The DMD (Developer Mode Dialog) was a huge amount of work, and if major changes to the module happens that should be changed as well, but for me now that's a show stopper for making changes since it's massively time consuming.

So I'm wondering how many users actually use actively the DMD and how many simply edit the ini file, even using the in sim editor included in the DMD but not the item by item window.

Can I have a feedback from you guys on this?

thanks in advance, Fred

 

[Interceptor]

Hi fred18,thanks for the sound fixes,sound works great now,but the Crawler,MSpad,and hangar are still flashing,using the default orbiter 2010 engine,but doesn't when using the d3d9 engine.You could try lifting the cog up on them a little more,or you could add a line for a config for all three,and then you could manually adjust the cog on all three,but thats up to you,you already have put a lot of work into this,but great job on the update,and,BTW,I do use the DMD mode more actively then just setting the config.

 

[1987VCRProductions]

If it doesn't already exist and I just don't know about it, you should add a way on rockets with SRBs where you can have the boosters ignite on the ground and have the core ignite at altitude like on the Titan III or Titan IV. Have a line in the guidance file like "BOOSTER()" to fire the boosters on the ground and then the standard engine throttle command with the proper timestamp can ignite the core at altitude.

With the BOOSTER() line, you can add in the booster numbers in the parentheses that you want to ignite (for example on a 4 booster rocket if you only wanted 3 out of four boosters to ignite). Say that only boosters 1, 3, and 4 ignite, so the line would be BOOSTER(1,3,4).

It was just a thought.

 

[fred18]

With the BOOSTER() line, you can add in the booster numbers in the parentheses that you want to ignite (for example on a 4 booster rocket if you only wanted 3 out of four boosters to ignite). Say that only boosters 1, 3, and 4 ignite, so the line would be BOOSTER(1,3,4).

It was just a thought.

That could be useful. Now there is only a workaround for this: ignite main engines for an instant and then turn them off, boosters will ignite and main engines will be off then. But that could be a useful command to add.



In the meantime I'm starting to think about the multiple vessels docked as multistage rocket seriously. It's actually the most realistic thing possible... but it would mean to rewrite the whole thing from ground up... I don't know if I'll have the time to really do it....

 

[boogabooga]

I say don't bother.

I think it is a huge advantage in multistage that the launch vehicle counts as one vessel through the entire launch. When the last stage is a different actual vessel as the first stage, MFDs, such as IMFD reset, or at least don't preserve your info. This happened with Velcro and it was kind of a pain to have to re-enter your plan.

 

[gattispilot]

I can this this to work. But my tester can't it looks like the ini are in the correct spot.

000000.000: Finished initialising world
000000.000: Module Multistage2015.dll .... [Build 151027, API 100830]
000000.000: Load State Started
000000.000: ARIES: Guidance File present: Config\Multistage2015\Guidance\ARIES_GNC.txt
000000.000: ARIES: Orbit Call Found! Targets: Apogee:185000.0 Perigee:185000.0 Inclination:0.0 Mode:1.0 GT initial Pitch: 0.0 Abside:185000.0
000000.000: ARIES: Config File: C:\Users\Barry\Desktop\2016\Config\Multistage2015\ARES2.ini
000000.000: ARIES: Number of stages in the ini file: 2
000000.000: ARIES: Number of boosters group in the ini file: 0
000000.000: ARIES: Number of Payloads in the ini file: 0
000000.000: ARIES: Texture n.1 Loaded Exhaust_atsme
000000.000: ARIES: Texture n.2 Loaded SLS_2016\SSME_Exhaust
000000.000: ARIES: Stage n. 2 Tank Added: 130000.000 kg
000000.000: ARIES: Stage n. 1 Tank Added: 646735.176 kg
000000.000: ARIES: Stage n. 1 Engines Exhaust Added--> number of engines: 1 , diameter: 2.400, position x: 0.000 y: 0.000 z: -28.900
000000.000: ARIES: Stage n.1 Mesh Preloaded: constellation\aresi_s1
000000.000: ARIES: Stage n.1 Mesh Added Mesh: constellation\aresi_s1 @ x:-0.000 y:0.000 z:0.000
000000.000: ARIES: Stage n.2 Mesh Preloaded: constellation\aresi_s2
000000.000: ARIES: Stage n.2 Mesh Added Mesh: constellation\aresi_s2 @ x:-0.000 y:0.000 z:36.300
000000.000: Load State Terminated
000000.000: Module EmptyModule.dll ....... [Build 161006, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: Post Creation Started
000000.000: status:0 hdg:0.000 lng:0.000 lat:0.000
000000.000: ARIES: Gravity Turn Initial Pitch by user: 0.000 Calculated:77.650
000000.000: RESET PEG
000000.000: ARIES: Planet Reference Pressure = 101325.0 Pa  Atmosphere Altitude Limit:2500.0 km
000000.000: Post Creation Terminated
000000.000: Finished initialising panels

but it ctd.

BEGIN_MFD Right
  TYPE User
  MODE Multistage2015_MFD
END_MFD

BEGIN_SHIPS
ARIES:Multistage2015
  STATUS Landed Earth
  POS -80.6758960 28.5227640
  HEADING 359.97
  AFCMODE 7
  PRPLEVEL 0:1.000000 
  NAVFREQ 0 0 0 0
  XPDR 0
  CONFIG_FILE Config\Multistage2015\ARES2.ini
  GUIDANCE_FILE Config\Multistage2015\Guidance\ARIES_GNC.txt
  CONFIGURATION 0
  MET -10
  GROWING_PARTICLES 
END
MS_LaunchPad_SATURN5:EmptyModule
  STATUS Landed Earth
  POS -80.6758960 28.5227640
  HEADING 359.97
  AFCMODE 7
  NAVFREQ 0 0
END
END_SHIPS

ini

[MISC]
cog=25.000
GNC_Debug=0
Telemetry=0
Focus=1
Thrust_real_pos=0
Vertical_Angle=0.000

[TEXTURE_LIST]
TEX_1=Exhaust_atsme
TEX_2=SLS_2016\SSME_Exhaust

[STAGE_1]
Height=55
Diameter=8.400
EmptyMass=111735.1763
FuelMass=646735.1763
Thrust=15794834.2759
BurnTime=476.000
off=(-0.000,0.000,4.700)
MeshName=constellation\aresi_s1
eng_1=(0,0,-28.9)
eng_diameter=2.400
PITCHTHRUST=14193633.100 
YAWTHRUST=14193633.100 
speed=(0.000,0.000,-10.000)
ENG_PSTREAM1=
battery=1.500
Reignitable=1
Eng_tex=SLS_2016\SSME_Exhaust
Eng_pstream2=
Eng_dir=(0.000,0.000,1.000)
Module=Stage
Rot_speed=(0.000,0.000,0.000)

[STAGE_2]
Height=25
Diameter=6
EmptyMass=13350
FuelMass=130000
Thrust=1217700.6672
BurnTime=476.000
off=(-0.000,0.000,41)
MeshName=constellation\aresi_s2
eng_1=(0,0,-12.6)
eng_diameter=2.400
PITCHTHRUST=14193633.100 
YAWTHRUST=14193633.100 
speed=(0.000,0.000,-10.000)
ENG_PSTREAM1=
battery=1.500
Reignitable=1
Eng_tex=SLS_2016\SSME_Exhaust
Eng_pstream2=
Eng_dir=(0.000,0.000,1.000)
Module=Stage
Rot_speed=(0.000,0.000,0.000)

 

[fred18]

I say don't bother.

I think it is a huge advantage in multistage that the launch vehicle counts as one vessel through the entire launch. When the last stage is a different actual vessel as the first stage, MFDs, such as IMFD reset, or at least don't preserve your info. This happened with Velcro and it was kind of a pain to have to re-enter your plan.

The idea was that the main vessel always is the last stage of the rocket, you'll always fly in the last stage, it's the rocket computer that fires the other engines (maybe passes on even the key presses? don't know). Do you think that this way would solve the MFD reset issue you refer to?

I'm still gathering ideas, even though from some tests seems like docked landed vessels are quite messy to handle, so it's just for brain storming a bit.



@gattis: first of all why there is the pad in the scn? take that out. Second: if it works for you and not for him (is that correct? your message was not clear) then it's not a multistage issue... maybe you did not pass the right files to him, or I don't know

 

[boogabooga]

Well, what is the advantage of docked vessels?
It might be nice to have payloads docked together. Perhaps for live vessel payloads, you undock rather than detach?

 

[jacquesmomo]

In the meantime I'm starting to think about the multiple vessels docked as multistage rocket seriously. It's actually the most realistic thing possible...

A very good idea... :thumbup:

And now, just to show you my new ELA-2 crawler (with your help :tiphat: ) : the Ariane 4 can stand on the crawler and It is fully functional !

 

[fred18]

Well, what is the advantage of docked vessels?

Well for now there is no immediate advantage, the scope would be to have the very same functionality of current multistage2015.

What I like about the idea is that anyway:
1) it would be much more realistic in this way, since it will be exactly as it happens in real life.
2) point 1 means also from programming point of view, which is probably fun only for my side, but still it's a point :lol:
3) it would be much easier to code: once the rocket is created it won't be needed to update it, to save or restore it or whatever it is, orbiter will take care about it automatically since each vessel will live its own life
4) point 3 means also an easiest portability for the future. Updates and changes may be implemented easier than now which is a huge code, bigger part of it consisting in building and setting the rocket
5) I'm also thinking about a "kerbalisation" when you can load your stages into the sim, assemble your rocket and fly. Not that I like it much, I don't even have KSP installed, but how much this is liked around?
6) last but not least: the actual way of detaching stages which basically delete the original mesh and spawns a stage module in its place still gives to me a sense of miscontinuity, even graphically. I don't know if that's like knowing where the magic trick is, so from then on you always see it even if the magician do it perfectly....

There are many downsides anyway I know. Also beacuse Docking is not meant to be used for this kind of activities. But it's also a bit of fun to test it. My target for now is to just create the SLS example with this new method and launch it with the orbit program, put Ms2015 SLS next to this and see if there is an advantage, if it's more beautiful, if it's more realistic, or if it's way worse.

It might be nice to have payloads docked together. Perhaps for live vessel payloads, you undock rather than detach?

yes. My idea is to simulate the jettison by deleting the docking port of the rocket on J press by the user.

 

[jacquesmomo]

5) I'm also thinking about a "kerbalisation" when you can load your stages into the sim, assemble your rocket and fly. Not that I like it much, I don't even have KSP installed, but how much this is liked around?

:woohoo:
That was exactly what I was thinking with a previous post I wrote here !
And about my wish to integrate in the "guidance_file"a command like "= Undock (123)" :thumbup:

 

[boogabooga]

Okay, after about two years I've upgraded my multistage 2015 to the latest version. Some thoughts/bug reports:

First of all, since apparently the SLS test scenario is my responsibility , I should say that the boosters are facing the wrong way. In the SLS ini, it should be angle =180 instead of angle = 3.14. IIRC, last fall the code was changed from radians to degrees but it appears that the ini file was not changed to match.

It seems that for some reason, since Oct. 2015, the default fairing jettison velocity has changed from +3X to -3Y. Not necessarily a bug, but it's something to be aware of since my old scenarios now look weird.

Orbiter 2010 only:
The camera vessel is not working properly for me. (Default SLS test scenario.) I can't see any terrain or vessels through the camera unless I pause the scenario. Only the horizon. Also, many CTDs when I switch to camera vessel. Everything works fine in Orbiter 2016.

Orbiter 2016 only:
It seems that the "GLimit" guidance command is only being respected if the complex flight is on and not when it is off. Or perhaps vice versa (memory fuzzy). I might test this some more and get back to you. But I did notice an issue in my Atlas V.

 

[fred18]

First of all, since apparently the SLS test scenario is my responsibility , I should say that the boosters are facing the wrong way. In the SLS ini, it should be angle =180 instead of angle = 3.14. IIRC, last fall the code was changed from radians to degrees but it appears that the ini file was not changed to match.

It seems that for some reason, since Oct. 2015, the default fairing jettison velocity has changed from +3X to -3Y. Not necessarily a bug, but it's something to be aware of since my old scenarios now look weird.

oh :facepalm:, I have to say that I had been using the SLS example also for testing purpose for the DMD and all the other stuff, so it's easy to guess that I messed up something at the time and never got back to fix it. I'll take what you provided at the time again and I'll fix it!

Orbiter 2010 only:
The camera vessel is not working properly for me. (Default SLS test scenario.) I can't see any terrain or vessels through the camera unless I pause the scenario. Only the horizon. Also, many CTDs when I switch to camera vessel. Everything works fine in Orbiter 2016.

seems like I put the wrong dll in the package or I compiled the MS_Camera vessel using wrong properties. I have to check this soon!

Orbiter 2016 only:
It seems that the "GLimit" guidance command is only being respected if the complex flight is on and not when it is off. Or perhaps vice versa (memory fuzzy). I might test this some more and get back to you. But I did notice an issue in my Atlas V.

That's interesting, I can't remember a relation among this two options. I'll go to check the code there.

Thanks for beta testing and bug report!! it's fundamental to have a working addon for everybody!! :tiphat: