Was able to play last night without issue. It appears to be fixed. TYVM.

When you fix this problem?
I have steelseries siberia v2 3.5(mm) jacks headset and i have this bug
Win 10 Pro 64bit
Memory 16 Gb 1600 Mhz
amd fx-8120 4.5 Ghz
msi 970 gaming motherboard
asus radeon hd7850 GPU
SSD Samsung 850 Evo 250 Gb+HDD 2Tb
it's impossible to play comfortably on 32bit client with 3fps bug, and on 64bit client with 16bit 48000 Gz audio settings

Ok, I created video (last game version, without mod).
I think, then this video show the problem sufficiently.

I tested this after the last hotfix, but I am not able to find any issue . Could you please test the issue with the current version of the game and if there indeed is an issue, could you please create a video?

The issue should be fixed on the dev branch.

Yesterday, we published a fix for the bad_module_info error. Please, try the game and let us know if the issues regarding this error still persist.

No, i'm using the vanilla game too.
The object is placed on a dedicated Server with the newest version of the game.

We just published a fix does the issue still occur? Also, have you tried contacting Neo Armagedon?

There is a new fix out. Could you please try the scouting mission if the issue still persists?

Please, create a video of the issue that you are having.

I just tested the mission and everything works as it should.

The fix is out. Could you please test the game if it solved the issue?

