- Joined
- Feb 4, 2008
- Messages
- 9,753
- Reaction score
- 1,024
- Points
- 203
Thanks, and it looks like the aft TAA position simply used a truss cradle similar to the External Airlock. Other than the truss cradle, it appears to be identical to the regular TAA. Interestingly enough I never got any CTDs, so I never thought to look in the Orbiter log. Here's my STS-95 mission file as it stands right now:HasTAA=TRUE
Currently it CTDs, as you changed the name of the mesh used in the aft position (we only have one mesh so it was used for both positions, but now the aft position is targeted to a non-existing mesh).
BTW: if the extra-stuff in the aft TAA is "addon" to the fwd TAA, then it should all be in one mesh, and things hidden as needed.
Code:
Name=STS-95
Orbiter=Discovery
OrbiterTexture=Discovery_9thmod
ET=SLWT
ETFRL=FALSE
SRM=RSRM
LaunchSite=KSC
LaunchPad=LC-39B
MLP=2
TargetInc=28.500000
TargetLAN=0.000000
MECOAlt=105000.000000
MECOVel=7966.023512
MECOFPA=1.326007
PerformRollToHeadsUp=TRUE
OMSAssistEnable=FALSE
OMSAssistDuration=102.000000
MaxSSMEThrust=104.5
ThrottleDown=843.333
ThrottleUp=1154.266
UseRMS=TRUE
UseKUBand=TRUE
UseSTBDMPM=FALSE
UseODS=FALSE
UseExtAL=TRUE
UseTAA=TRUE
AftTAA=TRUE
HasBulkheadFloodlights=TRUE
HasDragChute=TRUE
Bridgerails=0,1,2,3,4,6,8,10,11,12
SILTS=FALSE
LogSSMEData=FALSE
UseCISS=FALSE
CISS_GPrime=FALSE
UseASE_IUS=FALSE
ASE_IUS_AftLocation=FALSE
InternalPRSDTankSets=5
HasEDOKit=FALSE
EDOPallets=0
---------- Post added 07-27-19 at 12:48 PM ---------- Previous post was 07-26-19 at 10:49 PM ----------
Checked in an updated TAA mesh with the truss cradle hardware.
Last edited:
