Space Shuttle Ultra development thread

Offending file has been fixed. It should compile now.
Yes, it compiles fine now. What exactly are the changes? I don't notice anything different.

And the WING_NAME parameter is still broken.
 
Tried to compile the rev. 113 sources and it failed. Complains about missing
PayloadBaySystem.h file.

This time I am innocent.

But you can already prepare for: BasicVCComponent.h, BasicSwitch.h and ThreeWaySwitch.h - as well as the related cpp files.

Are all developers fit with the concept of name spaces? Because of the size of the shuttle project, I want to create two namespaces inside the project:

"vc" and "dps".


By using namespace, we could make it simpler to identify which component belongs to which major subsystem and keep the code structured better.
 
And the WING_NAME parameter is still broken.

You can fix it yourself - just locate the point where the texture is request from Orbiters API and correct the texture number. I think we will do such tasks more often in the future, at least until I can finish a better version of meshc.
 
You can fix it yourself - just locate the point where the texture is request from Orbiters API and correct the texture number. I think we will do such tasks more often in the future, at least until I can finish a better version of meshc.
OK, thanks for the tip. Speaking of the WING_NAME parameter: What is the future of this parameter? I'm thinking when we begin to support the different orbiters, they haven't always looked like carbon copies of each other. Just see the difference with Columbia and Challenger.
 
OK, thanks for the tip. Speaking of the WING_NAME parameter: What is the future of this parameter? I'm thinking when we begin to support the different orbiters, they haven't always looked like carbon copies of each other. Just see the difference with Columbia and Challenger.

I think the ideal solution (from my point of view), would be defining the type of shuttle in the configuration file. This could be done even so fine, that we could for example allow fictional or historic vehicle configurations.

But I am not sure on the wing name. Currently, the shuttles in orbiter got named by mission, which I think is not intuitive - I would prefer naming the shuttles by configuration file parameters or the name of the vessel in orbiter.

And define mission parameters by using mission definition files - like the name of the mission, the I-Loads (or I-Load files), etc... Ideally, all components, which need knowledge of the mission (for example a Mission control simulation) share the same mission definition.
 
Could someone send me a working build of the newest SSU, so I can be on the same page.

With the new placement of the aft view, I can put the COAS in it's correct position for viewing.
 
Could someone send me a working build of the newest SSU, so I can be on the same page.

With the new placement of the aft view, I can put the COAS in it's correct position for viewing.

I try to finish one ASAP, but give me a few minutes.
 
Thanks Dennis, take your time.
 
Thanks Dennis, take your time.

Well, will take a moment longer - the VC mesh is not to scale - all animations for the panels which had been fixed before are now ruined into the opposite direction.
 
I wish we had a way to detect that.
 
I can send you the smaller scale if you need it.
 
Urwumpe,

The first mesh I sent you turned out to be the wrong size, I downloaded it from sorceforge and thought it was the correct size. This new one is the correct size.
 
Basic modelling of the concrete hardstand is now completed. SSME/SRB flame deflector has been added with its sound suppression system nozzles.
 

Attachments

  • PadA_hardstand_2A.jpg
    PadA_hardstand_2A.jpg
    19.1 KB · Views: 491
  • PadA_hardstand_2B.jpg
    PadA_hardstand_2B.jpg
    16.7 KB · Views: 488
  • PadA_hardstand_2C.jpg
    PadA_hardstand_2C.jpg
    14.8 KB · Views: 504
  • PadA_hardstand_2D.jpg
    PadA_hardstand_2D.jpg
    16.3 KB · Views: 505
  • PadA_hardstand_2E.jpg
    PadA_hardstand_2E.jpg
    26.7 KB · Views: 487
Basic modelling of the concrete hardstand is now completed. SSME/SRB flame deflector has been added with its sound suppression system nozzles.

Doesn't the flame trench go down deeper inside the ramp? I miss the bridge for the RSS.

EDIT: And can somebody make a faint greenish plasma particle texture? That night launch really shows how much plasma gets created during launch (even at 100 km altitude)
 
I just saw MECO from a cornfield next to my house.
 
I just saw MECO from a cornfield next to my house.

Cool! Night launches are great, I hope we get a few videos from it. :cheers:

BTW:
An individual may submit a FOIA request to NASA by mail, fax, electronic mail, or in person to one of the thirteen (13) NASA FOIA Requester Service Center offices. Your request must be in writing. No telephone requests will be accepted .
If you do not know the exact title of the document you are seeking, you should provide a reasonable description of the documents. The more information that you can provide about the document, such as its author or date, the more expeditiously your request will be processed. Your request will be logged and a tracking number assigned to it. The tracking number assigned is of great importance to you as a requester because, in the event you would like to check the status of your request, the number enables us to locate where in the process your request is.
This NASA FOIA Homepage includes a link to each NASA FOIA Requester Service Center 's Homepage, as well as a link to the NASA FOIA Public Liaison Officers. Those individual FOIA Homepages list additional information concerning their center, including fax numbers, contract numbers assigned to that center, etc…
You should submit your request directly to the FOIA Requester Service Center , at the NASA center, that authored the documents. If you do not know which center to contact, then you may submit a request to NASA Headquarters FOIA Requester Service Center and they will attempt to identify the responsible center and forward your request.
A link is also included to the NASA FOIA Regulations, "Availability of Agency Records to Members of the Public" which will provide you with more detailed information concerning the processing of your FOIA request.
Also each NASA FOIA Requester Service Center has and maintains separate electronic reading rooms; and have records posted that have been previously released.

I think they mean US citizens with "an individual", but well... otherwise it sounds like somebody could at least try...
 
Doesn't the flame trench go down deeper inside the ramp? I miss the bridge for the RSS.
Not according to my reference data. And I will add the RSS bridge when I resume working on the hardstand later today.
 
Back
Top