Mike5560

What better of a pc experience can be had in terms of enjoyment and keeping your mind in shape than DCS? Day to day, we take for granted the overall experience that ED brings and focus on bugs, improvements (rightfully so) and when the hell DCS 2.0 will release! I haven't regretted a module purchase yet, and overall Im a very satisfied customer, thanks ED! Chief, overall I like hearing about the diversity of us simmers. I think you will find a lot of others on here willing to help you out or join you on online gameplay.

BMP 2s and 3s are a big nuisance while flying low altitude. They will engage before a shilka will, outside 2 nm. BMP 1s have a 105 cannon only, don't know if they fire back with it but I've never been hit by one, though it's difficult to differentiate them between BMP 2s anyway. If you're able to strafe from 5,000 AGL or higher, any strafe 15 deg. or more of dive and they will fire at a lot shorter distance. I have the pipper/PAC1 on them by 1.4nm and fire a one second burst at 1.2 with a brisk escape turn and very rarely do I get hit unless there's a closer threat. Shilkas and ZU-23s will fire at about 1.5. It's all about doing a good scan and developing a plan of attack, having good eyes looking out between wingmen in MP. All this is good info and pretty much "gaming" the tactics until a MANPADS or strela throws some missiles at you. Using Tacview will help immensely.

I can't confirm with 100% certainty, but I think it's a small bug of the sim's logic. I almost always use area track instead of PT on still targets for this reason. Sometimes when you use point track, the logic gate places the TGP cursor slightly off target. Since in DCS, the Maverick seeker is slewed to exactly the SPI point, I don't think the maverick recognizes whatever is dead center of its crosshairs as a target sometimes. I notice the same thing happens sometimes....I can't get a lock with TMS fwd only, but I find a quick bump on the slew control will either cause a lock, or cause the seeker to slew off of ground stabilization. In this case, china hat fwd long and repeat.

On SAM simulator, for instance, the SA8 Osa has seperate switches for acquisition radar emissions and the radar rotating.

Welcome! Everyone has a different learning path. Probably the most effective way to learn is to take some good suggestions about reading the manual, learning the navigation systems, MFCD pages, SPI and SOI, weapons employment, emergency procedures and that nasty CDU. Me personally, I did a combo of the training missions and making my own simple missions on the editor initially. Being familiar with the A-10A from flaming cliffs, I went ahead and tried the campaign with lots of good lessons learned. I would pause the sim and look at the manual if I needed to reference it. TrackIR and a good HOTAS stick with the right buttons mapped helps immensely. You can fly a mission almost exclusively without taking your hands of the throttle and stick and look around as needed. Youtube tutorials are your friend.

I realized this as well. So I did just like you suggested: taking a screenshot with my phone. Looking back, Im not sure if the objective zones are visible during the in-game menu under "briefing". I think right now, the bug where convoys have trouble crossing bridges is fixed. -So what I did was cleared out all threats friendly armor and mech through an exhaustive process, then landed and assumed control of the vehicles (first person view) and drove the M1s and Bradleys over the bridges myself.....but it worked! I believe you get a message when the friendlies have reached their zone.

That track was comical. Never tried Aim-9s on ground targets, so that was interesting. I was expecting the run-over pilot to be flattened, but it didnt happen, at least not on my replay. Bro, do you even PAC? It helps accuracy a lot.

Are you positive of the actual elevation above the SAM? You mentioned SU-25, so it was unlikely that you were able to determine the SAMs elevation relative to yours unless you paid specific attention to it. Also, what fltsimbuff said; "max altitude" is highly dependant on the aircraft speed, especially with CLOS guidance systems like SA-19. Those advertised specs could be against a mach 1 target, for instance. Firing from a higher elevation helps its range too. Heck, baseballs fly noticably further in Colorado. Air density means so much to a mach 2+ missile.

I've been forced to eject in a SU-25T when hit by a single Igla S, though my wingman seems to think he's on American Gladiators; flying over the enemy edge of battle popping flares, dodging about 5 missiles and ejecting after being hit 3-4 times. I have no problem taking them out on the ground with a one second burst of CM starting at 1.0nm. Your results are unusual, but not totally surprising.

Shilkas in DCS won't track you until you're within 7-8 km. Kind of a waste of an anti radiation missile, you can out stick them with vikhrs or fab-250s is you attack from high enough and know when to pull off on a bad rollout.

Fuze settings as far as airburst or delay aren't modeled on the A-10. IAMs, more specifically JDAMs use a very simplistic function in DCS, while in real life several additional parameters can be inputted into the weapons profile. I don't know if this was part of the agreement ED had, or because of classified reasons or if it is truly part of the early A-10C Suite 3 represented in DCS. RL A-10s are on Suite 7 or maybe 8 already.

Obviously SAMs are most effective with an IADS and all operational radars working, but the minimum requirements to actually engage are different based on each system. Most, if not all SAM systems deploy with: A search radar, which is usually omnidirectional (spinning)which supplies general location data. A tracking radar, which generally provides refined elevation and range to the launcher (command guided) and/or the missile (SARH guided). Typically the target tracking radar has a very narrow beam and without a search radar to provide azimuth and range data, it can become difficult to engage but still possible. On SAM sites that employ the search radar, track radar and missiles on seperate vehicles, it is usually most efficient to target the tracking radar as usually there only one of them or less tracking radars than vehicles with missiles.....target tracking is required for a guided engagement. (Patriot, SA-10/S-300, SA-3, HAWK) SA-11 Buk has a seperate search acquisition radar (SNOW DRIFT) but each launcher has an integrated track radar. So destroying the search radar greatly reduces it's effectiveness, but guided engagement is still possible. SA-6 Kub Has a search and track radar on one vehicle (STRAIGHT FLUSH) and the TELs, or launcher vehicles have missiles only. SA-8 Osa, SA-15 Tor, Roland and 2S6 Tunguska all are all all-inclusive, or Transporter Erector Launcher And Radar (TELARs) and require no additional supporting vehicles. If you check out sam simulator and read the documentation about the different systems if you want a more detailed understanding. Google it, it's a free download.

