SSU V1.25 Release

Status
Not open for further replies.
Now comes the stuff we can not see (yet). Latches and Hooks...
 
Now comes the stuff we can not see (yet). Latches and Hooks...
That and getting the ring into the ready-to-dock position. Currently into goes into the forward position. Ready-to-dock is the initial position.
 
That and getting the ring into the ready-to-dock position. Currently into goes into the forward position. Ready-to-dock is the initial position.

Already done, but not committed yet. Will come when I have done the other small stuff, most will be done by cheating currently anyway. Latches and Hooks indicators are now "operational" (latches closed, hooks open).

Now comes fixers.
 
Already done, but not committed yet. Will come when I have done the other small stuff, most will be done by cheating currently anyway. Latches and Hooks indicators are now "operational" (latches closed, hooks open).

Now comes fixers.
Good luck! Can't wait to dock to ISS with a working ODS! Any way you could make it with Donamy's ISS Experience add-on?
 
Good luck! Can't wait to dock to ISS with a working ODS! Any way you could make it with Donamy's ISS Experience add-on?

You just need to give Donamy's ISS a suitable docking port attachment point. Then I could develop the logic around his ISS.

EDIT: Small VC component change: The StandardLight class now has a second input port, named "test". If you set the test discrete, the light gets set - if not damaged.
 
You just need to give Donamy's ISS a suitable docking port attachment point. Then I could develop the logic around his ISS.
Easy. Is supposed to be a parent or child attachment and what's the ID?
 
Easy. Is supposed to be a parent or child attachment and what's the ID?

The ISS should be child and the ID should be "APAS9" (With "APAS7" and "APAS8" being reserved for older docking port versions)

The new behavior of the ODS is now uploaded.
 
The ISS should be child and the ID should be "APAS9" (With "APAS7" and "APAS8" being reserved for older docking port versions)

The new behavior of the ODS is now uploaded.
OK, will check things out as soon as I written up the summary of today's MMT briefing.


-----Posted Added-----


Just tested it and fantastic work so far. Works just like it's supposed to. And the CDS switch bug is gone again. Just a little note: the ring on the real Endeavour is scheduled to be extended around 9:35 pm EST(03:35 CEST).
 
Just a little note: the ring on the real Endeavour is scheduled to be extended around 9:35 pm EST(03:35 CEST).

Yeah, and except the power supply and DPS stuff, you can already follow the "DOCKING MECHANISM POWERUP" and "DOCKING RING EXTENSION" checklists.

But once we have initial contact and capture modeled, I will need to replace the simple AnimState to something more sophisticated (for having damped oscillations).
 
But once we have initial contact and capture modeled, I will need to replace the simple AnimState to something more sophisticated (for having damped oscillations).
Now that would be top of the line stuff:speakcool:! Any progress on the DPS screens?
 
Now that would be top of the line stuff:speakcool:! Any progress on the DPS screens?

Not yet, wanted to return to it once we can capture an object. Changed the order, so we are a bit closer to release most of the time.
 
DaveS: I've disabled some of the panel saving code, which was being called when the exception occured. See if this helps.
 
DaveS: I've disabled some of the panel saving code, which was being called when the exception occured. See if this helps.
That seems to have done it. No exception error messages or CTDs. Clean exits every time and this in the log:
Code:
SpaceShuttleUltra: Save panel states...
 Forward flight deck
 No panels to be saved here...
 Save panel "F6" ...
 Save panel "F7" ...
 Save panel "F8" ...
 No panels to be saved here...
 No panels to be saved here...
 Save panel "O6" ...
 Aft flight deck
 Save panel "R11" ...
SpaceShuttleUltra: Save subsystem states...
SpaceShuttleUltra: Saving state done.
So it seems to be cured(for now...).


-----Posted Added-----


Just discovered another problem: Orbit DAP PBIs are out of commission. Both the center and aft PBIs are affected. They light up in the correct modes, but you can't change them. Clicking them has no effect whatsoever, so it's stuck in whatever modes it was when the scenario was loaded.
 
I'll take a look at the DAP bug. The exception problem isn't really fixed, since the A7/A8 panel state isn't being saved.


-----Posted Added-----


DAP bug should be fixed now. I've also re-enabled some of the panel saving code, so the exception bug should be back.
 
DAP bug should be fixed now. I've also re-enabled some of the panel saving code, so the exception bug should be back.
DAP bug: fixed, thanks!
Exception bug: Not there and the log indicate a successful save.:hmm:
 
I've added all the panel-saving code again. See if the exception still appears.
 
I've added all the panel-saving code again. See if the exception still appears.
Nope. Good saves across the board. And no CTDs when quicksaving either.


-----Posted Added-----


A slight VC issue for whoever wants to fix it: the A7L panel is visible from the payload bay cameras, along with the aft RCS RHC. Slightly annoying.


-----Posted Added-----


Just checked in an updated ProjectAlpha_ISS.cfg and a STS-126/ISS docking scenario.
 
I've checked in code for Sense switch on PanelA6. If the VC camera is in the CDR, PLT, MS1 or MS2 positions, the forward RHC/THC are assumed to be used. Otherwise, SSU assumes that the aft THC/RHC are being used.
 
I've checked in code for Sense switch on PanelA6. If the VC camera is in the CDR, PLT, MS1 or MS2 positions, the forward RHC/THC are assumed to be used. Otherwise, SSU assumes that the aft THC/RHC are being used.
Works nicely here! Just did a final approach to docking with Aft Sense switch set to "-Z" which made flying by the C/L camera view alot smoother and easier.


-----Post Added-----


Any more progress on the ODS?
 
Any more progress on the ODS?

Worked last evening on making the ODS detect the PMA ring before docking, but also use only little performance each time step, by reducing the number of attachment points to be scanned.

Scanning all vessels to get those in 2000ft distance (CG-CG) and then find all attachment points within 250 ft (DP-DP) is sounding a bit too stupid to me, will add a blacklist of vessel handles without useful attachment.
 
Status
Not open for further replies.
Back
Top