Leftie

I think it's fairly safe to say that this is vaporware now. Another 8 years down the road and the developers have yet to release as much as an in-game video to the public. Since I was very sceptical of the vaporware possibility, I never bothered to pay for entry into their closed forum. If someone has something from there, which they can show publicly, I'd love to be proven wrong. Their forum is down for maintenance at the moment, with the message "Doing a bit of cleanup for 2015. Here's to a happy new year." The front page hasn't changed one iota since I last checked in on it a year or so back. So, not exactly a crazy amount of activity :rolleyes: Honestly, I've been rooting for this game for many years. I've been playing the Flashpoint/Arma series since 2001 and in games of this scope, there's just no competition. I believe the mil-sim community as a whole would benefit from having another alternative, but I no longer think that will be coming from Frantic Games.

OP here. Yes, the original post is a joke. We're poking fun at bugs, quirks and general weird behavior in the Arma series, as well as some in-clan stuff. ---- I do find the general discussion about achievements that has started up here, a bit interesting. On the one hand, you could completely ignore that achievements exist and play the game like you would without them. Nothing is forcing you to chase those goals. On the other hand, in MP you are likely to encounter people who are chasing those goals and those goals alone, thus wrecking the game for everyone else. This last case is not particular for achievements, though. Achievements are just another way for inconsiderate players (read: pr*cks) to act inconsiderate. The only problem I can see, is that it's actually an incentive for such behavior. But still; inconsiderate players will act inconsiderately, achievements or no, and I don't feel like playing with those people anyway. That's why I've never really bothered with public servers, and instead enjoy the fun we have on our clan servers. Like metalcraze here said: (My emphasis.)So I guess what I'm saying is: Or something like that :rolleyes:

Either that, or one of the moderators has just made a meta-joke :)

As we all know, the Arma series lacks the oh so popular achievement features that many games use these days. Some of the guys in our clan find this to be a weak point, so they sat down and hammered out a list of possible achievements and their corresponding requirements. I'm posting a copy of that list here, for your consideration. Even if BIS don't include these for Arma 3, feel free to use this as a manual check list: Game, expansions and addons W00t!? - Successfully starting ArmA 2 Madman - Successfully starting ArmA 2 with an addon INVINCIBLE! - Successfully starting ArmA 2 Combined Operations with an addon SNAFU - ArmA 2 crashes when starting with beta, addon or vanilla Waterworld - Run ArmA 2 CO with 5 additional islands Elementary My Dear Watson - Find an unmapped key on the keyboard Embrace The Pain - Play with the ACE addon Can't We All Just Talk About It? - Play with the ACRE addon Single player Sir! Yes Sir! - Start ArmA 2 Campaign I Have No Life - Complete the A2 Campaign I Totally Did That Without Cheating! - Complete the A2 Campaign without dying Pain Shared Is Pain Multiplied - Play A2 Campaign in COOP mode with 3 friends Beige Is The New Green - Complete the Arrowhead Campaign Baffling Sir, absolutely baffling - Complete the BAF - Campaign Multiplayer Is Anyone Out There? - Connecting to an ArmA 2 server I AM A GOD! - Running a dedicated server with addons and have people connect successfully It's not you ... well, it IS you - Kicking a player from a server A Is For Asshat - Getting kicked from a server B Is For Banhammer - Getting banned on a server WITCH! - Mentioning Battlefield or Call of Duty in ingame chat Gameplay I AM LEGEND! - Successfully landing a helicopter I'm From Down Under - Landing a helicopter upside down I Know What I Am Doing! - Crash a helicopter and kill everyone onboard Gun Nut - Firing every rifle, machinegun and handgun in the game at least once Piledriver - Using a plane to kill an enemy and then crash within one second No Cease Fire For You! - Kill a friendly AI Oh! Shiny! - Steal an enemy tank It's Called DEFENCE! - Get more than 20 kills while moving less than 20 meters in PvP Funpack - Start 10 missions with ACOG, grenade launcher and AT They've Changed The Ballistics Again - Miss three times in a row with RPG-7 or M136 Would It Help If I Jumped Overboard And Pushed!? - Travel on a fishing boat Wait! What time is it? - Start a night mission without NV-goggles MOAR GAMMA! - Complete a night mission without NV-goggles Where in the World is our objective? - Play a mission made by Sjaba Hovertank - Get 2 seconds of airtime in a tank More like Lamerover - Wreck an offroad vehicle while driving crosscountry Blinking line to the flashing dot - Shoot down an aircraft with a ZSU-23 Decoy THIS! - Shoot down a helicopter with a 120mm HEAT round Sorry, Wrong Gear - Reversing over friendlies in a truck Who's Side Are You On Anyway? - Killing a friendly while they are in an enemy vehicle In It For The Bang - Start a mission with 5 satchels and a Demolition backpack Not So Schnell - Blow up a petrol station Landing Is In The Advanced Course - Eject from pilot position while going faster than 150 Pizza Delivery - Kill a friendly by landing a helicopter on them Is This Your Door? - Wreck a house by driving a tank into it Armadillo - Drive every armoured vehicle in the game LeftFastLeftForwardReverseReverseREVERSE - Command a tank with AI crew What Goes Around Comes Around - Laserguide a bomb on to a Harrier or A-10 Weapon Of Gun - Kill an enemy with the A-10 Avenger Silent Automatic Weapon - Bring an M249 on a Covert Ops night mission Noisy End Towards The Enemy - Join a mission as private One Wing And A Prayer - Join a mission as Corporal Don't Sir Me! I Work For A Living! - Join a mission as a Sergeant Talking Out Of My Brass - Join a mission as a Lieutenant This Isn't The Love Boat? - Join a mission as Captain That's just wrong - Complete a mission without killing anyone Not So Hot Now, Are You? - Kill an enemy using a rifle with thermal sights I Swear, It's Not What It Looks Like! - Heal someone as a Medic The Second Coming - Die, abort and rejoin mission, then finish mission without dying again Showdown! - End a mission with the most TKs where everyone has at least one TK There!! The Guy By That Tree! - Identify 3 targets in 5 seconds I See You - Kill an enemy within 3 seconds of using your binoculars I See You More - Kill an enemy while they are using their binoculars Totally didn't see that - Get killed while using your binoculars Rogue Operations - Kill a sniper using a M9 or Makarov Cry Me A River - Destroy an armoured vehicle by driving it into a lake No Plan Survives First Contact With Your Troops - Mission failed within 5 min of starting The Map Is Mightier Than The Gun - Play a mission as Commander All Return To Formation - Play a mission as FTL Where Did THAT Come From? - Destroy a vehicle by driving it into the sea Beached SEALs - Hit land in a RIB travelling at top speed The Pointiest Stick - Shoot down a helicopter with an unguided AT rocket Community I'll give them something to complain about! - Create a mission and upload it ------ Disclaimer: Don't get me wrong. This list is made out of love. We've been playing the series for 10 years running, and though it has its quirks, we still enjoy playing. Also, some of the achievements listed, relate to specific people or events in our clan. If you can't understand/relate to some of the entries, don't fret too much :) Regards, the NoPryl of Norway clan

