Evil.Bonsai

1. Review mission details thoroughly prior to mission start. Make notes if necessary. And I just played that mission and had a similar issue: I did remember where the points were, but sent them to opposite points. Oops. 2. This has been happening to me lately as well. never did it before but has done it a few times recently. The only way I've been able to fix it is by ending the mission.

Uhm...look at a point on the ground, use 'smoothing' option for TRACKIR, move head along with point you're looking at? That's how I do it, anyway. Works fine. UNLESS you mean it keeps a specific point center of screen no matter how you move your aircraft. Then no, it won't do that.

One way of doing this is to setup a trigger to play/display amessage alerting player that enemy was spotted and to contact jtac on a specific frequency, then proceed as normal. I've never tried setting up a jtac 'zone', not sure if that is possible.

Land, taxi/park (if able), canopy open, ask for ground power, shut down engines. wait for repairs

I made a single mission (found under user files here), with no TGP. Your only 'view' system was an IR Maverick, at night.

Please upload the track and it will be WAY easier to help. As for MGRS and CDU, there are several excellent tutorials on youtube. But if you think you're doing it right but get a mission point that is VERY far away, check the cdu for 37T or 38T. Whichever it happens to be, change to the other, and it might fix your problem.

It actually is being worked on for the A10. Raytheon was awarded a contract in 2010 for it.

Actually, they did update GH for use with CA. Forget if it was a separate download or not, though. I have both GH and GH with CA enabled.

Download DCS world and install. Download the A10C module, install. Use your steam key to activate A10C http://www.digitalcombatsimulator.com/index.php?ProductId=21&end_pos=137&scr=product&lang=en http://www.digitalcombatsimulator.com/index.php?scr=product&ProductId=8&end_pos=136&lang=en

In other words, install the A10C module, use your existing cd-key (from 1.1.1.1.). This way, you can play DCS World and fly P51/A10/Su-25 as you like, and also fly dcs: a10c v1.1.1.1. as you see fit

Start your own, then. If I can't find one available, I just make my own. Sometimes people will join, mostly not. No biggie.

I use vipers cougar files as well. Made a few chages due to my radio hat not working so well, but otherwise works great.

http://war-hawks.net/private/index.php?option=com_content&view=article&id=122&Itemid=130

If you're shooting in a vacuum, sure. But that long distance is made of air, which will seriously degrade performance. At 3-4 miles, might as well just drop rocks on them, because by the time those bullets reach that far, pretty much all their energy will have been expended getting there. Effective range is about 1 mile. Better to fire at <1 mile http://www.military.cz/usa/air/in_service/weapons/cannons/gau8/gau8_en.htm

at 3-4 km, never mind miles, you really should not be pulling that trigger on ANYTHING.

FTFM

group ai off at mission start, then group ai on when you want them to go somewhere. And you will need to setup waypoints if you want them to go anywhere.

Yes. set an 'entry zone'; now set a flag so that when a unit enter's THAT zone, the flag is switched ON. if in larger zone (airspace), you need to 'verify' each units flag for that entry zone. If the unit passed through that zone, it's flag is on, thus it's ok to be in the larger zone. if a unit did not pass through that zone, it's flag will be off, such that when checked while in the large zone, it'll get the message to depart. Then, once the unit leaves the larger zone, the entry flag is turned OFF and you can start the process all over.

Just messed about with this idea. It's actually pretty complicated. In zone/out of zone and going back and forth is pretty easy, if you don't need anything else. However, you also need to check altitude while in that zone, so flags are necessary. Exactly how to frame the logic needed to check whether a given unit is in zone A and while in that zone if the unit's altitude is +/- a given altitude, started throwing me for a loop. Unless I missed it entirely, you can check for this OR that, but not this AND that. Plus, sending a warning to a specific unit I don't think is possible. You can check if a singe unit (ie, plane) is in the zone, but if that unit has a wingman that is no where near the zone, if the first unit is in zone and gets the warning, so will his wingman (group msg exists, unit msg doesn't) I also had the idea of several small zones leading to/from runway, then one large zone centered over those. But again, the logic of checking in this zone ok, that zone bad, in both zones, you're ok, escaped me. I'm sure it can be done, but it seems to be rather convoluted. Plus, you will be always checking every unit (all units you want to apply this to, anyway) for these conditions. For single player, it's not so bad, but I'd hate to have to set it up for multi-player scenerio. Update: actually, it might not be too bad: set flag 1 true if below 3000ft. set flag 2 true if in zone (both of these can be switched). then check continuously: if flag 1 equals flag 2, then you're ok. if flag 2 is greater than flag 1 (ie in zone, not below 3000ft), then play message "get out". I'm tired, time for bed. I'd like to actually work on this but need to get off computer now.

Yup. When CA first came out, was playing online (forget which map, though) and someone was flying a Blackshark and plinking tanks. I got killed a couple times. But I learned to just scoot back from a hill crest and started shooting "BVR" over the hill at the guy that was just hovering there. Took about four shots, but he went down. I couldn't see him but my target brackets never moved.

This is the first sim I've played and ever even attempted to land via instruments. This my first. Need to practice some more. Thing is, I was so happy after this I didn't want to ruin any further attempts by crashing, again. My first, and only ILS landing.

I go by what I perceive to be the highest threats: sead, cap, cas. That's just my opinion though.

I'm having trouble changing the behavior of the AH-64s in GH mission 1-3. I've already changed the behavior in 1-1, but for some reason it isn't working in 1-3 (these are the stock georgian hammer missions, except for a small change). I got tired of the Apaches getting shot down by SAMs that I decided to add an orbit hold and radio item to release them after SEAD and CAS got a few kills. Works fine in 1-1 but when I tried to make the same change in 1-3, they just continue to fly past the orbit/hold point, right into SAMs that have yet to be killed by SEAD. Anyone able to take a look and see what I might be doing wrong here? Thanks. jcCA-Push - 1-3.miz

103's and 105's are completely different weapons. The 103 drops bomblets that fall to the ground. The 105 drops parachute munitions that float (at first). Wind won't have nearly as much affect on the 103 as compared to the 105.

ammo depot, and friends, destroyed w/1 gbu-12 :music_whistling: ammo dep.trk