draeath

I've got test mode up, verified by the watermark on the lower-right of the screen... however the installer doesn't seem to act on this and executes as if test mode was not enabled.

I can't get ppjoy to install. Even though I've got "test mode" running, the installer still throws a hissy fit about test mode and tells me to enable it, or tries to (and fails, because i have to specify the bcd store) do it itself, then tells me to reboot and try again. if I just open the installer in 7zip, it's a big nasty pile and I'd have no clue how to install it myself. Anyone gotten 'ppjoysetup-0-8-4-6.exe' to install on Windows 7 64-bit?

One single FN-FAL round through a window did it for me. All the way from the southern vantage point! Beautiful shot! ... now I just have to deal with the damn APC that wants to chew on me now.

Here's my feedback: Boo! :P EDIT: boo to me. Note to self: FTP doesn't work though an http proxy. durr!

Case in point, it's the M1A2 that you see in OA. You also see the TUSK, which is far more modern. Stuff like cage armor, reactive armor etc.

Just weighing in here. Shot doesn't spread as much as you would "expect" (from other games, movies). Go rent a shotgun at a firing range and play around a bit :P

No need to keep voting, it's marked 'in progress' with a target version etc.

It is.

Don't use the analog. Set your stick to halfway, select "increase throttle" and slide it forward. Do the reverse for the "decrease throttle" The nomenclature doesn't quite explain what is going on. It seems to work as a normal throttle in this case.

Fixed. There's a "flaw" in the installation process: 1. Extract the .tar.bz2 2. Run ./install 3. (this then runs tolower etc) This doesn't work because: (note this is all case sensetive) Extracting the tarball puts ./expansion/battleeye/ in, then runs tolower. tolower doesn't convert Expansion or it's contents because expansion already exists. Proposed Solutions: 1. change the name of "expansion" in the tarball and make 'install' copy it over after tolower runs 2. patch tolower to 'merge' directories if the destination exists, rather than failing and skipping over BUT! It seems to work, ie we can join in. But in the browser, it shows a red dot-questionmark instead of a red-X or a green dot. A few other servers in the browser show this. Is this because I'm using the wrong gamespy reporting IP? This is what I have. Does OA have something different I should use? reportingIP="arma2pc.master.gamespy.com";

I'm trying to set up my squad's OA server. It's not working. I've got all the 'fluff' working (ie my modified launcher script that combines A2/OA, uses rsync to sync up our moddirs etc. BUUT I can't even get it working before all that would apply. Just running ./server gives this pile of output. It's huge, so see this log.. (yes, I did use ./install and tolower did run) Any help would be appreciated. I'd rather not release the launcher script (it's just a heavily modified arma2server script) but I can if I must. I copied over our working arma2.cfg to arma2oa.cfg (and server.cfg) (after checking that it would be compatible). I did the same with the profile directory. I wasn't sure of the profile name, so I linked player.arma2oaprofile to player.arma2profile. Note also that the tarball seems odd: draeath@pandora:~$ tar xf a2oa-server-1.52.71900.tar.bz2 bzip2: (stdin): trailing garbage after EOF ignored I would think this didn't matter, as tar itself didn't see a problem with what bzip2 passed on to it, but still.

So, it appears the throttle problem is still present. I don't fly planes, so I don't know about that, all I know is helicopters. On my stick (Saitek x52) ArmA2 and AO see the throttle as two separate axis ranges (X- and X+) like all the other axes. I can assign Increase Thrust and Decrease Thrust, but they behave like Q and Z, and not like a proper throttle does. I can set the analog ones, but it doesn't seem to work correctly at all. Is there some way to get a "normal" throttle behavior, where full X+ is 0% input, full X- is 100% input, and neither (neutral position) is 50% input? (this is not possible with the programming software either. I can map it to key emulation, but Q/Z is hardly fitting either!) EDIT: nevermind, I'm a tool. My deadzone was too high. For anyone searching: mapping the X-/X+ to "Increase Thrust" and "Decrease Thrust" (these default to Q/Z) does NOT do what you would expect (behave like buttons) and, in fact, does behave as you would want an axis to behave.

I don't script much, so I might be completely missing it. But in: {_x assignAsCargo heli1} forEach units myGrp1; {_X moveInCargo heli1} forEach units myGrp1; I see you use a lowercase _x, but then everywhere else after you use a capital _X. Was that intentional?

The patch has been updated. Couple fixes, including some extra logic to prevent duplicate servers from running (which kept happening to me). Removed the useless -profiles argument, etc. Let me know what you all think!