[StarBomber109]

Assert: (Weapon_info[Weapons[homing_object->instance].weapon_info_index].wi_flags & WIF_BOMB) || (Weapon_info[Weapons[homing_object->instance].weapon_info_index].wi_flags & WIF_CMEASURE)
File: J:\src\cvs\fs2_open_3_6_9.final\code\Network\MultiMsgs.cpp
Line: 7861
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    process_packet_normal()    multi_process_bigdata()    multi_process_incoming()    multi_do_frame()    game_do_networking()    game_do_state_common()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------


What the HELL happened here?

[FUBAR-BDHR]

Known bug that has already been reported.

[StarBomber109]

Known bug that has already been reported.

Ah ok, so, they are fixing it...

[karajorma]

Yeah. At first I thought I knew the cause but now I'm not so certain. It's the next bug on my list though.

[nubbles526]

This filename points to the location of a file on the computer that built this executable

Lol, wonder whos computer it was talking about.

Is this part of a tbl?

[karajorma]

Taylor's.

It's actually quite a useful line to have. More often than not I can tell who built that particular executable just from that one line alone. If for instance I see a line pointing at D:\C++\Freespace\ it's a reasonable bet that it's from someone using ShivanSPS's pack v1.5 rather than Turey's installer because that's the only highly distributed package with one of my exes in it.

The file it refers to is the specific file with the piece of code that crashed. I can open up my C++ program and find exactly where in the code that crash happened thanks to that line. Unfortunately it doesn't help as much figuring out exactly why.

[nubbles526]

Sorry, don't know a lot of about computer language is C++.

Anyways, since it happened more than one time, why don't we do what microsoft does.

You know how they always have those forms you have to fill out:

What were you doing when it happened?
Did it happen more than once....

So if we see a pattern to develop, then it is easier to locate the bug.

[karajorma]

I know what's happening. The homing missiles someone fired are homing in on something they shouldn't be (another weapon or something). The problem is figuring out why they're doing that. Which means that this is basically one that simply requires trawling through the code until I figure out why.