Space Shuttle Ultra 1.25 Revision B development

[Urwumpe]

The only errors I'm getting are from IDPSoftware.h and IDP_Software.cpp. Should these be deleted?

yes, they are obsolete. The IDP does less than I initially thought.

 

[DaveS]

Its MDU.h. And the version is uptodate did already commit it earlier today to make sure no parts of the DPS/VC stuff got AWOL.

Sorry, meant MDU.h. And I'm an idiot:embarrassed:! I forgot to do an update! Now just a few linker errors:

1>MDM.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall dps::BusTerminal::~BusTerminal(void)" (??1BusTerminal@dps@@UAE@XZ)
1>EIU.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall dps::BusTerminal::~BusTerminal(void)" (??1BusTerminal@dps@@UAE@XZ) referenced in function "public: virtual __thiscall mps::EIU::~EIU(void)" (??1EIU@mps@@UAE@XZ)
1>GPC.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall dps::BusTerminal::~BusTerminal(void)" (??1BusTerminal@dps@@UAE@XZ)
1>IDP.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall dps::BusTerminal::~BusTerminal(void)" (??1BusTerminal@dps@@UAE@XZ)
1>IMU.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall dps::BusTerminal::~BusTerminal(void)" (??1BusTerminal@dps@@UAE@XZ)
1>MDM.obj : error LNK2001: unresolved external symbol "public: __thiscall dps::BusTerminal::BusTerminal(void)" (??0BusTerminal@dps@@QAE@XZ)
1>EIU.obj : error LNK2019: unresolved external symbol "public: __thiscall dps::BusTerminal::BusTerminal(void)" (??0BusTerminal@dps@@QAE@XZ) referenced in function "public: __thiscall mps::EIU::EIU(class SubsystemDirector *,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,int,class mps::SSME *)" (??0EIU@mps@@QAE@PAVSubsystemDirector@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@HPAVSSME@1@@Z)
1>GPC.obj : error LNK2001: unresolved external symbol "public: __thiscall dps::BusTerminal::BusTerminal(void)" (??0BusTerminal@dps@@QAE@XZ)
1>IDP.obj : error LNK2001: unresolved external symbol "public: __thiscall dps::BusTerminal::BusTerminal(void)" (??0BusTerminal@dps@@QAE@XZ)
1>IMU.obj : error LNK2001: unresolved external symbol "public: __thiscall dps::BusTerminal::BusTerminal(void)" (??0BusTerminal@dps@@QAE@XZ)
1>GPC.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall dps::BusController::~BusController(void)" (??1BusController@dps@@UAE@XZ) referenced in function "public: virtual __thiscall dps::GPC::~GPC(void)" (??1GPC@dps@@UAE@XZ)
1>GPC.obj : error LNK2019: unresolved external symbol "public: __thiscall dps::BusController::BusController(void)" (??0BusController@dps@@QAE@XZ) referenced in function "public: __thiscall dps::GPC::GPC(class SubsystemDirector *,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,unsigned short)" (??0GPC@dps@@QAE@PAVSubsystemDirector@@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@Z)
1>MDM.obj : error LNK2019: unresolved external symbol "public: void __thiscall dps::BusTerminal::WriteData(unsigned long,short *)" (?WriteData@BusTerminal@dps@@QAEXKPAF@Z) referenced in function "public: virtual struct dps::BUS_COMMAND_WORD __thiscall dps::MDM::busCommand(class dps::BusTerminal *,struct dps::BUS_COMMAND_WORD,unsigned long,short *)" (?busCommand@MDM@dps@@UAE?AUBUS_COMMAND_WORD@2@PAVBusTerminal@2@U32@KPAF@Z)
1>ShuttleBus.obj : error LNK2019: unresolved external symbol "public: bool __thiscall dps::BusTerminal::Flush(void)" (?Flush@BusTerminal@dps@@QAE_NXZ) referenced in function "public: virtual void __thiscall dps::ShuttleBus::busPrePhase(void)" (?busPrePhase@ShuttleBus@dps@@UAEXXZ)

 

[Urwumpe]

Guess which CPP files are missing in your project now. :lol:

A BusTerminal.cpp and BusController.cpp
B BusStation.cpp and TrainStation.cpp

Call 555-SPACE now

 

[DaveS]

Guess which CPP files are missing in your project now. :lol:

A BusTerminal.cpp and BusController.cpp
B BusStation.cpp and TrainStation.cpp

Call 555-SPACE now

Success!!! Builds fine now!

 

[Urwumpe]

Success!!! Builds fine now!

Fine...then I can go to bed now and think about how I can ruin the repository tomorrow... :tiphat:

 

[DaveS]

