Evil.Bonsai

Haven't looked at mission, but make sure there are blue units positioned there. If there aren't, that may be why you're not able to re-arm.

It's somewhat a good idea, depending on situation, to place waypoints at altitude for ingress/egress waypoints, then place on ground for attack points. This makes it a lot easier to point your tgp when searching for targets. I like using the min altitude settings on the UFC, to give me a warning when I get too low. I'll set it for about 10k-13K feet. Then when I drop below this when attacking, I get a nice 'altitude' warning from the VMU.

why the sad face? every mission you go on ends with the sim asking you if you want to save the track. No need for acmi when it's done automatically with each mission.

Answered in previous posts: check your mfcd; usually will say 'check eo timer' or something . You can click 'ack' to indicate you've read it and 'note' will go away

The two nubs on the nose aren't MWS sensors as well? I always thought they were.

If you're in the Ka-50, perhaps. For A10, however, try the willy-pete (white phosphorous) m156 or practice smoke m274. Not really sure of the difference between the two, however. The WP might be brighter white and last longer? There's also the m257 parachute illuminator low-light/night. They don't last very long, however.

SEAD flights work fine. Search radars have issues, which is what the SEAD craft would be attacking if they were working. Try changing you AFAC aircraft to a 0h-58 heli and make it invisible. I've had good luck doing it that way.

Do they actually shoot, or are they just 'armed' so that enemy AI will shoot at them? I placed an 'armed house' next to a striker and they striker immediately engaged it. There was no return fire, however. I figured it was just a way of making a building something to be attacked w/o having to specifically target it

viper answered the first part. RE: parking lot. It's a reference to the book previously mentioned. Don't want to spoil it for those that haven't read it and/or plan to, but it basically is just that. During Desert Storm, the A10 guys had been assigned ALL KINDS of stuff that really wasn't very thought out. In one part they explain how they had to go WAY NORTH to take out a radar site. On their way back south, they found F16s practically just circling around doing some pissant sortie. The Hog drivers were a bit miffed they were sent on such dangerous missions while more suitable aircraft were held back. It really is a good book. And some of the things they happened across out in the desert were pretty interesting. As to my mission, it's my first REAL mission, so I'm taking my time trying to figure how things work. It'll be fairly simple. Something for n00bs, really. Including me :) The only complicated part will be NOT firing your last Maverick, as that will be your only sensor. Just like they did way back when. :)

You'll enjoy it. Working on creating a Gulf War-style A10 mission: night, with only IR Mav as sensor, radar and MLRS (nee, scud) targets. Maybe a 'parking lot' or two :)

Er...was thinking laser not emitter. Redact, please. :music_whistling:

Wow, I really did not expect the conversation to take the route it did. And for the record, I'm pretty sure NVGs do not have IR emitters. :)

Was going to mention this. That part of the book really showed what a suck job it was to cross with A10s. Also sucked for the tanker; had to fly so slow so that the A10s could keep up. Good book.

Well, you COULD set up air defense groups with multiple parts and then place them about the map. I just tried out multiple radars for a single launcher. Depending where I was and which radar picked me up, I got tracking warning on the RWR from that radar and a missile launch from the launcher. Next, tried multiple launchers with a single radar. Didn't quite work as expected, though both launchers worked. Had an issue where the missiles kept exploding immediately after launch. Didn't seem to be distance from radar, as I moved the launcher to other side of map, though same distance from radar, and they launched just fine. It's pretty easy to setup a mock IADS. Just move the various launchers and radars to where you want to. There MIGHT be coding to prevent some situations, but I placed an SA6 radar at the top of the map and one at the bottom, about 150 kilometers apart, range circles just overlapping at center, then put a single launcher at center; both radars worked just fine.

My bad. I guess seconds aren't THAT far off. I've always used a 'converted' number (as I posted above. I guess if you were going to program a JDAM with a specific L/L then it WOULD matter, but I've only used them the one time (in Smerch Hunt; JTAC pretty much always uses MGRS, that I've experienced so far anyway), and it was close enough to point the tgp at the target. Now to find a converter to see how far .27 minutes is versus 20 seconds. :) Thanks for the correction!

