Wing Commander II - Crash A22 to DOS prompt?

sgupta

1st Lieutenant
Hey all,

I've gotten this twice now, and I'm not sure why. Wing Commander II is playing really great for me in general in native DOS, but every once in a while, after completing a mission, upon trying to land (Request Clearance works fine, complete with authorization...then I approach the Concordia and it should go to the landing cutscene [or story cutscene]), but it instead exits to the DOS prompt with the text "A22" directly above it.

This isn't too annoying as it only happens occasionally, but later on in the game after a particularly stressful mission I can see it becoming punch-screen worthy. =oP

The only common thread I can come up with as to what may be happening is something with how it "grades" a mission for the cutscene. First time it happened, I had flown ahead of two ships I was escorting and took out the Kilrathi before the escorts caught up. After this error, I actually couldn't do this again as the enemy ships...I don't know how to explain it - disappeared except for their afterburner trails (no, they weren't supposed to cloak). So I assumed the mission had an issue with this tactic and had no problems (with crashes or ships disappearing) after staying with my escort ships.

This time out, on a patrol/scan, the only diversion was going back and revisiting a Nav point that I wasn't sure I hit (I think I did, but wanted to make sure it counted towards the scan), and another crash upon landing. Next playthrough, I just took the Nav's straight, and it finished fine.

Could be coincidence. I used to revisit Navs in WC1 without problem, and you're clearly supposed to be able to in 2 (same nav computer).

Much appreciated if anyone has any input on this issue. =)
 
Back
Top