[Window Title]
bad_module_info

[Main Instruction]
bad_module_info has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]

I appears that the special character in the mod path is preventing the game from properly locating the mod folders.

When Murray launches the game with any mods loaded they show up in the main menu as puzzle pieces, not with correct icons.

I have not been able to reproduce this crash event without Unsung 3.1b running. It seems that Unsung mod is the cause.

I would really like to know how to get rid of this content please. 12 GB now as the content exist in two places...

More logs...
https://www.dropbox.com/s/wroplxvbhw9ed9r/Arma3Launcher_Log_20160204T014226_HILL.zip?dl=0

That's the thing though. It doesn't list in the mods. I've already unsubscribed from the content via the steam workshop and A3 Launcher.

This evening, for no reason that I can discern, a Workshop download started again. 5.6 GB. I cannot stop or pause the download if the launcher is open and/or the arma3.exe is running. I have set Steam client to globally disallow downloading while playing and specifically when Arma 3 is running; no effect.

Do you need more logs? Every time I start the launcher it writes a .txt file to my desktop; I have lots...

We'll, the 5.6 GB workshop update finally completed so I have all this content I don't want and am not subscribed to.

Now, when I launch Arma 3 the Launcher perpetually says 'Checking for updates...' on the bottom.

In the Steam Client Downloads section Arma 3 Workshop content starts and completes in an endless loop.

Logs:
https://www.dropbox.com/s/vaxji10kmflrbcs/Arma3Launcher_Log_20160127T160522_HILL.zip?dl=0

After changing the description.ext parameter:
respawnOnStart = 1;
to
respawnOnStart = 0;
the problem was resolved.

Also noticed that the parameter:
respawnTemplates[] = {"MenuPosition"};
only worked for side WEST and not for EAST, CIVILIAN, or GUER.
I had to add specific respawn templates for each side.

I am unable to reproduce the issue running with no mods. I have narrowed the mods down to 6. RHS:RU, RHS:US, CBA_A3, ACE3, MCC, AiA Terrain pack.

I take it back. Seemed to work but, nope...

The issue is not dependent on switching sides just on re-entering from the lobby.

More rpt files uploaded.

Disabled the Steam overlay as per the Wiki suggestion.
https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0x00000001_.E2.80.93_UNABLE_TO_INIT_DXGI

Seems to have fixed it.

As much as Arma is community orientated toward modifications this should be a high priority. There shouldn't be a limitation on how many mods can be launched with the server.

Could you enlighten me as to what this mistake is? I have created this mission by porting an existing mission from Altis to Sratis. It was working fine and I was adding to the paramsArray in the description.ext when the crash started. Is it something I added to the description.ext?

Mission files uploaded.

I have narrowed the cause of the crash to be the presence of a mission in the mpmissions folder. What could I have done in the mission files to cause the game to crash when loading into a LAN host to edit.

Creating a new profile has resolved the crash.

New crash dump files uploaded.

Of course, I had intended to remove the param but forgot. New crash rtp files inbound in an hour or so. Dx-diag has been uploaded.

Related to this http://feedback.arma3.com/view.php?id=15983?
Also happens which static guns

Any chance this will be addressed in the next update?

@Fireball: I don't think that is specifically related to this issue other than it has to do with the zone restriction module.

To clarify a little; the zone restriction as set up per above does work after the player respawns now however, after multiple respawns (can't give exact number as it as the issue appears after a different number of respawns every time) the module stops firing. This happens for every player. Just take the mission I uploaded and play it on a dedi box. Keep having the module kill you over and over again, eventually it will stop working.

After 1.24 update I Loaded mission in the editor and re-saved. Uploaded to dedicated server. Issue still persists. The module seems to fire multiple times now but eventually stops working still. I got it to fire 4 times but in the 5th time it didn't fire.

This issue is not resolved. Zone restriction continues to have no effect once the unit has re-spawned.

Excellent! Thanks for the quick turn around on this.

An existing feature in A2. Simple wounding. Very much missed in A3. There is no reason this cannot be incorporated into the game. The feature should not be left to the community at large to implement as an addon to the vanilla game. It is expected of BIS to implement this feature as part of the game. The animations exist, the want from the community is expected. BIS, this ball is in your court as an expected feature; you have thought of it and planned for it. Finalize and release it.