Hello SaNdicek.
Were there any changes (software wise) on your computer prior to the issue appearing, which could cause the issue? Also, have you been experiencing the issue on both 64bit and 32bit executables? Have you tried switching to experimental version to check if it has any effect on the issue? And do you experience this issue with any other games other than DayZ?
Regards,
Geez

I get this error sometimes and i dont have gamemode active.

Hello MrDirtyDeedz and thank you for the feedback.
Your suggestion has been forwarded to the designer team and will be considered.
Regards,
Geez

Still occuring in last stable version...
This ticket is 2.5 years old , can you please have a look at it once for all ?
@Wulf @Adam @Dwarden @razazel

Thank you for the report. I see that you have mods enabled. Does the crash occur even with the mods disabled?

Thank you for the report. Some users have reported that disabling the Win10 Gaming mode fixed the problem, could you please try this and let us know?

Thank you for the report, we are aware of the issue and are looking into it.

In T127272#1657213, @Wulf wrote:

Hello.

Thank you for the report, we ill have a look at

As I understand it is enough to increase the distance between the head of the fighter and the sight. I hope to fix this old bug

Thank you for letting us know.

Sorry for LOOONG delay...

Hello SaNdicek and thank you for the report.
Are you using any other program that is using on screen overlays such as msi afterburner, nvidia shadowplay, fraps and similar? If so, can you try to turn everything off and then launch dayz only with no third party programs running in the background and let us know if that had any effect on the issue?
Regards,
Geez

Should I open a new ticket?

This also happens if you use stick+rag to make a fireplace (the rag disappears).

New video https://streamable.com/yo0wv
The same shrubs but observed from a different side (another location of the observer) behave correctly, however, driving a car straight ahead or rebirth of a character causes similar drawing of plant objects.

Have you tried this with a different unit/group if it does the same thing? Try creating your own unit attach it to a profile and test if the same thing happens.

No, the issue is still there (using the production, not development version).

The fix for this issue should be already released could you please confirm that the issue is fixed?

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

You can remove the parameter in the Launcher of the game.

I am unaware of how to remove said parameter. Linked page offers no explicit information. Excuse me as I'm not a technical person. Furthermore, after removing this parameter do I induce another crash, or use the old crash file?

???????????

Thank you for the information. WE will have a look at it.

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

You still haven't removed the -noLogs parameter.

Of worthy note, successful verification of game files and reinstallation has been attempted multiple times.

Good news @razazel Thank you

Please take a look at the attached sample mission, as it would answer all your questions so far.

According to
https://community.bistudio.com/wiki/landAt
1:
<UAV_x> landAt 3
should land the UAV at Selakano (quote: 3 = Selakeno Airfield) but it acts like
<UAV-x> landAt 5
and lands at 5 = Almyra Salt Lake Airstrip

@Wulf I can not trigger the error. this mistake comes with me indefinitely. with my colleagues this error comes constantly. another colleague does not have this mistake. we all play on the same server. since this arma mistake is already over 4 weeks. it annoys very much on duration.

Now I tried this in last game version (1.81.144040) and the first problem persists. Game is not modded.
No show items from enemy uniform at top of the hud (only weapon magazine). And of course I can't use it, only after move items to vest or ground and give back to uniform, yes, it will be work.

I already did that, and the mod'ders insist that the handling of UAV autopilot scripts are done by BI.

Found anything from my report log @Wulf, just curious.

@12horstschlemmer - I am not talking about the report in general or the basic.rpt, but about the .rpt file in your reports and dumps. Compare it to your colleagues rpt before you start accusing someone, there is something wrong with the file, that is why I asked you to trigger the crash and reupload the Arma report.

Seems like the issue was already fixed in our internal build, you can await a fix with the next update.

Video of the desired behaviour as it occurs on a typical cargo HQ building: Land_Cargo_HQ_V1_F

@Wulf this is the full arma report log. It's sad that you can not work with your own Arma Report Log. and want to push the mistake again the user in your shoes. FIX THE BAD MODULE INFO ERROR!!! Do not always refer to any Windows settings or arma reinstallation. These references do not fix the problem.

Hello Cid and thank you for the report.
We have confirmed the issue and it has been scheduled for a fix.
Regards,
Geez

Thank you for the report. but, could you please remove the -noLogs parameter? We can't see what was going on with the game before the crash. Also once you remove the noLogs trigger the crash once more and send us your Arma report. Here is how to do that.

Thank you for the report. This is a moded mission and not part of the vanilla game. Please contact the creator of this mission and let them know about the issue.

Edited my task, with new information, and a link to a new video recorded on Malden

Should be fixed now in the Dev Branch

@12horstschlemmer - You have an incomplete rpt file I can't see your setup and what is going on before the error occured. Please reupload the report whith complete rpt. This time into your own ticket not here.

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

For now, no new info I am afraid. We are working on it and looking for other issues that the update caused along the way so I ask of you for a little bit of patience. Thank you.

Hello. Please write your reports in English.
Reward "zero casualties" works fine for me. It´s necessary to don´t die. Anyone from your team needs to be without death. Reward is cancelled once one of your teammate is killed.

Hmm could you please send me the script you are using? By default you can't attach chemlights to the characters, you can only throw them, since this was never intended so I am not sure if we can do anything about this.

This mission is long and I don't plan to play it again and I assume that it does not happen often that the APC gets stuck so badly that it fails to continue driving. But obviously it can happen.

I will have a look at it. Though it would be good if you could revert the mission and test it if the issue persists even after reverting. Otherwise it might just be a one time thing.

Thank you for the report. Looking at your video this seems to be a modded map. Could you please recreate this on one of our default maps and create a video? Thank you.

I take it that the issue was resolved?

Great! Thank you for letting us know.

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

Hello mostafa1379.
As Rule.303 has mentioned, pistols cannot be put into plate carriers or holsters with flashlights attached. This is a design choice, not a bug.
Regards,
Geez

Hello FRIGER and thank you for the report.
The issues with character and AI clipping through various objects are going to be addressed with the new player controller that will be implemented in the 0.63 version. As for increasing the map size, currently we do not plan to increase the map size as it would have negative impact on the overall performance. However, it is possible that there may be some new locations added to the map as it is still being worked on and is not finalized.
Regards,
Geez

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