Space Shuttle Ultra 1.25 Revision B development

Sure, only I have to know how GPC downlist look like :)

Let me come home from work and I can tell you. It stands somewhere in the ALT software specs (I think it was page 32 or 33 in the Appendix E of Part 2... :lol:)

Wasn't a very complex format. Something like "GPC memory location" and "Value" interleaved.
 
Another table :P I think I achieved main goal :)
33a43ky.jpg
 
Nice... now I just need a second PC :lol:
 
Ok, so now my application can set shuttle attitude using data provided by slightly modified CRT MFD ;) Things to do tomorrow:
- multiple view (view from 3 different axes)
- earth
 
I just noticed the tiny function:

Code:
virtual int VESSEL3::clbkGeneric     (     int      msgid = 0, int prm = 0,void *      context = NULL )

This really simplifies a lot of the stuff I have done for intervessel communication for SSU, I'll look at how I can include this...

The same with some Lua fun... I think at least a way to script failures with it would be very good.
 
The same with some Lua fun... I think at least a way to script failures with it would be very good.
Well, for now can't it be used to control the GLS?
 
Well, for now can't it be used to control the GLS?

No, not completely I think.. I still read about it.

At least it seems to be possible to extend the Lua context with custom functions.
 
Okay, earth is done ;) Now I'm still figuring out how to attach camera to shuttle... Shuttle is now somewhere near North Pole.
testva.jpg
 
SSU isn't compiling; IOModule.h needs to be checked in.

There it is... have currently the problem that TortoiseSVN doesn't show which files are in the subversion or which are modified, possible I will miss some more files.
 
I finally attached camera to shuttle :) Algorithm needs slight modification to use shuttle orientation and fix camera position. In few days I should do 3 cameras in one splitted view.

testxo.jpg
 
I'm planning to finish up some old payloads I have been working on but one of them require the IUS, so I would like to know where we stand on getting that working and integrated with SSU?
 
I'm planning to finish up some old payloads I have been working on but one of them require the IUS, so I would like to know where we stand on getting that working and integrated with SSU?

I currently play with the Mercury stuff a bit, but when do you need a IUS for testing? The new clbkGeneric Callback could make things a lot simpler for the communication stuff, so the big bad feature is no longer big.
 
Well, the sooner the better. This is the order I have planned:

-New HST, in the original launch config(STS-31)
-DSCS-II F2/F3(STS-51J)
-DSP F-16(STS-44)
-Centaur G Prime/Basic G with the CISS
 
Can we do the HST first by making it a test vehicle for the Payload Interogator? I don't know if we have all panels ready, but a if the radio and radio command stuff would work good in the HST, we can use the same classes for the IUS, which would need also guidance, etc then.
 
Can we do the HST first by making it a test vehicle for the Payload Interogator? I don't know if we have all panels ready, but a if the radio and radio command stuff would work good in the HST, we can use the same classes for the IUS, which would need also guidance, etc then.
OK, anything you need from me for this? The new HST will essentially be just a new and more accurate mesh than the one that is included with the default Orbiter distro.
 
OK, anything you need from me for this? The new HST will essentially be just a new and more accurate mesh than the one that is included with the default Orbiter distro.

No, I would say not. I could even test things outside SSU, just with a MFD to talk to the DLL.

It would just need to be done first. Do you have a checklist or so about the initial HST?
 
Last edited:
Back
Top