Space Shuttle Ultra development thread

[DaveS]

Does anyone know where the air data probe animation code is?

 

[Urwumpe]

Does anyone know where the air data probe animation code is?

No such animation code in SSU currently, it would need to be defined in Atlantis and connected by a function "SetAirdataPosition(int probe, double pos)"

 

[DaveS]

No such animation code in SSU currently, it would need to be defined in Atlantis and connected by a function "SetAirdataPosition(int probe, double pos)"

That certainly explains why I couldn't find it despite numorous searches.

Then I have this message for Donamy: Could you make the air data probes stowed by default in the mesh? Currently by default they're deployed(I think).

 

[Urwumpe]

Then I have this message for Donamy: Could you make the air data probes stowed by default in the mesh? Currently by default they're deployed(I think).

The last time I looked, they had been stowed, but incorrectly - they needed to translate outside instead of rotating by 180°. That's why I did not touch it yet.

 

[DaveS]

The last time I looked, they had been stowed, but incorrectly - they needed to translate outside instead of rotating by 180°. That's why I did not touch it yet.

Donamy has fixed this(sort of). Take a look on the Config\Vessels\SSUAtlantis.ini file I checked in. Contains the new animation info for the air data probes and startracker doors.

 

[Urwumpe]

Will have a look at the animations today. I started slowly with removing some immediate constants from the code, will also include the new animations in that pass.

 

[DaveS]

will also include the new animations in that pass.

Does that include revising the elevon code?

 

[Urwumpe]

Does that include revising the elevon code?

I can try, I have a drawing where the hinges are.

The FSS test scenario does not work, is that intented?

 

[DaveS]

I can try, I have a drawing where the hinges are.

The FSS test scenario does not work, is that intented?

Could be the missing "fssb.ini" file or a mess-up in the scenario file. Both have been fixed now. So try an update now. Oh and the fssb.ini file goes into Config\Spacecraft.

 

[Urwumpe]

Could be the missing "fssb.ini" file or a mess-up in the scenario file. Both have been fixed now. So try an update now. Oh and the fssb.ini file goes into Config\Spacecraft.

OK. I have the umbilical door animation fixed now. The orbiter floats a bit in the air and the ET umbilical well looks a bit strange, can it be the ET parts are a tiny bit to wide?

 

[DaveS]

OK. I have the umbilical door animation fixed now. The orbiter floats a bit in the air and the ET umbilical well looks a bit strange, can it be the ET parts are a tiny bit to wide?

Hmm. The OFS_WITHTANK_ORBITER = parameter could need some further tweaking.

 

[myles]

Can someone help me?

"c:\space shuttle ultra\orbitersdk\space shuttle ultra\Keyboard.h(11) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
.\Atlantis.cpp(38) : fatal error C1083: Cannot open include file: 'CommModeHandler.h': No such file or directory"

".\Release\Atlantis_MLP.dll.intermediate.manifest : general error c1010070: Failed to load and parse the manifest."

 

[DaveS]

"c:\space shuttle ultra\orbitersdk\space shuttle ultra\Keyboard.h(11) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
.\Atlantis.cpp(38) : fatal error C1083: Cannot open include file: 'CommModeHandler.h': No such file or directory"

I can confirm these errors with the latest sources(rev. 101). Seems like someone forgot to check in CommModeHandler.h.

 

[Urwumpe]

I can confirm these errors with the latest sources(rev. 101). Seems like someone forgot to check in CommModeHandler.h.

Can't there be a version, which I did not touch for two weeks, without new files to add?

The CommModeHandler is still a prototype, I think I will make it optional like the MLP until I have made it playable.

It handles the keyboard events from the point you pressed TAB to the point you either pressed TAB again or finished a message. While you are in the Comm Mode, it displays annotations on the screen to show the last communication to you and the options you have to reply or to start a new message.

 

[DaveS]

Stll won't compile here. Still complaining about this error message twice:

[SIZE=1]
c:\orbiterultra\orbitersdk\space shuttle ultra\Keyboard.h(11) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
[/SIZE]

 

[Urwumpe]

Try it again, I made the implicit int (which was at least once OSI standard) an explicit one.

 

[DaveS]

Try it again, I made the implicit int (which was at least once OSI standard) an explicit one.

Success! Builds nicely now.

 

[Urwumpe]

Success! Builds nicely now.

OK, out of plain demotivation for something related to animations, I decided to implement the RCS tanks (currently we make a mixture of using OMS and forward RCS tanks) and implement the thrusters like in the real shuttle - but I don't know if it will be flying stable afterwards.

Thats why I will only make the tanks standard (forward, left, right) and make a configuration file option for the realistic RCS based on your exhaust positions. But we'll need to fix their positions anyway I think.

When the RCS is done and working, I want to make either finally the Air data probe animations or implement my next option... "AltGPC" a system to replace the current GPC function by 5 special GPC objects which are pretty much equal, but can run different software configurations.

 

[DaveS]

OK, out of plain demotivation for something related to animations, I decided to implement the RCS tanks (currently we make a mixture of using OMS and forward RCS tanks) and implement the thrusters like in the real shuttle - but I don't know if it will be flying stable afterwards.

Well, the real orbiter manages it. And it usually only uses 1 jet/manifold to conserve prop.

 

[Urwumpe]

Well, the real orbiter manages it. And it usually only uses 1 jet/manifold to conserve prop.

Yes, but when I see the logic diagrams correctly, that trick is part of the GPC software (DAP Jet selection).

So, it is suitable for us to use them all for testing until we can implement the DAP. But as we can't have the DAP without the real RCS, I thought it's a good idea to accelerate this task item a bit.