This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

This might be because the server your on didn't enable reviving or has different requirements for reviving. When a Zeus server is created, it usually doesn't enable reviving. It has to be changed by an admin.

I tried reinstalling but the error still persisted

Yes, even when they are disabled

We need Arma reports so that we can see what is going on. @RaisinBread does the crash happen even with mods disabled?

Dále, transportní vozidlo TEMPEST nemá neprůstřelnou ochranu(neprůstřelné sklo ani pancíř který odolá náboji 14,5 × 114 mm) osádky vepředu, pokud vím tak vozidlo TEMPEST vychází od reálného vozidla KAMAZ Typhoon a tohle auto disponuje touhle ochranou viz. se můžete dočíst zde https://en.wikipedia.org/wiki/Kamaz_Typhoon a ani neposkytuje ochranu minám i přes svou konstrukci podvozku do tvaru V,

I have the same issue. But i noticed that the game crashes with this error only when my pc is quite loaded and i have to fly for long time. In some random time the game get crashed with 409th error.

Hmm, if it is Battleye then I am afraid we can't do much from our end, your best bet would be to contact the Battleye devs.

Thank you for the report. I just tested the Edit Terrain module with Enable Damage disabled and the map building didn't receive any damage or got destroyed.

Yes, just downloaded one of the latest scenarios from steam workshop, attributes are displayed correctly in "steam subscribed content" (see screenshot 1), but when I place it in Arma 3\missions folder where all my own scenarios are placed, attributes are displayed incorrectly (see screenshot 2). Seems that I am the only who has this problem because I was looking for similar reports from other people but didn't find anything. If you need any information about my PC configuration or log files or I don't know what else I am ready to provide it to you.

@Wulf I have done everything listed there (exept contacting) but i have tried my best, its blocking a file in system32 and it ONLY happens while battleye is on, and there is no section dedicated towards it

Thank you for the report. We will ahve a look at it.

Thank you for the report. You have encountered the 0xC000009A - STATUS_INSUFFICIENT_RESOURCES error. This error may occur when you have an obsolete version of the BattlEye anti-cheat software or after an upgrade to Windows 10

Should the issue reoccur please let us know. Closing for now.

And a happy New Year to you as well.

I experienced this playing on an unmodded, unofficial Warlords server yesterday. The misbehaviour was sporadic, by which I mean it works as expected one minute and then stops working for a while, and it might eventually return to normal.

Thank you for the report. Could you please upload your Arma report here? Here is how to do that.

Thank you for the report. Have you tried veryfing integrity via Steam?

I have the same issues but crashed even in virtual arsenal

Thank you for the report. Just tested a Scenario and attributes all seem to display correctly. Are you sure that it is happening to other scenarios as well?

Thank you for letting know dedmen. Closing.

Thank you for the report. I see that you are using some mods it is possible that even the mods might be causing these random crashes.

Thank you for the report. Does this happen often?

Hello.

Thank you for the report. Could you please let us know on which map and where exactly you tested this behaviour?

Thank you for the report, we will have a look at it.

Thank you for the report, we will see what can be done.

We will just close it then.

Thank you for the report. Could you please upload your Arma report? The rpt might not be enough. Here is how to do that.

Thank you for the report. Please upload your Arma report here. Here is how to do that.

Thank you for the report. In your rpt before the game stops you receive "ErrorMessage: DX11 error : CreateTexture failed : E_OUTOFMEMORY" .

Thank you for the report. Does the issue still occur? I just tested the AI on the Official Warlords Servers and they work for me. I tried starting a new MP game I JIPed and the AI seems to be working fine as far as I can tell.

SOLVED BY TYPING IN C:\Program Files (x86)\Steam\steamapps\common\Arma 3 -malloc=system IN START OPTIONS OF THE GAME IN STEAM LIBRARY

For example in the uniforms that exhibit this behaviour, the hithands hit point position in the array is matched to the head_hit hit selection value... in all the other uniforms it is matched to the hands hit selection

It is the inconsistency in the *ordering of the hit selection array*. I do not know whether this has an adverse affect which is why I asked for confirmation of whether it is actually an issue.

https://feedback.bistudio.com/T123355 would imply that the caching is done independent of whether you pass code or string.

which has issues

Exactly the same issue over here.

Note that all vanilla ARMA 3 ghillies have the same issue. Tested in the Arsenal as well now

You reported this as an ARMA 3 bug.

I confirm it's still present on 1.88. It's happened to me twice before in previous versions, and I just had it happen again. The previous comments might be on to something. I was also in a vehicle with other players and not doing anything when they said my clothes and vest disappeared. I could still see them. 5 minutes before it happened, I had switched from driver to passenger, in case it has anything to do with it. But that was 5 minutes before...

Another year, another rabbit told to stop before reaching the road. Confirmed to have survived 2018 as well.

@Groove_C DIfferent issue. This exact bug is confirmed fixed.

No updates on this?

No mods used.
No script errors.
With database.
With 2 HCs.