Page MenuHomeFeedback Tracker

Game crash on mission launch in multiplayer
Closed, ResolvedPublic


There is a new bug that causes a crash when starting a mission in multiplayer (after mission has been selected,players have chosen roles and you click continue in the map/briefing screen).


Legacy ID
Game Crash
Steps To Reproduce

crash happens when you click continue to start the mission

Event Timeline

HydroBIGBANG edited Additional Information. (Show Details)
HydroBIGBANG set Category to Game Crash.
HydroBIGBANG set Reproducibility to Sometimes.
HydroBIGBANG set Severity to None.
HydroBIGBANG set Resolution to Open.
HydroBIGBANG set Legacy ID to 535002309.May 7 2016, 4:13 PM

We need dxdiag and files from this folder for solve your problem. C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When package will be smaller than 2,097k, so you can attach here. When package will be bigger, please use some free sharing service and post link here. Thank you.

Guts4 added a subscriber: Guts4.May 7 2016, 4:13 PM
Guts4 added a comment.Aug 30 2013, 9:02 PM

Exact issue happens to me and some of my other friends. The only workaround we've come across is to start a MP mission with just 2 people and have anyone else join in after those two are in game.

I looked in C:\Users\<Name>\ but I don't have an AppData folder
Also these crashes can be avoided if I launch the mission then tell my friends to join.

277787 added a subscriber: 277787.May 7 2016, 4:13 PM
277787 added a comment.Sep 1 2013, 4:21 AM

Easy way to get to your AppData. Open File explore and in the address type in %Appdata%. (Percent sign) Appdata (Percent sign again). It will bring you to your Appdata Roaming. This one folder ahead click on Appdata in the address bar and then you will see your local data folder in Appdata. Then you want to Winrar or 7-zip that folder to a smaller and easier package to transfer.

MadDogX added a subscriber: MadDogX.May 7 2016, 4:13 PM

Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.

If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.