synddd: well it seems that closing your ticket as related to this was fault and sorry for that. We're trying to do our best for wide community satisfaction(just because community is strongly helpful with giving feedback and thanks to you all for that) but you have to know, we are still a people like anyone else and even we can make a simple mistakes. So please be patient and I'm going to tell about this fact to someone who is in charge with this kind of bugs(PhysX related)

have a nice day anyway ;-)

Is this task still actual and reproducible? We played many long MP games (for more than a hour) and everything seemed to be fine

was already solved in the past

Is this task still actual and reproducible?

Can someone give me a feedback? I did some modifications around and now players can see which items are currently in DnD phase and these items can't be picked up(even with RMB)

In fact.. We're working on a new stable release build which could be distributed this during week

Well ok, I will take a look. But Does somebody have a clearly and "less time consuming" repro than: start server, connect some players and wait for crash? It would be very useful.

this issue could be related to http://feedback.arma3.com/view.php?id=4372 which has been already patched. Please can someone re-test it and give me a feedback?

DEV. 110838. [ADDED] new scripting command everyBackpack. Usage [everyBackpack "crateName"]

hurray... so I'm going to assign this issue to our moderators and they will decide if we will able to close it as Resolved

I guess that it was the same problem as http://feedback.arma3.com/view.php?id=4372 which I fixed yesterday(DEV version). So please could you update to the latest DEV ver and try it again?

Samatra: yep, your idea is not bad, but I can't decide it. After distributing my patch and testing main issue functionality, I will reassign this task to our SandBox designers so they can take a look and make proper decision

I have just assigned this task to our Sandbox design director.. he is the right guy to say If I will implement it or won't

DEV. 110837 - main issue has been fixed (spawn and death loadout match)

about primary and secondary weapons commands - in fact, they work exactly as they have been designed. But you have to realize that the game logic throws away primary and secondary weapons right after death, so you can't reach primaryWeapon name just because the dead soldier has no item like that. Only handgun will stay in soldier's inventory when he die

I know.. that's why I said try it on a DEV version. We have to be sure that it has been really fixed and right after we can merge it also into "Stable"

This issue has been fixed yesterday and was already merged into the latest DEV version, so can someone give me a feedback if my fix is really fix or miss-shot? ;-)

should be already fixed. Can someone confirm it?

Yes.. our distribution pipeline works this way: Each member has some assigned issues and when he fix a concrete one(at least when he think that he has fixed it ;-) ), He will propagate patch to QA and community (yes, you guys) and if QA nor community don't break to patch, so developer mark issue as fixed and patch will be listed into next stable build. So the latest stable was last week, but in that time I wasn't sure if my patch helped.. that's why we decided to did not propagate it into latest stable

It could be because of a patch which I added into DEV version yesterday. I had 100% repro before that patch and now the number has been reduced down to zero :-)

I already have 100% repro, so going to fix it..

duplicated. See: 0004143

As Terox said, it is because of a mess within connecting A3 Alpha users and A3 Alpha - Dev users. Today we have already distributed a new DEV version including a modification which DO NOT allow to cross-playing between DEV and Stable(default A3 Alpha) users. So now DEV users can't connect to a A3 Alpha-stable version and vice versa. This limitation has been needed because of a fact, that there can be a huge differences in these two sub-distributions (different game versions, data, etc.) which can have(and obviosly already have) an harmful effect on a bug issues clarity

given repro is not as clear as we can reproduce it

I'm out of the office right now. But I will take a look on it tomorrow. thanks for repro

Sorry, but unable to repro this task. Could you provide a concrete - step by step - repro? I tried this:

• open editor(map Stratis)
• place Blufor->Medic
• preview mission
• open gear
• DnD Binoculars from its slots into backpack
• DnD them back to a proper slot

everything seems to be ok

Where do you get this behaviour? In single or multiplayer? And is this task still reproducable?

We have distributed the new stable version which includes many MP fixes, so please can you tell us if your game is still crashing?

It seems to be fixed.. closing

We already know about this bug. Fix has been propagated into DEV build and will be delivered to you soon(maybe tomorrow 14.3.2013)

thanks for reporting and attaching really excellent background files

should be fixed in the latest stable and also DEV

