Waxi

I realized that the miss of my CBU-97s was probably not due to insufficient or wrong lead aim but due to the strong wind in the Devil's Cross campaign missions. I created a training mission with no wind and could always hit at least half of the vehicles in the column. After I added wind (5 m/s, 90 at sea level; 5m/s, 90 at 2,000ft; 10 m/s, 135 at 8,000ft as in the second stage of the Devil's Cross campaign missions) I could hardly hit stationary targets with the CBU-97s in CCRP, even when using the WIND settings in the CDU.

Yeah, I could take out a column of about 10 BTRs with almost only one salvo from the gun! You just have to disable PAC, line up with the column's moving direction, aim for the last vehicle of the column and hit the trigger. The bullets will be spread over the whole column by the recoil of the gun. That's really fun and effective ;-)

Where did you place the SPI exactly? On the first tank or at some point in front of the column?

What is the most effective way of taking out a moving column of MBTs, such as in the first missions of the Devil's Cross campaign? Any suggestions are welcome. I was trying to lead aim CBU-97s with CCIP but the tanks were moving too fast and always got out of the area covered by the bomb. I guess this is due to the bomblets being retarded by parachutes and that I just have to increase the lead aim. What do you think? Another approach could be hitting one of the tanks with a Maverick, which in the sim always causes the whole column to stop and spread making it an easier target for the CBU-97s. However, this may not be a valid tactic in the real world. What do you think?

Thanks for your opinions on this. I always suspected that there are different rules for the AI ;-)

The AI planes seem to decelerate rather quickly after touchdown. I never manged to decelerate that fast. Even at low touchdown speeds I need a much longer distance than the AI to bring the aircraft down to taxiing speed without applying full wheel brakes. Note that when I flare the aircraft, I set the throttle to idle and fully extend the airbrakes. Without applying wheel brakes it often takes almost the whole runway to decelerate the plane to taxiing speed. Hence, I wonder whether it is normal to apply full wheel brakes after touchdown to decelerate the aircraft. Thanks for your help on this!

Sorry for the late response but I was not in the forums for a while. I use a custom TARGET profile for my HOTAS Warthog and assigned the same key on the keyboard to "Mic Switch Up" and VAC activation.

Ich finde gut, dass ED die Neuerungen von neueren DCS Titeln auch für die "alten" DCS Teile verfügbar macht. Dass ED sich das bezahlen lässt, halte ich nur für gerecht. Erstens ist BS 2.0 laut Beschreibung mehr als nur ein Patch und zweitens müssen die von ED ja auch von irgendwas leben ;-)

You can fast-forward a track by accelerating time in the simulation. If I remember correctly, pressing Ctrl+Y should accelerate time and Shift+Y should switch back to real-time.

I also noticed DCS A-10C only by accident. I immediately bought it an did not regret it.

I use "Mic Switch Up" on my HOTAS Warthog to activate VAC.

Main main problem in evenly breaking seems to come from the toe breaks on the Saitek Combat Pedals: they are a way too smooth-running for my taste. I would have preferred a bit more resistance when pressing down the toe breaks.

Thanks for the hints. I will invert the toe brake axis and continue practicing.

Hi all, I just got my shiny new Saitek Combat Rudder Pedals and I am confused about how toe breaks are used: 1. DCS A-10C configures the toe break axis such that the wheel break is released, when the toe break (i.e., the top of the pedal) is pressed down. Is this the correct behavior? 2. I hardly manage to release both toe breaks evenly. As a result, each time I break only a little, the nose of the plane is turning. How do I prevent this? Maybe these are trivial things but it is new to me and I could not find any information on this in this forum. It would be really nice if someone could give me some hints on both issues...

This is the VAC profile I am using. It covers almost all radio commands and seems to be quite similar to jib's profile. I was creating it using a text editor (Notepad++), which in my opinion is much easier and faster than using the GUI provided by VAC. Being able to actually say "Wingman engage armor with missile from the east" instead of clicking through the radio menu greatly enhances immersion. Moreover, communication with JTAGs gets much more effective :thumbup: DCS A-10C Warthog VAC Profile.rar

