Mister Frag

I think maybe it's time we created a OFP Combat Videography thread. I'd be interested in seeing video from other members, especially previews of mods that people are working on. Here is my first contribution, a convoy attack by an Apache from "Ground Attack II" -- click on the still image to see the video. The ~11MB file is in Windows Media (WMV) format, and should stream as long as you can handle ~900Kbps download speeds. Otherwise, save it locally before opening it.

Nope, that's not crazy, that's the way the game was designed. If you repeatedly attack your own side, the AI will think of you as the enemy no matter what uniform you're wearing.

I downloaded it from Metaboli -- paid US$ 19.99. Works great with the Atari ArmA download.

It may make sense to destroy them, but not when there are still enemies shooting at you, and that's what I've seen the AI do. They don't mind wasting all their ammo to take out an unmanned crew-served weapon or vehicle.

And of course in real life you wouldn't do that, given the proper training. You're supposed to focus on the front sight and blur out the target.

Why would someone launch an AA missile at a body of water, much less a wave?

Actually, you would more likely use exactly what you are told/allowed to use. While some services may be tolerant of improvisation and field modifications, not all of them are. You certainly aren't going to have much luck if you decide to swap out the sling while you aren't deployed. Imagine lining up for inspection, and you are the only guy with a non-issue sling -- you are going to be scrubbing toilets for weeks. Having said that, I agree with you about the sling. I've got a couple of rifles, and all but my precision rifle have some form of three-point sling.

I had the same problem with VoIP and V1.08 on my Audigy, and had stopped using it (VoIP). I downloaded the driver from Station Drivers and installed it, but haven't had the opportunity to test it yet. The reason why I'm posting is because ArmA would not start up after installing the Station Drivers Audigy driver, and reinstalling DirectX (the June 2007 version) didn't help either. What did the trick for me was to reinstall OpenAL.

The cards that KODE suggested do have PS 2.0, and would therefore be able to allow sniperboy to run the game. They may not offer the best performance, but given the budget he has, they are one of his few options. sniperboy, before you commit to buying anything, please check whether your system has an AGP or PCI Express slot. Given that your current card doesn't have PS 2.0 support, the system may be old enough to date back to the days before PCI Express, and you don't want to wind up with the wrong card. pchaxor, being rude and insulting other members on the forum doesn't do much to enhance your credibility.

Microsoft has a tool called IMAGECFG that will modify the executable file header to change the Processor Affinity Mask. http://www.robpol86.com/Pages/imagecfg.php

I apologize for briefly taking this off-topic, but going from the FRAPS codec (which is lossless) to MPEG (which is lossy) and then transcoding again to DivX (which is also lossy) results in a needless loss of image quality. You're better off staying with the FRAPS codec while you edit, and transcode to your final delivery format at the very end.

<rant> Grrrr... this is so annoying. I like to play SP Mission #4, where you fly the AH-1 and attack a convoy. I try to fly as flawless a mission as possible, staying low and sustaining little or no damage, and earlier today while testing V1.08 I wiped out the convoy, destroyed targets of opportunity, and didn't take any hits. I was on my way back to the base, just above the water and well out to sea to avoid AA fire from a Shilka I knew was lurking in a canyon near the coast. Then I got a radio message telling me that I appear lost, and seconds later the screen fades to black and the mission ends in failure! One of the things I've always enjoyed about OFP and now ArmA is the freedom to choose how to get a particular task done. Having mission termination triggers like this one in place really kills the experience -- please don't assume that I'm a complete idiot who can't navigate (especially when the next waypoint is indicated). I hope BIS will consider the removal of these triggers, or at least make them less strict. </rant>

Just install the V1.08 patch by running the installer, and toss the shortcut to the Beta and the MOD directory it used. The beta didn't overwrite any game files and can be removed easily and cleanly.

Jeez, what were you guys hunting? Cadillacs?

There is nothing that prevents you from making your own backup of the electronic download version on a data DVD. You are responsible for backing up anything you don't want to lose in the event of a drive failure or some other mishap, and that goes far beyond having a copy of ArmA. I assure you that when the need for having a backup arises, you'll wish you had spent the $0.25 on a blank DVD to back up your download, and any other files and documents that you can't easily recreate.

If you have a 8xxxx nvidia card... definetly. Unless you have the US (Atari) version of the game, in that case it won't even start... Well thats an inaccurate statement if ever I've read one on these forums, and I have read a lot of them on here. Just because YOU have issues, which could for all anyone knows be hardware related or due to a third party addon confliction, not necessarily be due to the 1.07 BETA Patch, doesn't mean to say EVERYONE who has the US/Atari version will definately have issues. I've played MP games with a lot of Americans running the Atari version using the 1.07 BETA Patch and the worst they've reported is the occasional crash (more due to the CPU intensity of the Evolution mission we've played after 3 hours), and the rare graphical artifacts similar to those reported a few posts previously by Törni. There is nothing inaccurate about what I wrote. I never said the 1.07 beta doesn't work with the Atari ESD version -- I'm running that myself. This thread is specifically about the second 1.07 beta. If you install the second beta on a system running the original V1.07 beta applied to a Atari ESD version, you will not be able to start the game because it will require reactivation. The license key from the original purchase does not work with the updated beta, and Atari/Softwrap will not assist with this problem. Atari even sent out e-mail to registered users advising them not to install the public beta, probably because they got innundated with reactivation requests. I didn't save the message, but I received it not 24 hours after trying to activate the second beta.

If you have a 8xxxx nvidia card... definetly. Unless you have the US (Atari) version of the game, in that case it won't even start...

Yes it does.

Same here, I have the ESD version from Atari and can't run the updated beta, the activation fails. I can still run the non-beta, and was able to run the initial V1.07 beta, but not the update.

The download and activation of the US version from Atari is actually completely painless (if you can handle a 2+GB download), and has the advantage of being able to run without having a CD or DVD in the drive.

Use the "Launch Arma Beta Patch" shortcut in the folder one level up from the Beta folder.

Rather than disabling Hyperthreading completely for your system, try changing the Processor Affinity Mask (PAM) of the ArmA executable using the ImageCFG tool: http://www.robpol86.com/Pages/imagecfg.php The PAM determines which processor(s) a process is allowed to execute on, and restricting it to one processor (CPU 0) should have the same effect as disabling Hyperthreading.

Does the Game Controller applet in Control Panel see it? What about DXDIAG (in the Input tab)?

Your integrated graphics controller is not supported. Here is an excerpt from the README file:

In V1.07 Joystick Button #2 (NEXT TARGET) doesn't work, it behaves the same as NEXT WEAPON in-game. If you go into OPTIONS -> CONTROLS and try to map it, pressing JB #2 exits the configuration dialog. Cancelling the control configuraton, exiting V1.07, starting V1.06, and resuming the A-10 mission already in progress allows JB #2 to work, and it can also be configured correctly without ArmA exiting the dialog.