When hosting a non-dedicated server, Arma 3 will crash at the mission selection screen if any mission in your mpmissions/ folder has an #include statement with a path that can't be resolved in the description.ext file.
Description
Description
Details
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10
- Category
- Server
Steps To Reproduce
- Create a new multiplayer mission and save it
- Make a new description.ext in that mission's folder in mpmissions/
- Add the line: #include "\notamod\notapath\totalnonsense.inc"
- Go back to the main Arma 3 menu
- Host a new server and get to the mission selection screen
- Arma 3 will crash
Additional Information
A number of special gameplay mods for Arma 3 (in particular, the popular mod "Arma Commander") feature missions that require as standard practice an #include statement in the description.ext that pulls in various common defines from the mod. When you deactivate the mod, you also have to purge all of the missions from your mpmissions/ folder, or else Arma 3 will crash.
Arguably Arma 3 should handle this case a little more gracefully?
Event Timeline
Comment Actions
Any update on this? It's really bad when you want host a server and go to the mission select screen then arma will immediately crash. People are probably thinking what is causing their arma to crash when it's include dependency in a mission file