Recluse

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

I guess I am gonna have to learn how to use CTLD My Mission Editor JTACS are not very consistent in how they are working. As pointed out above, though, it would seem like a bug that PNVS and TADS FLIR don't show the IR pointer.

Interesting. I looked at the mission and it is using CTLD script for the JTACS. I don't really know much about it, but I GUESS that the CTLD autolase must have the IR POINTER active at the same time. I will try it with the Mission Editor built in JTAC with LASER ONLY and see if I can see anything in NVG's. You really SHOULDN'T see the Laser at all unless it is paired with the IR pointer.

I don't think you should be able to see the Laser only in NVG. For JTAC there is the option of IR pointer or IR Pointer + Laser.

So, FYI just did a multiplayer session and Buddy Lasing worked fine (as described for Single Player) with the Shooter using SKR as ACQ and matching Channels with the Buddy Laser code (actually we just left it at default Channel A, but later switched to B for Buddy Lase Code and Shooter Channel and it worked there as well. Everyone in the Back Seat.

Yeah, sorry. Don't know what happened with the quality there. So, basically, like Raptor9 said: - On WPN page set ACQ to SKR - Make sure HELLFIRE channel is what the JTAC is using (always 1688 for built in Mission Editor JTAC, may vary for CTLD) WAS Hellfires from back seat. - Point in direction of target (either from creating a TGT PT/Waypoint from JTAC coords, or with knowledge of another waypoint. -When the laser fires, you will see the CUED LOS cross on it, and a PRI CHAN TRACK message. Try this track.. JTAC_backseat2.trk

Yes.. I am converting my TRK to a video and I will upload it shortly... You can't do EXACTLY what you want, in terms of IDENTIFYING from the back seat other than getting a CUED LOS dashed cross where the LASER spot is. You can't slave it to TADS video from BACKSEAT, but at least you can SEE where the JTAC laser is pointing at from the backseat. In the video, the Cued LOS doesn't look like it is over the target due to the way the IHADSS is in the 2d. When I flew it, the Cued LOS was right over the target (as best as I could tell from 7 km out. As far as the video, you'll have to trust me on this . I'll try to get a TRK again later without the A-4 mod which should show it better. UGH don't know why the video quality is so bad either.. hopefully it will help. Video removed... wasn't useful.

Ahhh crap.. that's right, I had A-4 mod loaded in that mission.. Sorry.. Let me try again...

Actually you CAN when you set ACQ to the SKR... See attached TRK. Crappy flying... I always fly in VR, but this was pure 2d without TRACKIR or anything, I also forgot to call IN and wait for CLEARED HOT, but THIS time anyway, the JTAC didn't seem to mind. In this case, I knew my targets were at W01, so I used the W01 as a reference for direction and distance vs. punching in the target coordinates. JTAC_backseat.trk

In Casmo's video, YES, but it works just as well from the back seat. I'll try to upload a trk if I can..

If you have LOS to the target, you can essentially fire LOBL. Set ACQ to SKR and you will see the dashed cross on the Lased spot (not necessary but useful for reference - Casmo called this "Poor man's Laser Spot Tracker"). You'll see a message to the right of the High Action Disply, PRI CHAN TRK to show the missile is tracking a laser spot and you can fire it. - all from back seat without George in the mix

So I am having a similar issue. The JTAC has LOS and distance is short. At best, he will NOT do a laser mark. Often, he will immediately respond "NO FURTHER TASKING" when there are a ton of units. It is daytime. Things are complicated as: - there is ANOTHER JTAC marking targets in the same vicinity, though a different group. That one works fine. - the second JTAC is spawned by the same F10 Radio command that spawns the GROUP he is supposed to mark. - Even if I place the 2nd one VERY CLOSE to the first one, I get the odd behavior of either NO FURTHER TASKING or TASKING without MARK. Both are SCOUT HMMWV's. Was going to try making the second JTAC a Drone AFAC and see if that helps. Maybe you can't have to JTACS that close together? USING only Built in functions no CTLD/MIST EDIT: REAPER DRONE AFAC worked fine in conjunction with the the Ground FAC. Don't know WHAT the problem was with the second ground FAC.

Check the settings under the MISC tab and make sure FORCE FEEDBACK isn't checked. This happened to me (not sure HOW it got checked) and TRIM did not work until I unchecked it.

@ex81 Nice job. Only change I would suggest is that Mother is not always going to be on 127500 radio frequency. It depends on what was set in the Mission Editor, so I'd make this step more generic.

I had a similar issue lately and while it may not be the same as what you are seeing, and this is how it was resolved: Problem: So, all of a sudden, my TRIM stopped working. I saw the red X when I hit the trimmer, but when I returned to center (in either mode) the nose would pitch up like there was no trim. Solution: I found it buried in an older thread: Somehow, in the MISC tab, FORCE FEEDBACK got checked. I don't know how, but it was. Once I unchecked it, TRIM was working normally.

Ok, thanks. That makes sense. I just tried it in Single Player and this is the case.

Jumping on this thread rather than creating a new one. I think the question is related or at least related to the new implementation of the D/L settings that came with the ACL. - Previously, just turning on D/L would get you datalinked contacts with other flight members on the SA page. Last night in a Multiplayer flight, we could no longer see each other. Is there some additional setup needed now on the D/L MIDS menu? - Possibly we didn't setup the SENSORS subpage of the SA to enable LINK4, but it seemed automatic before and when I jumped into a Single Mission it was all set up. (We did Hot Starts) Was this changed? Thanks!!