Reinstalled Arma on new PC but the problem is still live.

It was vest and uniform. Backpack and headgear was not effected.

That already is added I believe @Zaco_Kick
Still surprised this hasn't been done yet tho, Zeus needs more modules and the community would gladly supply

Instead of the enter key for search, maybe dedmen can talk about adding this https://steamcommunity.com/sharedfiles/filedetails/?id=1908099028? there's gotta be a reason why this isn't base game.

Confirmed, thank you for the repro.

In T85234#2201955, @gardonw wrote:

Not sure if this helps but when I ran a Altis Life server we had this issue for multiple years and we called it the "nexus bug" because the bug was introduced with/or close to the nexus update. A players gear would become invisible for all other players except for themselves, and if I recall correctly this issue occurred when a player switched seats in a vehicle (I don't remember if there has to be other players in the vehicle or not, and the issue didn't always happen so there has to be some other contributing factor). We ended up adding a button that "refreshed" the players gear as a temporary fix while waiting for an official fix. "player setUnitLoadout (getUnitLoadout player);".

I only updated my card after it happened and i rolled back and uninstalled my driver completely and reinstalled

Not sure if this helps but when I ran a Altis Life server we had this issue for multiple years and we called it the "nexus bug" because the bug was introduced with/or close to the nexus update. A players gear would become invisible for all other players except for themselves, and if I recall correctly this issue occurred when a player switched seats in a vehicle (I don't remember if there has to be other players in the vehicle or not, and the issue didn't always happen so there has to be some other contributing factor). We ended up adding a button that "refreshed" the players gear as a temporary fix while waiting for an official fix. "player setUnitLoadout (getUnitLoadout player);".

Of course, I can create simple marker via something like

Its a known issue. I think it'll be fixed by next update

Thank you for sharing how you fixed the problem!

Yes a wireless G933 logitech gaming headset which uses a USB dongle

All right I will add it here even tho I feel noone reads this but if it can help somebody it would be nice. The best solution for me overall was that I just created new profile to Arma 3 root folder by using this command on launchers commandline. "F:\Steam Games\steamapps\common\Arma 3 -profiles=Profiles" This will be the command wich makes new profile that then it's not needed to run your profile from C: path... Also copied my edited missions to the main root folder FROM C:\Users\Edizon\OneDrive\Asiakirjat\Arma 3 <--I also think that when I linked my computer to OneDrive it started causing alot of these path problems. But this I feel was my issue.

For a SAM systems it works too

You can use more the one truck, but you needed to use your seat belt. Your tank can to flying to the sky.

UNABLE_TO_INIT_DXGI this could be graphics related. Have you recently updated the Graphics card drivers recently? If not update them, if yes ten try to roll them back to an older version if that helps.

Looks very much like a "won't fix"
always handling mouse clicks as mouse hold's was done intentionally because that makes more sense to the average player

This was not a duplicate of that ticket btw...

Yes, it's the contrary!
It's easy to notice that keyboard action (up/down nose, any binding) has not the same efficiency than joystick.
Perhaps the rolling actions garble the demonstration, on the video, for a same displacement climb/dive of the simulated stick (display: I know it's just a proof that player is actuating the command), the joystick is far more efficient (climb dive rate)
And I can add that's also true for the poor efficiency of the mouse (again for pitch/roll).... At the point I bound a key for immediate "pitch up full simulated stick", avoiding crash in recovery maneuver.

STEPS TO REPRODUCE

Unfortunately none. There is no reliable way to reproduce that.

Profiling branch 2.04.147757 https://youtu.be/J0HjlPaaMnU

In T127572#2201480, @greenfist wrote:

Hi Pi, no, this was fixed in November and I can confirm it still works in the current stable build.

I tried switching hardware. GPU RX 580 to RX 570 and PSU from old 530W to new 750w. did not help...

First of all, this was a bug and it`s been fixed a long time ago.

Hi Pi, no, this was fixed in November and I can confirm it still works in the current stable build.

Reviewed and fixed in SGD internal build.

Thanks for making this report and can confirm the details above are correct.

Works in the latest perf. build.

Yeah, this will never be addressed. Maybe Arma 4 will have this issue solved. In 2038?

Ahahha damned that why i see some dev make script that save stuff, clean stuff, get back stuff each time they go in or out from a vehicle ahahah

@Nark0t1k: I have reported this in 2015 - any questions? :D

Damned ... 2 year later i'm so suprised to received a email telling my this bug isn't fixed yet...

In T85234#1833026, @reekoj wrote:

still happening on latest branch

Still cannot reproduce on dev nor latest profiling branch

rev 147746 https://community.bistudio.com/wiki/getTextureInfo

Related to T150571.

i have now tried changing the parameters tab with the number of core avaliable, the bulldozer tab, memory limit, hyper thread and large page support with no change still the same error, i have played the game for over 500 hours without an issue till now

It is just crashing randomly I will try tomorrow changing my GPU. Maybe it's dying? running on Sapphire Radeon RX 580 nitro+

From google translate^^

It was not the quick access keys wich I thought it would be. I realized it MIGHT have something to do with my profile. Because I think while I am in game and try to bind some buttons. This crash might also happen again... crash after crash... this is getting on my nerves..

Closing due to age

Just tried to reproduce the issue in 2.04 but couldnt, please add reproduction steps.

fixed awhile ago

rev 147764

Create one ticket for each issue.

Closing due to age.

Still an issue in v2.04.