BIS_fnc_effectFiredRocket is broken
New, NormalPublic

Description

BIS_fnc_effectFiredRocket is broken, likely introduced in the latest patch. Whenever firing a weapon that uses this function, anyone on the server with script errors enabled will see the message in the included screenshot.

In the context of the community I play with, this makes certain assets unusable. I'd greatly appreciate it if this were fixed, thanks in advance.

Details

Severity
Tweak
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
1709
Category
Error Message
Steps To Reproduce

Fire a rocket from a weapon that utilizes BIS_fnc_effectFiredRocket. In my case I was using an SPG-9 UAZ from RHS, and I've also confirmed it happens with FFARs from CUP's AV-8B Harriers as well.

Wulf added a subscriber: Wulf.Jan 2 2018, 6:51 PM

Hello.

Thank you for the report. I tested all of our launchers that come with the vanilla game and the error does not occur which means that the error is caused by modded weapons. Please, contact the developers of these mods and let them know about the issue so that they can fix it.

Thank you.

This is a BI issue.

In an effort to optimize BIS_fnc_effectFiredRocket, Bohemia inadvertently introduced a few script errors in it. The function may not currently be in use by any BI assets, but that doesn't mean that breaking the function isn't a BI issue.

Here's an image of the diff, compared from A3 1.74.142559 and the current stable release as of 2018-01-02 (https://i.imgur.com/I5tmn2s.png), the first issue that is immediately apparent is on lines 29/30, where a private declaration was added on top of the local variables, but not padded with a space on the right side. I imagine someone made a mistake, and the function was never actually tested after it was modified. I am unaware of whether or not there are additional issues that the optimization may have caused.

Wulf added a comment.Jan 8 2018, 4:24 PM

Seems like the issue was already fixed in our internal build, you can await a fix with the next update.