SSU V1.25 Release

Status
Not open for further replies.
O6 switches work ?
 
Urwumpe: Now that the MCAs have been implemented, do you think you could add the operation of the AVS? The appropriate DPS screen for this is GNC SPEC 51 OVERRIDE. Prior to launch they're commanded to the OPEN position by the GLS at T-28 seconds.
 
O6 switches work ?

For now, all related to the GPCs, and two of the Star trackers.

Urwumpe: Now that the MCAs have been implemented, do you think you could add the operation of the AVS? The appropriate DPS screen for this is GNC SPEC 51 OVERRIDE. Prior to launch they're commanded to the OPEN position by the GLS at T-28 seconds.

Yes, should be possible, if the vent door groups exist. The mechanic actuator class needs some small improvements, though. I think about adding a primitive AC bus class to the simulation, some auxiliary classes, and the path from inverter to motor.
 
Yes, should be possible, if the vent door groups exist.
Well, they'll soon do! All that's left to do is to add the physical doors as the vent cavities have now been done. Done updating the fuselage texture.
 
Well, they'll soon do! All that's left to do is to add the physical doors as the vent cavities have now been done. Done updating the fuselage texture.

OK, I still have not found out how to get the talkbacks working, but this is it for this night for me.
 
OK, new files with the midbody vent doors added have been checked in.
 
Is there a problem with sourceforge? I can't commit the new Orbiter.msh, it says the file is outdated and I cannot update the file either, it quits at 589kb.
 
Is there a problem with sourceforge? I can't commit the new Orbiter.msh, it says the file is outdated and I cannot update the file either, it quits at 589kb.

Possibly the update is already done... there are the vent doors now.
 
Not sure how important this is, but having 2 shuttles in the same scenario seems to result in CTDs after moving through the different VC positions.
 
Not sure how important this is, but having 2 shuttles in the same scenario seems to result in CTDs after moving through the different VC positions.

hmm... We don't have many global variables, do we?

Maybe a problem with the CRT MFD?
 
Possibly the update is already done... there are the vent doors now.

I modified them.

Not sure how important this is, but having 2 shuttles in the same scenario seems to result in CTDs after moving through the different VC positions.

Only if we simulate a resue mission.
 
Is there a problem with sourceforge? I can't commit the new Orbiter.msh, it says the file is outdated and I cannot update the file either, it quits at 589kb.
Try these steps:

  1. Delete Orbiter.msh in Meshes\SSU\
  2. Now perform an SVN Update on the Meshes folder to get the very lastest Orbiter.msh
  3. Now replace Orbiter.msh with the one you wish to check in
  4. Now try to check in the Orbiter.msh again, hopefully it should work this time around
 
hmm... We don't have many global variables, do we?

Maybe a problem with the CRT MFD?
CTD still occurs when CRT MFD is disabled in Orbiter launchpad, so that's not it. The RMS and MPM components are not included in the scenario, so these can also be ruled out.
 
Committed modified vent doors and texture.

the groups and rotation points are

Code:
Vent door groups
StbdDoor3=65
ROT_POINT=2.79,0.60,7.20
ROT_AXIS=0,0,1
StbdDoor5=66
ROT_POINT=2.78,0.59,1.45
ROT_AXIS=0,0,1
StbdDoor7=67
ROT_POINT=2.78,0.56,-1.93
ROT_AXIS=0,0,1
PortDoor3=68
ROT_POINT=-2.79,0.57,7.23
ROT_AXIS=0,0,1
PortDoor5=69
ROT_POINT=-2.77,0.61,1.46
ROT_AXIS=0,0,1
PortDoor7=70
ROT_POINT=-2.78,0.65,-1.92
ROT_AXIS=0,0,1
 
SC: Remember that MM201 blank display bug? Thought it had been fixed but it isn't. And MM201 doesn't respond to commands anymore.

And I have a CTD when entering a (Current state) scenario.
 
committed correct MGAtlantis.dds
 
DaveS: Can you post a CurrentState.scn that's crashing? I did a quick test using the Atlantis Cocpit scenario, and it seems to be working. Also, I checked in some debugging code for the MM 201 bug. Instead of showing a blank display, the MDU should now display the current SPEC and DISP values.
 
Well, right now it's very random and no longer confined to Current state. It appears randomly loading any scenario.

---------- Post added at 04:09 AM ---------- Previous post was at 03:51 AM ----------

Managed to boot up a scenario for MM201 testing and still blank screen.
 
I've modified the MDU code: try it again. This time you shouldn't get a blank screen.
 
Status
Not open for further replies.
Back
Top