Project Multistage2015 - Development Thread

Star Voyager

Space Shuttle Refugee
Joined
Oct 25, 2008
Messages
1,975
Reaction score
32
Points
48
Config:

Code:
[MISC]
cog=0
GNC_DEBUG=1
FOCUS=1

[TEXTURE_LIST]
TEX_1=Nep-1\exhaust
TEX_2=Nep-1\Ncontrail1
TEX_3=Nep-1\Ncontrail2
TEX_4=Nep-1\Ncontrail3

[PARTICLESTREAM_1]
NAME=con1
SRCSIZE=1.4
SRCRATE=1500
V0=50.0
SRCSPREAD=0.05
LIFETIME=0.35
GROWTHRATE=-0.40
ATMSLOWDOWN=0.70
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=0
ATMSMAP=ATM_PLOG
AMIN=1e-4
AMAX=1
TEX=Nep-1\Ncontrail3

[PARTICLESTREAM_2]
NAME=con2
TEX=Nep-1\Ncontrail1
SRCSIZE=0.9
SRCRATE=80
V0=120.0
SRCSPREAD=0.2
LIFETIME=4
GROWTHRATE=14
ATMSLOWDOWN=1.0
LTYPE=DIFFUSE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=1
ATMSMAP=ATM_PLOG
AMIN=1e-4
AMAX=2

[PARTICLESTREAM_3]
NAME=con3
TEX=Nep-1\Ncontrail2
SRCSIZE=1.2
SRCRATE=600.0
V0=110.0
SRCSPREAD=0.05
LIFETIME=0.4
GROWTHRATE=18
ATMSLOWDOWN=0.0
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=0
ATMSMAP=ATM_PLOG
AMIN=0.7e-7
AMAX=1

[BOOSTER_1]
N=2
MeshName="nep-1\gem60single"
Height=13.15
Diameter=1.52
EmptyMass=3786
FuelMass=29697
Thrust=878692
angle=270
off=(0,2.6,8.1032)
eng_1=(0,0.248,-8.11)
eng_diameter=0.9
BurnTime=90.86
ENG_TEX=Nep-1\exhaust
ENG_PSTREAM1=con2
ENG_PSTREAM2=con3
Speed=(0,10,0)
Rot_Speed=(0,-0.25,0)

[BOOSTER_2]
N=1
MeshName="Nep-1\LES_60p"
Height=9
Diameter=4.08
EmptyMass=1555.2
FuelMass=43.2
Thrust=44496
Burndelay=208
BurnTime=210
angle=90.
SPEED=(5,3,30)
ROT_SPEED=3
off=(0.,0.,41.7)
eng_1=(0.9,0,-2.5)
eng_2=(-0.9,0,-2.5)
eng_3=(0,0.9,-2.5)
eng_4=(0,-0.9,-2.5)
eng_diameter=0

[STAGE_1]
Height=24
Diameter=3.5
EmptyMass=8546 ; 7311(fuel tank Antares 100 stage 1)+1235(NK-33 engine)
FuelMass=109000
Thrust=1682000
BurnTime=210.35
isp_sl=2912.56
off=(0,0,12.7)
eng_1=(0,0,-13.1)
eng_diameter=1.1
ENG_TEX=Nep-1\exhaust
ENG_PSTREAM1=con1
MeshName="Nep-1\Ts1"
SPEED=(0,0,-3)
ROT_SPEED=0

[STAGE_2]
Height=13
Diameter=3.5
EmptyMass=1718 ; 1088(fuel tank Falcon 9 1.1 stage 2)+630(Merlin 1C engine)
FuelMass=29200
Thrust=445000
BurnTime=220.07
off=(0.,0.,26.063)
MeshName="Nep-1\Ts2"
eng_1=(0,0,-4.637)
eng_diameter=0.95
ENG_TEX=Nep-1\exhaust
SPEED=(0,0,3)
ROT_SPEED=0

[FAIRING]
N=2
MeshName="Nep-1\Tf"
Diameter=3.5
Height=15
angle=0
off=(0.773,0,35.086)
Speed=(3,0,0)
emptymass=899 ; based on Atlas 401 extended fairing (4.2m x 4.2m x 13.1m - 2260kg)

[PAYLOAD_1]
off=(0.,0.,34.31)
MeshName="OK_SA"
name="OK_PAO_Active_servicemodule"
Module="spacecraft\spacecraft3"
Diameter=3
Height=2
Mass=7220.
speed=(0,0,1)
Render=1
Live=1

