MavericK96

After testing this some more, I stand by my vote which is that the new recoil is good, but it definitely needs to be toned down. You can barely even put a 2-3 round burst on target the way it is, which doesn't seem very realistic.

Just managed to beat it using the advice you guys gave me. Thanks again :) A couple of notes though: -When I went up to the tanks, there was a guard just standing there next to one. He didn't ever move or patrol at all. I managed to plant 3 of the 6 satchels, when I got somewhat close to him while crawling. He then turned toward me, and ran over right next to me. I sat there for a second, expecting to get shot. He looked at me a few times, but just stood there. So after a bit, I risked moving, and strafed (while prone), around him to go plant more satchels. Sometimes he would run over to me again, sometimes he would just stand there as if I didn't exist, but I managed to plant all the charges and crawl away while he just stood there like an idiot. Some sort of AI glitch, clearly. -I planted 3 satchels each on the secondary objective buildings and none of them seemed to have been destroyed when I set off all charges. How many should it really take? -The times when the alarm goes off seem really random and nonsensical. Sometimes I was prone, crawling near a building in the darkest dark, and it would go off. Sometimes I would be crouched, running through the center of the base under a light post, and it wouldn't. It doesn't seem to be related to if an enemy sees you at all, just if they magically hear you or some other seemingly random trigger. Frustrating, really. -One weird thing about this mission (maybe others as well, but this is all I've tested on it so far) is that sometimes when I would shoot an enemy in the head, I would see the impact, and then several seconds later he would drop dead. Sometimes I was able to shoot them half a dozen times before they finally dropped over, when they should have been dead the first shot. -I also found a weird bug where while using NVGs in this mission, switching Antialiasing from Very High to Normal in the menu would make some of the textures (including my character) appear black after the switch. Switching back to Very High during the mission returned the textures to normal.

I think something like this would be awesome. I was for some reason under the impression that an attachment system was going to be included in OA, but obviously it is not. Since so many variants already exist, making some sort of front-end to choose them makes a lot of sense to me.

Thanks for the tips, guys. I think I have been trying to enter the base from the wrong side, near the two guard towers and the barracks. It seems like they always hear me no matter what when I enter there, so I will try the back side.

I wasn't able to get into the base without somehow being seen, even though it's complete darkness outside.

I'm glad you guys will be working solely on OA from now on. ACE2 for ArmA2 has already reached such a great level that I think it's able to stand on its own without further updates. :cool:

Alt-Enter makes it so I don't have to reboot, but it seems like after the driver dies, SLI stops working or something, because I get terrible performance in OA until I reboot or disable/re-enable SLI.

64-bit version that utilizes the maximum amount of RAM possible. :D Yes, I would pay for this if BIS doesn't think it's cost-effective enough to make for free.

The beta is simply a new version of the executable (and potentially some other files) for OA.

I've created a CIT ticket for those wanting to provide more information to help get this issue fixed. http://dev-heaven.net/issues/11742

It's not the hardware. I get the driver death sometimes within like 5 minutes of just looking around in the editor with no other units present. It seems to happen more often when I turn sharply or change views (from a scope to normal, or vice-versa for example). No crashlogs because the game itself doesn't crash, so I'm not sure what's causing the issue.

I've gotten the driver death several times in OA now. Not sure why it happens there but not in ArmA2.

Maybe only in SP; otherwise it's way too big of a factor regarding fairness in an MP environment.

Or have 128 soldiers firing constantly, or 128 helicopters flying around, or some combination thereof. Should work okay for a benchmark as long as there are plenty of sounds going all at once and the benchmark is easy to reproduce.

...I see what you did there. :D

What if you have a fast dedicated sound card, such as an X-Fi card? Is the CPU load the same?

Not true. I play with just about everything on Very High on my rig (as in my sig), and only PP on Low because I don't like the way it looks otherwise. However, you are correct that one of the listed cards is definitely not going to be enough to run the game full-out.

Cool video, but looking at your specs versus your settings, you could probably be running it at a lot higher settings than you are. It's kind of no wonder it runs as well as it does. :P

Wrong. I've heard this said about 60 FPS too, and that's also wrong. Check out this site: http://www.100fps.com/how_many_frames_can_humans_see.htm

Not entirely sure what you're referring to here, but I think you mean changing the 3D resolution to be higher than the Interface resolution, which you can easily accomplish in ArmA2. Just got to settings and make the 3D resolution higher than the Interface res. EDIT: Beaten by NeMeSiS. :P

Agreed. Mostly I am having issues where using the batch file for the beta is not allowing me to use any other startup parameters, like -nosplash.

Cool, thanks for the instructions. :)

So, here's my solution: Take the ArmA2 profile and copy it to OA. I've done this myself and so far it seems to be working just fine, with a good improvement in performance. Here's how I did it: (NOTE: Requires latest (250-series) drivers) 1. Download the nVidia SLI Profile editing tool here: http://www.geeks3d.com/20100528/manage-your-sli-profiles-with-nvidia-geforce-sli-profile-tool/ 2. Export your current profiles with the tool. 3. Edit the exported .txt file to copy the Armed Assault 2 profile information (should be fairly easy to find) and then just rename it to something OA-related, and make sure to change the "Executable" field to arma2oa.exe. 4. Close and save the .txt file. 5. Import the profiles back in using the tool. 6. You're done! You just took all the nVidia app-specific profile information and transferred it to OA. No renaming .exe files, no fuss. If anyone has any questions about copying the profile I would be more than happy to answer them. I didn't explain in detail how to copy the information but if you look at the profiles in the .txt file you should be able to figure it out. Just add another profile entry below the ArmA2 one by copying and pasting the ArmA2 profile, and editing it to work with OA. Hope this helps!

Yeah, I turn it off. It's a little jerky but I feel like I'm a lot more accurate with it that way.

I just use the same settings as ArmA2, since it's the same engine. Max Frames Ahead = 8 Force Triple Buffer off Force VSync off Those are the main ones I use.