Thank you for the report. Please re-install .NET Framework 4 with the latest available version (currently 4.7 https://www.microsoft.com/en-us/download/details.aspx?id=55167)

Thank you LeonardoXD.
This is a known issue, which can occur on any server and the issue is scheduled for a fix.
Regards,
Geez

This should be fixed in our development branch could you please have a look and confirm that the issue is fixed? Thanks.

When you fix this problem?
I have steelseries siberia v2 3.5(mm) jacks headset and i have this bug
Win 10 Pro 64bit
Memory 16 Gb 1600 Mhz
amd fx-8120 4.5 Ghz
msi 970 gaming motherboard
asus radeon hd7850 GPU
SSD Samsung 850 Evo 250 Gb+HDD 2Tb
it's impossible to play comfortably on 32bit client with 3fps bug, and on 64bit client with 16bit 48000 Gz audio settings

FIXED BATLLEYE PROBLEM! battleye: client not responding.... 1.80 hotfix fucks us!

Here is the full errorlog:

Hi Geez, thanks to you and the devs for fixing TrackIR. Its a great addition to the Dayz experience. To bad now I just went to try it again I find my trackclip broken after 2 days of playing. None the less I'll order a new one. For the time being I noticed that I keep getting disorientated when it comes to the arms (of character) coordination compared to where I'm looking. Meaning that every time I raise my weapon it turns out to be pointing not where I expect it. I think this is because we use the circle cross hair as main aiming point but because of using the trackir it is detached from the character direction. My suggestion to resolve this is to have another crosshair that keeps visualizing where your character is pointed; i.e where you would point your weapon when you raise it. Do you think this would be possible? I think it would make playing dayz using some sort of head tracker/VR device more intuitive and pleasant. Regards Deacon!

Arma III ver: 1.80 vanilla
Open editor, Tanoa map by default
add a player
add any vehicle (mine was HEMTT fuel but that doesn't matter)
run preview
in debug console:

You should be able to get the files here:

Could you be a little more specific? Which weapon with 7.62? Could you please create a video of the issue and upload it here.

Thank you for the report. I am testing this command right now on the public build and everything is working as it should, no generic error occurs.

Thank you for the report. We are aware of this issue.

In T127403#1660319, @Wulf wrote:

Hello.

All the things you have listed are there and working.

This is awesome news, but none of these i found way how to use then :) , can you please help with that?
(We are talking about ingame GUI editor right?)
(not sure what it can be related to, but i'm on 100% sure that on my side (clean arm3) "undo" action do not working)

please try the performance binary from profiling branch , it contains multiple crashfixes

First. It means that you are missing all of those files. I am expecting they are needed for the game to run hence the fatal error.

We are aware of the problem that the last update of Windows caused we are in the process of fixing them.

All the things you have listed are there and working.

Your report contains old files from around July. Though your basic report shows 0xC0000135 - STATUS_DLL_NOT_FOUND.

Okay, so i have contacted Nvidia Support. They have referred me to what was apparantly a Windows issue. They let me set the 'Force WARP' option in DirectX. This solved the issue with Geforce Experience only giving a black screen, but ArmA III still gave the same error. I was then advised to roll back to Windows build 1703. Which i did.

As someone reminded me, this works with all laser guided bombs, namely: LOM, GBU, KAB and maybe others

Thank you for the report. Could you please send us your Minidump with any rpt. bidmp related to it?

Thank you for the report. We are aware of the problem and are working on a solution.

I will see what can be done. I I am going to suggest them that they should keep the old physics because of these time trials.

Thank you for the report. Are you using any mods? because, I am trying the model with the vanilla game in the Editor and I am unable reproduce it.

@redsky84 Oh. That is odd... I mean I am glad that you can play the game it just puzzles me a bit. Please keep me posted and if the issue doesn't occur again then I will close this ticket.

Hello Geez,
thanks for the info. As mentioned in the devs status reports we have to go a way to beta. My suggestion was based on the data we see (status box in experimental servers) and I think it's a possible way. Glitchers are players who ruin the fun of regular players and have a bad implication to the server they play.
So it would be nice to get rid of them as soon as possible. I hope we (players/admins) get a solution before beta comes.
Happy Christmas to you and the Devs.
Kindly
Tom

@Wulf - I will do this in the afternoon. Also I've got an update: After I've restarted the mission completely from the beginning, the problem did not occour anymore. I was able to play the whole cornerstone campaign without a single crash. Really strange.

@redsky84 - Thank you for removing the -noLogs. :) I see that you have a mdmp in your original report. But not in the one with the removed -noLogs. Try triggering the crash again and send us the report.

Thank you Spazzmo.
This is a known issue and it is scheduled for a fix.
Regards,
Geez

Does the game freeze occur also during the scouting missions received in the campaign, during the mission Gori?

Hello Cid and thank you for the report.
This is an issue we are aware of and it has been scheduled for a fix.
Regards,
Geez

Hello Cid and thank you for the report.
This is an issue we are aware of and it is scheduled for a fix.
Regards,
Geez

Hello theaussieck and thank you for the report.
This is a known issue and it is scheduled for a fix.
Regards,
Geez

Hello 766F69646565 and thank you for your feedback.
With the implementation of the new player controller and the other parts that are going to be included in the beta version it should no longer be possible to glitch into objects. However, we will note your suggestion and it is going to be considered.
Regards,
Geez

Interesting, could you please send us your most recent rpts right after the crash?

Hello lukCortezBR and thank you for your feedback.
Your suggestion has been forwarded to the designer team and will be considered for the future stages of development.
Regards,
Geez

Hello Lenita and thank you for the report.
Can you try to completely uninstall the GPU drivers on your computer and then install them again and let us know if the issue persists?
Regards,
Geez

Hello jedi_warrior.
Currently we are aware that only the polish UPC has the issue with IPv6 protocol, we had no reports of other providers having this issue, therefore we believe it is an issue on the providers side. However, we will keep investigating this issue. In case you know of players that have this issue with the IPv6 protocol even with different provider than polish UPC, please tell them to send us the information under this ticket.
Regards,
Geez

@Wulf I was hoping AnEnglishmanShels' solution would also solve the problem for me. I've completely reformatted and reinstalled my computer today. I've just finished completely updating and installing everything. however, I'm afraid this has not yet solved the problem, i'm seeing the exact same error every time i try to start the game. Both in x64 and in x86 versions... I'm at a loss here really.

This turns the helicopter into a suicide machine.

The tail rotor should be sufficient to change the flight path to the left and right at any speed. Limiting the stroke of the pedal at high speeds - serves to limit the maximum permissible changes in the angle of the blades at high speeds.
The blades of the rear propeller, first of all, compensate the rotation of the helicopter body from the main screw, its different modes and different permissible speeds.