Page MenuHomeFeedback Tracker

Adding virtual weapons to Arsenal throws an error.
Assigned, WishlistPublic

Description

Adding virtual weapons to Arsenal using BIS_fnc_addVirtualWeaponCargo with the "%ALL" parameter causes the Arsenal to throw the following error:

[BIS_fnc_baseWeapon] Class '%ALL' not found in CfgWeapons

The Arsenal still functions as it should but every time you select/reselect one of the weapon categories it throws the error again. All other categories are fine.

Details

Legacy ID
3731678602
Severity
None
Resolution
Open
Reproducibility
Always
Category
Virtual Arsenal
Steps To Reproduce

Put the following line in the init field for a box.
0 = [this, ["%ALL"], true, true] spawn BIS_fnc_addVirtualWeaponCargo;

Launch the mission and access the Arsenal.

If you go back to the editor and replace %ALL with a valid classname it works fine.

Additional Information

Using the other addVirtualCargo functions works fine.
BIS_fnc_addVirtualBackpackCargo
BIS_fnc_addVirtualItemCargo
BIS_fnc_addVirtualMagazineCargo

Event Timeline

mrCurry edited Steps To Reproduce. (Show Details)Jul 15 2014, 7:41 PM
mrCurry edited Additional Information. (Show Details)
mrCurry set Category to Virtual Arsenal.
mrCurry set Reproducibility to Always.
mrCurry set Severity to None.
mrCurry set Resolution to Open.
mrCurry set Legacy ID to 3731678602.May 7 2016, 7:00 PM
Bohemia added a subscriber: AD2001.Jul 15 2014, 7:41 PM

[this,["%ALL"],true] call BIS_fnc_addVirtualWeaponCargo;
[this,["%ALL"],true] call BIS_fnc_addVirtualItemCargo;
[this,["%ALL"],true] call BIS_fnc_addVirtualBackpackCargo;
[this,["%ALL"],true] call BIS_fnc_addVirtualMagazineCargo;

This worked for me on 1.24. Put this in your crates init and see how u go.

mrCurry added a subscriber: mrCurry.May 7 2016, 7:00 PM

Thanks oz but I think you missed the point of my report, it's only an error message, no actual error. The Arsenal works superb in other aspects but it prints the error message when used as designated by the documentation.

This only happens with allowFunctionsLog = 1; in description.ext so this is a minor issue on par with unnecessary log entries.

Apologies mrCurry. I was unaware of the allowfunctionslog =1 in the description.ext. Very handy to know. Cheers