Page MenuHomeFeedback Tracker

Problems looting ground items and vehicles involving Night Vision goggles and backpacks.
Closed, ResolvedPublic

Description

I have been unable to pick up backpacks and night vision from ground loot. Firstly, the night vision icon is not there, however the text is. When I hold left-click and drag the night vision space at the top right of the inventory is blocked or "red out", however the binocular spot is clear as if it's telling me to place them there. When I try both spots the night vision does not move or equip at all. Right clicking also produces no solution.

However, when the night vision is placed in a backpack and the backpack is in my inventory, then I can equip night vision goggles to the binoculars slot, but the faded out binoculars in the empty slot is gone, yielding the binocular slot completely void of any icon. When I mouse over the slot it will bring up a tool tip signifying that there is night vision in the slot by text. Night vision operates properly by pressing the default "N" key at this point, however there is no night vision physically visible in the game on my head. I have tested this with other players as well and they couldn't see it on my head either.

As for the backpacks, I can not loot them either by dragging to the proper slot or right clicking UNLESS it has been looted off a player's body. That means I can't loot it off the ground or from vehicles properly. However the slot itself shows up properly when selected while dragging.

This has happened on both Wasteland servers and my friend's server, however when I try it on the editor via preview or making my own internet server it works perfectly.

Details

Legacy ID
2240815928
Severity
Major
Resolution
Unable To Duplicate
Reproducibility
Always
Category
Inventory
Steps To Reproduce

Create a new mission after creating player, create a new "helipad (invisible) with the following script:

            // Spawn items
            _loot = "groundweaponholder" createVehicle (getpos _this);

            _loot addWeaponCargoGlobal ["arifle_MX_f", 1];
            _loot addWeaponCargoGlobal ["srifle_EBR_F", 1];
            _loot addMagazineCargoGlobal ["30Rnd_65x39_caseless_mag", 2];
            _loot addMagazineCargoGlobal ["20Rnd_762x45_Mag", 2];
            _loot addItemCargoGlobal ["muzzle_snds_B", 1];
            _loot addItemCargoGlobal ["muzzle_snds_H", 1];
            _loot addItemCargoGlobal ["muzzle_snds_H_MG", 1];
            _loot addItemCargoGlobal ["optic_ARCO", 1];
            _loot addItemCargoGlobal ["optic_Hamr", 1];
            _loot addItemCargoGlobal ["acc_pointer_IR", 1];
            _loot addItemCargoGlobal ["acc_flashlight", 1];
            _loot addItemCargoGlobal ["NVGoggles", 1];
            _loot addItemCargoGlobal ["ItemMap", 1];
            _loot addItemCargoGlobal ["U_B_Wetsuit", 1];
            _loot addItemCargoGlobal ["V_RebreatherIR", 1];
            _loot addItemCargoGlobal ["V_TacVest_khk", 1];
            _loot addItemCargoGlobal ["U_Rangemaster", 1];
            _loot addItemCargoGlobal ["U_B_CombatUniform_mcam", 1];
            _loot addItemCargoGlobal ["H_HelmetO_ocamo", 1];
            _loot addBackpackCargoGlobal ["B_AssaultPack_blk",1];
            _loot setPos [getPos _this select 0,getPos _this select 1,0.00];

Then save as a multiplayer mission, create a new server and then the person that joins the server remotely will have the issue.

Event Timeline

Sab edited Steps To Reproduce. (Show Details)Mar 25 2013, 7:35 PM
Sab edited Additional Information. (Show Details)
Sab set Category to Inventory.
Sab set Reproducibility to Always.
Sab set Severity to Major.
Sab set Resolution to Unable To Duplicate.
Sab set Legacy ID to 2240815928.May 7 2016, 1:06 PM

I am experiencing this also, in regards to the wonky NVGs. It is a randomly reproducible bug, and seems to happen when I do this addItem "NVGoggles"; this assignItem "NVGoggles" as init script for a civilian unit. this bug is also commonly accompanied by the error message "a3\weapons_f\data\ui\gear_x_ca.paa not found". Not sure if it's directly related though.

Is this still the case?

Feedback timeout. Plus I haven't encountered anything like this recently.