Fine...then I can go to bed now and think about how I can ruin the repository tomorrow... :tiphat:

Feel free by ruining it with the Ku antenna! BTW, Don: how's the RAMFD files coming along?

---------- Post added at 01:17 AM ---------- Previous post was at 12:55 AM ----------

Now I'm getting consistent CTDs whenever I try to switching positions in the VC.

 

[SiameseCat]

I'm still getting link errors; it can't find the constructor/destructor for the RAM32S class.

---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------

I added RAM32.cpp and RAM32S.cpp to the project; it compiles.

---------- Post added at 09:25 PM ---------- Previous post was at 08:44 PM ----------

Are there any objections to me checking in the .csproj files I have on my machine? They don't have any hardcoded paths, so they should work for everyone. After this we can update the project files when we add files, etc.

 

[Urwumpe]

DaveS: Let me first get done with the MDMs, then I can look at the Ku Band antenna stuff again.

Are there any objections to me checking in the .csproj files I have on my machine? They don't have any hardcoded paths, so they should work for everyone. After this we can update the project files when we add files, etc.

No problem for me, as long as I am warned ahead.

 

[DaveS]

I'm still getting link errors; it can't find the constructor/destructor for the RAM32S class.

---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------

I added RAM32.cpp and RAM32S.cpp to the project; it compiles.

---------- Post added at 09:25 PM ---------- Previous post was at 08:44 PM ----------

Are there any objections to me checking in the .csproj files I have on my machine? They don't have any hardcoded paths, so they should work for everyone. After this we can update the project files when we add files, etc.

DaveS: Let me first get done with the MDMs, then I can look at the Ku Band antenna stuff again.



No problem for me, as long as I am warned ahead.

I have no problem with source controlled project files.

 

[Donamy]

Any chance for the Range Rate instrument ?

 

[Urwumpe]

Any chance for the Range Rate instrument ?

Would be possible once the Ku Band antenna basics are done. I have still a small technical paper around here, that describes the pulse modulation of the Ku band antenna in RR mode, theoretically we could even model realistic doppler/range errors in it. If I am not mistaken, the Ku band antenna is directly connected to the A2 panel, so it could appear pretty soon after the radar mode is done.

If one of the meshers is not knowing what to do...having a good looking TDRS satellite in the Shuttle scenarios would be nice. :lol:

 

[DaveS]

If one of the meshers is not knowing what to do...having a good looking TDRS satellite in the Shuttle scenarios would be nice. :lol:

Well, I could finish my upgraded IUS meshes. Maybe Donamy would like to tackle the TDRS? Also, do you still have the STS-93 IUS Deploy C/L? I believe it contains some nice drawings of the IUS/ASE Standard Switch Panels(SSPs) that are used to for IUS and ASE operations.

 

[Urwumpe]

Well, I could finish my upgraded IUS meshes. Maybe Donamy would like to tackle the TDRS? Also, do you still have the STS-93 IUS Deploy C/L? I believe it contains some nice drawings of the IUS/ASE Standard Switch Panels(SSPs) that are used to for IUS and ASE operations.

I think I still have them in my library. What I don't have is information about the SM application software used for controlling the IUS deployment.

---------- Post added at 04:50 PM ---------- Previous post was at 04:40 PM ----------

I think you can also use this one for the IUS/TDRS:

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19800070343_1980070343.pdf

 

[Donamy]

Didn't Gazza make a nice TDRS ?

 

[DaveS]

Didn't Gazza make a nice TDRS ?

Yes, but we have the problem of using it without his permission. Also the hi-gain antenna animations were off. They're supposed to open like an umbrella, his rather just scaled from the stowed position to the open position.

 

[Urwumpe]

Also, I don't know if the scale is fitting. I'd rather have it right, and integrate well into SSU.

 

[DaveS]

Also, I don't know if the scale is fitting. I'd rather have it right, and integrate well into SSU.

Right. Any idea on how the IUS ASE well be integrated with SSU? It obviously need to be able to receive commands from the L11/L12 SSPs.

 

[Urwumpe]

Right. Any idea on how the IUS ASE well be integrated with SSU? It obviously need to be able to receive commands from the L11/L12 SSPs.

I'd suggest, such "payloads" are installed either fixed into SSU and we just set a flag in the mission file to use the IUS ASE in the payload bay, or we wait until I have written a proper DLL for inter-module communication and we make it a normal payload.

 

[Donamy]

hmmmmm, ...I'll have to think about how to animate an umbrella.

 

[Urwumpe]

hmmmmm, ...I'll have to think about how to animate an umbrella.

I know a way, but this one is mathematical insanity. :lol:

(Have a very simple mesh for the antenna screen and move the vertices manually, using the movement of the ribs as reference)