Recluse

Yeah

Thanks, to clarify, the issue is not with THREAT CIRCLES, but with actual Target/Threat points in the Apache database. The logic does appear to be related. You are spot on. Checking HIDDEN ON MFD makes the Target Points disappear. The reason only SA-8 and SA-6 appeared was due to their radars. When I placed units without radars, they didn't show up, but when I placed other SAM S&T radars (where they were not part of the TEL) they did indeed appear as Target/Threat points. OK.. problem resolved.. Thanks!

Not sure if this was reported: - I noticed that when I enter a mission with SAM sites, they auto-populate the Threat/Target points in the COORDS section. Helpful, if maybe a bug. - I noticed that they auto-populate EVEN when the SAM units are set to LATE ACTIVATION and are not present on the Map. Steps to Reproduce: - Create mission with SAM units (I saw it with SA-8 and SA-6). Note COORD page is populated with T01-T0x for placed SAM units -Set units to LATE ACTIVATION. Note COORD page is still populated as above Track attached. Sorry for all the scrolling on the map. I was using the SCRATCHPAD mod to capture the coordinates for comparison to the TSD, but I forgot that this overlay is not captured in the TRACK. Still you should be able to see that the COORDINATES for the LATE ACTIVATION SAMS are the ones that a populated at the beginning of the mission. Track is in Persian Gulf map. Edit: I tried with other SAM units and they don't all seem to show up. The SA-8 and the SA-6 STR radar unit DO. Late Activation Targets.trk

You can set the MSL ACQ to SKR. That way, at least when in a LOBL mode, you will see the CUED LOS cross representing the JTAC's Laser spot. This is basically LOBL except with the remote lasing. This will help you orient yourself for the best shot and also give you a clue that the Seeker has found the laser. You can still miss if you fire too far off "boresight" Most times you will get a warning, but what can I say? Sometimes between pulling the trigger and the missile coming off the rail, my Apache might just yaw a bit

Yeah, once you ground stabilize the TGP in the vicinity, it is easier to slew it and pick up the scattered vehicles. If close enough you can also use the Maverick seeker, but, that is a lot trickier.

You SHOULD be able to immediately switch to Maverick Seeker once you have a GMT Lock and Uncage the Maverick to the GMT target. I do this all the time with SEA Radar and SHIP Targets. I usually put up the TPOD to see the target but I do NOT switch TDC to the TPOD unless I am needing to fine tune the lock or switch target. - Early on, when you had a GMT lock (see RDR in HUD as indication of designating Sensor) and then switched to TPOD, you had to essentially switch the Designating Sensor to TPOD, or, in the case of an LGB attack, you might get out of the RADAR field of "view" when very close to the target. Usually this meant undesignating and re-acquiring. - CURRENTLY if you have a RADAR Lock and switch your TDC to the TPOD, the TPOD will automatically become the designating sensor, (See FLIR in HUD) which is something you MIGHT NOT WANT to happen. There are some bug reports on this which I will try to link to if I can find them. (NOT SURE IT IS REALLY A BUG) IF you put up the TPOD but don't switch TDC to it, you can maintain the Radar lock while getting a visual on the target. EDIT: Probably should move this discussion out of this particular thread. (and I can't seem to find the report about automatically switching Sensor to TPOD) So you see what I am talking about, though, see attached track: - SEA radar lock up ship at 50 miles - Switch to MAVF - Seeker uncages and snaps to target area. NOTE RDR in HUD - Enable TPOD, too far to see anything but the TPOD is pointing at the target - Move TDC to TPOD.. Note RADAR loses lock (RDR no longer appears in HUD, but neither does FLIR because it isn't locked either, just ground stabilized) - Mess with TPOD to get an AREA track, FLIR appears in HUD. - At around 18 miles, I do manage to get a Point Track on the Moving Ship. - From what I can see, the MAV remained locked on from the beginning by the upside down triangle. Switching to MAV seeker you can make out the ship under the MAV reticle (though at this point it might be cued to the FLIR PTRACK. Pretty sure the Mav seeker symbol hadn't moved since initial lock) RadarFlirMav.trk

I have that problem often. USUALLY successive CAGE/UNCAGE cycles will get it to lock, but sometimes have to Undesignate and Slew ever so slightly to get the seeker to lock. Not sure if it is an "LOS" issue or a "CONTRAST" issue (though we know that DCS doesn't really model contrast as such) or sometimes the Maverick will lock on to something ELSE and you can see the Maverick Seeker triangle slightly offset from the TGP diamond.

I haven't looked at the TRACK yet... but... Are you confusing CAGE/UNCAGE with ability to SLEW the seeker? If you have a target locked by another sensor and hand it off to the MAVERICK seeker, you cannot slew the MAVERICK seeker unless you UNDESIGNATE the target. The Seeker will remain GROUND STABILIZED (for that missile) so you can Slew around near the Target that is handed off and lock something with the seeker itself. Once fired, the next missile will be boresighted. In my experience with the AGM-65F, when I handoff a target from the TGP (maybe also GMT, I don't recall) the FIRST missile automatically uncages and attempts to lock onto the point. Subsequent target handoffs require manually UNCAGING. YES you need to hold down TDC DEPRESS to slew the seeker unless you turn off REALISTIC TDC SLEW in SPECIAL OPTIONS.

Works fine for me too. I don't always get a LOCK but it always uncages for me Have you checked you control binding to make sure you don't have something funny going on with CAGE/UNCAGE? Does CAGE/UNCAGE work OK with other weapons such as AGM-65E or HARM Handoff, or caging VV in the HUD with cross wind?