Actually, no :o I did some more digging, and found out that it apparently measures in Minutes of Angle (MOA), as opposed to MIL. (Those Americans and their archaic forms of measurement ... :rolleyes:) The famous Mil-dot reticle is known as a P3 type, whereas the TWS reticle is of the P4 type. See here for a comparison: http://www.schmidtbender.com/reticlesPM.htm NCStar has a good technical sheet for the P4 reticle here: http://www.ncstar.com/tech-faq.html

Whether or not it's worth it will always be subjective, but I can tell you that I'm very happy with mine. The stick itself is tight as hell and just oozes quality. (All my previous experience is from owning simple joysticks from Saitek and Logitech.) There is some sideways slack in the throttle-sticks, but it doesn't really affect anything. Bear in mind though, it is a replica stick, which means all the fancy extra buttons on the throttle base, are copied from the A10-C and labeled according to their original functions. This does make it somewhat less generic, but even if you end up not using any of those switches, the HOTAS setup has a metric buttload of keys, hats and switches to configure. I say, if you can afford it, and are in the market for a HOTAS setup, go for it

If the TWS scope has a different amplification (that is; a different field of view) from the M107 scope, then it follows that a MIL (milliradian) is a different size in that reticule, no?

Ok, no harm done, then. I'm glad :) Yes, pulse events with single keys seem to work OK. The problem only arises once I use modifier-keys (Ctrl, Alt and Shift). Because of the number of keys (not to mention some of the double-clicks) that are needed in A2, it's not really feasible to use only single keys. I know from experience, that other games do not have an issue with modifier-keys and "pulse" events, so I'm forced to conclude that the problem only occurs because of how A2 handles key-presses. I've played around a lot with timings now, and I can reproduce the same behaviour as the "pulse" events, by setting the pause between the event which presses Ctrl and the event which presses another key, low enough. The "pulse" events (which are basically preprogrammed "press" and "release" events) seem to set this pause as low as 1ms. Here are my findings with regards to pause-length between modifier-key press and other key press: <5ms: A2 consistently reports the keys in the wrong order. 5ms>20ms: A2 sometimes gets it right, but it's highly inconsistent. >30ms: A2 consistently reports the intended order of key presses. My recommendation to others who want to configure a T.A.R.G.E.T. compatible controller for use in A2, is to set the pause between modifier-key press and normal key press to at least 30ms. It may be that the response-time is dependent on e.g. CPU usage (a developer could tell us if this is the case or not), so you may want to give yourself a little more leeway, just to be on the safe side.