D3D Error - DXGI_ERROR_DEVICE_REMOVED means that video drivers crashed. Probably due to wrong instructions from A3 engine. The problem should not be only about a certain graphics card, but the whole HW configuration. We're trying to collect further information leading to fix the problem

DEV. 110902

[ADDED] now user can register list of compatible items through class compatibleItems and its sub classes. usage:

class CowsSlot: CowsSlot
{

class compatibleItems
{
  optic_Nightstalker = 1;
  optic_tws = 1;
  optic_tws_mg = 1;
  optic_aco = 0; // <--- inherited from parent and zero value means that given optics will be discarded
  optic_ACO_grn = 0; // <-- same as optic_aco.. value=0 means ACO_grn will be discarded
};

};

so now you have two ways to set list of compatible items - the old:
compatibleItems[] = {"muzzle_snds_L"};

and the new one.

P.S.: We're planning to allow modify inherited arrays in config like myArray[] = {-unwanted item} but it will take some time

should be fixed since A3 DEV version 103042 and greater. Will be distributed at night or tomorrow. Please update A3 DEV from steam after this date and re-test it again

should be fixed since DEV. 124414

We already distributed a new stable.. so can someone confirm if this bug has been successfully fixed?

I have just added some code which should fix this task(since my changes I have been unable to reproduce it anymore), so as I guess it will be distributed into DEV version at night. Unfortunately stable is locked so the patch will not affect it. Please try it tomorrow and let me know

zeko: thanks for a script.. I'm going to try Jedi's version (cause it is a little bit shorter :-) ), but the key information is that I'm working on..

ok.. I've got the 100% repro. thanks to all

Jedi: I am a quite "slow" so sorry for that :-) but I don't get it. So just for sure: your repro is:

• place two playable units into editor with removeAllweapons in initialization line
• place some additional gearbox(for getting some weapons after removeAll script)
• start MP session with two joined players

after start:

• now in a game there are two soldiers with no weapons
• rearm through ammoBox
• disconnect and reconnect with one of them

and the result should be no magazines stored even into the player who is still connected, right?

oOJedi0o: please.. could you prepare and upload "minimalistic" version of your mission script in which the problem will be still reproducable? It could be very useful for us. Anyway gear and especial its MP part is still in progress, so please take my personal apology for inconvenience.

I was solving this issue a year and half ago but can't remember if it was successfully solved or wasn't. I guess that it could be something with "removeAll" sorts of commands like removeAllMagazines, removeAllWeapons, etc. Does your script contain some these?

This task seems to be familiar with another ones which were solved last week. So please can someone try given repro and give me a feedback?

Can someone reproduce this issue?

reassigned to Astaroth, please test it and close when it is already fixed

Already fixed.. or have not?

should be already fixed.. can someone confirm it?

this issue is not related to a concrete mission at all. Neither A3 profiles, or HW configuration. Main problem is in MP implementation of a new gear system which is still in progress(let's say >90% is done in SP and +-70% in MP). So beg my pardon for that and stay tuned with DEV distribution. We are working in 14days milestones and the next one I will be focused on gear MP

Our big target in Multiplayer code is to solve proven or even possible duplication of items which represents a huge pain in loot based missions. We're currently on a good way to solve that kind of problems once for all. Right after that we will take a look on Global/Non-global commands, but I'm strongly afraid about the proper solution due to a fact, that Global/local commands completely break the whole A3(as for OA,A2,...) MP paradigm

FIXED in DEV. 113226 (will be distributed tomorrow.. maybe:-) )

sxp2high:

I bet that it will be something with JIP. thanks for nice repro.. going to check it

sxp2high:
do you have a "step by step" repro? These kinds of bugs is usually about asking non-local entity from wrong client so It is very important to add entities owner to repro steps like (client1: drop something into crate, client2: pick item dropped by client1, etc.)

"But now the inventory list goes back to the top every time I transfer an item to or from a crate. Its as if the gsme is hittin the "Home-key" every time."

this behavior should be fixed since DEV 110387(currently not on Steam servers - will be updated soon)

can someone give me a feedback if this problem is still actual or is not?

everyone calm down ;-) Now I have to struggle with another one, but I going to add this task into my list

This bug was successfully fixed this week. Patch has been already merged into DEV version, so can anyone reproduce this issue in the latest DEV version?