Bunny Clark

When everything you've done gets "corrected" by the patch, all the files you've modified are just placed in a folder inside your DCS install folder where you can simply copy them back again (at least on standalone, I'm not sure if Steam works the same way). Or you can use a mod manager to do it all for you.

Sometimes when you rearm George gets confused and selects Radar Hellfires. To solve it you need to hop into the gunners seat and manually change Type to SAL.

Yup, that's caused by changing DCS's resolution. Asto's PrestonAI_page_common.lua fix worked for me, but it'll depend a lot on how you have your monitors arranged.

Have you read through my guide here: That will hopefully give you a baseline understanding of what needs to be done.

The buttons to change kneeboards work for both the pop-up kneeboards and the leg-mounted kneeboards (it should be "[" and "]" by default, I think).

Which is why the A-10C II module has it, but not the Viper.

You program target points for each bomb ahead of time, and then selecting QTY allows you to release multiple bombs with one pickle. Once released, each bomb will go to the target point it was assigned. You can program 4 bombs to 4 different targets, select QTY 4 to release 4 bombs at once, and they'll all guide on their own different targets. If you want to drop multiple bombs on the same point you'll need to program multiple stations to the same coordinates, or if you're dropping GBU-38s double-loaded onto the same station you can program the station to the target point and both bombs off that station will guide to the same location.

In the Waypoint Type drop-down menu, set it to "landing."

You can give them a landing waypoint, then set them to orbit some distance away. Make a trigger to change waypoints to the landing waypoint at a certain time. You can use the ETA field in the ME to approximate when they'll arrive for landing. I expect it won't be as accurate as landing exactly when you want to the minute, but it should be a lot more accurate than waiting for them to bingo back on their own.

Yes. They may not be finished, but they were added some time ago and haven't been updated since.

Yah, the manual is pretty useless. I created the description for my HOTAS guide image based on testing how it worked in game. I don't find S/A or AUTO to be of any use at all in the Hornet. I wish it worked more like it does in the Viper where S/A just runs the auto selected program once and then stops.

I assume you're talking about the F-16-34, page 1-708 contains the text you're frequently quoting from. That sentence is intended as a caution that, in some circumstances, the AGM-65D may be able to lock a target at a range greater than the slant range of the missile. It doesn't mean that it will always lock on at that range, or even that it will frequently lock on at that range, just that it technically can. The A and B models were notorious for poor lock-on range, and pilots could safely fire the missile as soon as it locked the target without regard for range, as it would always fall within the max slant range (the A in particular was known for not locking on until within 2 miles of the target). The -34 is cautioning pilots that with the D model, they need to be mindful of missile range, as a valid lock-on does not necessarily mean the missile is within launch parameters. It does not mean that an AGM-65D will reliably lock on to a target beyond the range of the missile.

Because you retain the ability to actuate manual programs in all dispenser modes. S/A and AUTO replace the CMS Forward action, but CMS Aft will always run the Manal program. Here's what the breakdown looks like: S/A and AUTO both pick from a list of 3 programs which are independent of the Manual programs and are not editable in the aircraft. They can be edited in the CMDS_ALE47.lua file if you want to, same as setting the Manual programs default. The standard three Auto programs look like this:

I believe they have mostly been flying with dumb bombs, primarily Mk.84s. I recall reading that the King of Jordan was begging Obama for some guided weapons after Muath al-Kasasbeh was captured and killed.

It's there because when you have an AI controlled aircraft in your flight (like a wingman) it displays the AI waypoint path for that group (your group). Alternatively, it's there because someone at ED didn't think it was necessary to hide it entirely for a human controlled flight. It can still serve some purpose by showing you where your waypoints are on the map. Just don't pay any attention to the leader line connecting you back to Waypoint 1. Why are you so hung up on this? What purpose do you want the F10 waypoints to serve? Are you trying to actively navigate by them? If so, you're doing it wrong.

Looks interesting, I'll have to give it a try. I'm curious about the story though, Apaches fighting Syrians who are advancing west from Palmyra? That's a weird situation.

Correct. The profile uses Helios to create the touch screen control interface. The actual MFD displays are done within DCS. Unfortunately, nothing in Helios allows us to bypass the broken AH-64 displays, and all the limitations I mention in the display export guide are still a thing.

Yah, I messed around with doing exactly that myself a while ago and couldn't get it to work reliably either. In Helios everything is a toggle, while in DCS it's an explicit command, and getting those to sync up just causes problems, then if they get out of sync it's all screwed. I also settled on using two different buttons.

The feature you're asking about - incrementing the current waypoint in the F10 map - only works for AI aircraft. Yes, you can see the full route for human controlled aircraft (sometimes, getting it to display isn't reliable). But it will never show you advancing through your waypoint numbers. That part only works for AI aircraft. It does not work for human aircraft.

What they're trying to tell you is that the F10 waypoints are there exclusively for you to see the flight plans of other AI flights. The current waypoint will never increment for a human piloted flight. It's not possible. You will only ever see it happen for an AI flight. What purpose are you trying to use them for? The F10 map is not intended for primary navigation, you have in-cockpit displays for that.

Boresighting targeting pods is something that is done by ground crews using specialized equipment. In the Viper we currently need to boresight Mavericks to other sensors, usually the TGP. As far as I know this is a thing IRL with the Hornet and Hog as well (though the Hornet very rarely uses IR Mavericks IRL), but right now it is only modeled in the Viper.

The CPG does not fire rockets. Since rockets are aimed by flying the aircraft, the pilot always fires them. How steady are you flying? Too many rapid changes in orientation will make it difficult for George to keep the laser on target and result in a miss. I find if I'm careful with my flying, George has about a 90% hit rate with Hellfires, and most of the misses are because I was yanking on the stick.

https://github.com/HeliosVirtualCockpit/Helios/releases

With the new Helios update today, I've updated my profile to utilize the built-in Interface. No more needing to install a custom Interface for Apache profiles. With this update, I figured I'd make my own thread rather than continue this one. You can find it here:

Now that Helios has native support for the Apache module, I figured I'd make a thread for this by itself. This new version of my Helios profile does not require a custom Interface. Simply copy the Profile and Images into your folder and it'll work. Requires Helios version 1.6.5305.0. Download here: https://www.digitalcombatsimulator.com/en/files/3322990/ Includes a Pilot and CPG pit with MFDs, EUFD, KU, Master Armament Panel, Master Caution Panel, Lighting Panel, Video Panel, Tailwheel Panel, and a toggleable Comms Panel. I've also included bonus panels for the Engine Control Panel, Windshield Wiper Panel, Fire Warning Panel, and CMWS which are hidden and unused by default but fully mapped and functional if you'd like to unhide them and place them.