Hello, It seems that your crashdump got corrupted somehow.
Could you try to play again and if you happen to crash again, add a new crashdump?

Happy to hear it worked out for you.

Hello, we checked your crashlog seems the crash is happening in combination with XAudio2_7!LEAPCORE, what ever that might be.
Are you using a USB (Wireless) headset?
If so could you try playing the game without headset plugged in or with a wired headset to see if thats the cause?

i change the game language in Steam to English. but it dosen't work. crash report sitll show Culture: zh-CN UI Culture: zh-CN.
so as this method : %localappdata%\Bohemia_Interactive Delete all folders that begin with arma3launcher.
i think this launcher is hopeless

Ok I got it.. I can see where its crashing, but not why.
It doesn't make sense.

These are good captures
Sadly the first 4 are still stable branch, looks like its all the same as the last one I checked. But cannot really see whats going on.
And the new ones.. ugh.. you renamed arma3serverprofiling_x64.exe to arma3server_x64.exe, That just turned this from easy to really annoying

More crashes recently

I'm talking about however it tracks ammo could be used to modify the fouled-up way that magazine weight is calculated.

Thank you for your investigation and giving the solution.

Ah I thought you said it crashed when you wanted to start the game.
Well try this then:
press Win + R and type this and press Ok:

%localappdata%\Bohemia_Interactive

Delete all folders that begin with arma3launcher.

The load value of inventory things is not the weight of the item it is like volumetric weight, so it is not as simple as dividing max value and value remaining.

steam always star ARMA3 form launcher. but launcher crash before it show up

but i can't even make it to the luncher

Culture: zh-CN
UI Culture: zh-CN

thanks for the reply
unfortumately, it didn't work

Can't be replicated.

Both M60s are firing but due to a engine limitation it's not possible to have duplex tracers on a machinegun turret on a helicopter (UNLESS we make them as gunpods, which means no gas fx and no shellejection fx which are more important for these guns than say the external swivelmount m134s).

We switched to profiling branch and it wasn't crashing for a couple of days, but today it did again

There is a script that sets simple object params from vehicle config, you can compare that. AFAIK the data was gathered manually by one of the designers

Can you post new crashlogs with the USB headset removed?
If the issue isnt related to the headset we might be able to see something new

Found a solution: After digging online installing Microsoft Visual C++ 2008, 2015-2022 seemed to be the fix. I’m unsure which one was the actual fix but I installed them all.

Did all the steps from https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit#0xC0000135_-_STATUS_DLL_NOT_FOUND. I even tried going to back to a restore point on windows from 3 days ago. Nothing.

The solution is presented on the following StackOverflow question:
https://stackoverflow.com/questions/50970449/error-800700c1-in-instantiating-an-object-for-microsoft-office-interop-excel-a
Deleting the file "C:\Program" fixes the issue.

The modified gas block on SOG:PF M14A1 is solely to have the sling appear attached to the proper swivel - real-life M14A1 uses same gas block as the regular M14, and the different part on the SOG model is in fact the clamp mechanism of M2 bipod, which fits both variants of M14 rifle. Solution number two (separate bipod entity for M14) would be preferred.

Since patch 1.2 added M14A1 rifle, it might be interesting idea to allow it to use same optics as the M14/M21. That's because M14A1 was also used in a sniper guise in Vietnam. Used in very limited numbers by LRP company of 4th Infantry Division these rifles ditched the heavy M2 bipod (replacing it with a M16 clamp-on bipod), and (as evidenced by one surviving example) had the front-grip assembly removed, with a more traditional sling swivel appearing in it's place. They still had the pistol-gripped stocks and characteristic muzzle devices.

Verifying ArmA in Steam, reinstalling DirectX/Visual C++ and running the File Check Tool did nothing. However, I ran the 64 and 32 bit version of Microsoft Dependency Walker and got a ton of errors for several hundred DLLs for the ArmA EXEs. Same results for ArmA 3 Tools and the Publisher EXEs.

Regarding the sight appearance, it's something that people requested when SOG was released. IMO it should stay.

I have to disagree. Yes, it does look iffy (especially on the Garand), but it's what people wanted when the DLC first came out. Current version, despite the looks, performs more like real-life sight - until devs implement some other solution to the ironsight problem it should stay.

removed usb audio controller , deleted razer snapsyse service still occurs

Change the launcher language to English. If it still doesn't work, press Win + R and type this and press Ok:

%localappdata%\Arma 3 Launcher

anyone? help!

rev 149726

Hello can you try the steps posted here:
https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit#0xC0000135_-_STATUS_DLL_NOT_FOUND

can be closed?

can be closed?

Added a couple of trivial example missions with Altis and CamLaoNam bridges. Just start the mission and watch. Quad bike swerves violently to the right, about 2/3 of the way across each bridge.

If it's decided to let the command accept a number value rather than just on/off, it would be useful to also allow a "whatever the config value is" number in addition to the specific modes, e.g. -1. This would make it easy to let type-agnostic scripts switch between config and override values without needing to know the config value for every potential turret.

That is unfortunate but thank you very much.

Unfortunately, it is not possible, BI function will always use weapons assigned to gunner and this gun is not a pylon so it can't be reassigned.

Thanks for the answer,I have solved the problem.

Yes that works great. Thank you for the clarification.

Sorry for the inconvinence, it's related to the Huey fleet update. BIS_fnc_UnitCapture does not save which turret fired the weapons, during the playback it always tells the vehicle gunner (gunner _vehicle) to fire the weapons. After the updates the vehicle copilot is considered the vehicle gunner (can be recognized by the icon in 3den).