Evil.Bonsai

Hehe, watched video before reading that. Was thinking "WHY aren't they peppering him with .50? He should be in flames by now."

There'll still be time, in a simple mission, to get plenty done. I won't be home until tomorrow, but I can post something up, if no one else does.

Be aware that the track system isn't exactly the most robust. When a mission/track file runs a bit long, errors start to creep in, to the point that it drifts away from what actually happened. It may have gotten better with recent updates, but I've not heard anything saying it has. A fairly short custom mission lasting about 40 mins might be about max. Longer than that and you start getting errors, in a way that events unfolding on the screen as you watch won't necessarily match what actually happened.

You're welcome. :) I learned here, reading all the posts I could find about it, even checked internet for UTM and MGRS info. This is why I have my "Location" over there on the left. Zone is 14R, MGRS coordinates PU170610. And to add a small amount of confusion: there are actually 10 numbers used for a more precise location. You can see these in the Mission editor map and on the f10 map while flying. I don't remember the difference between using all 10 versus just 6 (leaving off the last 2 digits of the easting and northing). It's enough info to point the TGP in the right area and find your target. Good reference: http://en.wikipedia.org/wiki/Military_grid_reference_system also says using 6 numbers will give an error of 100m vs 1m for all 10.

I just added a full cloud layer at 4000m and reflew that same mission from the screenshot above: no change for me, works as intended. Although, I found a new feature: nvgs turn the eo tgp to nightvision as well. Sure you're not enabling a FOG layer or something? Using NVGs and looking out canopy, can you see the ground ok? Something just doesn't sound right.

No, no, no...you're getting them mixed up. The LN or KN or whatever is just as important as the numbers for the coordinates. That doesn't change from what you're given (ie, LN543987). 37T and 38T are a much larger area (that contains the coordinates, as example given above). The problem is that UNLESS you're right on the edge of 37T/38T you pretty much never have to worry about it. However, if you start/takeoff in one zone, say near the coast (37T) and attack targets a few miles east, you're going to have to change 37T to 38T in the cdu. Georgia is MOSTLy all in 38T except for a strip near the coast, which is in 37T. search youtube for dcs a10c cdu tutorials. You will likely have to play with it a bit before it really starts to sink in.

Enter either 37T or 38T in the cdu

Yeah. It's just a dimmer, like on some LED alarm clocks. Turns the brightness down so as not to wash out eye sensitivity. Doesn't matter much in the sim, but I'd guess quite useful in the real thing.

Doesn't change how you enter the coordinates, just changes where those coordinates are located. If your target is in zone 37T, you would need to enter that in the CDU else your coordinates will be WAY off. IF you're not sure and you're close to the line separating the two zones, just enter your coordinates. If they seem way off, change to the other zone and you should be able to find your target. Make sure to double check your coordinate entry. Several times I've swapped M/N w/o realizing it and sat trying to figure out why my coordinates are so far off.

Works fine for me.

I'm surprised they bothered to use a bridge; when I've tried telling a column cross a river, I click on both sides of bridge but they always decide to use their own 'ford' path, somewhere on either side of the bridge. Weird that they included multiple 'columns' to choose but no 'follow road'

sounds about right. The only way to tell for certain is to post a trk file. I believe the missing zeros was fixed. You should be given 6 numbers. For Smerch Hunt, you should be in zone 38. 37 is near the coast. If I remember correctly, Smerch Hunt is set pretty far east.

Could a controller be sending 'mission end' shortcut in some way? Maybe unplug all controllers but keyboard/mouse. I don't know of a specific 'mission end' shortcut as I always use the 'esc' key then click end, but there might be a specific key combo/shortcut that might be doing so.

Enemy air DEFENSES? Just stay far away and search with TGP. No other option, really, unless you're in multiplayer and someone plays JTAC for you.

CONFIRMED!

http://youtu.be/WmbMd_KxEM0

This is relevant to my interests. Must try this asap.

It looks to me that you're doing something to command the tgp look elsewhere. The image looks fine, just not what you were looking at a moment earlier. In the 2nd image, I see a shallow view of green/grassy area with either a road or small stream. PLEASE save the track file and upload it. That is the only way to see what you're doing.

DAT SOUND!!!

Hmm...dunno. I could cause them to go ballistic or track and destroy a target every time by moving the tracking radar farther/closer.

What's neat is you can set up a group with required launchers and control systems, place the launchers miles apart, and away from control/radar vehicle, and they still work just fine (at least they did when I tried it back in 1.1.1.1). Can't remember which (osa or kub?), but one of those has a launch vehicle and a radar vehicle (need both in a group). I put radar in center and placed two launch vehicles far enough north and south for their zones to just overlap the center, and as long as I was in the radar vehicles engagement zone, whichever launch vehicle I was closest to would launch. For all the systems with multiple entries (like patriot), you need to have a specific set of vehicles. If I were at home, I could look and tell you which ones. Some units are self-contained, some need a launcher and tracking radar. Some have launcher, control vehicle, early warning radar, search radar. I tested these all out once, a while ago, but things might have changed since then. Edit: did some testing with s300 system; if the track radar was more than 5nm from the launchers, the missiles went ballistic and exploded after launch. Going to try this some more, as I'm curious to see what each system can do.

Just checked, and yep, they're shooting nowhere near threat. Set up a quick mission with F5E at 7 o'clock of a Tu-95. The Tu does shoot, but instead of back at the F5E, it shoots FORWARD and UP. Switched a Tu-22 for the -95 and same result: tail gun shoots FORWARD and UP. EDIT: just tried same thing w/1.1.1.1 and tail guns work as they should.

Because it doesn't work that way. Your steam version of A10 is a complete, separate game. DCS world is, basically, the newest, updated version of A10C (or blackshard, or p51d), but without access to the A10C. DCS World is free, which is why A10C is not included. However, you own A10C and can easily get access to A10C in DCS World, by downloading and installing the A10C module. As posted above, the modules are small, and are only needed to add the complex sim part for whichever craft you buy (a10c, blackshark, p51). You already own A10C, so you do NOT have to purchase it again. Just download/install the module, use your steam cd key to activate.

I'd say stay away from the actual runway, especially in multi-player. Aim just off the side of the runway. This will leave the runway clear for other aircraft and you can still get repaired. Once repaired, taxi over to parking/taxiways, then follow normal ATC for takeoff

Not anymore. Time for the Z-Max ammo...