also note, depending on circumstances, if you're given 42deg 34.278mins, you'll have to convert that .278 into seconds. .278 is ALMOST 1/3 so if you use 42 34 20 (20 being 1/3 of 60), you'll get pretty close to your target, and can then use optics to adjust as needed. I mention this 'cause the CAOC guy in Smerch Hunt (just finished flying it again), I guess, is just passing along what's given him and gives you MGRS for your first target then uses L/L, with decimals, for a later target. :/

for east west (longitude) you have to enter xxx xx xx (7 numbers) and for latitude it's xx xx xx (six numbers). No spaces. Here's one post: http://forums.eagle.ru/showpost.php?p=1129615&postcount=3 search for 'cdu latitude' I found several threads. Read through them for a better understanding, as they have slightly different explanations. I think the first time I flew 'smerch hunt' I was able to enter L/L because I remembered reading the post where longitude is THREE numbers (need the leading 0)

Only in multiplayer with human pilots, I believe. Formation flying, as far as I know, has no significant tactical advantage and is dangerous in combat (think about what you would be doing if a SAM were launched at you...yep, right into your wingmen if you were in formation like that). You really WANT your wingmen far away, just for that purpose. The various formations that are available are of much more use (well, should be, barring AI stupidity) during combat and provide the separation needed to safely (to you and your flight; not the tangos on the ground wondering what that shiny thing was they thought they saw in the sky) employ ordnance. Want to fly like that? Logon to a multiplayer server and ask for a willing participant. :)

trk and miz files for both 1109 f16 sead sa6.trk 1110 f16 sead sa6.trk 1109 f16c SEAD vs SA6.miz 1110 f16c SEAD vs SA6.miz

1 F16c SEAD with 2 AGM-88s against Tunguska: both HARMs fired and shot down by Tunguska 1 F16C SEAD with 2 AGM-88s against SA6/SA8/SA10 and no action by F16C until shot at. Works in 1109, not in 1110. Note: I created same mission in each (did not use same saved mission)

Went to go test some of these ideas and found a major issue with 1110 vs 1109: SEAD is broke. SEAD flights won't engage many systems. I was able to SEAD engage the Tunguska, though the Tung. beat the HARM 7 of 8 times. Only 1 HARM made it through. SEAD vs SA6, SA8, SA10: no engagement at all. Created same mission in 1109 and SEAD engaged normally.

Not sure about offset, but using MGRS, every time I enter it into the cdu it pops up with elevation automatically. I write the elev. down and compare what they're telling over 9-line vs what pops up. If they're not close, I start to recheck everything. I don't think I've seen anything over 25ft of difference, unless I did something wrong.

Maybe mark the sam unit skill as 'excellent' and the tornadoes as 'average'? Dunno the exact engagement time, but I know there is one. Maybe make a test mission using a non-sead aircraft (or just disarm the tornadoes) flying at same speed/alt/range, see how long it takes the SAM to engage THEN go back and alter your waypoints so that the tornadoes 'loiter' for about the same? also, just because there's a bit shaded circle on the editor doesn't mean it's going to engage. That's mostly (I think) just detection area. See above for determining actual range. OR set waypoints for tornado so that their ROE is to NOT engage until they're a certain distance. As an example, set wp inside engagement range with ROE to 'do nothing' or 'hold fire' then put another wp close after the first and near actual engagement range (see above) with 'fire when attacked' or something.

Used Tornadoes? Try using F16s and see how well they fare. Those Tornadoes are Bad A$$. :)

http://files.digitalcombatsimulator.com/en/?arrFilter_CREATED_USER_NAME=&arrFilter_pf%5Baircraft%5D=&arrFilter_pf%5Bfiletype%5D=41&arrFilter_pf%5Bgameversion%5D=59&arrFilter_pf%5Bfilelang%5D=14&arrFilter_CREATED_USER_NAME=&set_filter=Filter&set_filter=Y