Agiel7

To input co-ordinates for a 9-line brief in conjunction with my HSI whenever the JTAC gives me an attack heading. If they don't, I just use the TAD page to designate a SPI instead.

Though I enjoyed Georgian Hammer, I did yearn for a bit more variety. So downloaded the two campaigns that for some reason were removed in the last version. However, the scripting seemed a little buggy at the moment. In Devil's Cross, the Tornadoes refused to go SEAD and left the entire Russian air defense network intact, making attacking with anything other than Mavs was suicide. In addition, my wingman had some difficulty following my orders, and flew off into the sunset when I ordered him to engage armor. Though we (or should I say "I) managed to take out a half-dozen T-80s, the campaign has us doing the mission all over again. As with the Shore, I've successfully completed the first CSAR mission with the Blackhawk picking up the downed Viper pilot and my flight returned to base, it also has us doing the mission again. I tried out the mission after that in a standalone version, but the game crashes just as I taxi to the runway. Symptoms of compatibility issues with the new update? Would love to try out my new CBU-97s and CBU-105s on these campaigns.

Make sure your radio is set to the right frequency. I'm assuming you're talking about the stock "Georgian Hammer" campaign, so I think it was 124.000.

Given how little data has been gathered from the performances of the F/A-22 and the F-35, not to mention that the exact workings of their avionics are locked up tighter than Fred Phelps' bunghole, I shall eat my shoe if the next aircraft modeled is any of the above two.

When going SEAD in preparation for my actual attack run against an armored column, I do occasionally wish I was back in the 'ol F/A-18E with some HARMs. With my weak-ass machine and the resolutions I'm playing this sim at, I can't tell a Zeus from a T-72 9 times out of 10 on the Maverick's seeker.

One more thing, the throttle on my Saitek Cyborg V.1 doens't work (What? I'm a university student with not a lot of disposable income, plans for grad school, and surely an insurmountable debt to pay off once I'm out in the work force). I find this odd since the stick worked absolutely swimmingly with Jane's F/A-18 and Falcon 4.0. For now, I've been using the +/- keys, which isn't exactly the most ergonomic solution.

Is the EAC step to the start-up the switch that's obscured by the throttle? I can adjust my view to see the switch, but the switch doesn't advance the sequence.

Well to put it lightly, it's a harrowing experience. Luckily, owing to my attachment to these types of games, I have an extraordinary amount of patience learning them. My uncle gave me Jane's Longbow 2 on my ninth birthday, and 688(i) Hunter Killer when I turned eleven.

Read up on the wikipedia article on DCS, and I wanted to ask why the developers settled on the "A" version of the Apache, sans improved fire control radar of the Longbow? Was it decided that integrating it would be too complex for even the most hard-core sim fans? Or was the army a bit nervous about guys trying to model it, even if it was for a game?