gachatar

It works for me. Did you switch to A/A TACAN mode and held down ON/OFF to turn it on?

Seconding, flied the mission twice and have the same problem. You switch to channel 8 on PRI as instructed, there is a Nail radio check, Smoke replies, and from that the script doesn't progress to the part where you would normally ask to rejoin the tanker. Edit: Flied it again from the first checkpoint save (R1 M03 ALT A.miz) and this time Arco was in the tanker radio list and mission prodceeded normally. First two times I played from the beginning.

It seems to have the same bug as the one with A-10C II launch. If terrain is uneven (ie. mountains), CCIP pipper is off.

I tried using HARMs, hit both SAMs and then I got mission failure for not doing first objective. I just ended up ignoring the SAMs and shooting the artillery from just outside SAM range with the Mavs.

Tried mission 2 three times, soldiers not entering vehicle. Latest openbeta at the point of writing.

And that's your first mistake.

Did you check at axis assign? It's normal that you cannot assign trackir to normal buttons and switches.

Speaking of different warheads, is there any INGAME GAMEPLAY difference in DCS between Mk-84 and BLU-109?

This is a bug that happens when turning off the radar while Air Ground Ranging is operating, then cancelling AGR mode while the radar is off. Don't ask why did I even do that in the first place. 1. Select Air to Ground mode 2. Select GUN on STORES page 3. Press Sensor Control Switch FORWARD to make HUD SOI and enable Air Ground Ranging 4. Point the aircraft's nose towards the ground so that valid AGR information is displayed on the right DDI ATTACK RADAR page 5. Turn off the radar on the right console 6. Press Sensor Control Switch RIGHT to make the right DDI with the ATTACK RADAR page SOI -the HUD is now stuck in AGR mode, even though it's no longer SOI -the ATTACK RADAR DDI page is now stuck and cannot be changed to a different DDI page with the menu button (PB 18) Turning on the radar again will unstuck both the HUD and the DDI. agr bug.trk

Page 182 of the F-18 manual states that single GBU-12 and GBU-16, and double rack GBU-12 can be loaded on station 5 (the central pylon). These are not available for that station ingame, only dumb bombs are allowed. Tested in mission editor and ingame ground crew loadout menus. Edit: Page 189 of the manual says that you should be able to carry 2xGBU-32(V)2/B on stations 2,3,7,8, just like you can carry double Mk-83. Ingame only single GBU-32 is allowed on those stations.

Not sure if this is a bug or not, but the inconsistency between the HUD and the STORES page fooled me many times. 1. select a bomb, for example Mk-83 and be in CCIP mode 2. designate a target point (WPDSG, HMD ground designation, FLIR TDC, etc) 3. bombing mode now automatically switches to AUTO and this is reflected on the HUD on the right side 4. the STORES page still shows CCIP bombing mode Expected behavior: STORES page displaying AUTO bombing mode. stores bug.trk

Even with the fixed missions in the user files?

Operation Piercing Fury, a previously paid campaign is now free. Get the 2.5.6 fixes from the user files. Sturmovik is also free. Both requires a bit messing around in the mission editor to change your player aircraft to A-10C II since the missions are for the old A-10C.

I've been through training, flied some sandbox missions practicing against both air and ground targets and want to start playing the campaigns. I'm not anywhere as comfortable with the F-18 yet as with the good old A-10, so I'd rather start with something easy so I don't have to replay missions over and over. Which campaigns are relatively easy/simple and which ones are more challenging? Here's the list, let me know if I missed anything: Task Force Challenger Serpent's Head Raven One Rising Squall Operation Pontus Also feel free to recommend some of the free campaigns available to download, there's a few of them but I have no idea if they are any good. So far I've seen this one recommended: Operation Cage The Bear (and of course Liberation, but that's another kind of beast).

Would you recommend reading the book before playing the campaign?

Same issue. I was looking forward to playing the campaign without having to mess with the mission editor, but I guess I'll just change the parking spots. Also the first mission's waypoints are all wrong. Oh and mission 2 pathing broke again too with the convoy getting stuck into each other or a bridge or something on the road on Delta. Kinda losing hope of ever playing this campaign without major issues.

Maybe you accidentally switched to a different crosshair with DMS LEFT/RIGHT with HUD as SOI. We use COOLIE UP a lot now to make HMCS SOI, so it's easy to make a mistake and press inputs on the HUD.

If it really bothers you, you can make some autohotkey script that quickly presses OSB keybindings for TGP standby and AG and put that on your hotas.

Just switch to open beta. It's not like the "stable" version is much more bug free.

TMS right makes a mark point (with any sensor), and TMS right long turns that into a SPI. Yet there is another function, China Hat forward long, that slaves all sensors to SPI. The first one is useful to make a markpoint and turn it into SPI without having to make it your steerpoint first. Second one makes all your sensors look at it. They work together perfectly. Yes I understand that I have 5 sensors-HMCS,TAD, TGP, HUD,MAV, AA. But the issue is I have only one focus in my brain. If I am dealing with ONE SPI (by default the A10 only gives you one), it can be confusing to have different sensors looking at different things. It would be pretty awful if looking out the window with the HMCS kept changing your SPI while the TGP was nicely tracking a tank, wouldn't it? For example, people have noted that different objects can be 'hooked' with different sensors. And that hooked data is different with different sensors. If I can hook only one thing at a time, then how is that different than a SPI? Hooking is basically selecting an object, but you don't necessarily want to make it a target. For example hook your wingman on the TAD to display his bullseye coordinates. Then besides hooking/marking, there is the idea of 'slaving' - basically deciding when to collapse any two interfaces on to the same data point. If TAD is SOI , why do I want to be messing with slaving the TGP to HMCS? Looking at something with the HMCS and slaving the TGP to it is such a useful function that it always works regardless of your sensor of interest. It would be safer to have a kinesthetic domain where my brain would know-looking out the front windshield is for driving, looking down at the right MFCD is for weapon targetting. The whole bomb thing could happen on the MFCD. Dive bombing on the MFCD wouldn't be terribly safe, you'd crash into the ground. You really want to see where you're flying. Guns and rockets are still too stupid to do their own thing so I guess those cues still have to pop up in the HUD when I use them so I can point the whole aircraft where I wanted them to go. Can you imagine, I have point the whole massive aircraft a certain way to deploy a little weapon? You can use APKWS now, but unfortunately the A-10 isn't equipped with laser or GPS guided bullets.

It's normal, but there should be some instant action missions. You can edit missions and campaigns in the mission editor and fly them with the A-10C II, just change the player aircraft.

I highly doubt it would be this bad in real life, at this point it messes up nearly half of the attack runs.

Those CMS controls look completely wrong to me.

Probably a side effect of swapping the mouse buttons (again) so that right click is up/clockwise and left click is down/ccw.

That's wrong, you can edit DRM protected campaigns in the mission editor and swap your plane to the A-10C II, you just can't save the mission. If you fly the mission from the mission editor's flight menu it will work fine. For The Enemy Within 3 try to stick to the original weapons loadout because some scripting relies on you dropping those weapons.