The hammer also does a jab/stab animation rather than a swing.

This should now be resolved via the Steam configuration, so no game update was needed.
(Steam client was recently updated to include a fix to a many year old glitch that had this side effect for Arma 3.)

Some of the other angled Fortress parts seem to be slightly off as well, for example Fortress Wall (Outer Corner, 50 deg) is off by 3 degrees.
I'm not sure with the other ones but the severe obtuse and acute angled fortress parts are more noticeable.

Cannot reproduce.
Mi-2 flies as expected, checked in both Standard and Advanced Flight Model.

I went through all the assets in the list, checked the load/mass of the items which are in the assets, listed them and also cobbled together a list of suggested maximumLoads based on comparable sized already existing assets by BI.
Whilst going through that it also came to my attention that a lot of the crates are comparatively overfilled when looking at the maximumLoad capaticies of similar sized vanilla assets.
Nevertheless, as the content is hardcoded it should be no issue to set the maximumLoad over the filled capacity.
This should only prevent players from putting items into the crate unless the current load is lower than the maximumLoad.

Solution works for me too!

Note: I'm not a dev.

Can confirm - worked for me too. Thank you for posting the solution.

And by the way it's the same for the Type 63...

SOLUTION: 1) open steam console with WIN+R type steam://open/console

2. in steam console type this command: testappcloudpaths 107410

ok thank you. These still a big problem have little more to publish or update

Cloud access is disabled on steam side, not our fault. We didn't do anything.
We'll get in contact with Steam and see what they can tell us...

Hello Dedmen , Do you think the error came from steam? I asked support, they told me that it came from arma 3 and that they cannot do anything .

This doesn't confirm the "steam update broke it" theory.

Yep, the two might be connected

Same Problem for me , since the May 18 . I have désinstaled all game and steam , But the problem persist . No one know the solution ?

In T158403#2192729, @Socrates wrote:

In T158403#2192726, @dedmen wrote:

"Since the DLC came out" or "Since the last Arma update 2.04 came out"
when exactly did that start? So far it doesn't seem to be caused by Arma.

It is tied to recent Steam update. I guess they changed their Steam Cloud API and Arma needs to update it too.

Steam support won't help me, they keep refering me to Bohemia's support.

In T158403#2192726, @dedmen wrote:

"Since the DLC came out" or "Since the last Arma update 2.04 came out"
when exactly did that start? So far it doesn't seem to be caused by Arma.

"Since the DLC came out" or "Since the last Arma update 2.04 came out"
when exactly did that start? So far it doesn't seem to be caused by Arma.

I have the same problem. I had it before 19th May when i was on Steam Beta branch, but since i opted out of it things became good again. Until today.
Error started appearing today again, i guess this Steam Beta update moved into their stable Steam branch.

I have the DLC and get the same problem. Can't update any of my S.O.G. missions for anyone anymore. Hope this gets fixed soon.

I don't have the dlc, get the same problem, tried reinstalling entire steam and arma, restarted modem, disabled firewall, nothing helps.

Same issue and I am also not opted into Steam Client Beta. I have verified all files on both tools and Arma 3 and yet the issue persists. I have tried forcing an update in Steam but none are available in case the issue existed there.

If the ATGM in use is the Malyutka this could be related to the bug I reported yesterday wherein the AI does not fire the AT-3 at all.

I'm having the same issue and I'm not opted into Steam client beta.

Confirmed this is present in the Editor with just SOG PF running.

in the config files for almost all sog helos:
configfile >> "CfgVehicles" >> "vn_b_air_ah1g_04" >> "HitPoints" >> "HitEngine1" >> "name"
has the same string as
configfile >> "CfgVehicles" >> "vn_b_air_ah1g_04" >> "HitPoints" >> "HitEngine" >> "name"