VKing

Am I understanding correctly that you are flying by lining the steering line up with the gun cross? If so, then that's your problem. The gun cross at the top of the hud is irrelevant; a CCRP attack is flown by putting the FPM on the steering line. It doesn't matter if the line is left or right in the HUD, the computer will compensate for drift as long as the FPM is lined up with the steering line. For a strong crosswind, the correct lineup might look something like in this screenshot.

I missed this part. That is indeed a bug.

This is the same behaviour as before (or at least I believe it's currently correct). It starts HUD/HMCS-stabilized, then the first TMS up action changes to ground-stabilized where you can slew it around to fine-tune it, then the second TMS up action saves the markpoint.

This is an example 4-ship setup where the flight lead can get the distance to his second element, or swap channel X for Y to get the distance to the wingman without having to change any numbers. ETA: The distances are just examples, not any kind of TACAN limits.

My guess is that they don't want to accidentally confuse - or worse, merge - information about the datalinks in the DCS game and any sort of acual Link 16 or VMF simulation they might be doing in their defence products. So they call it TNDL and SMDL instead of Link 16 and VMF, so that when someone in the company says Link 16, nobody thinks they're talking about DCS.

I believe the problem in this thread is an expression of the bug that causes the HARMs to go active before they are in their terminal phase. If the HARM does no go active before the terminal dive, you won't get HARMs that miss by the width of the map if the radar turns back off again.

Here's a track showing that the underlying issue still exists in MT 2.8.8.43704.

Retest on MT 2.8.8.43704 HARM_EOM_Tracking_bug_F-16_MT-2.8.8.43704.trk

@BIGNEWY The track I posted has the bug in it. I don't understand how the replay thing works that you can't replay it; do you know if there's a way of getting partly through the replay and restarting the track recording or something like that?

I have the same error happening in both MT and ST exes.

It crashes in the Single-thread exe as well.

Due to the randomness of the bug, I haven't been able to get a shorter track, but playback works fine on my end, so I've gotten a recording showing what it looks like. (The IHADSS decided to stick to my actual head as I was recording rather than the head position in the track, so that's why the symbology goes weird) Every time George goes "Ah.. Aircraft's Armed" is a down command to cease, while any up commands to slave are ignored. When I go to the CPG seat, I only ever switch to HMD as sight, the reset to TADS is automatic. Same with slaving, I only ever initiate the slave, all unslaving is automatic.

I'd call that in itself somewhat abnormal, as I didn't crash while recording the tracks.

Apache_George_CPG_Arm-Slave_bug_full.trk Managed to get a track of the full bug. @Lord Vader Can confirm ump104's statement that switching to the CPG seat and changing acq source to PHS lets you use George again, albeit slightly broken.

Apache_George_CPG_Arm-Slave_bug_partial.trk Here's a track in SP that shows part of what I saw when I had the bug previously. I don't know if this is a fully separate bug or not from George not safing the aircraft and refusing to slave again. Towards the end of the track, when commanding George to disengage, instead of slaving the TADS to FXD, he slaves it for a short while and then deslaves, leaving the TADS space stabilized instead of fixed. What's different in this instance is that George safed the aircraft and I could arm/disarm it at will, and George accepted the slave command again after not slaving the TADS back to FXD.

I got this bug in MP, and when I jumped into the front seat to try some manual control, George/the aircraft would turn slaving off when I tried to turn it on as the CPG, and switch back to the TADS after I to selected HMD. As CPG I could safe the aircraft, but as soon as I returned to the pilot's seat, George would unsafe it again.

I think the terms are getting a bit muddied here. The missile can't be LOBL if it acquires a target after launch.

Are you in AG master mode? You can also go through the WPN page by pressing the button labeled UFC in the top right.

The Apache requires 8-digit grid coordinates, so if you want to use a 10-digit coordinate, you must round or truncate the last digit of the easting and northing. 36S YE 70467 07694 doesn't work, but 36S YE 7046 0769 will.

Alternatively, go to the Special Options and check the option to disable the trigger guard.

Another track, recorded with 2.8.4.38947 MT. This shows four HARMs fired at four different SAMs, but when the SAMs activate, all four HARMs turn to the same radar, leaving three of the four SAM sites unengaged. Edit: Second track with F-18. This time two radars got hit because they activated later and one of the HARMs spotted one radar while the three others went for another. HARM_EOM_Tracking_bug_F-16_InadvertentFocusFire.trk HARM_EOM_Tracking_bug_F-18_InadvertentFocusFire.trk HARM_bug_earlyactivation.webm

The blue sector? That's the Radar FOV.

I've been flying the Apache quite a bit again after the MT release, and I find it a blast to fly now. The collective SCAS fixes seems to have done the trick of no longer attempting to counter my altitude changes. I always fly pressing and holding the trim release any time I'm doing basically any kind of manoeuvre, with or without hold mode enabled. Probably more than is strictly necessary, to be honest, and I tend to fly like I'm using attitude hold even when I'm not using the hold mode, especially when turning: Holding force trim and banking, trimming the aircraft in the bank and releasing force trim, then holding force trim and trimming out of the bank when I'm on the desired heading. I also frequently use hover hold and velocity hold with no issues, nor with holding hovers without the hold mode. I've basically never experienced oscillations induced by the SCAS that I've seen others get sometimes. The weirdest flight model thing I've had is the aircraft rolling over when I've transitioned from a hover into sideways flight, but those were done under "oh-<profanity>-pop-up-SAM" circumstances, so there's a fair chance I was outside of normal acceptable parameters for the helicopter.

Yea, that was it. I don't know why it stopped working in the first place, but it works again now.

I'm getting an issue where the script can't access the countermeasure files because of write protection (apparently). 2023-04-11 15:40:13.561 ERROR EDCORE (Main): [C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device\CMDS_ALE47.lua] CreateFile(REWRITE): Access is denied. 2023-04-11 15:40:13.561 ERROR EDCORE (Main): Can't open file 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device\CMDS_ALE47.lua' from fs. 2023-04-11 15:40:13.561 ERROR LuaHooks (Main): [string "C:\Users\Kristian\Saved Games\DCS.openbeta\Scripts\Hooks\DiCE-hook.lua"]:705: attempt to index local 'file' (a nil value) The file itself is not read-only, but it seems like all the folders in the DCS directory are. And I'm not sure if it's a windows problem, but I can't seem to be able to make the folders non-protected. Any tips?