Bug #4257

No exception handling or error for 'nil' dispersion in BIS_ARTY_F_SetDispersion

Added by Inkompetent over 5 years ago. Updated about 5 years ago.

Status:Expired Start date:09/03/2009
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:BI Modules
Target version:-
Affected ArmA II version:1.03.58627 First affected build:
Reproduced by another DH user:No First affected ArmA II version:
I am using some Mods: Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you: NGUrl:
Related to content of DLC: WIKIurl:

Description

When using non-spawn artillery fire missions there is no exception handling or error message for if the dispersion set with BIS_ARTY_F_SetDispersion is nil. The result of the dispersion being nil is that the artillery battery fires as normal, but the rounds will never ever impact. They simply disappear.

History

Updated by Headspace over 5 years ago

Inkompetent: What happens when you try setting dispersion to an extremely low value, such as 0.001?

Updated by Inkompetent over 5 years ago

Extremely low values such as 0.000001 still works, as does it with dispersion plainly set to 0. Only when the dispersion is defined as nil (like for example using an uninitialized variable for dispersion) the bug appears.

Simply throwing an error message saying that the dispersion is undefined would be a good solution, imo :)

Updated by Inkompetent over 5 years ago

I decided to test how spawned artilley reacts to the dispersion, and it works exactly like non-spawn artillery. As soon as dispersion is set to 'nil' the rounds never impact without any thrown error message.

Updated by Headspace over 5 years ago

I guess this begs the question as to why anyone would set dispersion to nil. It was never documented as being a compatible parameter, although I will clarify that in the documentation.

Dispersion starts out with a default value and needs to contain a real number.

Updated by zGuba over 5 years ago

Hmm is there any default value?

Updated by zGuba over 5 years ago

  • Status changed from New to Feedback

Updated by Inkompetent over 5 years ago

The reason I discovered this was that I had renamed variables where I initialized them. I did however fail to rename them where they were used to set the dispersion, ending with the variable sent as parameter to BIS_ARTY_F_SetDispersion to be uninitialized. Took me nearly two days to figure out. Since it didn't give me any error it took a long while before I looked there.

Would just be nice if it gave a "blablabla is Nil. Expecting Number" error message, since I would have found it in 15 seconds instead in that case. I'm just happy if others don't get to suffer from the same exhausting bug-hunt as me :)

Updated by Fireball over 5 years ago

  • Status changed from Feedback to Assigned

Thanks. Hope you will be heard.

Updated by kju over 5 years ago

  • Due date changed from 09/17/2009 to 12/17/2009

Updated by Fireball about 5 years ago

  • Due date changed from 12/17/2009 to 12/27/2009
  • Status changed from Assigned to Feedback
  • Reproduced by another DH user set to No

Still an issue?

Updated by kju about 5 years ago

  • Due date deleted (12/27/2009)
  • Status changed from Feedback to Expired

Unfortunately no feedback. Please reopen if still an issue and provide fresh info. Ty.

Also available in: Atom PDF