Project Multistage2015 - Development Thread

fred18 said:
Well the command was thought for the most common use: keeping the G forces at a set value at the end of first stage when G forces can reach the maximum. After first stage is jettisoned the acceleration gets much lower so even if the check i performed, it is not seen by the user.

I never inserted a time parameter in order not to complicate things too much. Please consider that a large number of parameters I created were not even present in the original multistage, I think you are really pushing the limit of all the options available, of course I like it :thumbup:

Before changing this I have one question: how does it work in reality? do they have a check on acceleration and throttle down to keep the desired value or do they have a pre programmed throttle-down and throttle up program? If the latter then the command "engine" alone would be more correct.
Click to expand...
Due to the flat line in the G graph, and the curvy line in the throttle graph, I'd say it is the throttle responding to the G's, not the other way around.

Though I've already considered it as a work around.

A way to avoid the issue is to have an "engine" call first and a g-limit call later. That should work.
Click to expand...
I'll give that a try, but it seems like it shouldn't, I'll ETA the result.

ETA:
As I expected, it still didn't work, the engine throttles up, but goes right back down for the 2 G's The higher Glimit is ignored no matter what. I guess I'll try to match the throttle graph with the engine command for now.
 
Last edited:
I'm having an issue based around adding exhaust plumes to strap-on boosters. I've been experimenting with Buran 4.8 by upgrading it to use Multistage2015 and updating the exhaust plumes.

tumblr_o3asn4mmN21rpuj2so3_1280.png


Here I'm using the default Exhaust2 texture and loru's SRB replacement texture for the flames coming from the LOX and Kerosene burning boosters.

tumblr_o3asn4mmN21rpuj2so1_1280.png


I'm using the default shock diamonds typical of LOX and liquid Hydrogen burning engines for the Energia Core Stage.

To get to the point, I've been adding the exhaust plumes to the LRBs one by one, eventually getting this much done:

tumblr_o3asn4mmN21rpuj2so2_1280.png


I can get three plumes on the boosters but, when I try to add a fourth, I get a CTD. This is an issue that I first discovered when adding the exhaust plumes to my Saturn IB. I found that the issue there was that I had 8 plumes overlying each other at (0,0,0) before placing them at their proper positions in each engine nozzle. Here with the Energia, I have no idea what's causing the CTD.

Here's the text of the Orbiter log file after a CTD:

