Where can I find CEV-Orion?

[MJR]

Where can I find francisdrake's CEV-Orion? I have checked a whole bunch of links but they do not work.

 

[Chupacabra]

It depends on what you want.
\If you want the original Orion capsule you might want to check out ESAS CEV.
\If you want the current version of Orion, which is actually in beta development, check
here for his update.

 

[MJR]

What are all the downloads I need for the Ares download to work. I am missing the launch mesh and I don't know where to find it. Can someone please give me a link to the download? I am pretty certain there was a thread on the origanal orbitersim forum but I found no solution to finding the download.

 

[Chupacabra]

I could be very well mistaken but I believe the Ares is the work of Simcosmos. The readme should include some insight into what you should need.

\For the ESAS CEV, try [ame="http://www.orbithangar.com/searchid.php?ID=1957"]this[/ame]. (again I haven't checked)
\And for the beta development Orion, try [ame="http://www.orbithangar.com/searchid.php?ID=2770"]this[/ame].

 

[simcosmos]

What are all the downloads I need for the Ares download to work. I am missing the launch mesh and I don't know where to find it. Can someone please give me a link to the download? I am pretty certain there was a thread on the origanal orbitersim forum but I found no solution to finding the download.

Hi MJR,

If talking about my Vinka's multistage2.dll implementation of AresI,

[ame="http://www.orbithangar.com/searchid.php?ID=2770"]NASA AresI SC - 20070107dev[/ame]

the required CEV-Orion addon would be the CEV-Orion-0d.zip
( http://orbit.m6.net/Forum/default.aspx?g=posts&t=13896 )

However, it seems that such older '0d' development version - the one for which I have made integration with AresI, when released the addon - is not available anymore (also because is outdated by more recent Orion files available at francisdrake's development thread).

Possible solutions would be:
a) to manually edit / adapt my AresI 20070107 INI payload definition (position, mass, etc) to point to the most recent Orion spacecraft version

b) to use instead francisdrake's AresI performance / custom dll implementation (I gave permission to Franz to include the AresI 20070107 meshes inside his Orion package)

c) to wait for me to upload a new AresI (perhaps also with AresV) package including updated performance and visual implementations for the launchers and a more recent integration with francidrake's CEV+LSAM spacecraft (but might only be able to do it after July)

d) (...)

Sorry for anything, from my side: it is the nature of development files + quite some lack of time vs other factors that are preventing me to keep addons updated.

Meanwhile, if interested, I could try to post here the simple INI changes that could be compatible with the currently online AresI (I mean, that older Vinka's generic dll implementation from Jan2007, which is still using a J-2XD and also some outdated parameters) and the most recent Orion mesh / files spacecraft (by francisdrake). Let me know if wanting this last option and then please wait (I'm not using the 20070107 files anymore for development work and would need to go back to check what would be the parameters for a more recent integration with the latest CEV606 and those older Ares 20070107 files).

António

 

[MJR]

Thank you.

 

[simcosmos]

AresI 20070107 - CEV-Orion '0i'

Hello, sorry for the big delay! Will use this post to also answer to a recent bug report for AresI20070107 (at Orbit Hangar Mods).



Would first like to remember (never enough) that 'NASA AresI SC - 20070107dev' addon has been released more than one year ago and with files configured specifically for integration with francisdake's CEV-Orion 0d version, using the same directory structure of CEV-Orion (in order to facilitate the migration of my files for francisdrake to code them).

However, some things have changed since the time of that AresI release, many months ago:

- francisdrake has a new site url: http://home.arcor.de/francisdrakex/

- Orbiter Main Forums are now located here

- Orion's Development thread is at:
http://www.orbiter-forum.com/showthread.php?t=1043


In the moment I write these lines, the most updated version of the francisdrake’ s CEV-Orion addon seems to be 0i:
http://home.arcor.de/francisdrakex/d...V-Orion-0i.zip


