Space Shuttle Ultra development thread

For the event timer on the A6U panel, should I name the numbers Clocknum5-8 and the toggles A6Utog1-4 ?
 
Finished new VC mesh with A6U and A7U panels with hi-res texture.

Urwumpe, you have mail.
 
For the event timer on the A6U panel, should I name the numbers Clocknum5-8 and the toggles A6Utog1-4 ?

Clocknums5-8 would be good, but the A6U "toggles" are actually DAP pushbuttons and only display different values as the C3 DAP while the aft workstation is not powered up. DAPIndicators would be a better texture name.

Finished new VC mesh with A6U and A7U panels with hi-res texture.

Got it, checking it out.
 
The SCOM I got the panel pic from shows the event timer the same as the one in the C2 panel. I wonder if they were available both ways. I can change it if you want. Also, should I copy and paste a MDU to the monitor in the AFT flight station, so it can be programed ?

I'm doing the A2 panel next, and I will include the needles as groups to be animated, if someone wants to tackle the range finder.
 
The SCOM I got the panel pic from shows the event timer the same as the one in the C2 panel. I wonder if they were available both ways. I can change it if you want. Also, should I copy and paste a MDU to the monitor in the AFT flight station, so it can be programed ?

I'm doing the A2 panel next, and I will include the needles as groups to be animated, if someone wants to tackle the range finder.

Would be good. I just redo the VC code for the MDUs, so they use all the same definition code and VC event handling. I already added support for 11 MDUs in the code.

Doesn't the needles of A2 show attitude rates?
 
Managed to dig up some OBSS panel info. PDF is attached to this post.
 

Attachments

Last edited:
Has there been any progress on egtting the C/L latches animated? Or any other other progress?
 
No progress here, was busy with university stuff this weekend.

I have started adding the OPS 0 to CRTMFD, but the Shuttle currently lacks some stuff to use it. Also I have a replacement for the current MDU code 80% done, which would fix the mouse event trouble.
 
I have the A2 panel done.

What should I name the needles ?
 
Also I have a replacement for the current MDU code 80% done, which would fix the mouse event trouble.
Great! Speaking of that, the CRT keypads on C2 are dead. CRT mode switches are on and correctly configured, but no action visible on CRTMFD.
 
Great! Speaking of that, the CRT keypads on C2 are dead. CRT mode switches are on and correctly configured, but no action visible on CRTMFD.

I know. That's why I work on it. I first wanted to do just a quick fix, but there are too many cross references for a quick fix AND add a eleventh MDU.

Now the MDU gets implemented as VC component and all MDUs will be practically equal.

All DPS related stuff, just like the DPS mode of the MDUs will get moved into four IDP subsystems, which communicate with the MDUs. Port switching could be made possible - but is not important now. The IDP will also handle keyboard entries.

The painting will get two modes: the default painting method uses CRTMFD like we have it now, the alternative paints on any device context (DC), you give the MDU - MFDs, windows, textures, printers. :rofl:
 
I have the A2 panel done.

What should I name the needles ?

No idea, I don't know their exact function. I would suggest "A2H" and "A2V", but that would be very rough.
 
Well, they are not for me. Anything special to command themto operate?

The last information for me is, that the animations are defined now, but still not used during opening. The opening sequence will have to get reworked anyway. Currently, we do both doors with one animation, in reality, both doors can be operated independently over OPS SM 202.
 
The last information for me is, that the animations are defined now, but still not used during opening. The opening sequence will have to get reworked anyway. Currently, we do both doors with one animation, in reality, both doors can be operated independently over OPS SM 202.
OK.
 
There are four needles 2 for Azimuth and 2 for elevation, AFAIK
 
Well, they are not for me. Anything special to command themto operate?
I forgot to add the latch parameter lines into the scenario files. Try the Atlantis cockpit scenario, and you should see the latches moving after the doors close.
 
Dennis, You have mail.
 
Dennis, You have mail.

Weeeeeeee!


Now that looks like a aft station.
SSUAftWorkStation080421.jpg
 
Back
Top