Menu

#55 Apollo 4 Scenario CTD (reproducable)

closed
nobody
None
5
2005-06-21
2005-05-02
Reyn Xero
No

I realize that the apollo 4 and 6 missions aren't a
priority, considering that all one does is watch the
fireworks rather than participate, but I thought I
should submit this anyway.

Every time I run the apollo 4 scenario with NASSP
6.4.1, it crashes Orbiter to the desktop at the point
where (presumably) the CSM seperates from the SIVB
after the "mock" lunar insertion described in the
scenario file. This occurs every time I run the
scenario fresh, and also in any saved scenario file
from that mission run as well. I have included one for
reference and testing. At MJD 39803.6945 is when the
crash occurs on this scenario save.

I think it has something to with the seperation because
I hear the sound play briefly, as well as see the CSM
rerendered by itself (without the SIVB) before the
screen goes dark.

Also, it should be noted I used time acceleration of
10x for maneuvers at first, then none, and both 100x
and 1000x for waiting for the window to the TLI where
the warp automatically cuts off. CTD no matter what.
The only thing I haven't tried is no acceleration at
all, because that would require me to leave the sim
running for quite a while, due to the 3 orbits or so
that the ship is in parking orbit, and I just don't
have that kind of time.

Some pertinant information:
NASSP 6.4.1 stock (No NEP installed)
Orbiter version 050216 (with the high res texture pack
from the same download site)
OrbiterSound 3.0

I mentioned Apollo 6 because I tried to run and watch
it, and it CTD at the second stage seperation, so there
may be a correlation.

Discussion

  • Reyn Xero

    Reyn Xero - 2005-05-02

    Apollo 4 crash testing

     
  • Mark Grant

    Mark Grant - 2005-05-12

    Logged In: YES
    user_id=1209252

    Works for me with the latest code from CVS. I wonder if it's
    a missing mesh in the released code, as Apollo 4 has one of
    the engineering payloads in the SIVB and it isn't added to
    the model until the CSM seperates.

    LTA_2R.msh in your meshes directory should be about 240k.
    Check that you don't have a zero-sized mesh there.

    You could also try setting S4PL in your scenario file to 0
    for a normal LEM, as a test to see if that is the problem.

     
  • Mark Grant

    Mark Grant - 2005-05-12

    Logged In: YES
    user_id=1209252

    Incidentally, time acceleration shouldn't matter, as the sim
    should slow to 1x time acceleration whenever anything
    'interesting' happens (e.g. burn, stage seperation, etc).

     
  • Reyn Xero

    Reyn Xero - 2005-05-12
    • status: open --> closed
     
  • Reyn Xero

    Reyn Xero - 2005-05-12

    Logged In: YES
    user_id=1213399

    LTA_2R.msh is, in fact, 0 bytes. There ya go.

    I also set the S4PL to 0 as instructed, and the separation
    occurs just fine.

    I guess I'll make this closed now.

     
  • Tschachim

    Tschachim - 2005-05-12
    • status: closed --> open
     
  • Tschachim

    Tschachim - 2005-05-12

    Logged In: YES
    user_id=1204264

    Damn, I forgot that file (and apollo8_lta.msh) in the 6.4.1
    patch, so I think I'll release another patch the next days.

    xerozohar: I set the bug to open again, please try with the
    new patch (and S4PL 2) and set it to closed, if it's working.

    Many thanks for pointing that out!!!

     
  • Nobody/Anonymous

    Logged In: NO

    Ok you guys forgot the 2 files...
    LTA_2R.msh and apollo8_lta.msh

    How come you won't attach them here, or post them online for
    us to download?

     
  • Tschachim

    Tschachim - 2005-05-18

    Logged In: YES
    user_id=1204264

    Missing mesh attached. All these files are also public
    available via anonymous CVS...

    The patch is delayed because I want to do some further tests
    (and have a horrible flue...)

     
  • Tschachim

    Tschachim - 2005-05-18

    Missing Mesh

     
  • Tschachim

    Tschachim - 2005-06-21

    Logged In: YES
    user_id=1204264

    No news are good news, so I closed the bug because the patch
    seems to work...

     
  • Tschachim

    Tschachim - 2005-06-21
    • status: open --> closed
     
MongoDB Logo MongoDB