Eviscerador

You need to fire at mor than 4 km from the tanks, because they have AT missiles which are faster than yours, so you can't kill them before they kill you. If you can keep moving, centering the viviane and firing while not breaking the wire all the time, good for you. I can't, so I search for ridges or forest lines at around 4 km and do pop up attacks. Also turn off all the lights, AI will take longer to spot you if you don't have any light on.

I always used the fuze option. If you want high drag, select nose fuze, if you want a standard Mk82 performance, set tail or N/T fuze. As simple as that.

You need to reload dts and recycle the countermeasures panel. That worked for me.

I guess next time a dev should have just said: "Battery is not modelled because according to Gazelle manual both batteries have enough juice to complete a night flight even if the generator fails in flight, and we considered that it wasn't needed to model battery consumption" We could have spared 6 pages of nonsense.

The only way I get an antiskid warning and a dropped switch is in case I pull the emergency brake lever, I blow one tire or I just have a catastrophic failure (both engines and hyd sys down). We need more info on that issue.

Yes. The Hog was my first DCS module (heck, I own it from before DCS was even a thing) and I still go back to flying it low and slow. It is an old school mud pounder. You don't have speed, you don't have finesse, but you have 11 ordenance stations, over 2 hours of station time and 1150 rounds of 30 mike mikes. Also, the targeting pod, D-Link, CDU and DSMS gives a LOT of deep to the module. I just can hope that the hornet will reach the same level of module polish the A10C has now. Even if the Hornet is the current flagship of DCS and Eagle Dynamics, the A10C module is still where the excelence bar is set. Buy it, you won't regret it.

I guess this is a bug. I've been able to lock other helicopters with the Mistral IR missile through solid terrain, like mountains and valley ridges. I was on an ambush waiting for the enemy team to close by, and suddenly my Mistral got a lock tone. I zoomed in and there was nothing there, but the "lock" was definetly moving. After it got over the ridge, there it was, an enemy Mi 8. I tested it again with friendly helicopters and I always got a lock no matter if I had line of sight or not. I might be wrong, but this is not supposed to happen, right?

I already solved the problem. I was a bug with the SAA and the NVG layout. I just disabled SAA and everything went back to normal. I think they already solved the issue, but I'm leaving the SAA off because I don't see any difference in graphics and I have more performance this way. Thanks for your reply.

I usually use the JTAC coordinates to get a rough estimation of where the convoy is. Then I look with the MK1 Eyeball untill I find it. Sometimes they are in a road, sometimes they are off road. If they are in a road they are easy to spot, and if they are off road and moving, look for smoke and dust clouds. Anyway if the convoy is large (over 6 vehicles) it is easy to spot, even without zoom.

Thanks! I know I've been bitching with the inconsistency of the JTAC and the AI but don't get me wrong, the campaign is superb, I enjoyed every mission. Looking forward to your training campaign for the Hornet. Because there will be right? «Wink, wink, nudge nudge»

Well, I managed to finally finish the mission and the campaign. Since my wingmen were uncooperative and just didn't acknowledge any directed attack order, (they did in other missions, maybe has something to do with the LoS as I said in my previous post) I proceeded to anchor them at the IP, destroy Target 1 and Target 2 as fragged expending most of my ordenance (except 210 cannon rounds and 2 mavs) Then I managed the CAS with the support flights and the gunship and finally when all the support flights were killing stuff left and right, I ordered my wingmen to attack weapons free (since any other order was just a "join up" "RTB" cycle) To my surprise their priority order was nice and I managed to pass the mission with Q qualification. Loved the "final surprise" by the way. All in all, it was a SUPERB campaign as all the others, good job with the documentation, the voice lines, the triggers and the whole immersion. It is a bit frustrating sometimes when the JTAC or the AI don't work as planned, but that is mostly due to the inconsistency with JTAC in DCS world.

Aside from the full combat campaigns, I also recommend the training ones. Sure they are not as flashy but if you really like the plane they are a must. If you want a pure combat one, Piercing Fury and TEW are both great.