Survivability goes way up. How many times have I found strelas or AAA with the TGP prior to coming in for a dive attack. Now sometimes I like not bothering with a TGP so much for a little challenge on a quick mission, when a JTAC passes all the neaby threats with his eagle eyes...but if Im taking time from a cold start and a long flight Its a real buzzkill to eat a missile and be forced to eject knowing I couldve done more. -pull out survival radio, "2, engage air defences, at smoke trail, with maverick, youre now Sandy 1!" Anyway about the topic. I recently discovered that mavericks can be launched (force correlate) before the range caret appears on the screen. Killed an SA-6 from 14.5 nm away. Lol ok I guess Ill take it. That was at 22000ft at 300kt TAS with both H and K.

I watched the track. I think after you saved your profile and selected it, your switching to CCRP via master mode button seems to have reset the autolase function. I'm guessing it loads a default CCRP profile outside of your settings for CCIP. So before going into your "CHG SET" page I recommend switching from CCIP to CCRP first, so CCRP is tied to the profile.

The JTAC does not provide a grid zone designator (e.g. 37T), only a 100,000 meter identifier (e.g. EK) plus the coordinates. Go to the options under main menu, go to the misc. tab, and check "Allow F10 map view", and in the block below it, select MGRS as the coordinate format. Now, when in a mission and are handed coordinates, look on the F10 view and place the mouse arrow where the general target area is. In the top left, it will provide you the full set of coordinates. These do not need to be accurate as a grid zone is very large, usually 6x8 degrees of latitude x longitude. On your CDU, the 100,000 meter square identifier and 10 digit coordinates are entered by OSB 16. Note if the 100,000 meter square identifier is already the same as the one you need, you do not need to enter it, only the 10 digit coordinates. On OSB 17 you can enter the grid zone designator into the scratchpad and change it here.

I noticed that I'm starting to have a problem with vikhrs that I didn't in the past. Some of the vikhrs seem to only temporarily catch the laser beam and then stray off target. This seems to happen when the missile launch zone reticle is far to the left or right off center vs when it's near or on center. I used to get a solid 15-16 good hits off of a full load of them and now Im getting about 8-10 or a little over 50% probability of a hit. Note: I am placing the target dead center of the missile launch zone reticle and I'm keeping the aircraft manuevering as little as possible. I normally never did this, but I even tried turning on the laser rangefinder prior to launch with no improvement.

So I had a mission in the Georgian Oil War campaign where I had to recon three target areas and destroy targets of opportunity. On the mission planner screen, all three target areas fall within an SA-8's engagement zone. This has happened on previous missions, and the SA-8 wasn't there, so I flew the whole mission like a boat with two KH-58Us and fuel tanks weighing me down. I only ended up taking one, and didn't think to give my wingman any since he was pretty useless in the past. I took off, and fired my KH-58u as soon as I got a spike from the SA-8. I turned away and watched the F6 view for peace of mind. Turns out that nasty Osa took out my only ARM. It ended up killing me even trying to maximize standoff from my vikhrs into the first target area. Has this been a change in one of the updates? I've played DCS hundreds of hours and never seen this happen in SP. I do know in CA this can be done if you play as an SA-8.

Looking at the HSI helps. Look at the attached image. In my example ATC ground tells me to taxi to runway 7. So approx 70 degrees on the HSI.....visualize that as which way you will be facing when you're on the runway about to take off. I will use the F2 view along with this if I'm confused.

Are you familiar with the fact that the parameters for dropping unguided bombs CCRP are different than guided ones? By default, mk series bombs are in "5 mil" mode, meaning the PBIL must be within the very small circle in the middle as the countdown reaches zero, with the pickle button pressed.

DCS F/A-18C should make lofting bombs fun. Who needs a maverick when you can loft a GBU-38 7+nm?

The mission "kill box" off the dcs website user files has tankers and a 700 nm round trip commute, IIRC. Autopilot and phone games are your friend.

Nice mission! Not too invasive but informative and a cool ending. My first try took a while since I got all but 3 tanks on one load and had to rearm.

Ideal turning performance is around 425-450 knots. Many fighters say "speed equals life" in general. You might not have the best turn rate on your first turn of a dogfight going 550 kts (and certainly large turn radius), but you will have more energy left over than from starting at 425 kts.

Not sure if this is a repost. Title seems wrong. Looks like strictly a SU-25 doing ground attack. Natasha doesn't seem she's into the whole 'brevity' thing. I'm going to fly the frog for a bit....

I have never seen a reason to use any HOF higher than 700 feet, as the dispersion of the submunitions seems to be the same as a low HOF......and the wind drifts them off target more. HOF is not based on MSL altitude, but AGL, since the CBU has a radar proximity fuze. Keep in mind you need to beware of the offset that is imposed by 97s and 105s. Your CCIP release point or SPI from a CCRP release is not exactly where the submunitions will be falling on. Basically the weapon falls or guides itself to your release point of SPI and deploys the submunitions at the prescribed HOF setting. Since the parachutes stop the forward momentum of the submunitions and the bomb (typically) doesn't fall at a 90 degree angle, the footprint of the submunitions will be short, unless you account for this. It took me a while for me to get a good idea as to where my bomblets were going. Best thing I can recommend is practice with CBU 105s and experiment where you set your SPI in relation to the target and when you release the weapon. I try to launch at min range so as to reduce the seperation between my SPI and the bomblet footprint.