SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
No, Windows 7. Both key combinations work here.


I think then it is something on your end that intercepts the keys. Do you have any special display software running that might be responsible?
 
I have seen that issue very recently on a laptop (and a modern one), not on a Desktop. Both with Windows 7, ovbiously. It´s not a SSU or Orbiter thing, is a Windows or Display driver option.
 
Last edited:
Same here, also working on a Notebook.
 
Now that has been settled, key-mappings can be changed in the keymap.cfg file. The ones you're looking for is the Lean commands.
 
Now that has been settled, key-mappings can be changed in the keymap.cfg file. The ones you're looking for is the Lean commands.

Fine. You may remove the code for the additional VC positions, because I won't be doing this. :dry:
 
Fine. You may remove the code for the additional VC positions, because I won't be doing this. :dry:
I'm not saying that they should be removed. I was just trying to understand why you couldn't use the default lean commands.

---------- Post added at 03:46 PM ---------- Previous post was at 11:31 AM ----------

I have now checked in the corrections to the Ku band DA animations.

---------- Post added at 07:09 PM ---------- Previous post was at 03:46 PM ----------

Panels R13L and C2 do not have the switch throw sound effects that the others do. Also the rotary switches on A8 lacks them.

---------- Post added at 07:15 PM ---------- Previous post was at 07:09 PM ----------

Another VC problem: The coordinates for the APDS CONTROL COMMANDS push-buttons on A7L (APDS Control Panel) needs to be altered.
 
Panels R13L and C2 do not have the switch throw sound effects that the others do. Also the rotary switches on A8 lacks them.

Can be fixed.


Another VC problem: The coordinates for the APDS CONTROL COMMANDS push-buttons on A7L (APDS Control Panel) needs to be altered.

Only those buttons or others as well?
 
I have seen that issue very recently on a laptop (and a modern one), not on a Desktop. Both with Windows 7, ovbiously. It´s not a SSU or Orbiter thing, is a Windows or Display driver option.

possible "fix"
X7YiP.png
 
Progress on the mesh. OMS pod completed and seperated the tiles from the base, for earlier missions. Question: should the pods be seperated into right and left ? I believe there was only one mission, of Discovery's where you had one OMS pod with black tiles, and one without.
 

Attachments

  • SSUOrbiterWIP.jpg
    SSUOrbiterWIP.jpg
    155.1 KB · Views: 462
Progress on the mesh. OMS pod completed and seperated the tiles from the base, for earlier missions. Question: should the pods be seperated into right and left ? I believe there was only one mission, of Discovery's where you had one OMS pod with black tiles, and one without.

If it is just about me, we can pretend that the mission did not exist.
 
Progress on the mesh. OMS pod completed and seperated the tiles from the base, for earlier missions. Question: should the pods be seperated into right and left ? I believe there was only one mission, of Discovery's where you had one OMS pod with black tiles, and one without.
That was STS-51J, Atlantis first mission on October 1985. Payload was two Block III DSCS satellites on a single IUS.

And I just confirmed it, STS-61B, also an Atlantis mission flew the same OMS pod configuration (TPS-modified ROMS, standard TPS LOMS).

---------- Post added at 04:19 PM ---------- Previous post was at 04:09 PM ----------

And while on the subject of TPS, for all of the pre-ISS missions Discovery, Atlantis and Endeavour had the entire midbody and aft engine compartment sidewalls covered by AFRSI (quilted) blankets. When ISS assembly got near, the midbody sidewalls as well as aft engine compartment AFRSI was replaced by FRSI blankets.

This photo of Discovery in the DFRC MDD shows the original TPS configuration quite well. Disregard the OMS pods, they're the ALTA pods from Enterprise. Discovery's OMS pods were already KSC undergoing flight-preparations.
https://dl.dropboxusercontent.com/u/24122088/STS41D-036B-EC83-27080a-11.5.83.jpg

And this photo of Atlantis at the pad mid-era, shows the PLBD TPS configuration:
https://dl.dropboxusercontent.com/u/24122088/KSC-97EC-0711.jpg

The darker portions are the FRSI blankets. As you can see the TPS changed alot in order to reduce the weight of the orbiters.
 
Last edited:
That was STS-51J, Atlantis first mission on October 1985. Payload was two Block III DSCS satellites on a single IUS.

And I just confirmed it, STS-61B, also an Atlantis mission flew the same OMS pod configuration (TPS-modified ROMS, standard TPS LOMS).

---------- Post added at 04:19 PM ---------- Previous post was at 04:09 PM ----------

And while on the subject of TPS, for all of the pre-ISS missions Discovery, Atlantis and Endeavour had the entire midbody and aft engine compartment sidewalls covered by AFRSI (quilted) blankets. When ISS assembly got near, the midbody sidewalls as well as aft engine compartment AFRSI was replaced by FRSI blankets.

This photo of Discovery in the DFRC MDD shows the original TPS configuration quite well. Disregard the OMS pods, they're the ALTA pods from Enterprise. Discovery's OMS pods were already KSC undergoing flight-preparations.
https://dl.dropboxusercontent.com/u/24122088/STS41D-036B-EC83-27080a-11.5.83.jpg

And this photo of Atlantis at the pad mid-era, shows the PLBD TPS configuration:
https://dl.dropboxusercontent.com/u/24122088/KSC-97EC-0711.jpg

The darker portions are the FRSI blankets. As you can see the TPS changed alot in order to reduce the weight of the orbiters.

That really doesn't have anything to with the mesh, that would fall under textures.
 
Are the payload door mechanisms still used?
 
Ok, but they are no longer attached to the doors for some reason. I'll reposition them.
 
Should there be a flag, assigned to the parts that need to be omitted, such as the two tails and the OMS base tiles?
 
Should there be a flag, assigned to the parts that need to be omitted, such as the two tails and the OMS base tiles?

Would be a possibility.
 
And how would I do that ?

I would need to look into the Orbiter documentation, but I remember there is a FLAG value for that... we used it for the BlackDart wheel blur, remember?
 
Status
Not open for further replies.
Back
Top