Technical support > Feature Requests

Crash when using secondary lander team, and at base attacks.

<< < (2/2)

Zenerka:
Mercutio, you are talking about that (cp) assertion for cl_team.c or other one?
If the first one, if you can bring the backtrace, which would be the best, please do. If you mean other assertion, please tell the file name and line number it reports.

Mercutio:
Zenerka, thanks for the help in reporting errors properly.  I'm still a noob to UFOAI.  I'll post more complete information here.

I'm running WinXP, UFOAI-2.1
This particular crash happens when the aliens attack a base of mine that does not have any inhabitants.  I send a ship with 8 troops to the base being attacked.  When I select a weapon and then a firing mode that's when the crash occurs.  Here's what I see in the window:

Assertion Failed!
Program: ufo.exe
File: ../../src/qcommon/cmodel.c
Line: 1951

Expression: headnode < curTile->numnodes + 6

Then I have the MSVCRT  info about how to debug, plus I have Abort/Retry/Ignore.  
A Retry causes the whole program to lock up w/ an empty gray screen.
Abort, of course, ends the program.
Ignore causes a similar error to popup, the only difference being the line number:  
Line: 1871

All other info is the same.  I hit ignore again and I'm back at the gray screen and I can't pull up the console.  The HDD light is flashing like the program is doing something, but I have no sound.  I've let the program run for several minutes to see if anything interesting happens - eventually I get the famous Windows message: "UFO: Alien Invasion has encountered a problem and needs to close.  We are sorry for the inconvenience."   I happen to have MS Visual Studio 2003 so I could probably do some debugging, but I'm a bit green on that kind of stuff.  If you've got any pointers you'd like to share I'd be happy to do what I can.

Thanks!

-Mercutio

bob9000:
I also have this bug, under winxp and all that. The error message I get is the same, so no need to reproduce that, however, I used to get it when I used the team from my second base. Then I rebooted the computer, and now I get it when I use the team from my first base, but everything is fine when i use the team from my second base.

Just to complicate the issue.

Navigation

[0] Message Index

[*] Previous page