Bunny Clark

The Dash 34 is ambiguous on this question, and doesn't mention the AUTO / MAN function at all (nor is the option even visible on the TGP Page in illustrations). My guess is that the function was added when the CCD versions of the Maverick that aren't capable of an auto track were introduced. MAN mode would then allow the TGP to place the Mav seeker in about the correct place but require the pilot to confirm final targeting, as the F-16's computer can't perform an automatic image match between the TGP and a CCD Maverik seeker. It makes sense to leave the "HANDOFF IN PROGRESS" message on the TGP in both cases, as it allows the pilot to easily see which station is being commanded to LOS slave. IRL, the computer will step to a new station automatically if a handoff fails, and you can also handoff two missiles in a row automatically for simultaneous tracking.

Contact the ground crew with the basic radio button "\" and request Rearm and Refuel. That will bring up a window where you can select your weapons.

The original campaign may be by ED, but Eight Ball put a fair amount of work into. I'm not willing to upload modified versions of his work without his permission.

It's a function that was added to the real Apache for possible future use, but ended up not getting used.

Interesting, I'll have to see if I can reproduce that. You may have found a bug in Helios.

What's in the screen shot is correct. The light should be bound to "Set Indicator." The Set Physical State bind changes the button position in Helios. If the indicator light is set to change the button position, that may explain your problems. Weird that that disappeared. The "set Wiper Control Switch" action should be bound to "Position Changed." That will tell Helios to set the position of the in-game switch to the position of the switch in Helios whenever the Helios switch is changed. There should also be an inverse binding in "Input" that will do the reverse, so that Helios will match the in-game position at startup and if you change it with the mouse or a keybind.

Once you've placed them that's all you should have to do. Everything on them is already bound and tested in game. Everything is working with the Tailwheel button on my end. You're using the newest version of the Profile and Interface? Yes, for both Pilot and CPG. And the Fire Detection Panels included in my Profile are programmed and functional.

Mission 4-1 is also impossible, because someone forgot to assign flags correctly and ordering the friendly units to advance does nothing. These escort friendly armor missions are a pain in the ass. Mace and Pine need stop conditions assigned on their hold holders triggered by flags 601, 602, and 603. @Eight Ball are you working on updates for the campaign? Do you want me to upload fixes as I make them? Assign your flight to 251 MHz in the Mission Editor or Mission Planner. I'm having trouble getting wingmen to work on VHF, but have had better luck UHF.

Something is wrong with the copy of the campaign on your system. It's acting like there's only a single mission in the campaign. There should be another mission on the list below the first one with a status of "Active" and a "Skip" button instead of "Play Again."

Waypoints can be added just fine in the Mission Editor. You can't add any other types of point right now. Hopefully that'll come eventually, though the Apache is hardly unique in this regard, both the Viper and Hornet have additional waypoint functions that currently cannot be added in the ME. Maybe when we get the universal "DTC" system ED has been talking about for ages it'll add those.

I'm not using it at all in my personal setup, I have the switches I need on it bound to my throttle base. If you want to use it, you'll need to find a home for it on your display.

Yup, you can see to the left that you have BIT and A/P advisories. Unfortunately this line blanks the display all the way across the page. BIT means there is a BIT (Built In Test) problem, which you can see and resolve on the BIT page. A/P means that Autopilot is active. This is why it's not recommended to place flight critical pages, like the Radar, HSI, and SA pages, on the Left DDI.

Mission 3-1 is impossible to complete because the Pine M2A2s gets stuck trying to cross the bridge.

The old Nite Hawk pods had a tendency to burn out the laser if it was fired too long. Apparently building a safety switch linked to bomb fall time into the pod itself wasn't an option, so the aircraft was modified to safe the laser a few seconds after TTI hit zero. When Nite Hawk was replaced with ATFLIR this feature was retained, though I don't think it's needed.

Can you post a screenshot of exactly what you're talking about? My guess is you're seeing the blacked out area created by the Advisory line. The Hornet displays pilot advisories on the Left DDI, and it'll overlay anything under it.

Update to my profile. Changes include: Un-fucked Tailwheel buttons, rearranged the Pilot screen to match the real cockpit orientation a bit better, made custom switch graphics to replace the stock Helios ones. I also added a bunch of new fully-functional panels, which are hidden by default, but available to unhide and use as you want. These include: Pilot and CPG Windshield Panel, Pilot and CPG Fire Detection and Extinguishing Panel, CMWS Panel, Engine Control Panel, and an alternate not-split-in-half Pilot Armament Panel. Bunnys AH-64 Profile.zip

Curious, I see all of those in the Profile Editor, and they are all bound and working on the CPG COMM Panel in my profile. Are you using the most up to date Interface file? Have you performed an "Update DCS" action in Helios?

Wow, I really screwed that up. The On and Off appearance images are also switched. I'll try to get an update out soon with that fixed (plus more functioning panels), or you can swap them yourself pretty easily. I'm not sure what you mean? On my end the Pilot and CPG COMM panels are both fully functional. Two IDENT buttons? VOC? There's only one KU_init.lua file, Oze exported it twice, I don't expect it would show two different things, does it?

There's only one display window in DCS for the KU. I believe that's very intentional, from what I understand the real Apache always displays the same thing on both Pilot and CPG KU scratch pads. You can even use it to send each other text messages.

Technically, every Maverick version has Force Correlate logic in it, it's just not usually user-selectable. It was originally built into Mavericks as a terminal guidance mode. Once the missile is close enough to the target that the seeker can no longer identify a contrast blob to lock onto and centroid track, the missile goes into force correlate, essentially using the seeker image to fly straight for the very last moments of flight. It functions by trying to keep identifiable shapes in the image traveling outward from the center as consistently as possible, causing the missile to fly straight. When the Maverick got a new seeker and optics, the engineers realized that the terminal guidance logic could be useful as a user-selectable mode to attack targets that did not present a good contrast lock. Buildings were intended as the primary target for this mode, which is why it was only implemented in the heavy warhead versions of the missile. With building sized targets it was considered acceptable that accuracy was mediocre in this mode. Force Correlate was never intended for use at long range, and was never intended for use on a point target where a contrast lock should be achievable. The weapons delivery manual explicitly says not to use Force Correlate on a point target like a tank.

I'm fairly certain there are multiple datalink UFC pages, and pressing D/L will cycle between them. Just like the IFF has separate transponder and interrogator pages. My guess is he only wanted to show new ME options, and that the TACAN and ILS setup is unchanged from what it was before. My question is what about the radar beacon? It was hinted that we would need to use the BCN button on the UFC for ACL setup, but that was not demonstrated in the video. Are there more details yet to come?

That's true, though he doesn't zoom in as far when you haven't selected a target, which makes it more difficult to ID them yourself. If you play with labels on, you can follow the TADS aiming cross in your HDU and see what label it's pointed at in the outside world. That's been my workaround so far.

Not by default, and I didn't add that to my monitor export guide files, but it is possible. Go to \Mods\aircraft\AH-64D\Cockpit\Scripts\ASE\CMWS and open the CMWS_init.lua file and add the following text to it: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("AH64_CMWS") Then you'll have AH64_CMWS available as a viewport. Or you can name it whatever you want. Derp. The indicator should be assigned to the "Set Indicator" field and not "Toggle Indicator." Looks like I screwed that up on both the Pilot and CPG Tailwheel buttons.

Down is darker. I build it in Helios using a clickable indicator object, which uses 4 button images: an "on" up and down, which is what you posted, and an "off" up and down, which use the blank button images.

The texture files have everything, what are you using to open them?