Before moving on and just as a complementary side note, if users install CEV-Orion 0i first, my addon in second place and then run the scenarios labelled as being powered by Vinka dlls (the scenarios I have originally provided), the result will be that my original 'upper stage to CEV adapters' will look a bit short. Such adapters were made for the outdated / different CEV service module used in 0d Orion release and for the also outdated AresI20070107 integration, as can be seen next:
http://www.flickr.com/photos/simcosmos/352796285/

About integration of AresI 20070107 (my Vinka’s multistage.dll powered version) with francisdrake’s CEV-Orion '0i', this is probably what is being referenced in the bug report at OHM and what I have mentioned in the previous post.

So, if users install my AresI '20070107dev' implementation in first place and then the CEV-Orion '0i' on top of that, such action will most probably result in the adapters being placed at the height of the escape system. The original adapters have now the function of being service module covers, because most of the CEV’s service module changed to a smaller, fully enclosed diameter (on CEV606+ design iterations).

Such visual bug then happens because CEV-Orion '0i' includes updated 3D models for the adapters (in order to better fit such new service module design and related AresI upper stage integration) but kept the original 3D parts names, which means that, depending of the order of installation for my launcher implementation and for the latest CEV, some 'funny' things will happen in those panels / adapters locations either on my scenarios (or in francisdrake's scenarios).




-----------------------------
The Fix (visual only)

-----------------------------


Long story short, some coordinates of specific elements need to be updated at least to fix the visuals (but my implementation will still carry those covers to injection… the following fix does *not* update ascent events).

So, a step-by-step quick fix would be to open my INI configuration files:

AresI_CEV-Orion_ISS.ini
AresI_CEV-Orion_Moon.ini
(located at Config\CEV-Orion)

Browse to +/- the end of those files, locate and change the following entries (commented the old values):

[FAIRING]
N=1
MeshName="CEV-Orion\AresI_LAS"
Off=(0,0,62.78)
;Off=(0,0,62.51)

(…)

[PAYLOAD_1]
MeshName="CEV-Orion\CEV-Orion-launch"
off=(0,0,52.8)
;off=(0,0,52.2)

(…)

[PAYLOAD_2]
MeshName="CEV-Orion\AresI_CEVadapter_1"
off=(0,0,36.11)
;off=(0,1.36,50.20)

(…)

[PAYLOAD_3]
MeshName="CEV-Orion\AresI_CEVadapter_2"
off=(0,0,36.11)
;off=(0,-1.36,50.20)


There seems to exist one missing texture too, on the upper stage (if installing CEV-Orion 0i on top of AresI 20070107): I have originally included those textures all under 'Textures\CEV-Orion'. Francisdrake seems to be using the main texture directory but overwriting some original meshes (to facilitate his development + updates work). For that texture to appear, once updating to '0i' CEV, please go to Textures\CEV-Orion, locate AresI_LOGO_Agency.dds, copy + paste to main Textures directory.





Final comments: not sure when will update my ARES package but when doing so, in part to avoid some of these issues (but also to better prepare the path for other upgrades), I will revert to using my own custom directory structure (other than CEV-Orion directory).

Ok, I think it is all for now,


António

 

[Chupacabra]

Hey, thanks for the update. I was wondering if work would continue on this great add-on. It looks very slick.

I've seen your website recently and I want to comment that it is still one of the best sources of information for anything on Orbiter. I've seen your projects page and would love to see them in completed form.

 

[Acepilot]

I myself also download the CEV Orion. It works there is just one problem when I'm on the launchpad and I press the key "F" to see my FPS I get a CTD! Why is that? Can the button be changed?

 

[simcosmos]

Chupacabra: thanks for the kind words. Will write the same old story: I do not make on purpose but these virtual projects seem to take a good bit to being released (due to many constraints of several nature)... The years of 2007-2008 and 2009-2010 are also being (or might be) a bit more busy and somehow 'important' here than usual, which means that have lots of stuff on hold (some of it working fine here but missing what I call of 'boring final touches for public release'). Same can be said for several personal site updates that would like to make but that keep delaying forever (haven’t even written the last ‘operational year’ balance yet!).

The above to answer to your question (and running the risk of being repetitive, from past posts in this forum): yes, I continue to work on several Orbiter projects but... being limited to just a few minutes per day (which is a bit disruptive way of doing something). As a side note, currently trying to focus in KSC launch pads 39 work (because can then adapt such work for several addons) and in some Direct SDLV stuff plus also a few other alternative reality concepts.



Acepilot: could you please be a little more specific? I assume that you have installed AresI '20070107dev', then francisdrake's CEV-Orion '0i' on top of that, then applied the fix(es) above, then are trying to run the scenarios labelled as being powered by Vinka's multistage dll, correct?

If doing so I do not have any CTD, even if pressing F while at the launch pad. However, would like to remember a few things:

a) the F key is associated to fairings jettison on Vinka's multistage.dll: this is something hard-coded and that can't be changed

