[juliensteel]

For some reason, when I finish the first mission, the game lames itself. It cuts to the desktop + a series of errors, and asking me if I want to run the debugger. Thing is, the program is still running, I can still hear music, and ships flying around, and HQ telling me i can jump back to base, though when i tab back to it, it doesn't go back into the game, and hitting alt-j(in an attempt to finish the mission), does not work. I can get all the error codes etc for you guys if you need, but I've seen other ppl have this problem on other forums, so I immagine its fairly common, I just haven't ever seen it fixed. Ne ways, any help would be appreciated. :

Here is the information that it spews at me:
Warning: Null vec3d in vec3d normalize.
Trace out of vecmat.cpp and find offending code.
File:math/vecmat.cpp
Line: 776
[This filename points to the location of the file on the computer that built this executable]

Call stack:
--------------------------------------------------------------------------------
fs2_open_367_p4_d.exe 0042f109()
fs2_open_367_p4_d.exe 0042f291()
fs2_open_367_p4_d.exe 005d9aef()
--------------------------------------------------------------------------------

[This info is in the clipboard so you can paste it somewhere now]

Use Yes to break into Debugger, No to continue, and Cancel to Quit.

[karajorma]

That's a new one on me (And judging from the lack of a response pretty much everyone else too).

By first mission do you mean the first training mission? If so shoot the instructor and tell me if that crashes it or if it allows you to warp out. 

Also report back which build you're using (3.6.7, a CVS build etc.)

[StratComm]

Mmm, null vector errors.  It shouldn't be dependent on finishing the mission unless either it's got to do with the player or some other ship warping out, and that event doesn't occur at any other point in the mission.  That seems unlikely, but in the case of training certainly within the realm of possibility.  At any rate, what's going on when it happens is critical to figuring out what's causing it, both mission and code-side.

[taylor]

I've fixed most of the null vec problems, but that has been post 3.6.7.  Newer builds should work better for that particular issue.

Regardless, the null vec problems are just warnings, the code will (as far back as retail) automatically fix the issue if it would have been a problem.  The warning is just to let you know that something it was doing could have messed up if the check wasn't in place.