Hello, I'm finally trying to finish the campaign and I'm finding trouble with the last mission. I destroy the Target 1 no problem, but when I try to destroy the second target (convoy) I find that the convoy is moving along a road which is totally surrounded by trees, making it really difficult to spot, and once you spot it, your wingmen cannot attack it, because they lose sight of the objectives. Even if you make them break the road (usually after killing one or two vehicles) both wingmen just refuse to acknowledge any attack order on the convoy. The problem is that if I use all my ordenance to kill the convoy, then I don't have enough to reply to the other threats, while my wingmen usually die in the first attack run so I can't complete the mission. Oh, and the bandit spawn makes them going defensive and I think they drop ordenance, because ANY attack order I give them to use bombs is either bugged or they don't comply. I will keep trying to do the mission, maybe one day the wingmen will acknowledge the orders, don't die, and I can complete the mission, but I'm under the impression that my skill and knowledge is irrelevant, since I just need to use wingmen to destroy all targets, and they usually DERP a lot. This is a main feeling in this campaign. Both the basic and the Advanced ones were based on your skills. The tactical campaign is based on JTAC and AI behaviour, which is very inconsistent, and it is very frustrating.

Didn't they tweaked something about the landing gear drag? I also noticed that I loss more speed on landings than before.

That is nice, I had to stop the campaign because it was impossible to play without the IR camera. Time to hop again into the Gazelle!

This is what I did till I upgraded mi rig. Just click "later" when the updater tells you to upgrade to 2.5.2 version.

Finally! It seems that SSAA just offset the NVG because for some reason it forgot to readjust the NVG frame to the final resolution. It seems it is a known (and not fixed) bug since at least March. When I erased my DCS folder I got default settings which mean SSAA OFF, then I tested and I got it to 2X, that is the reason I kept getting off set NVG. Now it is just all about not using SSAA until they fix it.

This is still bugged by the way. Any ETA on a fix for this?

Well... it is back! for some reason after a few games the NVG is again offset... I don't understand it and I don't know what to do anymore... after deleting my Saved games DCS folder the only thing I copied again was the Profiles and logbook, but that shouldn't do anything right? Any tips? PS: I thought it was a A10C related bug, but it seems to be a general one. Gazelle attached, same offset.

I did that, removed the FXO and metashaders and is still in the same place... I guess somewhere in some file I should be able to fix this right? Could it be something in the options or config files? I uninstalled the A10C module and installed it again. Still there... Solved, I just erased the whole SavedGames\DCS folder keeping my logbook and control settings. I guess something was wrong there...

Hi everyone: I updated to 2.5.2 the last week after upgrading my rig and I found that the NVG in the Hog are offset to the left and to the top, making flying a pain in the arse. Is this intended or is something that is wrong with my client? I did a repair but nothing changed... Any help?

Hi! I installed 2.5.2 one week ago after upgrading my rig. I found that now the A10C NVG works like this image. Is this intended? Because flying a night mission or even worse, doing AAR or low level interdiction is hard as shit with the vision tilted to the right so I can see where I'm going...

I will repair and reinstall to see if it is a local issue. When doing the SEAD mission the jtacs were totally missing, I had to find the strela and the shilka by baiting them... and then the chevy chopper crashed when landing and I got misdion failed.

Something is wrong, maybe with the last update something went wrong. Just made TTQ13 and the JTAC behaviour was really weird. No reply to "contact" calls, WP not firing, no further details read on... I just had to check out and call in again a lot of times until I got the proper readings, and most of the time I used weapons based on my own guesses because the JTAC didn't call anything. Oh, and the cherry on top was the final target that was so close to the JTAC that they themselves killed it, so the FE called "end of VUL" and I returned to base expecting a failed mission, just to find out that I "had killed" every target, even if half of them were killed by the JTAC themselves. I attached the log for this mission. I will keep playing the campaign but currently the unconsistent behaviour of the JTAC make it a bit frustrating. But don't worry, I can see the amount of effort put into the campaign. It is still great. 1.rar

I replayed the mission. Same problem. I check out and call again, it worked but when I had to contact Uzi again for the final set of targets, he didn't respond at all. I had the proper frequency, and he responded the first time the FE told me to contact him. I spent all the play time till the FE made me leave and got mission failed again for not destroying all targets... As I said I'm loving the campaign as I did with the previous ones, but the JTAC inconsistency is becoming an issue.