linkin93

I am a really big fan of ARMA, I loved 2 and OA, especially with JSRS/ACE2/Blastcore. Have clocked up maybe 2000 hours over the years. I was very sad to see my clan shut down their A2:OA server and move it to A3 after it was released, though. So I left the game since release, and came back to it a few days ago. It was immediately obvious that I would still not enjoy the game as much as A2:OA. Please don't get me wrong - there are a lot of great improvements to core mechanics. I love the stance adjustments, weapon deployment, the arsenal, and modularity of weapons and attachments. I'm going to break down my gripes with A3 into categories below. GAMEPLAY MECHANICS Fatigue system - ARMA 2 was better for gameplay, but not very effective at game balance Weapon sway - Far too excessive, completely unrealistic Weapon recoil - I feel like I'm playing as an untrained skinny wimp who's never handled a firearm AI - Spots you from ages and murders you with pinpoint precision in one shot. You need at least 2-4 shots to take them out with any weapon except bolt action or semi auto heavy calibre rifles. Fatigue and weapon sway/accuracy make you useless at return fire. VISUALS Why is the fog blue? FOV is zoomed out too far for ironsights when not zooming/holding breath Blastcore is still a worthwhile addition AUDIO Still have to run JSRS because the standard sound system is not good enough SETTING I personally just do not like the made up futuristic junk - give me real settings with real equipment. PS: I was really looking forward to ARMA3... until the release... as is evident I have the supporter edition of the game. I feel as if ARMA 3 is catered to suck in the CoD and Battlefield crowd, instead of improving on previous releases, and was really undercooked and lacking content on release. Strictly in comparison to A2 and OA + expansions.

Well I'm going to bump this because of the update that occurred. Sway and innaccuracy is better, but still not good enough. I have CUP installed and my clan uses it along with the arsenal. We do multiplayer so this is not an issue that can be fixed by tweaking my gameplay settings.

Hi, I am look to modify a mission that already has ACE enabled/built in so that the wounding system is enabled for AI and toggle-able in mission params, like Xeno's ACE domination. It's already enabled for human players but not for AI. I came across this page which explains it a little: http://wiki.ace-mod.net/Wounding_System+notes#Global%20Variables I want AI to be subject to ACE wound effects, same as players. I've got the mission files / de pbo'd, but I've got no clue what to edit. Can someone lend a hand? I'm a complete noob at this, never done it before. Thanks.

So for all interested, I've found out how to do it. Once un-pbo'd or if you have the source files, open the mission in the editor, place the ACE wounding module (and any others you want), then save and export to singleplayer/mp missions. Then PBO the files and you're golden

Guys, the server key link for 1.5 is 404'ing, and I need it for my server :(

I've just tried to join my clan's ARMA 2/OA server which hasn't changed since last I played it, but now battleye is kicking me for an unknown game version. The server is not on any beta patches as far as I know. This same setup worked for me last week. Is anyone able to shed light on this?

I will try 103419 and see how that goes.

Have you got a controller or pad of some sort plugged in? Try unplugging it and see how that goes.

They break some missions too... For example only being able to face north after landing a parachute

What? That's not cool - I run this version because anything newer breaks my mods. In any case, which is lowest build still supported?

Edit arma2oa.cfg and reduce gpu max frames ahead to whatever you've set in your gpu driver control panel

I want to see at least all of the Operation Arrowhead content... since this covers a fair amount of ARMA 2 content there is no point in doubling up.

Just run CBA + ACEX_SM or JSRS, or one of the many other sound mods. I find JSRS to be the nicest for stock ARMA2/OA stuff

There's an issue since build 6400 where parajump scripts lock the player's direction to north after landing, trying to look around results in the view resetting rapidly, many times per second. I'd give a mission for repro but it's a private mission that isn't meant to be put anywhere public...

Been trying out the TrackIR since I got it.

So... Since the 1.62 patch there's been a lot of changes to how vehicles work... I was wondering everyone's opinions on some things: Vehicle thermals have changed from white/black background to green (for main gunner) and orange (for commander) - Is there any reason for this? I thought thermals was FLIR? (black-hot white-hot, with black or white background) The Fire Control System no longer works for all vehicles. Why is this? The auto-range and especially auto-lead features are extremely useful. I find myself using the betas for the changes in various other areas (movement, rocket gravity, etc), but these other changes I find quite strange and/or backwards.

OK... I don't control the settings on our server where auto-guide AT is turned off... unsure as to the server exe version

Do you see the green arrow on your HUD? That is a pointer of where your mouse is "pointing" the tank. Try not to move your mouse when you drive your tank/vehicle unless you are using freelook (holding alt) Moving the mouse and then trying to steer using the keyboard will result in the tank responding to your key presses, but it will also steer the vehicle so that the green arrow marking where your mouse is, is in the centre of the screen.

Hi all. I am noticing a keybind issue that concerns aircraft, and only with ACRE running. Press ALT, SHIFT, and Q at the same time (in my case, accelerating with booster, and using freelook) engages some sort of ACRE menu for "vehicle rack" or something along those lines, and renders me unable to control the aircraft. You have to press this key combo again to close the menu and regain control of the vehicle.

Performance is too poor on my system to use that much AA. I think 6xAA is an AMD-specific thing anyway. I can only use 2/4/8 etc. I heard forcing AA through drivers performs better than using the in game setting, do you know anything about that?

It only happens with this latest beta, I'm on the latest WHQL nvidia drivers. EDIT: It only starts when I launch the game with this patch, then it persists outside of the game until I reboot my system.

I am having a strange issue with this patch. As soon as I launch the game, the main menu becomes all blurry and pixelated. This persists even if I exit the game, it's still present in windows. Takes a full system restart to fix the issue. Not a problem on earlier betas. Screenshot won't work as I tried that already and it turned out fine once I restarted, but it looks like GPU memory corruption

My OS, Game, and page file are all on the SSD. It occurs on all maps. Vehicles, buildings, and units, use the lowest-quality model (ie blocky, all wheels are diamonds, etc) at some distance (in the centre of my screen) and then immediately pop into a high detail one when moved closer or near the edges of my screen. I am using a modified field of view (zoomed out) but it occurs all the same on regular 16:9 fov (which is too zoomed in for me) It's a big pain because when you need to look at buildings from a distance (to spot infantry hiding in them) you cannot see them, but being AI they can see you just fine.

Yes video memory is set to default, as always