You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the IniObjectCategory is 3 (a static) it hits the if clause, because it is not event.id==31, it hits the else clause and because there is no Event.IniDCSUnit, it errors to main logs with "the unit does not exist".
I need to check with you on three things:
A check on what the "Event.IniObjectCategory == Object.Category.STATIC" is really for and if it is being used consistently by ED
Is this the only weapon that uses static category?
A check on the impact of this.... I need to ask, why do we even care about OnHit events?
The text was updated successfully, but these errors were encountered:
thebgpikester
added
Bug
Moose bug that needs to be fixed.
Todo
On the list but work has not started yet.
Low Prio
Low priority issue. Could take time before being addressed.
Reproduced
Issue could be reproduced.
labels
Jul 5, 2020
I had introduced the if condition when the new event S_EVENT_LANDING_AFTER_EJECTION was introduced (before, there was no if condition for static objects at all). The initiator for that event is a static representing the pilot. However, unlike "normal" statics, the getName() function (and others) dont work for this object.
Yes, I think it is the only weapon as the code ran well for years. In fact, I would say this is a DCS bug as the object category should be OBJECT.Category.WEAPON (=2) and not OBJECT.Category.STATIC (=3).
Because people might hook into Hit events and do stuff (suppression class uses it, scoring also, users of cause).
The bug was REPORTED but Grimes fedback it was known, I'm not entirely sure which is true, but if it is the latter, wouldn't expect to see much movement on this bug. We should leave the ticket open until the releases have matured past this point before giving up hope. The impact of the issue is fairly small amountd of log writing unless people want to hit handle torpedoes and are not aware of the issue. The impact would be they might exclude torps or have a few hours of confusion in the future.
funkyfranky
removed
Bug
Moose bug that needs to be fixed.
Todo
On the list but work has not started yet.
Low Prio
Low priority issue. Could take time before being addressed.
labels
Oct 27, 2020
Current Code block around line 7500
When a torpedo hits, it creates an event like:
{[id]=2,[time]=28910.681,[initiator]={[id_]=33561088,},[target]={[id_]=16778240,},[weapon]={[id_]=33561088,},[IniObjectCategory]=3,[weapon_name]=weapons.torpedoes.G7A_T1,}
Because the IniObjectCategory is 3 (a static) it hits the if clause, because it is not event.id==31, it hits the else clause and because there is no Event.IniDCSUnit, it errors to main logs with "the unit does not exist".
I need to check with you on three things:
A check on what the "Event.IniObjectCategory == Object.Category.STATIC" is really for and if it is being used consistently by ED
Is this the only weapon that uses static category?
A check on the impact of this.... I need to ask, why do we even care about OnHit events?
The text was updated successfully, but these errors were encountered: