Bunny Clark

Alright, I decided to try and solve this problem, because it seemed fun. And pulling textures is easy, so I made some more of those too you for. Here's some new background panels for the CMWS, FIRE DET / EXTG, Engine Control Panel, and Windshield Panel. And all the buttons and covers needed for the FIRE DET / EXTG panel, and a Profile with a working example of one. Images.zip DCS Apache.hpf

Alright, here's an updated Interface. This adds: CMWS Panel, Engine Controls Panel, Windshield Panel, Canopy Controls, Pilot Fire & Extinguish Panel, and CPG Fire & Extinguish Panel. Thanks to @osram for some of the programming for the CMWS, Engine Controls, Windshield, and Canopy Controls. I renamed a bunch of his work to fit in with everything else, but the data values were handy to copy over from his Interface. 1. I use Photoshop. The buttons and the lights both come from different files, the lights are done as a transparent overlay. You'll find the CMWS panel in ah-64d_cpt06, the FIRE DET / EXTG panel in ah-64d_cpt04, the switch guards are in ah-64d_cpt22, the buttons in ah-64d_btns, and the lights all in ah-64d_cpt_lamps. 2. Those are going to be tricky. The button guards I would do as a simple toggle switch, which covers another button object when in the down position. The buttons themselves will be a bit special. Helios can do lighted indicators as a standard function, but only if the button has a single light on them. That'll work fine for the Discharge buttons, but the other three need to be something else. I'd build them as standard buttons, with the FIRE and RDY text as transparent cutouts, and then put a solid block of amber and green behind each transparent part of the button and tie them to the indicator lights. I attached a modified version of my Helios profile I used for testing the fire panels. It's super rough and basic, but may give you a starting point for making a pretty version. DCS.AH-64D.hif.json DCS Apache.hpf

It is actually just like a crosswind landing. Not only is the ship (hopefully) pointing into the wind, but the motion of the carrier relative to your plane is in essence creating a relative wind. A crab into that relative wind, the direction the carrier is moving, is exactly what you should do. If you imagine the carrier staying completely still and a wind blowing down BRC at the speed of the carrier + real wind speed, the result would be the same.

I've already got the CMWS buttons and switches programmed into the Interface. I can do the Fire Detection Panel too pretty easily. Don't know if I will add them to my Profile, but once they in Helios they're pretty easy for anyone to add.

This campaign, like the A-10C Georgian Hammer campaign it's based on, is randomized. There are three possible missions that can happen as Mission 2. My Mission 2 was 1-3-0, where I had to destroy an arty position. Destroying a bridge is mission 1-2-0. Mission 1-1-0 has you supporting an allied armored advance. Which mission you get is totally random. Additionally, there is quite a lot of randomization in the mission itself. Most air defenses have a 50% chance of spawning, so how much resistance you need to deal with will be different every time you play the mission.

It means that the Radar and Laser Warning Receiver is active and has detected an emitter. Somewhere around that green box will be one or more yellow symbols representing an emitting radar system that your Apache is detecting (I don't believe laser warning is implemented yet). The box will go away when no active emitters are detected by the system. If you're not seeing it at all from a cold start though, you probably didn't turn the system on. From the WPN page go to the ASE sublevel, select UTIL, and toggle on the RLWR. And what does it mean about you that you're willing to put in the effort to scold someone online for asking a question about a computer game? Seriously, just not responding would have been the better option.

Doesn't GIMP support .psb now? I'm a Photoshop user, so I can't really say, but I recall reading that .psb support was added to GIMP some time ago. Converting them all to .psd is simply not possible. A number of the files are over 2GB in file size, and .psd does not support files of that size. Photoshop will not allow you to save them as .psds.

Metal doesn't "give off" heat exactly, it conducts heat. If there is a heat being generated by a metal vehicle, such as a running engine or weapons being fired, that heat will be fairly readily conducted to the surface of the vehicle and cause it to appear hot on a FLIR camera. Metal skinned vehicles can also heat up quite well in the sun. But if the engine is off, no weapons are being fired, and if it's not in the sun or it's night time, metal vehicles can pretty quickly match the ambient temperature. The same quality that causes metal vehicles to conduct heat from the inside to the outside works in reverse too. The temperature of the surrounding environment plays a role too, as to see a vehicle easily on FLIR there needs to be a high temperature contrast between the vehicle and the background. In a desert sun-baked sand can get quite hot, and even a running tank may not be a significantly different temperature than the sand it's sitting on. The visible light TV versions of the Maverick missile were developed specifically because of difficulties in finding tank on hot sand in Iraq using IIR sensors. Conversely a tank with a running engine on a cold day should be picked up by FLIR very easily. Atmospheric conditions play a role too, humidity significantly impacts FLIR clarity, and IR can't see through clouds at all.

CoreMods is the folder for the external models that DCS uses for rendering all the things you don't own. No cockpit textures in there because there's no reason for them to be. You want \Mods\aircraft\AH-64D\Cockpit\Textures

I always just enable it with startup.

The closest I've experienced to this is vehicles that have received "critical damage" and become mission killed and are burning. They'll remain like that for some time, usually a few minutes, before exploding and being completely destroyed. This has been a DCS function for ages, though it does seem that the Hellfire tends to cause critical damage rather than outright destruction on most main battle tanks, probably because it packs a lighter punch than a Maverick or Mk.82.

What do you mean re-host? The download in this post should still be available and the most up to date for my profile:

Hmmm, everything is working just fine on my end. To confirm you're using the most recent version of the profile and interface from this post?

Not only would this help with things like faction ID, but it would be very useful for missions where you need to destroy specific targets. Trying to figure out exactly what generic name the mission objective is can be really unintuitive.

Why do you want to quickly reset the TGP to forward? It's much more useful pointing at a target location. Or if you see something visually it's way easier to cue the TGP directly onto it using the HMD.

This is a DCS issue. As far as I am aware, there is nothing we can do by editing display lua files to solve it. I'm not a programmer, someone with more knowledge and experience may be able to find away around the DCS limitation, but a "proper" fix will need to wait on ED.

Make sure labels are enabled in your game options. Label setting can also be forced by the mission you are flying, so regardless of what your settings are they may not be available in some missions.

The George AI CPG seems to be unable to hit ZU-23s with Hellfires. I've got no problems getting him to hit tanks and APCs all day, but every single missile I've had him fire at a ZU-23 misses long. He can hit them fine with guns, but that's a rather dangerous maneuver...

This is exactly it. F-16s standing alert duty will be started up and a full alignment completed, then they are shut down in place. The aircraft then must not move from that parking location, and a Stored Heading alignment can be completed quickly if the aircraft is scrambled. DCS always assumes that a cold aircraft has not been moved since it was last aligned and shut down, so you are essentially always ready to scramble when you hop in a cold jet.

Yup, the IFEI isn't set up to export by default, but that's easy to change. Drop the attached lua file into \Mods\aircraft\FA-18C\Cockpit\Scripts\IFEI\indicator and overwrite the existing file. Then you have a FA_18C_IFEI viewport that can be defined in your monitor config. DCS updates will revert this file though, so you'll need to restore it every time you update DCS, or use a mod manager. IFEI_init.lua

@MrReynolds Yup, this can be a bit confusing, but it looks like you've sorted it out. DCS draws a rectangle that is its total display area. This rectangle needs to include the main game window and all display exports. The total size of this rectangle is the resolution and aspect ratio you set in game settings. Then each viewport is placed within that. The Center viewport is where the game itself renders, and that will most likely want to be the resolution and aspect ratio of your primary monitor. Then all viewport x and y values reference that main rectangle defined in game settings, which means you usually need to do math to calculate them.

I just had this problem and George had selected radar Hellfires as active his type, which wasn't working as the aircraft didn't have any. Jumping into the CPG pit and changing the type selection from "RF" to "SAL" got them working again.

Yup, pretty much. No, I do not believe so, not directly. You can always select the target on the FCR page, or point an ACM mode at the icon. No. The AIM-120C does not support network guidance, it needs to receive mid-course updates from the launching aircraft's radar. Network guidance is an AIM-120D capability, which we do not have in DCS. Who knows? Maybe someday when ED gets around to updating the wingman commands. Though, if you're going to command your wingman to attack a datalink target, PDLT isn't really the way to do it. You can directly transmit targeting instructions to a wingman over L16.

I can't see your images anymore, so I'm not sure what you're seeing. You should just be able to hit the 'Accept" button to continue. But, if you want to skip a mission, one shouldn't need to edit the logbook anymore, you can just skip missions in the campaign menu.

"Fine" is pretty relative. If it works it's fine, if it doesn't you have no recourse. And it can stop working unexpectedly and without obvious cause. I had some issues with it years ago that caused my Pro Throttle to randomly stop working entirely until my computer was rebooted. When I e-mailed CH support about it I was told that it was no longer supported and "not fully compatible with Windows 10." They recommended uninstalling it and calibrating with Windows, and even linked to Joystick Gremlin for more advanced features. Uninstalling Control Manager solved my issue, and I never had another problem with my Pro Throttle until I retired it.