Space Shuttle Ultra 1.25 Revision B development

[DaveS]

Is anyone looking at this ticket?

It is really starting to annoy me.

 

[Donamy]

I used to get it with the D3D9 client every other load.

 

[DaveS]

I used to get it with the D3D9 client every other load.

I'm getting it just about every time. It's very random and unpredictable.

 

[Donamy]

Just SSU scenarios ? Mine were with all of them.

 

[DaveS]

Just SSU scenarios ? Mine were with all of them.

I have only tried SSU scenarios and after testing some random non-SSU scenarios, I have found it's only the SSU scenarios that produces the problem.

Maybe it's something that SSU does that's the problem or it's due to the complexity of SSU.

 

[Urwumpe]

Maybe it's something that SSU does that's the problem or it's due to the complexity of SSU.

It sounds like an uninitialized variable in one of our classes. Does it happen randomly, or can you repeat it with the same (Current State)?

 

[DaveS]

It sounds like an uninitialized variable in one of our classes. Does it happen randomly, or can you repeat it with the same (Current State)?

The interesting thing is that this is intermittent. Sometimes it happens and sometimes it doesn't. It's very random and there's no telling at all if it's going to happen. But it's always the same mesh/texture that it ends at.

But once it happens, it will repeat for some time. It's very much like the LH2 LLCO sensor failures that plagued the real program during 2005-2008.

 

[Urwumpe]

The interesting thing is that this is intermittent. Sometimes it happens and sometimes it doesn't. It's very random and there's no telling at all if it's going to happen. But it's always the same mesh/texture that it ends at.

But once it happens, it will repeat for some time. It's very much like the LH2 LLCO sensor failures that plagued the real program during 2005-2008.

Sounds very much like an uninitialized variable then. we should maybe try a standard pattern in our Orbiter callbacks: Catch all exceptions and handle them, before we leave them to Orbiter.

 

[DaveS]

The last SSU logged event in the log is the creation of the various data buses.

 

[Urwumpe]

The last SSU logged event in the log is the creation of the various data buses.

Can be a cause, but must not. There is a long chain of events happening unlogged afterwards. Also the databus system is pretty self-contained with only few variables that had to be initialized.

 

[DaveS]

Can be a cause, but must not. There is a long chain of events happening unlogged afterwards. Also the databus system is pretty self-contained with only few variables that had to be initialized.

Let me know if you have anything that you want me run through.

 

[Urwumpe]

Let me know if you have anything that you want me run through.

Let me get into the SSU mainline development first, I am still fighting against the negative results of having spent months without using the Orbiter API. :lol:

Wrapping the callbacks into try catch blocks should be easy enough though, I will let you know when I have committed something about it.

 

[DaveS]

How are we doing at the proposed release date-7? Looking at the recorded tickets, the two biggest ones are tickets 20 and 22.

 

[Urwumpe]

How are we doing at the proposed release date-7? Looking at the recorded tickets, the two biggest ones are tickets 20 and 22.

I won't be active this weekend, but then, thats not really a great change in activity.

But good news for Donamy... I have the adapter for reading my old HDD now. :lol:

 

[SiameseCat]

How are we doing at the proposed release date-7? Looking at the recorded tickets, the two biggest ones are tickets 20 and 22.

I've been doing some work on both of these, but I haven't had much time for Orbiter stuff recently. For the CG issue, I've been trying to actually update the CG location during flight, and this seems to improve the performance, although the stack is still too low at staging.

 

[DaveS]

I've been doing some work on both of these, but I haven't had much time for Orbiter stuff recently. For the CG issue, I've been trying to actually update the CG location during flight, and this seems to improve the performance, although the stack is still too low at staging.

How is this table looking compared to SSU?

 

[SiameseCat]

That's the same lookup table the SSU code is using for first stage guidance.

 

[DaveS]

That's the same lookup table the SSU code is using for first stage guidance.

And we're still coming up short on velocity?

 

[SiameseCat]

It's too low. The velocity is close to the correct value.

 

[DaveS]

It's too low. The velocity is close to the correct value.

What are you using for comparison? The only source for altitude I have is the Ascent cue cards from the Ascent FDFs.