trekari

1) Dive compass on WRIST instead of floating in the middle of your screen. 2) Better yet, a Dive Computer on your wrist.

Quite a load of nonsense that this issue was FIXED for ArmA2, and yet ArmA3 it comes back with a vengeance.

Erm, please stop treating *nix users like second-class customers and release client AND server patches simultaneously and the clutter you complain about will be a non-issue in the first place.

B1n4ry, In case you aren't aware, BIS now cares about DayZ more than the players who bought their game before it was popular. They've decided it's part of their "best practices" to release client patches without warning, and ensure the dedicated server executables aren't released for a few weeks so people can't play. Unless they're playing DayZ, of course. Great system where Steam users can't tell the game NOT to update, and thus get locked out of their own linux servers. Of course, the entire problem could be alleviated by delaying patches until the dedicated server .exe's are also available, but evidently that hasn't occurred to BIS.

1) Steam was told not to keep OA up to date, and it did so anyway. 2) The practice of releasing client updates before server binaries are available for the dedicated servers (all platforms) is NOT something that should happen twice, let alone every time. BIS making this their status quo is beyond idiotic. My group had an operation scheduled this Saturday - our server is Linux and hosted hundreds of miles away in a data center. Now we have no Op this Saturday. Their answer of "install WINE" is bull**** when it should be released WITH the client update in the first place.

I'm sorry that my fanboy glasses broke and I cannot reasonably defend the practice of FORCING updates on Steam customer who now have NO F***ING WAY of playing on dedicated Linux servers until BIS fixes this screwup. In case you aren't aware, even DELETING the entire goddamn game and trying to reinstall as a Steam user means we'll DOWNLOAD 1.62 AUTOMATICALLY. Of course, the simplest solution here is to release the 1.62 CLIENT AND SERVER binaries at the same time. Explain to me how it's ok to **** that up? I'd really love to hear your justification.

Well, not releasing a buggy game in the first place is a good start. And yes, not releasing updates at all actually allows the MP crowd to play together, because they all have the same version between CLIENTS and SERVERS.

I for one, say thanks for nothing. You've released how many patches for ArmA, and you still insist on releasing client updates before server updates? Why the hell can't you WAIT until you have server binaries available for all platforms before releasing client updates and screwing your customers over? Are you going to continue screwing this up with ArmA3? Please tell me now so I can steer clear of your products from here on out. There's no excuse for this kind of face-palming behavior. Release client/server together, or don't release it at all. Those of us who TRIED to tell Steam NOT TO UPDATE the damn game STILL got updated, and now cannot play on our own linux servers. We had an operation planned for this Saturday which we now CANNOT DO because half our group has 1.62 and can't downgrade, and the server can't be brought up to 1.62. Thanks for nothing.

I'm sorry. I didn't realize that my SSD drives were supposed to be 1TB in size. :rolleyes: Dwarden, thank you for the clarification. It would still be nice to get a truly merged install.

Not true. You can install the disk version of Operation Arrowhead into the ArmA2 directory and save some space.

Quoted from: http://forums.steampowered.com/forums/showthread.php?t=1337127 The bolded part is what I'm asking about. There's no need for CO to take up all the space on the HDD it currently does for Steam users.

Question: Years ago it was stated that Steam users would be able to download and install a CO version of ArmA2 and OA, instead of requiring two separate installs (and thus more HDD space). Is this going to be completed anytime soon?

This event is approaching the point of cancellation unless some interest is shown. ArmA2 is compatible with ArmA2 Free. There's no need to install a new version, just head over to Fightersims.com and signup!

The American Government has reliable intelligence on the location of Petr Strudinsky - a known Chechen terrorist linked to dozens of bombing massacres in the last decade. Moving to neutralize this threat, a 26-person strike team has been assembled under the code-name Operation Deepcut, with the intent to kill or capture Petr and his Lieutenant Jaromir Yultsin. This raid is planned for December 3rd 2011, at 2200z utilizing the ArmA2 Free game platform. (Click here to get ArmA2 FREE) See the Fightersims forum below for more information. Operation Deepcut Event Forum Who or what is Fightersims? Fightersims is a couple of guys who have hosted large-scale events for Falcon4: Allied Forces in the past (24 people events) and have plans to host more LFEs for BMS Falcon4 and ArmA2 in the future. We aren't a clan and the only 'members' list is whoever is registered on the Fightersims forum and requests a roster spot for the LFEs. This is not a recruitment effort, and in fact we prefer if clans/groups can bring multiple people to participate as a full element/team! We've got more scenarios created for ArmA2, and provided Operation Deepcut goes well, we'll be hosting more LFEs on a regular basis. (The next one has 47 slots) We hope to see you there!

Mando Thanks for the explanation about TrackIR. I'm not a scripter, or a mod-maker of any kind. All I know is that you've said the gun tracks via FreeLook just fine, so I was hoping that there was a way to make it track via TrackIR. If this is beyond your ability, then I apologize for pushing for it. If not, then perhaps someone with more scripting/programming knowledge than myself can help find a way to make it work. After all, who doesn't want to shoot things with a 30mm cannon simply by looking at their target? :) If that feature were somehow implemented, you'd never get me out of the front seat of the Apache. Here's hoping it isn't something BIS needs to implement, or we'll be waiting until ArmA 3 I'm afraid.