Armed Assault

From VaafWiki

Jump to: navigation, search

Welcome to the VAAF ArmA area. Hopefully you'll find something to keep you interested and will play online with us occasionally.

We currently run co-operative missions with no fixed time/day.

Contents

Introduction

Armed Assault is a tactical combat simulator which covers a ficticious conflict on a fictitious island Sahrani. The player takes part as a single soldier fighting for the allies or for the Sahrani Liberation Army. The player can fight as a foot soldier, command a tank, drive transport vehicles, fly transport and assault helicopters, or fly a harrier (and probably other stuff). The game is more of a simulator rather than an action game like the Battlefield series. It shares many similarities with the older "Operation Flashpoint" as in essence the same people wrote it.

The single player missions are very difficult but don't let that turn you off. The short and simple multiplayer missions that we've created so far have provided quite a few hours of fun for young and old.

Version

The last stable (non-beta) patch is 1.08. It's an incremental patch from 1.05 so you'll have to get both and apply them in order.

Most of the good Australian servers are running the 1.11b patch. When installing the beta patch you'll get a new arma shortcut icon that will run it instead of the 1.08 version. You can still run the non-beta version.

Demo

Before you buy it's always nice to try out a demo. Fortunately Bohemia Interactive have provided one [1]

Addons that we use

Maybe it'd be nice to list only the most commonly used addons here and put links to the oneoffs next to the mission that requires them on the ((ArmA Mission Library)).

Networking

Arma seems to have no particular requirements for playing/hosting as I didn't need to forward any ports on my router to host a game. When you host a game it automatically shows up on the global list on everyone's screen so there is no need to exchange IP addresses.

It has a dedicated server so there are quite a few gaming ISP's running public servers around the place. There are even a couple of Australian dedicated co-op servers (running big missions with helo lifts a neccessity). We've recently been playing as a squad in public servers.

Ports

Although it doesn't appear to be necessary to port forward for ArmA, you may find yourself curious about what ports it needs. Slake your curiosity right here, soldier.

  • Default main .exe port: 2302 UDP (you may change it by -port command line argument)
  • Server reporting port: port+1 UDP
  • VOIP Port: port+3 UDP

Other Armed Assault WIKI's

Here's a pretty nice wiki dedicated to Armed Assault: http://community.bistudio.com/wiki/Armed_Assault

It has some very nice information related to the mission editor.

Dedicated Servers

Some of our guys occassionally run a dedicated server. You can identify them in the multiplayer browser because their names begin, unsurprisingly, with VAAF and they have the word "dedicated" somewhere in there. Pretty straightforward really. Some are public (no password) but can be adminned by VAAF members (changing missions etc) using the standard VAAF password. Others, if they need a password to join, the password will be the standard password.

Voice Comms

For the moment we're sticking with teamspeak as it supports the use of a separate USB headset for voice comms.

From 1.09b onwards the ingame voip (voice over IP) has improved dramatically to the point where it can be useful to shout out a warning or an occassional message to someone not on teamspeak on a public server. You can't use separate audi output for voice comms but you can use a usb microphone by setting it up for voice input in windows control panel. Then in ArmA set a key for press to talk and anyone nearby should hear you in direct mode.

Note: From my searchings I think that it's important to forward the VON (2305 UDP) port to lessen problems. If the ports are forwarded the VON is peer to peer but it all falls back to going through the game server if it can't peer to peer. This could be why it seems a bit flakey and dependant on the server load.

TIR

ArmA supports the use of TrackIR for head movement which is quite nice but I had a weird prob where my soldier would stop running and thereafter would only walk everywhere. It turned out to be TIR related. Updating the TIR software and disabling all axes except for pitch and yaw seems to have fixed the problem.

Flight Controls

ArmA currently supports the use of a HOTAS only if it appears as a single device (CH gear can do this for all of their controls).

Links

Retrieved from "http://www.vaaf.net/wiki2/index.php5?title=Armed_Assault"
Personal tools