@KillaALF: I apologize for the brusqueness of my previous reply. I realize that I'm the one asking strangers for help, and I do appreciate all the help I get. I took your advice about the "press" and "release" type events, and set up each switch action to trigger four separate events, in order to simulate a slower execution of a CTL+key pulse. For example, here's what happens when I switch to the FLAPD position: Immediately: R_CTL is pressed 30ms later: k is pressed 60ms after that: k is released 30 ms after that again: R_CTL is released This actually works! I do, however, consider it a workaround (and a cumbersome one at that), so I'll be looking into playing with the different timers in order to find out if that is the only thing preventing me from using a "pulse" type event. For those who are interested, here's the current script code for the different flaps functions: MapKeyIOUMD(&Throttle, FLAPU, CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL)); MapKeyRIOUMD(&Throttle, FLAPU, CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL)); MapKeyIOUMD(&Throttle, FLAPD, CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'k', D(60), UP+'k', D(30), UP+R_CTL)); MapKeyRIOUMD(&Throttle, FLAPD, CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL), CHAIN( DOWN+R_CTL, D(30), DOWN+'i', D(60), UP+'i', D(30), UP+R_CTL));

Nope, haven't tried that, but I don't imagine it would help. As I stated in my first post, the Event Tester shows what seems to be the proper behaviour. The "hold" type event is used for keys which should be held down for as far as the joystick button is engaged (such as an MG trigger). This is not the case for the flaps. Configuring it as two "press"- and "release"-type events also seems counterintuitive, since what I want to emulate is that the fairly normal key-combination CTRL+k is pressed, and then immediately released. Unless I've misunderstood something fundamental, that is precisely what the pulse action does. If the length of time for which the combination is held is the problem, then I could simply increase the pulse time setting in order to achieve the same goal.

Well, yes and no. I've managed to do most things directly in A2s config, but there is no way to what I want with the HOTAS Flaps switch without using T.A.R.G.E.T. The reason is that the MVR position needs to trigger either flaps up or flaps down, depending on the previous position of the switch. No, it was just pseudo-code in order to explain my setup in simple terms. Here's the actual script code: MapKeyIOUMD(&Throttle, FLAPU, PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i'); MapKeyRIOUMD(&Throttle, FLAPU, PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k'); MapKeyIOUMD(&Throttle, FLAPD, PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k', PULSE+R_CTL+'k'); MapKeyRIOUMD(&Throttle, FLAPD, PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i', PULSE+R_CTL+'i');

First of all, apologies if this issue has already been brought up and resolved. I did some googling and BI Forum searches, but couldn't find any relevant threads. I'm trying to adapt the Thrustmaster HOTAS Warthog to work with A2:OA, and am running into some issues. In A2, I've configured Flaps Up -> R_CTRL+i Flaps Down -> R_CTRL+k And then I set up the following events in T.A.R.G.E.T: FLAPD Press -> R_CTL k Release -> R_CTL i FLAPU Press -> R_CTL i Release -> R_CTL k Aside from the fact that this needs to be used with some patience (waiting for the flaps to move between steps), it should - in essence - work. It doesn't. Whenever I toggle the HOTAS Flaps switch, nothing happens. When I went into the A2 Controls config to check and try to reset the flaps control settings, the apparent problem showed itself: Whenever I try to use the HOTAS Flaps switch to configure the Flaps Down function, A2 does not register it as R_CTRL + k, but rather as k + R_CTRL. (And similarly for the Flaps Up function, of course.) The Event Tester in T.A.R.G.E.T. shows Key Press: RCTL Key Press: K Key Release: K [31ms] Key Release: RCTL [33ms] So apparently, input ought to be sent in the correct order. Has anyone else seen this behaviour, and does anyone know of a way to resolve this problem?