- Oct 17, 2007
- Reaction score
- Dallas, TX
Can you post the cfg and guidance
[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
-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)
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?
Just tried it and when I pull up the MFD I get a CTD.Anyone tested this with Orbiter 2016 beta ? Many thanks.
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.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:
Scenario - Why does my new Multistage2015 vessel crash LUNAR scenarios?Hello Citizens, I have created a vessel using Multistage2015 and have been flying it around in Orbiter 2016. Scenarios involving launch from and/or orbit around Earth and Mars work fine. Any (and ALL) scenarios involving the (Earth's) MOON will not work - Orbiter acts as if it is loading the...www.orbiter-forum.com
Could you post the entire log file of a crashed scenario?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.
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.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.