When adding items via "call BIS_fnc_addVirtualItemCargo" in a custom Arsenal, any bipod added will not be available for players through the Arsenal. It is as if bipods aren't whitelisted at all. Testing other items being added manually does work (aka Silencers, Scopes, IR pointers, etc).
Description
Description
Details
Details
- Legacy ID
- 508263431
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Category
- Virtual Arsenal
Steps To Reproduce
Step 1: Place an object (ammo crate usually). Place: null = [this] execVM "virtual_arsenal_init.sqf"; in the init line of the box.
In virtual_arsenal_init.sqf , put:
_crate = _this select 0;
["AmmoboxInit",[_crate,false,{true}]] spawn BIS_fnc_arsenal
_availableItems = [
"Item_bipod_01_F_blk",
"optic_Hamr" //to show that a custom weapon attachment can be added.
];
[_crate,(_availableItems)] call BIS_fnc_addVirtualItemCargo;
Additional Information
All other custom items appear to work fine.
Event Timeline
Comment Actions
I should add to the notes, once the first two steps are done, preview the mission. An "Arsenal" option will appear on the object you placed. If your weapon supports bipods, the bipod does not appear. If there is a bipod in the crate then:
[_crate, (itemCargo _crate(+ _availableItems))] call BIS_fnc_addVirtualItemCargo
Will add the bipod from the crate but not from the list.
Neither "Item_bipod_01_F_blk" or "bipod_01_F_blk" work (Item or no Item, regardless of bipod type).
Comment Actions
hm? in 1.90 bipods and some scopes etc. are always available, even if there are not whitelisted??
is that a workaround? A feature or a bug??