2.5.4 openbeta setMissile crash solved

[Acidictadpole]

We've been experiencing this issue on our Georgia at War server a lot recently:

 

 

 

2019-01-04 01:44:44.971 INFO    EDCORE: 0x000007FEE12D3666 (Weapons): woMissile::setMissile + 0x816
2019-01-04 01:44:44.972 INFO    EDCORE: 0x000007FEE12AD37A (Weapons): wRocket::Create + 0x1EA

We've narrowed it down to the F-18 firing the AIM-7F missile (not sure if the E also causes it but the F definitely does). It seems to be pretty consistent but didn't happen in 100% of cases for us. We're theorizing that the server having F-18 installed may prevent it from happening but we can't verify it.

 

 

We've posted our findings here:

 

 

We solved this by modifying our warehouses to not have the 7F anymore. I'm not sure of a proposed solution for someone using unlimited weapons unfortunately.

 

 

EDIT: It may be that calling `getDesc()` on the weapon within scripts is causing this too. We've done a bit more testing but it's not conclusive just yet. I think SLMOD will always run a getDesc() on any weapon fired, so if you run slmod or any scripts which call that, this may be what's causing it.

Edited January 4, 2019 by Acidictadpole

[HC_Official]

We too have experienced this, thanks for doing a root cause analysis of it

[HC_Official]

Though I would say it has a "work around" and is not "solved" only ED can do that

[Acidictadpole]

Though I would say it has a "work around" and is not "solved" only ED can do that

 

 

I guess I meant that the mystery behind it was solved, but not fixed. In any case as long as people who care about the crash can find it then I'm happy.

 

 

We also may have tracked it down a bit further to anything doing a `getDesc()` call in scripts on that missile. I think slmod by default will do that on all weapons fired too, so if you have slmod installed you might be susceptible to this.