b) I have implemented the launch abort system in the fairing definition (might later change that to payload definition or to something else): this to say that the abort system in my implementation is just and only a rough visual, non-operational, representation


So, would recommend that if wanting to see the FPS while running the scenarios that I have originally provided, people only press F after the proper moment for launch abort system jettison.

Not sure if was able to help (?)

António

 

[francisdrake]

I understand Antonio has adapted his launcher for the 0i-version, which is the current development status.

If required, I can also re-post the older 0d-version.

Just for information: This is the link to the download-section of my website. http://home.arcor.de/francisdrakex/download/

 

[Acepilot]

Yeah I think the Od-Version would be of great use to the CEV-Orion 20070107dev.

 

[francisdrake]

I have uploaded the old '0d' version to the download-folder of my website:
http://home.arcor.de/francisdrakex/download/CEV-Orion-0d.zip

 

[Acepilot]

Thanks.

 

[Orbinaut Pete]

Orion scenarios

If it helps anyone, i have just released some scenarios hat combine francisdrake's orion 0i, ESAS CEV & also NASA VSE_SC

These are scenarios only, they simply combine all addons together to make a realistic constellation experience!

Can be found at [ame="http://www.orbithangar.com/searchid.php?ID=3475"]Search[/ame]


Please keep up good work on orion cev, will look forward to next version!


Cheers,

-Orbinaut Pete

 

[simcosmos]

Quick notes:

a) I strongly recommend that orbinauts use different Orbiter installs if still wanting to use the older CEV-Orion '0d' with AresI '20070107dev'. This is also partially my fault because not (re)releasing things in order to keep up with francisdrake's most updated and cool CEV-Orion releases: so, in order to avoid overwriting, this should be a safer approach.

b) About the Exploration Scenarios package: thanks for the notice, haven't tried them yet but would like to remember that some of my pre-2006 addons might be quite a bit outdated or even a bit more 'creative' from the point of view of some assumptions vs a more careful performance implementation (making reference, for example, to NASA VSE SC v1.0, one of my first bigger public addons): have kept improving it (as well several other addons) in a number of ways (visuals + performance implementation) but haven't released much of those updates yet (at least not in OHM).


António


[FONT=&quot][/FONT]

 

[MJR]

What is a good addon for launchpads using ares. It looks dumb launching from PAD39A.

 

[T.Neo]

What is a good addon for launchpads using ares. It looks dumb launching from PAD39A.

Won't Ares supposedly launch from LC-39 in reality? (That is, if it ever flies. )

 

[MJR]

I know it probably will but it won't have all the things it has now. It will be different. I was wondering if there was something more rocket launch oriented.

 

[T.Neo]

I know it probably will but it won't have all the things it has now. It will be different. I was wondering if there was something more rocket launch oriented.

Rocket launch orientated?

LC-39 has been used for the Saturn V and Saturn 1B, as well as the Shuttle.

It is very much "rocket launch orientated". It is used to launch rockets!