Code: 
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.79976e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) Graphics Media Accelerator HD)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module GPCMFD.dll ............ [Build 111222, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module LaunchMFD.dll ......... [Build 130413, API 100830]
Module B3OP.dll .............. [Build 101129, API 100830]
Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module TransX.dll ............ [Build 150909, API 100830]
Module ReFuelMFD.dll ......... [Build ******, API 060425]
Module Load.dll .............. [Build 110920, API 100830]
Module PylonMFD.dll .......... [Build ******, API 060425]
Module GS2.dll ............... [Build 131201, API 100830]
Module BGPCMFD.dll ........... [Build 120101, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1366 x 768 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module Multistage2015.dll .... [Build 151027, API 100830]
Load State Started
Energia: Guidance File present: Config\Energia\Energia_guidance_1.txt
Energia: Orbit Call Found! Targets: Apogee:120000.0 Perigee:20000.0 Inclination:51.6 Mode:-1.0 GT initial Pitch: 0.0 Abside:107700.0
Energia: Config File: C:\Users\User\Desktop\Desktop Files\Orbiter 2010 P1\Config\Energia\Energia.ini
Energia: Number of stages in the ini file: 1
Energia: Number of boosters group in the ini file: 4
Energia: Number of Payloads in the ini file: 1
Energia: Texture n.1 Loaded Contrail2
Energia: Texture n.2 Loaded Exhaust_atsme
Energia: Texture n.3 Loaded Exhaust2
Energia: booster n. 1 Tank Added: 320000.000 kg
Energia: booster n. 2 Tank Added: 320000.000 kg
Energia: booster n. 3 Tank Added: 320000.000 kg
Energia: booster n. 4 Tank Added: 320000.000 kg
Energia: Stage n. 1 Tank Added: 820000.000 kg
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: 1.694 y: 1.954 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: -1.614 y: 1.954 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: -1.614 y: -1.408 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: 1.694 y: -1.408 z: -31.600
Energia: Booster Engines Exhaust Added--> Booster Group: 1 number of engines: 3 , diameter: 0.600, position x: 4.769 y: -4.675 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 1 number of engines: 3 , diameter: 0.600, position x: 3.519 y: -3.825 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 1 number of engines: 3 , diameter: 0.600, position x: 5.619 y: -3.375 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 0 , diameter: 0.600, position x: 4.692 y: 3.606 z: -31.000
Energia: Booster Engines Exhaust Added--> Booster Group: 3 number of engines: 3 , diameter: 0.600, position x: -5.892 y: 3.256 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 3 number of engines: 3 , diameter: 0.600, position x: -4.442 y: 2.956 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 3 number of engines: 3 , diameter: 0.600, position x: -4.792 y: 1.506 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 4 number of engines: 3 , diameter: 0.600, position x: -3.469 y: -3.925 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 4 number of engines: 3 , diameter: 0.600, position x: -4.769 y: -4.625 z: -30.230
Energia: Booster Engines Exhaust Added--> Booster Group: 4 number of engines: 3 , diameter: 0.600, position x: -5.519 y: -3.375 z: -30.230
Energia: Stage n.1 Mesh Preloaded: Energia\Energia
Energia: Stage n.1 Mesh Added Mesh: Energia\Energia @ x:0.000 y:0.000 z:0.000
Energia: Booster Mesh Preloaded: Energia\booster1_1
Energia: Booster Mesh Added Mesh: Energia\booster1_1 @ x:4.919 y:-4.075 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster2_1
Energia: Booster Mesh Added Mesh: Energia\booster2_1 @ x:4.692 y:3.606 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster3_1
Energia: Booster Mesh Added Mesh: Energia\booster3_1 @ x:-4.692 y:3.606 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster4_1
Energia: Booster Mesh Added Mesh: Energia\booster4_1 @ x:-4.919 y:-4.075 z:-10.000
Load State Terminated
Module Buran.dll ............. [Build 120102, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Post Creation Started

I know that the original Energia.ini file called for 4 plumes on each booster but I still get a CTD every time I try to substitute in the old ini file.

---------- Post added at 08:12 AM ---------- Previous post was at 07:46 AM ----------

A little update, I can add the 4th plume to each booster if I change the configuration back to Multistage2 but I get a CTD when I try switching back to Multistage2015.

tumblr_o3asn4mmN21rpuj2so4_r1_1280.png


---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------

Here's the log for the CTD with all 4 plumes on each booster:

Code: 
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.79976e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) Graphics Media Accelerator HD)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module GPCMFD.dll ............ [Build 111222, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module LaunchMFD.dll ......... [Build 130413, API 100830]
Module B3OP.dll .............. [Build 101129, API 100830]
Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module TransX.dll ............ [Build 150909, API 100830]
Module ReFuelMFD.dll ......... [Build ******, API 060425]
Module Load.dll .............. [Build 110920, API 100830]
Module PylonMFD.dll .......... [Build ******, API 060425]
Module GS2.dll ............... [Build 131201, API 100830]
Module BGPCMFD.dll ........... [Build 120101, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1366 x 768 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module Multistage2015.dll .... [Build 151027, API 100830]
Load State Started
Energia: Guidance File present: Config\Energia\Energia_guidance_1.txt
Energia: Orbit Call Found! Targets: Apogee:120000.0 Perigee:20000.0 Inclination:51.6 Mode:-1.0 GT initial Pitch: 0.0 Abside:107700.0
Energia: Config File: C:\Users\User\Desktop\Desktop Files\Orbiter 2010 P1\Config\Energia\Energia.ini
Energia: Number of stages in the ini file: 1
Energia: Number of boosters group in the ini file: 4
Energia: Number of Payloads in the ini file: 1
Energia: Texture n.1 Loaded Contrail2
Energia: Texture n.2 Loaded Exhaust_atsme
Energia: Texture n.3 Loaded Exhaust2
Energia: booster n. 1 Tank Added: 320000.000 kg
Energia: booster n. 2 Tank Added: 320000.000 kg
Energia: booster n. 3 Tank Added: 320000.000 kg
Energia: booster n. 4 Tank Added: 320000.000 kg
Energia: Stage n. 1 Tank Added: 820000.000 kg
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: 1.694 y: 1.954 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: -1.614 y: 1.954 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: -1.614 y: -1.408 z: -31.600
Energia: Stage n. 1 Engines Exhaust Added--> number of engines: 4 , diameter: 2.420, position x: 1.694 y: -1.408 z: -31.600
Energia: Booster Engines Exhaust Added--> Booster Group: 1 number of engines: 0 , diameter: 0.600, position x: 4.919 y: -4.075 z: -31.000
Energia: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 0 , diameter: 0.600, position x: 4.692 y: 3.606 z: -31.000
Energia: Booster Engines Exhaust Added--> Booster Group: 3 number of engines: 0 , diameter: 0.600, position x: -4.692 y: 3.606 z: -31.000
Energia: Booster Engines Exhaust Added--> Booster Group: 4 number of engines: 0 , diameter: 0.600, position x: -4.919 y: -4.075 z: -31.000
Energia: Stage n.1 Mesh Preloaded: Energia\Energia
Energia: Stage n.1 Mesh Added Mesh: Energia\Energia @ x:0.000 y:0.000 z:0.000
Energia: Booster Mesh Preloaded: Energia\booster1_1
Energia: Booster Mesh Added Mesh: Energia\booster1_1 @ x:4.919 y:-4.075 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster2_1
Energia: Booster Mesh Added Mesh: Energia\booster2_1 @ x:4.692 y:3.606 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster3_1
Energia: Booster Mesh Added Mesh: Energia\booster3_1 @ x:-4.692 y:3.606 z:-10.000
Energia: Booster Mesh Preloaded: Energia\booster4_1
Energia: Booster Mesh Added Mesh: Energia\booster4_1 @ x:-4.919 y:-4.075 z:-10.000
Load State Terminated
Module Buran.dll ............. [Build 120102, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Post Creation Started
 
Last edited:
I have found good looking Space Shuttle SRB exhausts:
 

Attachments

  • Shuttle-launch.jpg
    Shuttle-launch.jpg
    49.5 KB · Views: 43
MS2015 PEG limitation

I found a limitation in the PEG autopilot. It's not a big issue because of a very limited context(see below).

Context:
- launch from a high latitude spaceport (ex: Plesetsk)
- launch to a polar orbit (ex: 98 equatorial inclination)
- second stage of the launcher is underpowered so when switching from north to south the PEG autopilot is still running in a suborbital flight (ex: launch Angara 1.1 with Briz-M(underpowered stage))

Result:
- uncontrollable stage when passing from north to south (still in suborbital flight)
- after start heading south the stage control is recovered

Example:
- Angara MS2015 v160109([ame="http://www.orbithangar.com/searchid.php?ID=6880"]Angara MS2015 v160715[/ame]) - require Angara Launch Vehicle Family([ame="http://www.orbithangar.com/searchid.php?ID=1098"]Angara Launch Vehicle Family[/ame])
- scenario: Angara 1.1 - Plesetsk - Polar

Workaround:
- use old vinka's guidance style implemented very well in Multistage2015
- optional: when the north to south change is finished, start using "orbit" autopilot for the final part of the orbit insertion (not tested yet for this case)

Tested with latest OH version and DMD(http://www.orbiter-forum.com/showthread.php?p=522019&postcount=375).

PS: First time when I tested the DMD for MS2015. Excellent work :tiphat:
 
Last edited:
Hello, I begin to think that multistage 2015 does not work in Orbiter RC1 (and in RC2 maybe too)...
When staging - CTD. At first I thought I am missing some cfg file, but now I have a suspicion that it is some incompatibility...
 
crisbeta said:
I found a limitation in the PEG autopilot. It's not a big issue because of a very limited context(see below).

Context:
- launch from a high latitude spaceport (ex: Plesetsk)
- launch to a polar orbit (ex: 98 equatorial inclination)
- second stage of the launcher is underpowered so when switching from north to south the PEG autopilot is still running in a suborbital flight (ex: launch Angara 1.1 with Briz-M(underpowered stage))

Result:
- uncontrollable stage when passing from north to south (still in suborbital flight)
- after start heading south the stage control is recovered

Example:
- Angara MS2015 v160109(Angara MS2015 v160715) - require Angara Launch Vehicle Family(Angara Launch Vehicle Family)
- scenario: Angara 1.1 - Plesetsk - Polar

Workaround:
- use old vinka's guidance style implemented very well in Multistage2015
- optional: when the north to south change is finished, start using "orbit" autopilot for the final part of the orbit insertion (not tested yet for this case)

Tested with latest OH version and DMD(http://www.orbiter-forum.com/showthread.php?p=522019&postcount=375).

PS: First time when I tested the DMD for MS2015. Excellent work :tiphat:
Click to expand...

I see, I think in some particular conditions (launch latitude and orbit inclination very similar) the yaw control equations fly through a singularity... I solved it for most of the cases but probably some are still missing.

Have you tried to disable yaw control with the MFD?

Marg said:
Hello, I begin to think that multistage 2015 does not work in Orbiter RC1 (and in RC2 maybe too)...
When staging - CTD. At first I thought I am missing some cfg file, but now I have a suspicion that it is some incompatibility...
Click to expand...

That's highly probable: since updates on the beta were happening quite often while my time available was quicly running out for some real life matters I decided to wait for the definitive release of the new orbiter for updating ms2015, otherwise I would have had to keep chasing updates and didn't have much time to do it.

As soon as it is released definitively I will make the final update.

Anyway in the meantime it seems also to me that it's not the ms2015 itself the issue, but the stage.dll, since CTD is happening at staging events. Have you tried to change the module of the spawned stages? you can put whatever you want there in order to check.
 
Kyle said:
Not sure if this is relevant but this still works with Orbiter 2016 RC1 :)
Click to expand...
Seems to be you are right, that CTD at least are not happening anymore (only stages disappear). I did not copy stage.cfg to a new Orbiter RC installation :facepalm:
 
fred18 said:
Maybe the wrong stage.dll installed?
Click to expand...
No, not wrong, it was not installed at all... :facepalm:
I must announced that all was my fault... multistage 2015 package works OK, as previously had.
 
back to coding here... since the final version of orbiter2016 has been released I'm going to fix the remaining bugs and deliver the final version of ms2016 for the beta
 
So the module is pretty much done, I'm working on a developer mode a bit also Eye Candy with the hangar and everything you need to build your own rockets.

The work in progress module is here: http://www.intech-srl.eu/MS2015WIP.zip

it's only the configs and the dll.

I added also the launch effects which will be a circular simmetrical array of particles with the following syntax in the ini file:
Code: 
[FX_LAUNCH]
N= Number of particles in the effect (can be up to whatever you want)
Height =  Height of the effects from the ground
Distance = Distance of the effects from the center of the array
Angle = Reference angle of the first effect (0 = along ship's X axis, 90 = along ship's y axis etc)
Pstream1 = name of the fist particle
Pstream2 = name of the second particle
CutoffAltitude = height of the vehicle at which the effects stop, if 0 or not set the effects will stop as soon as the vehicle detaches from the ramp, other wise they will be linearly interpolated up to the cutoff altitude

the DMD has been updated with this new function, I took out from the DMD some items of the vents and mach effects, you can define in the dialog up to 5 effects for each, if you want to define more, you have to do it manually in the .ini file (I think it's fair, 5 are already a lot IMHO).

Besides this, I've been thinking that now that orbiter allows for docked landed vehicles a new multistage infrastructure can take place, where you can load single stages and mount one on the other in the hangar and then launch your rocket. I've never played KSP but I know that should be something like that. Would this type of infrastructure be welcome here?
 
HI fred18,it looks like some great features in the upcoming MS2015,I like the idea of the hangar ,but it would be nice if you could have an option to be able to build the rocket in the hangar,or not depending on the preference,I also like the docked multistage idea too just my 2 cents.BTW thanks for making this.
 
fred18 said:
Besides this, I've been thinking that now that orbiter allows for docked landed vehicles a new multistage infrastructure can take place, where you can load single stages and mount one on the other in the hangar and then launch your rocket. I've never played KSP but I know that should be something like that. Would this type of infrastructure be welcome here?
Click to expand...

I think that'd be excellent idea. Both for gameplay and prototyping/developement. I think that if it'd work with any vessel (assuming it has proper "mounting points" defined in .cfg and/or .ini) that would bring lot of new users to Orbiter trained previously on KSP.
 
Some shots of what I'm working on. Maybe it's more a just for fun than really useful, but I think it's worth it.

0009.jpg

0011.jpg

0013.jpg
 
You must log in or register to reply here.

Similar threads

Matias Saibene
Update Multistage2026 - Development thread
5 6 7
Replies
137
Views
21K
gattispilot
gattispilot
polaris149Tiberius
Project Tutorial Development On Orbiter 2016 Stock Space Shuttle to ISS Scenario Case Study Project -v1.0
Replies
7
Views
4K
polaris149Tiberius
polaris149Tiberius
Matias Saibene
Update Multistage2015 Update to OpenOrbiter2024
6 7 8
Replies
156
Views
42K
Matias Saibene
Matias Saibene
MVA
Hardware Developing low-cost flight control (WIP)
Replies
3
Views
3K
MVA
MVA
dgatsoulis
Project TrajectoryOptimizerMFD open for testing
Replies
16
Views
5K
drgullen
D
Back
Top