Here: By default: R (Release, Forward). When held, releases the force trim system and attitude hold mode. When released, re-engages the force trim system, using the cyclic’s current position as the new center point. • AT (Attitude Hold, Left). Toggles on or off the selected attitude hold mode (position, velocity, or attitude hold). • AL (Altitude Hold, Right). Toggles on or off the selected altitude hold mode (barometric or radar altitude). (NOT YET IMPLEMENTED) • D (Disengage, Aft). Disengages attitude and altitude hold. (not sure if this is Implemented yet) I bound my Down to the RESET TO DEFAULT option below the TRIM options Attitude hold does different things based on your speed. See below for WAGS' video on it. null WAGS explains ATTITUDE HOLD:

This .trk is so small you can do that. For longer tracks that get very large, you can open the .trk file with 7-zip or similar app and remove the large track portion while retaining the mission information. This is how you can take over and fly from a track replay as all the mission info is there. So you could remove the TRACK and TRACK DATA folders first, but this one is so small it doesn't really matter. BTW, targets are at WO1 in the Apache.

Also, if you want to try something in a more controlled environment, you can take my TRK, change the extension to .miz and fly it. Apaches at Kobuleti, short ingress to old Kobuleti with unarmed targets. JTAC autolase on 1688, so no need to change anything just to verify proper function. I have always gotten constant lasing of all targets. You can also spawn new targets via the F10 menu which will also spawn another JTAC (AFAC) lasing on 2111 (default Channel B) to see if the channel affects things. (This is kind of my all in one training mission, so there are other aircraft to fly, Carrier ops etc., Just pick one of the 4 Apache clients at Kobuleti).

Post a track if possible.

Happy to have helped!

Unfortunately, I don't think this can be done currently from the back seat. Maybe when the LST is implemented, it will allow a Target point to be generated. I definitely could be wrong here. The CPG could slave the TADS to the SKR ACQ and STORE, but I don't think the Pilot has any way to do this. I think the best you can do now is to put your Pilot Helmet Sight over the dashed cross and ask GEORGE to target it and store it. If you punch in the coordinates from the JTAC, though, you can generate a Target or Way point and select it on the TSD to get ranging information, and also set that TGT/WPT as the ACQ or DIR steering point.

You are there!! Ready to rock with JTAC on 1113! Note that it is not necessary to do the ACQ-->SKR. It just makes it easier for me to have a visual cue as to where to point the aircraft without punching in Coords to orient myself. Of course, the SKR cue doesn't give you any indication of RANGE. As the most common usage would be in a LOAL mode, when the target designation is possibly masked, you won't see the CUE anyway, but it is good for quick orientation of LOBL attacks with known range. It will show ?SKR until your MASTER ARM is on and HELLFIRE's are WAS'd Once you change a FREQ for a CODE as CASMO showed, you can select that as a CHANNEL CODE as well. Here's a short .trk, but you already got it. Set ACQ to ?SKR I changed the FREQ for Channel Q to 1776, then selected it as the PRI CHANNEL. Then I Armed (with GROUND OVERRIDE) and WAS'd Hellfire Channel Change.trk

Ahhh got it.. makes sense that servers would set different JTAC codes. The Video from ~3:40-4:30 shows customizing channels... Hmmm.. while he shows setting custom codes for the LRFD/LST he doesn't show setting custom Channels, but I think it works the same way. Once you have customized a FREQUENCY as he shows, you can select it as a channel. I'm gonna jump in and try it.

Watch this video. It should start at the beginning of the CHANNEL setting part at around 3:40 The JTAC code you mention as an example is non-standard to any of the PRESETS, so you are going to have to manually set the channel as described in the video. First off, though, WHY is the JTAC on such a non-standard PRF? - Built in JTAC is on 1688 and even CTLD defaults to that. If the JTAC is on a preset PRF, you just need to select that. For 1688 you don't have to do anything as Alpha is the default at 1688

Neither. Change the CHANNEL to set the Hellfire seeker to the JTAC code. (When the LST is actually implemented, then it would make sense to set that as well, but not just yet)

Will try it. I've read that OPENXr doesn't do much for Oculus headsets. I see that the Kegety mod I have has some NVG scaling options. I might try them first before slotting in another mod, though 3DMigoto looks really good!

Hmm as an aside. I fly in VR also (Quest 2). When I put on the NVG's, I am not seeing the Circular NVG area, my entire screen is NVG-like which makes it really easy to fly, but hard to read any cockpit displays. I do have a Shader Mod loaded, which does have some tweaks to NVG's, but I don't think it does this. Am I missing a setting somewhere??? This thread would seem to indicate others have the issue as well..

FInally managed to get unstuck and flew the mission. First night mission ever. Wow.. its a whole new world. Got all the targets (second attempt) using the SKR ACQ trick and punching in MGRS to orient in the right direction to pick it up. In VR, there was enough ambient light that I didn't use the NVG's though I did put on the PNVS a few times just to experience it. Really had to crank down the brightness or it was overwhelming. Edit: Flew it again with NVG just to see the IR pointer to orient better. Couldn't fly very long without my IHADSS symbology, though, so I had to switch back.

LOL... not a DCS crash... a "CAN'T TAKE OFF FROM THE FARP WITHOUT HITTING SOMETHING AH-64D Crash"

In the Apache, the MGRS format has 4 digits instead of 5 in each coordinate. To enter points in the KU, you pretty much just drop the last digit from each IT gets you "close enough" usually. CTLD script can PROBABLY be tweaked, but I wouldn't know how. I assume that is what YOYO meant.. I didn't fly the mission (LOL... I did but kept crashing before I could lift off the FARP) so I am not sure if there is another place where MGRS is given.

Thanks for the info. I guess not all Night Vision is created equal