View Issue Details

IDProjectCategoryView StatusLast Update
0000414FSSCPgameplaypublic2005-06-20 15:07
ReporterGoober5000 Assigned Tophreak  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0000414: Weapons try to home in on other weapons that aren't bombs
DescriptionWhen testing the docking bug with the GTT Fox in Inferno, I kept on hitting the "only allowed to home in on bombs" Assert in weapon_home (in weapons.cpp). Apparently someone's firing a weapon that tries to home in on a Hornet, a non-bomb weapon. Curiously, I had cheat-killed all the enemy fighters by that point, so no enemies should have been firing Hornets. Maybe a friendly Hornet was trying to home in on itself? Someone needs to trace through that function, find out who fired the weapon at what, and fix it. It might be as simple as repairing an "if" in the target selection, but who knows.
TagsNo tags attached.

Activities

phreak

2005-05-13 13:31

developer   ~0002376

i'm not taking this. i've already had too much fun with tracing through the turret code.

phreak

2005-05-14 20:38

developer   ~0002400

i think i may have fixed this. In evaluate_obj_as_target(), turrets would evaulate non-bomb missiles and possibly select them. It may have been the case that the installations were firing missiles (i believe those installations have missiles) at the hornets and the assertion kept occuring.

fizz

2005-05-15 09:24

reporter   ~0002410

Just in case it isn't fixed (haven't upgraded to latest CVS, yet), here's a trace. I've been hitting the assert frequently lately, so far only in missions with capships (King's Gambit, Bearbaiting). Seems to be a fairly recent issue since I've never seen it with older (<May 05) versions.

fizz

2005-05-15 09:26

reporter   ~0002411

Eh, uploading doesn't work, so I'll attach here:

ASSERTION FAILED: "Weapon_info[Weapons[hobjp->instance].weapon_info_index].wi_flags & WIF_BOMB" at weapon/weapons.cpp:3294

# 0 0x40309001 in kill () from /lib/libc.so.6
# 1 0x40233a22 in raise () from /lib/libpthread.so.0
# 2 0x4030a401 in abort () from /lib/libc.so.6
# 3 0x083590ed in WinAssert (
    text=0x83f3120 "Weapon_info[Weapons[hobjp->instance].weapon_info_index].wi_flags & WIF_BOMB",
    filename=0x83f1ba1 "weapon/weapons.cpp", line=3294) at windows_stub/stubs.cpp:109
# 4 0x083383eb in weapon_home (obj=0x9e496a4, num=24, frame_time=0.0250091553) at weapon/weapons.cpp:3294
# 5 0x083398a2 in weapon_process_post (obj=0x9e496a4, frame_time=0.0250091553) at weapon/weapons.cpp:3766
# 6 0x0827dade in obj_move_all_post (objp=0x9e496a4, frametime=0.0250091553) at object/object.cpp:1763
# 7 0x0827e51d in obj_move_all (frametime=0.0250091553) at object/object.cpp:2015
# 8 0x08057ceb in game_simulation_frame () at freespace2/freespace.cpp:5265
# 9 0x0805866a in game_frame (paused=0) at freespace2/freespace.cpp:5671
# 10 0x080592aa in game_do_frame () at freespace2/freespace.cpp:6110
# 11 0x0805b7d5 in game_do_state (state=2) at freespace2/freespace.cpp:7943
# 12 0x080d3617 in gameseq_process_events () at gamesequence/gamesequence.cpp:657
# 13 0x0805c7ee in WinMainSub (argc=5, argv=0xbffff7d4) at freespace2/freespace.cpp:8580
# 14 0x0805c83d in main (argc=5, argv=0xbffff7d4) at freespace2/freespace.cpp:8642
# 15 0x402f8c6f in __libc_start_main () from /lib/libc.so.6

phreak

2005-05-15 14:53

developer   ~0002413

you're really not going to catch the proper trace since that stuff is evaluated long before the weapon starts to home.

phreak

2005-05-16 02:14

developer   ~0002417

if nobody reports that this is occuring in new builds in the next week, assume its fixed. I ran debug builds all day today and never ran into this.

phreak

2005-06-20 15:06

developer   ~0002663

assume fixed, hasn't cropped up in a month or so.

Issue History

Date Modified Username Field Change
2005-05-12 09:12 Goober5000 New Issue
2005-05-13 13:31 phreak Note Added: 0002376
2005-05-14 20:38 phreak Note Added: 0002400
2005-05-14 20:59 phreak Status new => assigned
2005-05-14 20:59 phreak Assigned To => phreak
2005-05-15 09:24 fizz Note Added: 0002410
2005-05-15 09:26 fizz Note Added: 0002411
2005-05-15 14:53 phreak Note Added: 0002413
2005-05-16 02:14 phreak Note Added: 0002417
2005-06-20 15:06 phreak Note Added: 0002663
2005-06-20 15:07 phreak Status assigned => resolved
2005-06-20 15:07 phreak Resolution open => fixed