Floyd1212

True, but the one included in the install folder is current. Mine appears to have been updated with the patch two days ago. i.e. "G:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Doc\DCS AH-64D Early Access Guide EN.pdf" It would be nice if the online manual was updated as well, though.

It does indeed look like you have two black pixels in your uimask file.

Ideally you would have some friendly CAP to engage those hostile fixed-wings, but I understand that can be difficult to rely on in a public server. There’s not much cover in that area that you are working in, but aggressively side-slipping behind that mountain may have evaded his missile, but my guess is he would circle around to try again. You can fly with a buddy in a Kiowa equipped with Stingers, or even better, a Gazelle with Mistrals. I find fixed-wing players hate getting killed by a Gazelle. I’ve seen quite a few rage-quit after getting shot down.

It appears George lases the target and rifles, so there is no "failure to fire" problem in this situation. I can't tell what part of the aircraft he is lasing, or if he is actually lasing past the aircraft, but even if he does have a good lase on the center of mass of that F-14B, I think you are expecting a bit too much out of a Hellfire in this situation. Also, at Mach .92, I'm not sure I would classify him as a "slow-moving" aircraft.

I don't think you are going to be able to transfer the TARGET DATA? to the missile simply from the JTAC's laser energy. It might help you find where the target is located, but you (or George) will need to put the TADS on the target and lase it for 3 seconds to transfer the data to the missile, or use the FCR. Really, you are better off with SAL missiles when working with JTAC like that. Now a "buddy" in another Apache with an FCR can hand off the data for a single target to you over DataLink, and you can send a missile off that way.

I don't think your videos are demonstrating the issues described in this thread, but I will ask anyway... Did George have a solid IAT track on the center of mass of the enemy helo? I'm guessing he was lasing the tail or some extremity of the helo, and it changed aspect and the laser ended up lasing a point on the ground way beyond it. As a result, the missile tried to climb to be able to reach the new designated target. Just a hunch.

Yes, we get double messages all the time. For a while we thought it was only when there was a human in both seats, but it happens even when solo, too. it was mentioned in a big report a while back, but it has not been resolved yet. We do use FM1 for DL most often, but FM2 is on a different frequency. We will have to try VHF/UHF and see if we get it there as well.

Do you have the pitch and roll axis bound to your joystick axis for both the PLT and CPG seats?

Ah, okay. Good to know in case I ever getting around to building a TEDAC. Right now the two MPDs with Helios is working well for the 90% of the time I am in the back seat.

Yeah, this is definitely still a problem for me, as well. I think you are probably in the minority here. I'm not sure why your exported displays are not super dark like everyone else's but I'm glad it is working for you. I suppose if you only use your additional screens for flying, you could jack the gamma up in your display settings for that monitor (maybe to match the default 1.8 gamma in DCS?), but I use my screens for other things when I am not flying. And, increasing the overall gamma would then wash out the virtual buttons and bezels I have around the exported display using Helios. Maybe one day ED will pay closer attention to this issue that their hardcore fans are struggling with...

A track file would be most helpful here. In my experience, a good lase on the center of mass, or at the wheelbase of the vehicle, will give me a 95+ percent success rate with Kilos in LOBL mode.

Hopefully you have reported this in the Huey forums?

Okay, enough with the 3D renders already. Seriously, though, that looks fantastic. What is your technique for getting the grips so smooth? Those look injection molded.

Which is why you engage these units at 6-8km, at which point they stand no chance. Edit: Sorry, forgot this thread was about radar engagement. If you only have Limas on board, and can only use your FCR for some reason, you can peak and do a scan then drop behind cover to engage those targets.

I think he is talking about how to deal with it in VR specifically. In 2D, boresighting is easy and accurate. He is suggesting that you use trial and error (by telling George to slave to your LOS) to find the correct offset to use in the future to get repeatable results. Sounds like a pain to me, but I guess the benefits of VR outweigh the negatives that come along with it. Though that workaround with ReShade seems to do the trick.

Actually, I did some more testing and figured it out, and learned something in the process. I was assuming it had something to do with the Random_Num flag, but it turns out to be a different sort of RNG feature in the ME. The value shown here is a percentage chance that the group will exist at mission start. And 10% is not a very high chance, so that is why there were very few of these groups to encounter. So to answer my own question, bumping this number up to 50% (or whatever) will produce a higher probability of those groups being there waiting for us.

@Mistermann I have a question about some of the enemy units that are placed in the missions for the players to encounter. Some groups are set to Late Activated and there is a trigger zone that counts the number of players that are flying the mission, and activates the appropriate number of groups. But there are also groups with "RNG" in their name, and are not Late Activated, but during runtime only a few of these groups appear. How does this RNG mechanic work in the ME, and is there a way to increase the chance of some of these groups appearing? We flew "M05 - Moonlight" last night, and after reviewing the mission in TacView, it doesn't appear that any of the RNG groups were present. Thanks for everyone's work bringing these missions to the community!

Earlier in this thread I mention how to use Joystick Gremlin to solve this problem. You can define a trigger pull from 20% to 90% to be one digital button (first detent), and 90% to 100% to be a different digital button (second detent), though I didn’t find this personally useful. There were mentions of other software that will also do the same. It sounds like your workaround of adding the modifier is working for you, but I figured I would mention this again, since it is what the thread was originally about.

Maybe while you are pressing Request Control from George, a ghost image of the cyclic/collective/pedals appears where George currently has them so you can look down in the cockpit and alight your controls in game, then when you release the button you resume control.

I have a question/suggestion: When setting up DL entries, would it save time to enter the C/S and ID as you iterate through the entries the first time through, overwriting what was there, and then DEL the ones at the end that need to be blank? Right now it goes through a pass to DEL every slot, then runs through them again inputting the desired data. (You probably thought of this approach already, and there is something preventing it from working that isn't obvious to the casual observer, but thought I would ask.) Thanks for this very useful tool!

I think this has been discussed here before, and the suggested practice is to truncate the last digit. I think it had to do with how some grids are actually slivers and not an entire square. In most cases rounding up will do no harm, but in other cases it may be a problem. Maybe someone else has a more concrete example of this...

In your Special Options for the AH-64D, what setting are you using for "Detent in LOCKOUT position"? What do your "Tune Combo Axis" settings look like for your throttle, for both PLT and CPG? After watching the track, it looks like you are using the mouse to bring up the throttles. It definitely looks like the "detent" option has been changed so that you can take them straight to full LOCKOUT mode instead of stopping at FLY.

@Terrifier You don’t mention in your posts anything about Force Trim and what mode you use for your cyclic trim. You will have a more direct feel of the aircraft if you are holding FTR while you are maneuvering, and using the “Center” trim mode (instead of the “Instant” mode) also provides more immediate response from your cyclic inputs.

Yes, you have to take a hand off either the cyclic or collective to reach up and manipulate the MPDs. In the sim, this probably means manipulating the mouse to click buttons in the cockpit. My recommendation would be to trim the aircraft and fly for a moment with your left hand, assuming you use your right hand on the mouse. I would hazard to guess that IRL the pilot would often reach up and do this themselves. I can think of many other things that the PLT has to do for themselves while flying, and can't ask the CPG to do for them, like panning around on the TSD, or setting your ACQ, or changing the radio you want to transmit over, so selecting a new WP as your DIR shouldn't be a big deal.