Guidance:
Code:
-10=orbit(200,200,51.6,1,70)
-5=engine(0,100,5)
0=disable(jettison)
0=engine(100,89,1)
1=engine(89,100,72)
73=engine(100,100,5)
92=jettison()
150=fairing(98)
200=jettison()
214=jettison()
215=engine(0,100,3)
218=engine(100,100,5)
420=engine(100,70,3)
 

Gargantua2024

The Desktop Orbinaut
Joined
Oct 14, 2016
Messages
1,043
Reaction score
1,250
Points
128
Location
San Jose Del Monte, Bulacan
Forgive me if this has already been brought up before (tried searching but to no avail): I have O2010 with M2015 for 2010 installed. The add-on I'm using was built with M2015 for O2016. The issue is when the main engine starts to throttle up, the rocket accelerates to around 1600 m/s in around 4 seconds until it reaches full throttle (when acceleration returns to normal). Is there a way to remedy this in the configuration, guidance, or scenario?

Hi, Star Voyager, this weird acceleration for some reason happens when Attachment Manager is activated, you need to disable it first before opening up any scenarios with MS2015 vessels :)


(In the bright side, sometimes I'd like to see it explode when Damage Module is activated) :) :)
 

Star Voyager

Space Shuttle Refugee
Joined
Oct 25, 2008
Messages
1,975
Reaction score
32
Points
48
Yep, this did the trick. I knew I saw something about Attachment Manager not being compatible, guess I should've read closer. Thank you for the tip!
 

jacquesmomo

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
611
Reaction score
449
Points
78
Location
FRANCE
Website
francophone.dansteph.com
Hi Fred :tiphat:

I think I have found a little bug in multistage2015 in the section [PAYLOAD_n] :
it seems that there is a problem with the coordinates "x" in the line "OFF=(x, y, z)".

For the value of x we can not put a negative value with decimal:
I think you'll understand easily with the following examples:

Suppose the values of "x" in this line:
2 => ok
2.0 => ok
2.1 => ok
-2 => ok
But :
-2.0 gives 0 for x
-2.1 gives 0 for x

For "y" there is no problem.

All this is not very serious, but I wanted to mention this to you.

Very friendly
Jacques
 

Interceptor

Well-known member
Joined
Mar 28, 2008
Messages
2,718
Reaction score
76
Points
63
Location
Michigan,Florida
Help,the MS-CAMERA feature in multistage2015 I can’t seem to get it working correctly it points to the rocket I am launching but the rocket launches toward the sky,and the camera does not follow it instead it just zooms in on the launchpad,is the MS-CAMERA suppose to follow it as it ascends into the sky?Thanks
 
Last edited:

N_Molson

Addon Developer
Addon Developer
Donator
Joined
Mar 5, 2010
Messages
9,256
Reaction score
3,231
Points
203
Location
Toulouse
Anyone tested this with Orbiter 2016 beta ? Many thanks.
 

CurlSnout

Well-known member
Joined
Feb 22, 2011
Messages
49
Reaction score
106
Points
48
Location
Pacific NW
I've been seeking guidance elsewhere in the 'General Questions & Help' sub-forum regarding a problem I have been experiencing with my Multistage2015 vessel. Rather than hashing through it all over again, I'm posting a link to that discussion - hoping someone well-versed with Multistage2015 might offer assistance in finding some kind of resolution.

The discussion is here:


Hi-Ho,

cs
 

jacquesmomo

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
611
Reaction score
449
Points
78
Location
FRANCE
Website
francophone.dansteph.com
I don't have time tonight, but I'll try to see this tomorrow.
your problem intrigues me : I don't understand what's going wrong.
and I don't like when I can not understand !!!! ?
 

fred18

Addon Developer
Addon Developer
Donator
Joined
Feb 2, 2012
Messages
1,666
Reaction score
100
Points
63
I've been seeking guidance elsewhere in the 'General Questions & Help' sub-forum regarding a problem I have been experiencing with my Multistage2015 vessel. Rather than hashing through it all over again, I'm posting a link to that discussion - hoping someone well-versed with Multistage2015 might offer assistance in finding some kind of resolution.

The discussion is here:


Hi-Ho,

cs
I will give it a look. It s really been a while since ms2015 so by memory is hard. I am pretty sure that the module does a check on the planet is landed onto to make an orbit simulation assuming the proper value of gravity acceleration. It would seem that moon is not included but that would be very strange because i remember to have thought to even use ms2015 to simulate a lem ascent... a tentative workaround that comes to my mind maybe just for testing purpose is to create a separate sol.cfg, name it sol_test.cfg in which you change the name of the moon to something like "moon1" and see if it works.
In the meantime i will dig into the code to see if there is a bug there and if there was a prevent to exclude it somehow.
 

CurlSnout

Well-known member
Joined
Feb 22, 2011
Messages
49
Reaction score
106
Points
48
Location
Pacific NW
OK. I tried your suggestion (created a separate sol.cfg [Sol_MoonTest.cfg], and renamed Moon to Moon1) but I still see the same behavior - scenarios that reference 'Moon1' fail to load.

I was really hoping to resolve this on my own, and not have to bother anyone else. Although I've been using Orbiter for years, I have only recently tried creating my own content. Have been working on the assumption that I'm missing the obvious.

In any case, thanks a million for all of your work building Multistage2015 and generously sharing with the rest of us. This has really opened the door for amateurs like me.

cs
 

fred18

Addon Developer
Addon Developer
Donator
Joined
Feb 2, 2012
Messages
1,666
Reaction score
100
Points
63
OK. I tried your suggestion (created a separate sol.cfg [Sol_MoonTest.cfg], and renamed Moon to Moon1) but I still see the same behavior - scenarios that reference 'Moon1' fail to load.

I was really hoping to resolve this on my own, and not have to bother anyone else. Although I've been using Orbiter for years, I have only recently tried creating my own content. Have been working on the assumption that I'm missing the obvious.

In any case, thanks a million for all of your work building Multistage2015 and generously sharing with the rest of us. This has really opened the door for amateurs like me.

cs
Could you post the entire log file of a crashed scenario?
 

CurlSnout

Well-known member
Joined
Feb 22, 2011
Messages
49
Reaction score
106
Points
48
Location
Pacific NW
Will do. First, here is a copy of my 'Bare-Bones' Moon-test scenario, which fails to load (but loads fine if I replace 'STATUS Landed Moon' with 'STATUS Landed Earth').


BEGIN_DESC
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 60305.6143359083
END_ENVIRONMENT

BEGIN_FOCUS
Ship S-IVB
END_FOCUS

BEGIN_CAMERA
TARGET S-IVB
MODE Extern
POS 4.00 180.00 80.00
TRACKMODE AbsoluteDirection
FOV 40.00
END_CAMERA

BEGIN_SHIPS
S-IVB:Multistage2015
STATUS Landed Moon
POS -54.00 14.00
HEADING 0.00
PRPLEVEL 0:1.000
CONFIG_FILE Config\S-IVB\S-IVB_CFG.ini
CONFIGURATION 0
END
END_SHIPS


And, here is the Orbiter.log file that is generated in the wake of such failure:

000003.558:
000003.558: **** Creating simulation session
000003.558: D3D9: [DirectX 9 Initialized]
D3D9: 3D-Adapter.............. : NVIDIA GeForce GTX 960
D3D9: MaxTextureWidth......... : 16384
D3D9: MaxTextureHeight........ : 16384
D3D9: MaxTextureRepeat........ : 8192
D3D9: VolTexAddressCaps....... : 0x3F
D3D9: NumSimultaneousRTs...... : 4
D3D9: VertexDeclCaps.......... : 0x30F
D3D9: MiscCaps................ : 0x2FCEF2
D3D9: XNA Math Support........ : Yes
D3D9: Vertex Texture.......... : Yes
D3D9: Separate AlphaBlend..... : Yes
D3D9: Shadow Mapping.......... : Yes
D3D9: D3DFMT_A16B16G16R16F.... : Yes
D3D9: D3DFMT_A32B32G32R32F.... : Yes
D3D9: D3DFMT_D32F_LOCKABLE.... : Yes
D3D9: D3DFMT_A2R10G10B10...... : Yes
D3D9: D3DFMT_L8............... : Yes
D3D9: D3DDTCAPS_DEC3N......... : No
D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
D3D9: Runs under WINE......... : No
D3D9: D3D9Build Date.......... : 210805
D3D9: Available Texture Memory : 4068 MB
000003.558: D3D9: [3DDevice Initialized]
000003.558: D3D9: [Loading Constellations]
000003.558: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module Multistage2015.dll .... [Build 170626, API 160828]
000000.000: Multistage Version: 170506
000000.000: Load State Started
000000.000: S-IVB: Config File: C:\Orbiter\Config\S-IVB\S-IVB_CFG.ini
000000.000: S-IVB: Number of stages in the ini file: 1
000000.000: S-IVB: Number of boosters group in the ini file: 0
000000.000: S-IVB: Number of Payloads in the ini file: 0
000000.000: S-IVB: Texture n.1 Loaded Contrail
000000.000: S-IVB: Texture n.2 Loaded Contrail3
000000.000: S-IVB: Texture n.3 Loaded Contrail1
000000.000: S-IVB: Texture n.4 Loaded Exhaust2
000000.000: S-IVB: Stage n. 1 Tank Added: 96714.965 kg
000000.000: S-IVB: Stage n. 1 Engines Exhaust Added--> number of engines: 1 , diameter: 2.100, position x: 0.000 y: 0.000 z: -12.800
000000.000: S-IVB: Stage n.1 Mesh Preloaded: S-IVB\S-IVB
000000.000: S-IVB: Stage n.1 Mesh Added Mesh: S-IVB\S-IVB @ x:0.000 y:0.000 z:0.000
000000.000: Load State Terminated
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Post Creation Started
000000.000: S-IVB: Gravity Turn Initial Pitch by user: 89.500 Calculated:70.050
000000.000: Creating Launchpad
000000.000: Module EmptyModule.dll ....... [Build 170626, API 160828]
000000.000: RESET PEG
 

fred18

Addon Developer
Addon Developer
Donator
Joined
Feb 2, 2012
Messages
1,666
Reaction score
100
Points
63
I think I might have found the issue. There is a builtin system in Multistage which performs a series of calculation to determine a reference launch profile for its guidance system. Within this calculation it also checks for the top of the atmosphere by querying the atmospheric module of the planet it is landed onto. And the moon does not have the atmosphere so it breaks down there. I gave a thought and the only other body of the solar system withouth the atmospheric model that came to my mind was mercury and guess what? same behaviour! so I think that is the issue. A brute workaround is to open the scenario with landed earth (or any other planet with atmosphere) and then use the scenario editor to move the rocket (the pad actually to which the rocket comes attached to) to the moon. This will work, but the orbit autopilot should not because all the basic calculation is made with references to the first planet at scenario opening. I found that if you use Mars or even better Titan as the opening scenario planet, and then move everything to the moon it actually might work because the data are not completely off in comparison. Of course this is just a rude way to make it kind of work.
I will now look if I can bug fix this quickly and post an updated dll, even though I haven't been coding for Orbiter in years so I am not sure if I can be successfull and in how much time. But at least we understood why this is happening.
 

fred18

Addon Developer
Addon Developer
Donator
Joined
Feb 2, 2012
Messages
1,666
Reaction score
100
Points
63
well, I think i might have overestimated the time needed. I simply added a check to the procedure and it worked on my end. Could you please use the attached dll instead of the default included package and check if it works? If you are not familiar with Orbiter folder structure you need to put the dll contained in the attached zip file into the orbiter_root/Modules/ folder. As simply as that. Let me know
 

Attachments

  • Multistage2015.zip
    111.9 KB · Views: 12

CurlSnout

Well-known member
Joined
Feb 22, 2011
Messages
49
Reaction score
106
Points
48
Location
Pacific NW
Success! Thank you, fred18, for your expert detective work! I spent a lot of time trying to figure out what I was doing wrong. Very happy that you were able to sort it out in speedy fashion.

08_orbiter.jpg

Peace,

cs

ps: For someone who is just starting to try and learn how to create for Orbiter, but is not savvy with Visual Basic and/or C++, is Multistage2015 not the way? Should I be looking at something like VesselBuilder instead? One of the things that I really like about Multistage2015 is that the documentation is so thorough - and makes it easy for an amateur like me.
 

fred18

Addon Developer
Addon Developer
Donator
Joined
Feb 2, 2012
Messages
1,666
Reaction score
100
Points
63
ps: For someone who is just starting to try and learn how to create for Orbiter, but is not savvy with Visual Basic and/or C++, is Multistage2015 not the way? Should I be looking at something like VesselBuilder instead? One of the things that I really like about Multistage2015 is that the documentation is so thorough - and makes it easy for an amateur like me.
Multistage is focused just on launchers/rockets. Vesselbuilder is definitely more comprehensive, theoretically you could even implement a multistage rocket even with vesselbuilder (even though it won't be so easy). So for reaching orbit with rockets MS is the way to go, but once you are in orbit and you want to create your own spaceship/satellite/station or whatever it is VesselBuilder is surely the best option for that kind of vessels. Also, the scheme with which VesselBuilder is built is replicating (or at least trying to) what C++ does behind the scenes, so it might come in handy the day you wish to start to play with c++ yourself. VB is scarcely documented (my fault, I was almost finished with the development and got caught in an immense new work project that cut me out from all the rest of coding) but, on the other hand, it is mostly self explanatory and is based on the c++ orbiter sdk scheme, so whatever is not in the VB documentation can be found in the official orbiter sdk documentation. And I'll be here to help, even though I am quite away from orbiter lately, I always try to help whoever is using my modules.
 
Top