Request Any SLS and Orion MPCV in development?

[Astro SG Wise]

Oh. That is the term that I coined. It is the combination of the ARV, the Neeseys module, and the NTR. I haven't learned how to make addons yet, so I just use Universal Cargo Deck to connect them. On Pappy's Hangar, there is the Eranda.

Also, really both at the same time? Is it big enough?

---------- Post added at 12:51 AM ---------- Previous post was at 12:50 AM ----------

Thanks for making that scenario file. Do I need anything else but what you gave us earlier?

---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------

Try this second stage version. This has a newer tower mesh
https://dl.dropboxusercontent.com/u/71242599/SLS2NDSTAGELAUNCH.zip

It has the Altair lander from here:
http://www.orbithangar.com/searchid.php?ID=6621

Do I need anything else besides this and the LTV?

 

[gattispilot]

With that scenario and this zip and the Phoenix. It should be all you need.

https://dl.dropboxusercontent.com/u/71242599/sls105cargo.zip

No you would need 3 cargo SLS's.
Here is a scenario with the Eranda loaded:
https://dl.dropboxusercontent.com/u/71242599/SLS130_CARGO_ERANDA.SCN

 

[Astro SG Wise]

What types are you using? Are you using Block IA Cargo for the MTV Pheonix (Mars Transfer Vehicle) and the SLS Block IIB cargo?

---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------

Sorry, correction Block II cargo

 

[gattispilot]

yes. Did it work?

I am checking on how to have 2 vessels attached using Velcro Rockets.

 

[Astro SG Wise]

If you really wanted to, I had a mission design that NASA may or may not replicate, but it would definitely aid our missions to Mars. Basically, it is a 10 day mission to HEO. If you think of the Apollo 9 mission, you got the right idea. SLS would launch the Orion MPCV and the MTV Phoenix Lander into LEO, then the second stage would carry it to a HEO that takes 1 day to get to apogee, and the perigee would be at LEO . Then, the crew prepares to do tests for 4 days, which means that they have orbited 2 times. On the 4th day, as they are passing over the Gulf of Mexico, the 4 person crew would split up between the MTV and the Orion. Once this is completed, they undock from each other, and MTV would do maneuvering tests, just like the spider lander during Apollo 9. After the two vehicles pass perigee, and then are re-ascending into HEO, Orion would dock to the MTV, and they would finnish tests for the day. On day 6 of the mission, on the 3rd orbit, the Orion and the MTV reach LEO once again. At this point, they would conduct a spacewalk that would transfer to the back of the MTV and do scientific tests at the panels there. On day 8, the crew transfers back into the Orion, and they jettison the MTV, which autonomously re-enters earth's atmosphere. After 10 days and 5 orbits, Orion re-enters and lands off the cost of Cape Canaveral.

In a sum, this is what the mission would look like.

DAY 1
1) Launch
2) Second stage boost to HEO
3) Orion MPCV Extract MTV
DAY 2
1)Begin spacewalk/MTV test preparations
DAY 3
1) Crew Rest Period
DAY 4
1) Undock from MTV
2) MTV Maneuvering Tests
3) Docking
DAY 5
1) Spacewalk Checks
DAY 6
1) Spacewalk
2) Science Experiments in MTV Bay
DAY 7
1) Crew Rest Period
DAY 8
1) Jettison MTV
2) MTV re-entry
DAY 9
1) In-orbit science tests
2) Crew Rest Period
3) Re-Entry burn
DAY 10
1) Re-entry
2) Splashdown


This type of mission would be a beneficial test to try out any sort of lander that NASA was going to use. I thought this would be a good mission to try first, but NASA is planning the Asteroid Redirect Mission first. Because Orion can last in space for 21 days, this would also test all of it's systems for a multi-day mission. If you want to, you can make this one. It would use the Block II Crew rocket, and it uses the big cargo second stage to bring both of them to the 2 day orbit.

---------- Post added at 12:37 PM ---------- Previous post was at 12:36 PM ----------

Looks Great! Just saw it!

---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------

yes. Did it work?

Check what? If you are referring to the LTV and Eranda scenarios, I have not been able to try them. Orbiter is not available at the moment. I will probably check them on Saturday. Thank you anyway!

 

[gattispilot]

You should have what need. The 130 ton BLOCK ii Cargo and the 105 ton Block 1A to carry the MTV. and the 10 ton Block 1 crew

Email me :[email protected]

I am not a good pilot so if times need to be adjusted let me know.

 

[Astro SG Wise]

So, maybe you could put some sort of fairing ON the MTV, but otherwise, you could put it upside down, so that it is not floating off the core.

---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------

You should have what need. The 130 ton BLOCK ii Cargo and the 105 ton Block 1A to carry the MTV. and the 10 ton Block 1 crew

Email me :[email protected]

I am not a good pilot so if times need to be adjusted let me know.

So, you mean I should have all that I need for the Mars Stack Mission, right? Ok. Good. Thank's a lot!

 

[gattispilot]

Yes. On the Lander. Just adjust the attachment point . It is hard as the save state doesn't seem to work. And you can't see thru the fairing.

so adjust this
PAYATCH LTV 0 -65 0 0 -1 0 0 0 1

here are the 2 cores.

Well it seems Velcro can only use 1 PAYATCH. So not sure how to add more special vessels like have the Altair and Orion.

It might be time to start back on a dll version.

 

[4throck]

