 |
I fixed the code below to transmit the right entity, but I'm not entirely sure if this fixed the crash, since the crash happened rarely to start with. Need feedback on whether hitting stuff extremely close to you (objects, the world, AI) still causes an intermittent crash. |
|
|
Nope, crash is still happening. For some reason it happens right away when I load up test/stack and hit the brick wall near the stacked bottles/boards. It seems like the first attack hits nothing (when it sould have hit the world), then the second attack crashes. I swung at the pile of carrots before this. This is the last in the log: [.\DarkMod\MeleeWeapon.cpp ( 99):DEB (WEAPON) FR: 1169] Activate attack called. Weapon CMeleeWeapon_attachment_meleetest_shortsword_339, owner player1, attack name slash_rl. [.\DarkMod\MeleeWeapon.cpp ( 99):DEB (WEAPON) FR: 1294] Activate attack called. Weapon CMeleeWeapon_attachment_meleetest_shortsword_339, owner player1, attack name slash_rl. [.\DarkMod\MeleeWeapon.cpp ( 153):DEB (WEAPON) FR: 1294] Attack clipmodel started out inside something it hits. The first is the attack that doesn't seem to hit anything, second is the one that crashes. |
 |
The stacktrace is showing that the access violation is here: if( tr->c.material != NULL ) type = tr->c.material->GetSurfaceType(); // crash This is due to the material pointer pointing to uninitialised memory (0xbaadf00d). I see that the trace_t tr structure is not cleared after construction, I'll try to nullify the structure's contents with memset and see whether the crash is still happening. |
|
|
No, this didn't help. I see that the call to the closed source method in line Clip.cpp:1055 collisionModelManager->Translation( &results, start, end, trm, trmAxis, contentMask, 0, vec3_origin, mat3_default ); is returning a trace_t structure with a pointer set to invalid memory. I'll see what can be done here. |
|
|
resolved, with some aesthetic problems (now all surfaces make the default metal surface sounds when you hit them at point blank... maybe change the defaults? Also, velocity direction is somewhat wrong when you hit moveables point blank) |
- Anonymous
