Difference between revisions of "Arma 3 Experimental Ports"

From Bohemia Interactive Community
Jump to navigation Jump to search
(Video Drivers Update on Linux)
m
 
(42 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Please visit [http://dev.arma3.com/ports this '''overview page'''] to learn more about our experimental client ports to Linux and Mac, including the limitations and a
+
Please visit [http://dev.arma3.com/ports this '''overview page'''] to learn more about our experimental client ports to Linux and Mac, including the limitations and F.A.Q.
F.A.Q
+
 
 +
 
 
== Installation ==
 
== Installation ==
 
# Check the [http://dev.arma3.com/ports limitations overview] to decide whether you find them acceptable.
 
# Check the [http://dev.arma3.com/ports limitations overview] to decide whether you find them acceptable.
# Check the [http://dev.arma3.com/ports minimal requirements] to determine whether your system is able to run the port.
+
# Check the [http://dev.arma3.com/ports minimal requirements] to determine whether your system is able to run the ports.
# Download and install Steam client, create an account and purchase the [http://store.steampowered.com/app/107410/ Windows retail version of Arma 3].
+
# Download and install the Steam client, create an account and purchase the [http://store.steampowered.com/app/107410/ Windows retail version of Arma 3].
 
# Install the game (it will automatically download the data for Mac or Linux, depending on the platform you are installing from).
 
# Install the game (it will automatically download the data for Mac or Linux, depending on the platform you are installing from).
 
# Play!
 
# Play!
 +
  
 
== Known Issues ==
 
== Known Issues ==
* The in-game news feed references the latest Windows version, rather than the actual port version. This information may not be applicable to the port version.
+
* <s>Potential Out Of Memory client crashes/freezes when playing for longer periods of time - the ports are limited to 768 MB of VRAM on Linux and 512 MB on Mac.</s>
* Potential Out Of Memory client crashes when playing for longer periods of time  
+
* <s>Being a 32-bit process, Arma 3 has 4 GB of memory available to it. However, unlike Direct3D, OpenGL stores texture data in the game's address space. Using more VRAM would fill the available memory much more quickly, leading to more frequent crashes.</s>
* Potential crashes when playing demanding missions in the "Win" campaign - random / non-blocking
+
* Lower FPS after long gameplay - this may hint at an incoming OOM crash. Restarting the game cleans the memory.
* AMD OpenGL drivers have trouble handling FSAA for vegetation (white outlines). It is being addressed, but AMD drivers below version 15.5 are not supported currently.
+
* Lag and desync under heavy multiplayer load
* Frame rate drops when Steam overlay pop-ups appear
+
* Problem with different languages and diacritics - only English works properly. Non-ASCII characters are not supported.
* Minor Linux OpenAL sound issues (occasional mild static or stuttering in dialogues and intense firefights)
+
* Low FPS on OS X - running the OS and the native display resolution eat up a lot of computing power.
* Potential Windows 10 compatibility issues in the 1.42 ''legacyPorts'' branch
+
* AMD Mesa drivers can cause graphical glitches, such as white blinking vegetation LODs.
* Any issues fixed since [http://dev.arma3.com/post/spotrep-00040 update 1.42] in the primary Windows version
+
* Occasional Alt + Tab crashes
 +
* Aspect ratio changing CTD - changing the aspect ratio in-game can cause issues and/or CTDs.
 +
* Joystick, gaming devices - Xbox 360 controllers should work plug-and-play on Linux and Mac, but it's not always possible to remap their buttons in-game. Joysticks, Xbox One gamepads and other game controllers need user alterations of the SDLGamepad.config file located in the Arma directory on Linux.
 +
* The VP wrapper can lower Arma 3’s performance by up to 30 percent on several systems, but the performance drop should not exceed 10 percent on a vast majority of systems.
 +
* Video options have some limitations dependent on the system’s computing power. It can disable your option to set up High or Ultra quality levels on less powerful machines.
 +
* Some keys (e.g. "Alt") are designated for something else in the system (on Mint for example), so you may need to re-map your keyboard settings.
 +
* The shader cache file can become corrupted during some crashes. Deleting "~/.local/share/bohemiainteractive/arma3/eONprecompiledShaders.dat" fixes the problem.
 +
* Drivers on AMD cards - AMDGPU-PRO Beta and MESA drivers - are in development and are prone to cause unexpected issues from time to time.
 +
* Potential sound issues (e.g. static and stuttering)
 +
* Arma 3 Server running on Linux may suffer from BattlEye client not updating properly. Try restarting the server to trigger the update.
 +
* Issues with shared memory management in PulseAudio drivers in some community missions.
 +
* DLC content errors after update 1.64: deleting the contents of the Steam/depotcache folder and a subsequent data verification in Steam should help.
 +
* Legacy versions (e.g. 1.64 and 1.68) work on older OS X (10.9.5) as they don't use Metal 2.0 yet.
 +
* Steam overlay on Linux/Mac platforms may lead to crashes or other major issues.
 +
* If you get a Steam Library error when starting a dedicated server, try starting it using this command ''LD_LIBRARY_PATH=~/.steam/bin32/ ~/.steam/bin32/steam-runtime/run.sh ./arma3 -server -config=server.cfg''
 +
* Apple AudioToolbox crashes might sometimes happen.
 +
* ATOC might cause rendering issues with AMD cards using MESA drivers.
 +
* User on distributions using the Wayland display server may find that the following issues occur (read on for a way to disable it and restore the functionality).
 +
** Cannot select any resolutions other than the highest one your monitor supports.
 +
** After restoring a minimized game window, it will have an empty space where the title bar should normally be.
 +
* Using a multiple monitor setup and using Alt + Tab may cause aspect ratio issues or CTDs.
 +
* Any issues fixed since the [https://dev.arma3.com/post/spotrep-00080 1.82] Windows version
 +
=== Disabling Wayland ===
 +
Disabling Wayland protocol / display driver and switching back to X Server:
 +
# Open /etc/gdm/custom.conf for editing
 +
# Uncomment the line WaylandEnable=false
 +
# Reboot   
 +
 
 +
 
 +
== Distros ==
 +
Supported Linux distributions are:
 +
* Ubuntu 16.04 64-bit and later LTS versions
 +
* Mint 18 64-bit and later LTS versions
 +
* Fedora 25 and later LTS versions
 +
* SteamOS 2.87 and later stable versions
 +
 
 +
<s>32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play Arma 3 on them.</s>
 +
The Arma 3 ports are now 64-bit processes, so no further testing was done on 32-bit systems and Arma 3 ports will not run on them.
  
[[Category:Arma 3]]
+
We support only default desktop environments such as Cinnamon on Mint and Unity on Ubuntu. It should be possible to run the game on Debian and Gentoo, but it was not the part of the QA process, therefore we cannot guarantee support.
  
 +
There are community tests of Arma 3 on other Linux distributions such as Arch Linux. You can find more information on [https://forums.bistudio.com/forum/196-arma-3-ports/ the forums] and [http://feedback.arma3.com/ Feedback Tracker] regarding issues on unsupported distros.
  
== Distros ==
 
  
Supported linux distributions are:
+
== Linux Graphics Drivers Updates ==
*Ubuntu 14.04.2 LTS 64bit and later, recommended is Ubuntu 14.10 64bit
+
=== NVIDIA ===
*Mint 17.1, 64bit and later
+
A quick 'how-to' on updating NVIDIA drivers on Ubuntu and Mint systems:
 +
# Open Terminal
 +
# Enter "sudo add-apt-repository ppa:graphics-drivers/ppa"
 +
# Enter "sudo apt-get update"
 +
# Enter "sudo apt-get install nvidia-390"
 +
Your drivers should now be updated after restarting.
 +
 
 +
Check https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa for newer drivers.
 +
 
 +
A quick 'how-to' on updating NVIDIA drivers on Fedora systems:
 +
# Enable both (free & paid) RPM Fusion Repositories [https://rpmfusion.org/Configuration here]
 +
# Open Terminal
 +
# Enter "xorg-x11-drv-nvidia akmod-nvidia "kernel-devel-uname-r == $(uname -r)"" and install everything the package requires
 +
# If you're on a 64-bit system, enter "sudo dnf install install xorg-x11-drv-nvidia-libs.i686" after the previous operation finishes
 +
# Reboot (you may find that the boot process takes longer than usual; this is normal the first time)
 +
 
 +
=== AMD ===
 +
Ubuntu 16.04 and all distros with Xorg1.18 or higher, need the AMDGPU-PRO beta driver (for newest GPUs) or Oibaf MESA drivers (recommended). Installing AMDGPU-PRO: http://support.amd.com/en-us/download/linux.  Oibaf driver info can be found [https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers here].
 +
As MESA drivers are quite frequently updated, we've been using the latest version (18.1.0-devel) for testing and found that many graphical issues and crashes have been fixed.
 +
 
 +
In addition, Fedora 25 with AMD GPUs need to disable the Wayland display driver and re-enable X Server for the game to work correctly.
 +
 
  
32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play ArmA III there.
+
Installing MESA drivers for AMD:
 +
# Open Terminal
 +
# Type in and execute: "sudo add-apt-repository ppa:oibaf/graphics-drivers"
 +
# Type in and execute: "sudo apt-get update"
 +
# Type in and execute: "sudo apt-get dist-upgrade"
 +
# Reboot
  
We support only default desktop environments such are Cinnamon on Mint,Unity on Ubuntu.
 
  
It should be possible to run the game on Debian but it was not the part of QA process, therefore we cannot guarantee the support.
+
Installing MESA drivers on Fedora:
 +
# Follow the installation instructions [https://copr.fedorainfracloud.org/coprs/che/mesa/ here].
  
There are community tests of ArmA on other linux distributions, such as Gentoo and Arch Linux. You can find more information on forums and Feedback Tracker regarding issues on unsupported distros.
 
  
== Video Drivers Update on Linux ==
+
In the case Steam is not working with MESA this may help :
 +
#  Open Terminal
 +
#  Type in and execute: "gedit .bashrc"
 +
#  Add line "export LD_PRELOAD='/usr/$LIB/libstdc++.so.6' DIAPLAY=:0"
 +
#  Save and exit
 +
#  Steam should now launch by typing "steam" into Terminal
  
*Quick "how-to" on updating Nvidia drivers on Linux PCs :
 
# Open terminal (CTRL + ALT + T)
 
# Enter "sudo add-apt-repository ppa:mamarley/nvidia"
 
# Enter "sudo apt-get update"
 
# Enter "sudo apt-get install nvidia-349" (or possibly newer versions. When in doubt, check https://launchpad.net/~mamarley/+archive/ubuntu/nvidia for more info)
 
Your drivers should now be updated after restart.
 
  
*AMD Catalyst is a bit more complicated. The only method we have found that works reliably, is to install the driver from the archive that AMD provide for download. The drivers that Ubuntu 14 ships with are outdated, have known performance problems and bugs.
+
== Joysticks & Gamepads==
http://support.amd.com/en-us/download/desktop?os=Linux+x86
+
Unfortunately, Steam’s standard only supports standard Xbox and Windows XInput gamepad schemes, which means that more sophisticated schemes present in Arma 3, and using DirectInput and allowing reconfiguration of gamepads and joysticks in-game, had to be turned off in the ports. It is possible to reconfigure them by modifying the mapping text, but it’s not intuitive. Alternatively you can try to remap your keybinding using third-party software (e.g. AntiMicro).
*There is a guide to manually installing them here:
 
http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide
 
The guide mentions the 13.12 drivers, but the process is the same for the later ones.
 
  
== Joysticks and gamepads==
 
  
Windows version of ArmA uses DirectInput and XInput methods for mapping of peripheries, which turned out to be insufficient for ports.
+
== Dedicated Servers ==
For this reason, with Linux and Mac ports of games, where gamepads are concerned, we decided to go with Steam's Big Picture controller configuration instead, which slowly becomes standard for controller setup on Mac and Linux, as it cooperates with SDL in that regard, and we use SDL's gamepad mappings.
+
=== Mac ===
 +
# Run the Steam client (if you do not start the normal game first, it will not let you launch after the Dedicated Server is on).
 +
# Run Arma 3 and wait for the game to get to the main menu.
 +
# Run Terminal.
 +
# Change the current directory to the path where the ''Arma3.app'' is (e.g. ''"cd ~/Library/Application\ Support/Steam/SteamApps/common/Arma\ 3/"'').
 +
# Run the Dedicated Server by command: ''"./ArmA3.app/Contents/MacOS/ArmA3 --args -server -config=Server.cfg"''.
  
To make the most of your gamepad for Arma 3 on Mac and Linux, first you need to make sure that the gamepad is enabled in Steam Big Picture, and configure it there. The exact steps are as follows:
+
=== Linux ===
 +
==== Method 1 ====
 +
# Launch Arma 3 via Steam normally (if you want to run server and client on the same PC).
 +
# Find your Arma 3 installation folder by using your right mouse button to click on the game name in Steam's library and go to the Properties click on Local files tab, then click on Browse local files button to open the file browser at that location. You should also put the server.cfg file there. Default installation folder is: "~/.steam/steam/steamapps/common/Arma 3".
 +
# Open Terminal and type in: "cd 'your Arma 3 path'" and then press Enter. It should change to your game folder.
 +
# Type in and execute: "export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32""
 +
# Type in and execute: "./arma3 -server -config=server.cfg"
  
# Launch Steam.
+
Your Dedicated Server should run alongside the normal game now.
# Connect your gamepad and make sure it's on.
+
Note - you can skip #4 by entering "export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32" directly into the ~/.bashrc file.
# Launch Steam Big Picture, if it's not in Big Picture mode (it's an icon depicting a gamepad in the top right corner of Steam window).
 
# When Steam's Big Picture menu shows up, navigate to Settings (it's an icon near the 'exit' one in top right corner of the screen.
 
# Select 'Controller' option.
 
# At this point you should see your controller mappings. Make sure that they're all as you want them, and then select 'Save' option.
 
# Steam may ask you to share your mapping with others at this point - agree or decline.
 
  
Now, for Arma 3, this should really be enough, in theory. If you are launching the game from within Steam client, and you have configured the controller, then Steam most likely placed the information about controller configuration in its config.vdf file, and will provide this information to the game as environment variable during the game's launch. So, the proper way to configure and remap controller settings on Linux and Mac is to configure them in Steam Big Picture, instead of the game. Every controller in existence in theory should be supported in this manner, even those that on Windows show up only as 'controller with scheme'.
+
==== Method 2 ====
 +
[[Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29]]
  
== Dedicated servers ==
 
  
How to start dedicated server on Mac:
+
== Fedora Firewall  ==
 +
There may be an issue with connections on Arma 3’s server on Fedora caused by a firewall. For disabling this you may use this:
 +
https://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/sec-Disabling_firewalld.html.
  
# Run Steam Client (If you will not start the normal game first, it wont let you to launch after the dedicated server is on)
+
Keep in mind this will open your firewall completely, and opening ports just for Arma 3 is advised (default ports are: 2302-2305 UDP)
# Run Arma3, wait till game gets to the menu
 
# Run Terminal
 
# Change current directory to path where Arma3.app is, in my case: "cd ~/Library/Application\ Support/Steam/SteamApps/common/Arma\ 3/"
 
# Run dedicated server by command: "./ArmA3.app/Contents/MacOS/ArmA3 --args -server config=Server.cfg"
 
  
There are two ways how to start linux dedicated server.
 
*1st way:
 
# Lauch Arma3 via Steam normally. (If you will not start the normal game first, it wont let you to launch after the dedicated server is on)
 
# Localise your Arma3 by RMB in Steam library on Arma3>properties>local files>browse local files and copy the path. You should also put the Server.cfg file there.
 
# Open terminal and write: cd 'your Arma3 path' and hit enter. It should open your game folder.
 
# Type in the terminal: ./arma3 . It should write you this message: error while loading shared libraries: libSDL2-2.0.so.0
 
# Type in the terminal: sudo apt install libsdl2-2.0-0:i386, hit enter, enter password and let it install. Agree by pressing Y.
 
# Type: sudo dpkg --add-architecture i386 in terminal and hit enter.
 
# Type: sudo apt update in terminal and hit enter.
 
# Write: ./arma3 -server -config=Server.cfg in terminal and hit enter.
 
Your dedicated server should run now alongside with the normal game.
 
*2nd way:
 
https://community.bistudio.com/wiki/Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29
 
  
== Xplatform compatibility with Windows game ==
+
== Cross-Platform Windows Compatibility  ==
 +
The Linux / Mac ports presently use the current Arma 3 [https://dev.arma3.com/post/spotrep-00080 version 1.82]. For now, the version of the Linux / Mac ports and primary Windows version should be compatible, at least until further Windows version updates.
 +
When that happens, players on the Windows platform, who wish to keep playing with players on the ports version, must use the legacyports beta branch, as described below.
  
Linux/Mac port uses Legacy 1.42 ArmA´s version. You can only access servers with this version. (Greenlighted in server list)
+
1.82 version installation on Windows:
1.42 Legacy version installation on Windows:
+
#Open the Properties of Arma 3 in the Steam library
#Hit the right button on the Arma in Steam library and open Properties. Then open the Local Betas tab. Enter the code: Arma3LegacyPorts. This should unlock the LegacyPorts version.
+
#Open the Betas tab
#Download and play.
+
#Enter access code: Arma3LegacyPorts. This should unlock the legacyports - Legacy Build (1.82 - ports).
 +
#Download and play

Latest revision as of 13:17, 24 July 2018

Please visit this overview page to learn more about our experimental client ports to Linux and Mac, including the limitations and F.A.Q.


Installation

  1. Check the limitations overview to decide whether you find them acceptable.
  2. Check the minimal requirements to determine whether your system is able to run the ports.
  3. Download and install the Steam client, create an account and purchase the Windows retail version of Arma 3.
  4. Install the game (it will automatically download the data for Mac or Linux, depending on the platform you are installing from).
  5. Play!


Known Issues

  • Potential Out Of Memory client crashes/freezes when playing for longer periods of time - the ports are limited to 768 MB of VRAM on Linux and 512 MB on Mac.
  • Being a 32-bit process, Arma 3 has 4 GB of memory available to it. However, unlike Direct3D, OpenGL stores texture data in the game's address space. Using more VRAM would fill the available memory much more quickly, leading to more frequent crashes.
  • Lower FPS after long gameplay - this may hint at an incoming OOM crash. Restarting the game cleans the memory.
  • Lag and desync under heavy multiplayer load
  • Problem with different languages and diacritics - only English works properly. Non-ASCII characters are not supported.
  • Low FPS on OS X - running the OS and the native display resolution eat up a lot of computing power.
  • AMD Mesa drivers can cause graphical glitches, such as white blinking vegetation LODs.
  • Occasional Alt + Tab crashes
  • Aspect ratio changing CTD - changing the aspect ratio in-game can cause issues and/or CTDs.
  • Joystick, gaming devices - Xbox 360 controllers should work plug-and-play on Linux and Mac, but it's not always possible to remap their buttons in-game. Joysticks, Xbox One gamepads and other game controllers need user alterations of the SDLGamepad.config file located in the Arma directory on Linux.
  • The VP wrapper can lower Arma 3’s performance by up to 30 percent on several systems, but the performance drop should not exceed 10 percent on a vast majority of systems.
  • Video options have some limitations dependent on the system’s computing power. It can disable your option to set up High or Ultra quality levels on less powerful machines.
  • Some keys (e.g. "Alt") are designated for something else in the system (on Mint for example), so you may need to re-map your keyboard settings.
  • The shader cache file can become corrupted during some crashes. Deleting "~/.local/share/bohemiainteractive/arma3/eONprecompiledShaders.dat" fixes the problem.
  • Drivers on AMD cards - AMDGPU-PRO Beta and MESA drivers - are in development and are prone to cause unexpected issues from time to time.
  • Potential sound issues (e.g. static and stuttering)
  • Arma 3 Server running on Linux may suffer from BattlEye client not updating properly. Try restarting the server to trigger the update.
  • Issues with shared memory management in PulseAudio drivers in some community missions.
  • DLC content errors after update 1.64: deleting the contents of the Steam/depotcache folder and a subsequent data verification in Steam should help.
  • Legacy versions (e.g. 1.64 and 1.68) work on older OS X (10.9.5) as they don't use Metal 2.0 yet.
  • Steam overlay on Linux/Mac platforms may lead to crashes or other major issues.
  • If you get a Steam Library error when starting a dedicated server, try starting it using this command LD_LIBRARY_PATH=~/.steam/bin32/ ~/.steam/bin32/steam-runtime/run.sh ./arma3 -server -config=server.cfg
  • Apple AudioToolbox crashes might sometimes happen.
  • ATOC might cause rendering issues with AMD cards using MESA drivers.
  • User on distributions using the Wayland display server may find that the following issues occur (read on for a way to disable it and restore the functionality).
    • Cannot select any resolutions other than the highest one your monitor supports.
    • After restoring a minimized game window, it will have an empty space where the title bar should normally be.
  • Using a multiple monitor setup and using Alt + Tab may cause aspect ratio issues or CTDs.
  • Any issues fixed since the 1.82 Windows version

Disabling Wayland

Disabling Wayland protocol / display driver and switching back to X Server:

  1. Open /etc/gdm/custom.conf for editing
  2. Uncomment the line WaylandEnable=false
  3. Reboot


Distros

Supported Linux distributions are:

  • Ubuntu 16.04 64-bit and later LTS versions
  • Mint 18 64-bit and later LTS versions
  • Fedora 25 and later LTS versions
  • SteamOS 2.87 and later stable versions

32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play Arma 3 on them. The Arma 3 ports are now 64-bit processes, so no further testing was done on 32-bit systems and Arma 3 ports will not run on them.

We support only default desktop environments such as Cinnamon on Mint and Unity on Ubuntu. It should be possible to run the game on Debian and Gentoo, but it was not the part of the QA process, therefore we cannot guarantee support.

There are community tests of Arma 3 on other Linux distributions such as Arch Linux. You can find more information on the forums and Feedback Tracker regarding issues on unsupported distros.


Linux Graphics Drivers Updates

NVIDIA

A quick 'how-to' on updating NVIDIA drivers on Ubuntu and Mint systems:

  1. Open Terminal
  2. Enter "sudo add-apt-repository ppa:graphics-drivers/ppa"
  3. Enter "sudo apt-get update"
  4. Enter "sudo apt-get install nvidia-390"

Your drivers should now be updated after restarting.

Check https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa for newer drivers.

A quick 'how-to' on updating NVIDIA drivers on Fedora systems:

  1. Enable both (free & paid) RPM Fusion Repositories here
  2. Open Terminal
  3. Enter "xorg-x11-drv-nvidia akmod-nvidia "kernel-devel-uname-r == $(uname -r)"" and install everything the package requires
  4. If you're on a 64-bit system, enter "sudo dnf install install xorg-x11-drv-nvidia-libs.i686" after the previous operation finishes
  5. Reboot (you may find that the boot process takes longer than usual; this is normal the first time)

AMD

Ubuntu 16.04 and all distros with Xorg1.18 or higher, need the AMDGPU-PRO beta driver (for newest GPUs) or Oibaf MESA drivers (recommended). Installing AMDGPU-PRO: http://support.amd.com/en-us/download/linux. Oibaf driver info can be found here. As MESA drivers are quite frequently updated, we've been using the latest version (18.1.0-devel) for testing and found that many graphical issues and crashes have been fixed.

In addition, Fedora 25 with AMD GPUs need to disable the Wayland display driver and re-enable X Server for the game to work correctly.


Installing MESA drivers for AMD:

  1. Open Terminal
  2. Type in and execute: "sudo add-apt-repository ppa:oibaf/graphics-drivers"
  3. Type in and execute: "sudo apt-get update"
  4. Type in and execute: "sudo apt-get dist-upgrade"
  5. Reboot


Installing MESA drivers on Fedora:

  1. Follow the installation instructions here.


In the case Steam is not working with MESA this may help :

  1. Open Terminal
  2. Type in and execute: "gedit .bashrc"
  3. Add line "export LD_PRELOAD='/usr/$LIB/libstdc++.so.6' DIAPLAY=:0"
  4. Save and exit
  5. Steam should now launch by typing "steam" into Terminal


Joysticks & Gamepads

Unfortunately, Steam’s standard only supports standard Xbox and Windows XInput gamepad schemes, which means that more sophisticated schemes present in Arma 3, and using DirectInput and allowing reconfiguration of gamepads and joysticks in-game, had to be turned off in the ports. It is possible to reconfigure them by modifying the mapping text, but it’s not intuitive. Alternatively you can try to remap your keybinding using third-party software (e.g. AntiMicro).


Dedicated Servers

Mac

  1. Run the Steam client (if you do not start the normal game first, it will not let you launch after the Dedicated Server is on).
  2. Run Arma 3 and wait for the game to get to the main menu.
  3. Run Terminal.
  4. Change the current directory to the path where the Arma3.app is (e.g. "cd ~/Library/Application\ Support/Steam/SteamApps/common/Arma\ 3/").
  5. Run the Dedicated Server by command: "./ArmA3.app/Contents/MacOS/ArmA3 --args -server -config=Server.cfg".

Linux

Method 1

  1. Launch Arma 3 via Steam normally (if you want to run server and client on the same PC).
  2. Find your Arma 3 installation folder by using your right mouse button to click on the game name in Steam's library and go to the Properties click on Local files tab, then click on Browse local files button to open the file browser at that location. You should also put the server.cfg file there. Default installation folder is: "~/.steam/steam/steamapps/common/Arma 3".
  3. Open Terminal and type in: "cd 'your Arma 3 path'" and then press Enter. It should change to your game folder.
  4. Type in and execute: "export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32""
  5. Type in and execute: "./arma3 -server -config=server.cfg"

Your Dedicated Server should run alongside the normal game now. Note - you can skip #4 by entering "export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32" directly into the ~/.bashrc file.

Method 2

Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29


Fedora Firewall

There may be an issue with connections on Arma 3’s server on Fedora caused by a firewall. For disabling this you may use this: https://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/sec-Disabling_firewalld.html.

Keep in mind this will open your firewall completely, and opening ports just for Arma 3 is advised (default ports are: 2302-2305 UDP)


Cross-Platform Windows Compatibility

The Linux / Mac ports presently use the current Arma 3 version 1.82. For now, the version of the Linux / Mac ports and primary Windows version should be compatible, at least until further Windows version updates. When that happens, players on the Windows platform, who wish to keep playing with players on the ports version, must use the legacyports beta branch, as described below.

1.82 version installation on Windows:

  1. Open the Properties of Arma 3 in the Steam library
  2. Open the Betas tab
  3. Enter access code: Arma3LegacyPorts. This should unlock the legacyports - Legacy Build (1.82 - ports).
  4. Download and play