Habe mir extra wegen A-10 ein TrackIR 5 mit Track Clip Pro gekauft und möchte es nicht mehr hergeben. Kann es nur empfehlen! :thumbup:

I changed from a Saitek x45 to the Thrustmaster Warthog. This was a pricey deal but I don't regret it.

Ich habe endlich mal Zeit gefunden das Ground Operations Manual zu lesen und habe folgende Anmerkungen: Seite 19: Soweit ich weiß schaltet man das CMSP beim Start-Up nur in den Stand-by-Mode, um ein versehentliches Auslösen von Chaffs/Flares beim Take-Off zu verhindern. Erst nach dem Take-Off schaltet man das CMSP in den aktiven Modus (Manual/Semi-Automatic/Automatic-Mode). Außerdem habe ich noch ein paar Kleinigkeiten gefunden: Seite 23: Hier ist ein unvollständiger/kaputter Satz: "[...] erbittest Du um „Request to taxi to runway“ Nach Erhalt der Erlaubnis zum Anrollen kannst" Seite 23 und 24: Das Callsign "Enfiel" sollte "Enfield" sein. Seite 24: Tippfehler: "gemessene Luftdruck" => "gemessener Luftdruck" Nochmal vielen Dank für die tolle Arbeit! Als nächstes werde ich mir den Sensor Guide vornehmen. Im Umgang mit den Sensoren habe ich auch noch etwas Lernbedarf... :book:

Yes, I am running the latest firmware (version 11 on the stick and version 20 on the throttle) and driver version, which is dated 2011-02-22. Throttle and stick are hardware revisions V.3. The funny thing is that the stick seems to work sporadically. After some while I connected the stick again and it worked until I tried to load my TARGET script. While loading the script, the TARGET Script Editor crashed and the stick was dead again. After this happened, I unplugged the stick, uninstalled and reinstalled the TARGET software, waited for about 30 minutes, and connected the stick again. This time I could load my TARGET profile and the stick worked for about one hour until it died again. I hope it's just a firmware problem that can be solved quickly and without returning the HOTAS. I already sent an email to Thrustmaster support but they will probably only respond on Monday the earliest. UPDATE: I found out that my stick can be reanimated by plugging it out, waiting about 15-20 minutes and reconnecting it. Then it is possible to reinstall the firmware and to use the stick as usual until it dies again after about 15-20 minutes. UPDATE 2: Eventually, I had to mail my joystick base to Thrustmaster technical support in France. One week later I received my repaired joystick. The customer support was quick and friendly. Moreover, I will get my shipping costs refunded. It's nice to see that they are at least anxious about their customers' satisfaction

This afternoon my stick died :cry: It is no longer recognized on any of the USB ports of any of my computers, neither in bulk mode (that's where you have to hold down the gun trigger and weapon release button while plugging it in) nor in normal mode. This is just ridiculous, in particular with regard to the price of this piece of hardware! :mad:

So far, I have called in SEAD and CAS as soon as possible and CAP as soon as AWACS warned me of hot bandits closer than 30 nm. Concerning the ground units movement: I usually carefully look at the mission briefing map and identify all potential ground threats on the corresponding ground units path. Then I note down the coordinates of all potential threats to the advancing friendly units and/or set my target waypoints accordingly (usually I note down the coordinates of one ground threat per group and remember the relative positions of the others). When flying the mission I usually don't call the JTAG and attack the ground threats identified in the briefing directly. After all of them have been destroyed, I command the ground units to advance and call the JTAG for further tasking if I still have some weapons left.

I also bought a TMWH and TrackIR5 for DCS A-10C. Now I am looking for rudder pedals and started thinking about a multi-monitor setup, which would also require a new graphics card... I urgently need to win in the lottery :cry:

Ich habe eben mal Euer Handbuch zu Falcon 4.0 AF durchgeblättert. Nicht schlecht. Ich freue mich schon auf das DCS A-10C Gegenstück ;-)

Thank you so much. Must have missed the other thread...

After installing the latest patch (1.1.0.9), the main menu of my DCS A-10C installation is in German. How can I change the language of the main menu back to English?