Experimental Ports – Arma 3

From Bohemia Interactive Community
Jump to navigation Jump to search
(Edit to 1.54)
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 F.A.Q.
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.


== 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 port.
# 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!
Line 10: Line 10:


== 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.
# Potential Out Of Memory client crashes/freezes when playing for longer periods of time
* Potential Out Of Memory client crashes when playing for longer periods of time  
# Lower FPS after long gameplay: May hint at upcoming OOM crash. Restarting the game cleans the memory.
* Potential crashes when playing demanding missions in the "Win" campaign - random / non-blocking
# Lag and desync under heavy MP load
* 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.
# "Diary" key, "j" as default key, may cause game to freeze momentarily.
* Frame rate drops when Steam overlay pop-ups appear
# Faulty ATOC on AMD GPU cards (white outlines on vegetation): It can be disabled in video settings.
* Minor Linux OpenAL sound issues (occasional mild static or stuttering in dialogues and intense firefights)
# Problem with different languages and diacritics: Only English works properly. Non-ASCII characters are not supported.
* Potential Windows 10 compatibility issues in the 1.42 ''legacyPorts'' branch
# Low FPS on OS X: Running OS and native display resolution eat up a lot of computing power.
* Any issues fixed since [http://dev.arma3.com/post/spotrep-00040 update 1.42] in the primary Windows version
# AMD graphical artifacts: Black and white squares appear on screen and AMD GPU does not show all shadows correctly.
 
# Occasional ALT + TAB crash
# Unusually large dedicated server RPT file: Can eat up more than 800 MB on Mac.
# Aspect ratio changing CTD: Changing aspect ratio in-game can cause issues and/or CTD.
# Unable to use free camera (double alt key) in some planes: Player may not be able to change to free camera in planes.
# Joystick, gaming devices: Xbox 360 controllers should work plug and play on Linux and Mac, but it's not possible to remap their buttons in-game. Joysticks, Xbox One gamepad and other game controllers need user alterations of SDLGamepad.config file located in Arma directory on Linux.
# VP wrapper can lower Arma’s performance by up to 25 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 on less powerful machines.
# Any issues fixed since 1.54 in the Arma’s Windows version


== Distros ==
== Distros ==
Line 24: Line 31:
*Ubuntu 14.04.2 LTS 64bit and later (recommended is Ubuntu 14.10 64bit)
*Ubuntu 14.04.2 LTS 64bit and later (recommended is Ubuntu 14.10 64bit)
*Mint 17.1, 64bit and later
*Mint 17.1, 64bit and later
*Fedora 22 and later


32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play Arma 3 there.
32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play Arma 3 on them.


We support only default desktop environments such as Cinnamon on Mint and Unity on Ubuntu.
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 the support.


It should be possible to run the game on Debian, but it was not the part of the QA process, therefore we cannot guarantee the support.
There are community tests of Arma 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.
 
There are community tests of Arma on other Linux distributions, such as Gentoo and 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.




Line 37: Line 44:
=== NVIDIA ===
=== NVIDIA ===
A quick 'how-to' on updating NVIDIA drivers on Linux systems:
A quick 'how-to' on updating NVIDIA drivers on Linux systems:
# Open Terminal (CTRL + ALT + T).
 
# Enter ''"sudo add-apt-repository ppa:mamarley/nvidia"''.
Open Terminal (CTRL + ALT + T).
# Enter ''"sudo apt-get update"''.
Enter "sudo add-apt-repository ppa:graphics-drivers/ppa".
# Enter ''"sudo apt-get install nvidia-349"'' (or possibly newer versions - when in doubt, check [https://launchpad.net/~mamarley/+archive/ubuntu/nvidia here] for more info).
Enter "sudo apt-get update".
Your drivers should now be updated after restarting.
Enter "sudo apt-get install nvidia-361" .
Your drivers should now be updated after restarting.
 
Check https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa for newer drivers.


=== AMD ===
=== AMD ===
AMD Catalyst drivers are a bit more complicated. The only method we have found that works reliably, is to install the driver from the archive that AMD provides for download. The drivers that Ubuntu 14 ships with are outdated, have known performance problems and contain bugs (http://support.amd.com/en-us/download/desktop?os=Linux+x86).
AMD Catalyst drivers are a bit more complicated. The only method we have found that works reliably, is to install the driver from the archive provided by AMD for download. The drivers shipped with Ubuntu 14 are outdated, they have known performance problems and contain bugs (http://support.amd.com/en-us/download/desktop?os=Linux+x86).


There is a guide to manually installing them [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide here]. The guide mentions the 13.12 drivers, but the process is the same for the later ones.
There is a guide to manually installing them [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide here]. The guide mentions the 13.12 drivers, but the process is the same for the later ones.
Line 50: Line 60:


== Joysticks & Gamepads==  
== Joysticks & Gamepads==  
The Windows version of Arma uses DirectInput and XInput methods for mapping of peripherals. This turned out to be insufficient for the ports. For this reason, in the Linux and Mac ports of the game, where gamepads are concerned, we decided to go with Steam's Big Picture controller configuration instead. This is slowly becoming the standard for controller setup on Mac and Linux, as it cooperates with SDL, and we use SDL's gamepad mappings.


To make the most of your gamepad for Arma 3 on Mac and Linux, first you'll need to make sure that the gamepad is enabled in Steam Big Picture, and configure it there. The exact steps are as follows:
# Xbox 360 controller should work plug and play on Linux and Mac, but is not possible to remap it. Joysticks, Xbox One and other game controllers need user alterations of SDLGamepad.config file located in the Arma directory on Linux. Adding GUID and controller map of your gaming device might work.
# Launch Steam.
# Steam Big Picture mapping is unfortunately not working with Arma at this moment.
# Connect your gamepad and make sure it's on.
# Launch Steam Big Picture, if it's not already there (it's an icon depicting a gamepad in the top-right corner of Steam client).
# When Steam's Big Picture menu shows up, navigate to ''Settings'' (it's an icon near the 'exit' one in the top-right corner of the screen.
# Select the ''Controller'' option.
# At this point you should see your controller mappings. Make sure that they're all as you want them, and then select the ''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. It 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'.




== Dedicated Servers ==
== Dedicated Servers ==
=== Mac ===
=== Mac ===
# Run Steam client (if you will not start the normal game first, it will not let you launch after the Dedicated Server is on).
# Run the Steam client (if 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 Arma 3 and wait for the game to get to the main menu.
# Run Terminal.
# Run Terminal.
Line 74: Line 75:
=== Linux ===
=== Linux ===
==== Method 1 ====
==== Method 1 ====
# Launch Arma 3 via Steam normally (if you will not start the normal game first, it will not let you launch after the Dedicated Server is on).
# Launch Arma 3 via Steam normally (if do not start the normal game first, it will not let you launch after the Dedicated Server is on).
# Find your Arma 3 by right mouse button in Steam's library and go to the ''Properties'' > ''Local files'' > ''Browse local files'' section to copy the path. You should also put the ''server.cfg'' file there.
# Find your Arma 3 by right mouse button in Steam's library and go to the ''Properties'' > ''Local files'' > ''Browse local files'' section to copy the path. You should also put the ''server.cfg'' file there.
# Open Terminal and write: ''cd 'your Arma 3 path''' and hit Enter. It should open your game folder.
# Open Terminal and write: ''cd 'your Arma 3 path''' and press Enter. It should open your game folder.
# Type in Terminal: ''./arma3''. It should output this message: ''error while loading shared libraries: libSDL2-2.0.so.0''.
# Type in Terminal: ''./arma3''. It should output this message: ''error while loading shared libraries: libSDL2-2.0.so.0''.
# Type in Terminal: ''sudo apt install libsdl2-2.0-0:i386'', hit Enter, enter the password and let it install. Agree by pressing Y.
# Type in Terminal: ''sudo apt install libsdl2-2.0-0:i386'', press Enter, enter the password and let it install. Agree by pressing Y.
# Type in Terminal: ''sudo dpkg --add-architecture i386'' and hit Enter.
# Type in Terminal: ''sudo dpkg --add-architecture i386'' and press Enter.
# Type in Terminal: ''sudo apt update'' and hit Enter.
# Type in Terminal: ''sudo apt update'' and press Enter.
# Type in Terminal: ''./arma3 -server -config=server.cfg'' and hit Enter.
# Type in Terminal: ''./arma3 -server -config=server.cfg'' and press Enter.
Your Dedicated Server should now run alongside the normal game.
Your Dedicated Server should now run alongside the normal game.
note:
In case of dependency problem during launching dedicated server on Ubuntu:
./arma3.i386: error while loading shared libraries: libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
solution:
Enter the following into terminal:
export LD_LIBRARY_PATH="<.steam install path>/ubuntu12_32"
example: export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32"


==== Method 2 ====
==== Method 2 ====
[[Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29]]
[[Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29]]


== Fedora Firewall  ==
There may be an issue with connection on Arma’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 is advised (Default ports are: 2302-2305 UDP)


== Cross-Platform Windows Compatibility  ==
== Cross-Platform Windows Compatibility  ==
The Linux / Mac ports use Legacy version 1.42 of Arma 3 currently. You can only access servers with this version (green in the server list).
The Linux / Mac ports use Legacy version 1.54 of Arma 3 currently. You can only access servers with this version (green in the server list).


1.42 Legacy version installation on Windows:
1.54 Legacy version installation on Windows:
#Open the ''Properties'' of Arma 3 or Arma 3 Server in the Steam library.
#Open the ''Properties'' of Arma 3 or Arma 3 Server in the Steam library.
#Open the ''Betas'' tab.
#Open the ''Betas'' tab.
#Enter access code: ''Arma3LegacyPorts''. This should unlock the ''legacyPorts'' version.
#Enter access code: ''Arma3LegacyPorts''. This should unlock the ''legacyPorts'' version.
#Download and play.
#Download and play.

Revision as of 16:57, 9 March 2016

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 port.
  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

  1. Potential Out Of Memory client crashes/freezes when playing for longer periods of time
  2. Lower FPS after long gameplay: May hint at upcoming OOM crash. Restarting the game cleans the memory.
  3. Lag and desync under heavy MP load
  4. "Diary" key, "j" as default key, may cause game to freeze momentarily.
  5. Faulty ATOC on AMD GPU cards (white outlines on vegetation): It can be disabled in video settings.
  6. Problem with different languages and diacritics: Only English works properly. Non-ASCII characters are not supported.
  7. Low FPS on OS X: Running OS and native display resolution eat up a lot of computing power.
  8. AMD graphical artifacts: Black and white squares appear on screen and AMD GPU does not show all shadows correctly.
  9. Occasional ALT + TAB crash
  10. Unusually large dedicated server RPT file: Can eat up more than 800 MB on Mac.
  11. Aspect ratio changing CTD: Changing aspect ratio in-game can cause issues and/or CTD.
  12. Unable to use free camera (double alt key) in some planes: Player may not be able to change to free camera in planes.
  13. Joystick, gaming devices: Xbox 360 controllers should work plug and play on Linux and Mac, but it's not possible to remap their buttons in-game. Joysticks, Xbox One gamepad and other game controllers need user alterations of SDLGamepad.config file located in Arma directory on Linux.
  14. VP wrapper can lower Arma’s performance by up to 25 percent on several systems, but the performance drop should not exceed 10 percent on a vast majority of systems.
  15. Video options have some limitations dependent on the system’s computing power. It can disable your option to set up High or Ultra quality on less powerful machines.
  16. Any issues fixed since 1.54 in the Arma’s Windows version

Distros

Supported Linux distributions are:

  • Ubuntu 14.04.2 LTS 64bit and later (recommended is Ubuntu 14.10 64bit)
  • Mint 17.1, 64bit and later
  • Fedora 22 and later

32bit Linux systems are considered too unstable due to crashes in MP, although it may be possible to play Arma 3 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 the support.

There are community tests of Arma 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 Linux systems:

Open Terminal (CTRL + ALT + T). Enter "sudo add-apt-repository ppa:graphics-drivers/ppa". Enter "sudo apt-get update". Enter "sudo apt-get install nvidia-361" . Your drivers should now be updated after restarting.

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

AMD

AMD Catalyst drivers are a bit more complicated. The only method we have found that works reliably, is to install the driver from the archive provided by AMD for download. The drivers shipped with Ubuntu 14 are outdated, they have known performance problems and contain bugs (http://support.amd.com/en-us/download/desktop?os=Linux+x86).

There is a guide to manually installing them here. The guide mentions the 13.12 drivers, but the process is the same for the later ones.


Joysticks & Gamepads

  1. Xbox 360 controller should work plug and play on Linux and Mac, but is not possible to remap it. Joysticks, Xbox One and other game controllers need user alterations of SDLGamepad.config file located in the Arma directory on Linux. Adding GUID and controller map of your gaming device might work.
  2. Steam Big Picture mapping is unfortunately not working with Arma at this moment.


Dedicated Servers

Mac

  1. Run the Steam client (if 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 do not start the normal game first, it will not let you launch after the Dedicated Server is on).
  2. Find your Arma 3 by right mouse button in Steam's library and go to the Properties > Local files > Browse local files section to copy the path. You should also put the server.cfg file there.
  3. Open Terminal and write: cd 'your Arma 3 path' and press Enter. It should open your game folder.
  4. Type in Terminal: ./arma3. It should output this message: error while loading shared libraries: libSDL2-2.0.so.0.
  5. Type in Terminal: sudo apt install libsdl2-2.0-0:i386, press Enter, enter the password and let it install. Agree by pressing Y.
  6. Type in Terminal: sudo dpkg --add-architecture i386 and press Enter.
  7. Type in Terminal: sudo apt update and press Enter.
  8. Type in Terminal: ./arma3 -server -config=server.cfg and press Enter.

Your Dedicated Server should now run alongside the normal game.

note: In case of dependency problem during launching dedicated server on Ubuntu: ./arma3.i386: error while loading shared libraries: libSDL2-2.0.so.0: cannot open shared object file: No such file or directory

solution: Enter the following into terminal: export LD_LIBRARY_PATH="<.steam install path>/ubuntu12_32"

example: export LD_LIBRARY_PATH="/home/user/.steam/ubuntu12_32"


Method 2

Arma_3_Dedicated_Server#Instructions_.28Linux_o.2Fs.29

Fedora Firewall

There may be an issue with connection on Arma’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 is advised (Default ports are: 2302-2305 UDP)

Cross-Platform Windows Compatibility

The Linux / Mac ports use Legacy version 1.54 of Arma 3 currently. You can only access servers with this version (green in the server list).

1.54 Legacy version installation on Windows:

  1. Open the Properties of Arma 3 or Arma 3 Server in the Steam library.
  2. Open the Betas tab.
  3. Enter access code: Arma3LegacyPorts. This should unlock the legacyPorts version.
  4. Download and play.
Retrieved from "https://community.bistudio.com/wiki?title=Arma_3:_Experimental_Ports&oldid=94748"