Space Shuttle Ultra 1.25 Revision B development

SC that launch works fine for me, but when I switch to free mode in the DAP the thrusters won't fire, to perform the plus X and pitch manuever.
Make sure the Flt Cntrl Pwr switch is ON.
 
Make sure the Flt Cntrl Pwr switch is ON.


Cool, that did it !! Why don't people tell me about these new added features ? :thumbup:

---------- Post added at 06:38 AM ---------- Previous post was at 04:58 AM ----------

When was this camera added ? Could it be moved to the other side, and forward on the ET ?
 

Attachments

  • ETcam.jpg
    ETcam.jpg
    52.7 KB · Views: 615
When was this camera added ? Could it be moved to the other side, and forward on the ET ?

I think I did this when I reworked the camera VC interface, a long time ago... I remember doing something like that.
 
Could it be updated ?

No, it is cast in stone and can't be changed...just kidding.:lol:

All I need is a long wish-list of modifications for the engineering camera positions, the rest is straight forward. I can even move the position data into the configuration file, if you need to have it that way.
 
What ever is easiest for you, although if it could be attached to the ET, that would be the bee's knees. :thumbup:
 
What ever is easiest for you, although if it could be attached to the ET, that would be the bee's knees. :thumbup:

Would require a focus change, but it is possible to make this automatically when the ET is discarded AND change the position of the ET view right after the focus change.
 
When do you think it will be ready ? :tumbleweed:


j/k :thumbup:
 
When do you think it will be ready ? :tumbleweed:
j/k :thumbup:

Let me get this added to the ET, by making the ET equipped with a VC. Then I can try the rest... Since it does not touch the DPS stuff I have broken so far, i could commit it without risking making the rest of the team angry.
 
I promise I'm not angry,just yank'n yer chain.
 
I promise I'm not angry,just yank'n yer chain.

Didn't understand it differently. :cheers:

It is not that I am annoyed or under pressure because of it, you gave me a puzzle to solve and I just think about it...

If I wouldn't do this, I would now work on the DEU format buffer reverse engineering. I know that I am crazy doing it that way, but I can't do it differently.
 
I know, it's a detail thing, right ?
 
Donamy: Could you send me the PLBD radiator panel markings texture in *.psd format please?
 
I know, it's a detail thing, right ?

A bit more, it moves the format of the DPS displays into files and so that adding/changing/removing displays can be done by putting new displays into the DEU format file, just by editing the file with a editor and select a new format load on the Mass Memory Units in the configuration file.

Detail thing would be having the COAS on the commanders window during launch.
 
Let me get this added to the ET, by making the ET equipped with a VC. Then I can try the rest... Since it does not touch the DPS stuff I have broken so far, i could commit it without risking making the rest of the team angry.
Speaking of ET camera, how about making the position of it a mission file parameter? Prior to RTF after Columbia, they flew a RocketCam on STS-112/9A mounted on the LOX tank cable tray.

For RTF they moved the camera inside the LOX feedline fairing on the intertank to protect it from what happened with the STS-112 RocketCam: it got smudged by the RH SRB FWD BSMs!

Here's what the view from the STS-112 RocketCam looked like:
 
Speaking of ET camera, how about making the position of it a mission file parameter? Prior to RTF after Columbia, they flew a RocketCam on STS-112/9A mounted on the LOX tank cable tray.

I think it would be done best by implementing a mechanism in the mission files for selecting the external tank version used, for example by a class name string "SLWT-xxxxx" ...

This way we could also address many more features of the historic tanks, like implementing the first Shuttle launches.
 
I think it would be done best by implementing a mechanism in the mission files for selecting the external tank version used, for example by a class name string "SLWT-xxxxx" ...

This way we could also address many more features of the historic tanks, like implementing the first Shuttle launches.
That would be good. And each ET designation is ET-xx. STS-114 for example flew with ET-121, a modified SLWT.
 
Isn't "ET-xxx" just the serial number of the ET in the flight manifest?
 
Isn't "ET-xxx" just the serial number of the ET in the flight manifest?
Maybe, but LMSSC uses it as well in NASA status reports as well in internal MAF status reports.
 
Back
Top