Floyd1212

Yeah, huge MP tracks are not very helpful. When you find some time to hop in an Instant Action solo mission and try to reproduce the issue, feel free to post it here.

A track file of this happening would help a lot. When transitioning from forward flight to a hover, she needs quite a bit of collective to keep your altitude and not settle. But if you are in an established hover, it shouldn’t just drop out of the sky like a rock.

Agreed. When George moves to the back seat, he (aggressively) moves the throttles to FLY. I don't have the throttles bound to anything for the front seat or back seat, as I only use my mouse to move them in the cockpit, and the same thing happens to me. This shouldn't be an issue though, if you have the collective all the way down.

I think if you let George do his normal startup procedures in the front, he boresights the IHADSS on his own.

@GeoS72 I was able to view this one. Not sure why the other one said it wouldn't load. The failure for George to fire (this time) was he was not in constraints. There could be more than one reason for not being in constraints, but in this situation you can see the "ROLL LIMITS" message in the High-Action Display area of his video feed. The aircraft is banking too hard for the system to let a missile come off the rail. Prior to this point, you were having him scan for the targets, but you were either outside *9999 or outside George's engagement range of 8000m. Once you got within 8km, you had him acquire the target again and turned in to get the nose on. During this time, you can see the small constraints box (in LOAL mode) was moving around as you were getting onto the target and it was a dashed box the whole time. Then just after this screenshot, the constraints box went sold and George did rifle, but by then it was too late... A couple things I noticed here, and I am by no means an expert, but will venture forth with my observations anyway: 1) You are going up with a full load of Limas. This means every time George lases the target with the TADS, he loads the TARGET DATA to the missile and then stops lasing. To get new range info, you have to have him de-WAS missiles and re-WAS them to clear the TARGET DATA and start the cycle over again. You can get around this issue by setting him to No Weapon and Laser On so that he continually lases the target and you get updated range info. Then, when you are getting close to being under his 8000m engagement range, switch him to missiles and let him load the data and rifle. The other option here is to go with a mixed load-out of Limas and Kilos and keep him on SAL to continuously lase and get range info, then switch him over to RF when you are ready to fire. Personally, I often go up with 12 Kilos and 4 Limas, and save the Limas for dangerous threats (like SAMs), but use the Kilos when I can take my time and can out-range the enemy. 2) This is more of a tactical observation. Getting out over the water and coming back to attack an SA-8 is going to be a challenge every day of the week. He will out-range you and get his missile off before yours every time, and yours still has 30+ seconds to reach the target. Yes, with the Limas you can fire your missile and duck for cover, but out over the water you have no cover. You might be better off staying over land and using the terrain and trees to your advantage. Sneak up on him and either use George to attack, or bring an FCR and fire the Limas yourself. And once your missile is in the air, get back down behind cover. I suppose if you want to get out over the water to find him, then Store him as a TGT point, you can then get back over land and know exactly where he is. 3) This doesn't effect George's ability to acquire targets and kill them, but it doesn't look like you have a good boresight of the IHADSS as you can see your reticle is off a little bit from what George is actually looking at in the TADS. Not a huge deal, but having the IHADSS boresighted accurately will help with your SA once you turn on CSCOPE and you see all your shot marks and radar returns overlayed on the IHADSS. If you don't ever use CSCOPE, I recommend you give it a try.

If that track is from the new paid campaign that came out, I think only people that have purchased it will be able to view it. First guess would be, have you selected which rockets to fire? Maybe a screenshot showing the symbology you were seeing when it wasn’t working?

I tried to watch your track and it looks like this is a .miz file, renamed to .trk, and not an actual track file. A track file will have a "track" and "track_data" folder in them. When I run your file, it lets me choose a slot to load into, etc. I also tried to watch your track file a couple time, and got a "Mission Load Fail" each time that then hung DCS. Maybe someone else will have better luck.

So, that may make it a little more difficult to troubleshoot, but the good thing is, there are a lot of servers out there that use server-side scripting. ED, please don't give up looking at this issue because it doesn't happen in your clean-room environment; this bug effects a lot of people that fly on popular public servers, some of which you even promote in your monthly newsletters.

Page 254 of the AH-64D Early Access Guide talks about setting DIR routes. Select RTE, then DIR, then POINT>? and type in the point "W44" in the KU.

Maybe it's a multiplayer thing? Can you reproduce it in a short single player mission?

I can confirm this bug, as well. Just never sat down to post about it.

What would also be helpful when providing a track is the time in mission when the (non)event occurred. The EUFD has a clock showing Zulu time, and is often visible as your are replaying a track. Make a note of the time when the issue occurred and then someone is much more likely to ffwd through your track to find it. Especially since there is no rewind function.

Can we find out of these fixes should already be in the game at this point? Or maybe a list of the known issues that remain with DL in multi-player and multi-crew situations? We are still getting instances of DL not working after setting it up on the pad and testing before lifting off. Still getting double transmits. And still getting NACK messages when the message has in fact been received. I can spend some time organizing a multi-player DL bug report again, but I don't want to waste my time if these are still known issues and being worked on.

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.