Velcro is setup by scenario and some parameters like the height of the stage above ground are not saved.

Your best option is to create a simple launch situation in your Orbiter's situation folder. Name it starting with "a" so that it comes up first on loading.

I usually keep the situation open in notepad and cycle trough loading it in orbiter for resting, trying new values and saving, reloading, etc, etc.

Having n payloads is as simple as attaching them. But there are other ways, whatever works.

How's the velcro launch autopilot doing? I'm yet to find good parameters to get my Velcro Ares V into a circular orbit....


Looking good :thumbup:

 

[gattispilot]

On the other vessels. I tried using attachment manager to add the Orion and Altiar but couldn't

 

[orbitingpluto]

Multiple PAYATACH lines don't cause any problems(at least not if I remember correctly), so you should be able to attach as many payloads as you need.

Seeing the one screenshot with the lander reminds me that I never did spend the time to get the fairing jettison to look right. Perhaps I'll have a moment tonight to try fixing that.

 

[gattispilot]

Well then maybe I am doing it wrong. I posted the scenario with the Altair and Orion.
What do you mean about the fairing jettison to look right.

One thing that would be nice and I haven't been able to do is have different jettison directions. Like the LAS should jettison differently than the side parts

 

[Interceptor]

Well then maybe I am doing it wrong. I posted the scenario with the Altair and Orion.
What do you mean about the fairing jettison to look right.

One thing that would be nice and I haven't been able to do is have different jettison directions. Like the LAS should jettison differently than the side parts

Hi John in my experience attachment mfd,and Velcro don't mix.

 

[Donamy]

Hi John in my experience attachment mfd,and Velcro don't mix.

I think you mean UAP.

 

[orbitingpluto]

If you look closely, the fairings are falling down, having passed down through the rocket and now falling through the exhaust, and are also rotating away from each other kind of like hands on a clock face. The way they should be is something more like this illustration:

Falling outwards, away from the vehicle, and rotating with a motion like a shell opening. It's not an effect I have experience in creating, so in the last scenario file that I sent you a while ago, I just gave the fairings some quick numbers that result in what happens in the screenshot.

Since I meant to come back to it, I think I will, if your willing to accept the work.:tiphat:

I think I'll look into straightening out the PAYATACH strings as well, since I don't have much on my plate this weekend.

 

[gattispilot]

Well I got the Orion and Altair to be together.

I read the docs and saw how the Saturn V was done. So I made the Orion a series burn and the altair the PAYATACH.

Here is the latest SLS files with the Orion/Altair Scenario
https://dl.dropboxusercontent.com/u/71242599/slscaargoaltair.zip

 

[Astro SG Wise]

Gattispilot, I am pleased to report the orbiter log that gave me trouble. I just tried your crew scenario, and this is what happened when the fuel in the core stage depleted.

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.41329e-007 sec
Found 1 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 5450 )
==> Direct3D T&L HAL (ATI Radeon HD 5450 )
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ProjectApolloConfigurator.dll [Build 120715, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module Themis_MFD.dll ........ [Build 130317, API 100830]
Module GenesisMFD.dll ........ [Build ******, API 060425]
---------------------------------------------------------------
>>> 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 LTV-MFD.dll ........... [Build ******, API 060425]
Module transx.dll ............ [Build 100824, API 100823]
Error loading module Modules\Plugin\ProjectApolloMFD.dll (code 127)
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module TrackIR.dll ........... [Build 100830, API 100830]
TrackIR module not found.
Module PitchProgram2.dll ..... [Build ******, API 060425]
Module CSSC_Spawner.dll ...... [Build 120331, API 100830]
Module HCLV_MFD.dll .......... [Build 130722, API 100830]
Module Meshdebug.dll ......... [Build 100830, API 100830]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module CalculationMFD.dll .... [Build 111017, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1926 x 1064 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Joystick throttle: SLIDER 0
Joystick throttle control detected
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 EarthAtmJ71G.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
---------------------------------------------------------------
>>> 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.
---------------------------------------------------------------
Module SLSTOWER.dll .......... [Build 141012, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
ERROR: DDraw object is still referenced: 1366
---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1034]
---------------------------------------------------------------
**** Closing simulation session

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1926 x 1064 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Joystick throttle: SLIDER 0
Joystick throttle control detected
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 EarthAtmJ71G.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
---------------------------------------------------------------
>>> ERROR: Missing texture: c-white.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: lernasa_2.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
Module SLSTOWER.dll .......... [Build 141012, API 100830]
---------------------------------------------------------------
>>> ERROR: Missing texture: cev-white.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: cev-white.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: cev-white.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
**** WARNING: Mesh not found: .\Meshes\slsorionlas.msh
**** WARNING: Mesh not found: .\Meshes\.msh
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------


I have no clue what Mayfly is, but apparently it had something to do with detachment of the second stage. Great job otherwise! I loved flying it! I also tried the SLS Block II cargo, and I saw the same problem with the fairings falling through the ship. You may have a few minor things to work on, but it is looking great! :thumbup:

 

[Donamy]

Do you have velcro rockets addon ?

 

[gattispilot]

You need this Mayfly:
[ame="http://www.orbithangar.com/searchid.php?ID=2155"]http://www.orbithangar.com/searchid.php?ID=2155[/ame]
added that missing mesh
https://dl.dropboxusercontent.com/u/71242599/slscaargoaltair2.zip

 

[Astro SG Wise]

Thanks. I'll make that install soon.