TFLIR & Trigger button & laser designator issues(?)

[LordOrion]

Premise: I'm using HOTAS Warthog with a configuration made up with TARGET software.

 

 

Issue 1:

Now: I'm following the procedure described in Chuck's Guide to fire AGM-65E Laser Maverick with the aid of Litening: all goes fine until I activate the TRIG option to activate laser with the gun trigger: laser fires, but when I release the button laser is deactivated.

To make it works I need to keep pressed the gun trigger button but that will conflict with weapon release button (Gun Trigger = 'Space', Weapon Rel Button = 'CTRL+Space') and hence missile wont' launch...

Is this the expected behavior (laser off when releasing gun trigger)? I've noticed that pressing straight the WRB the laser is turned on and stays on. I've temporary 'patched' by assigning the WRB button into the DCS configuration menu disabling it in TARGET but I would like to come back to full TARGET

 

 

Issue 2: I've noticed that LTD/R switch is set back to off after launch or if you pass over the target without launching in some cases. Is there a reason for this or it is just a bug?

[BarTzi]

Issue 1:

 

The TGP will lase automatically for each laser guided weapon. What you should do instead is press and hold pickle. The TGP will start lasing, the missile will then track and launch. Let go of the pickle only after whe weapon is fired. I believe Chuck's guide doesn't cover the latest changes to the TGP.

 

Issue 2:

 

That's intended.

[Noluck]

Issue 1:

 

The TGP will lase automatically for each laser guided weapon. What you should do instead is press and hold pickle. The TGP will start lasing, the missile will then track and launch. Let go of the pickle only after whe weapon is fired. I believe Chuck's guide doesn't cover the latest changes to the TGP.

 

Issue 2:

 

That's intended.

 

In my observations in the designate/lase steps. I'm just learning the TPOD as of last week. I see that there are changes? Just trying to get this all down and learning.

 

1) FLIR is selected on RT DDI and timed out

 

2) you have to press TDC designate and then 'pinky un-designate' to get FLIR or other video to show up at all. Strange...

 

3) ensure laser is enabled using RT console->Sensor Panel->LDT/R switch

 

4) select [TRIG] on the DDI using OSB, will now be boxed/highlighted

 

5) with SOI on that DDI, slew the diamond to the target with throttle TDC

 

6) press TDC/designate button, FLIR diamond now locked onto target and stabilize

 

7) press and hold trigger, lase will start. Let go of trigger, lase will end. I ask why, I now do have a target designated?

 

I have to press and hold the trigger *and* fire the weapon (AGM-XX for me) and now TPOD will continue lase without holding the trigger until weapon impact

 

Also, after the last update to OB 2.5.6.53756 : you can no longer change the FLIR FOV using the throttle HARM SEQ/RAID/FLIR FOV push button. It now changes the selected weapon FOV no matter if SOI is on the FLIR display or not. It used to work.

 

---

[BarTzi]

 

7) press and hold trigger, lase will start. Let go of trigger, lase will end. I ask why, I now do have a target designated?

 

I have to press and hold the trigger *and* fire the weapon (AGM-XX for me) and now TPOD will continue lase without holding the trigger until weapon impact

 

Also, after the last update to OB 2.5.6.53756 : you can no longer change the FLIR FOV using the throttle HARM SEQ/RAID/FLIR FOV push button. It now changes the selected weapon FOV no matter if SOI is on the FLIR display or not. It used to work.

 

---

 

When trigger is boxed, pulling the trigger will manually lase. No pull- no laser is fired.

 

However, when you launch a weapon - it will automatically lase for you. The steps to launch the AGM65E are as I explained above. Just press and hold the pickle. The pod will start lasing, and when the missile tracks it will leave the rail. Let go of the pickle and the pod will continue to lase until impact + 5/10 seconds. Read what I wrote above again.

 

Since day one, any AGM (65F/65E/88.) has priosity over the TGP when it comes to the HOTAS, doesn't matter which one has the sensor priority (diamond). So you can't use the FOV switch to control the TGP FOV if any AGM is displayed on any display.

Edited August 24, 2020 by BarTzi

[LordOrion]

When trigger is boxed, pulling the trigger will manually lase. No pull- no laser is fired.

 

However, when you launch a weapon - it will automatically lase for you.

 

 

 

Yes, I've noticed this too.

But then, what is the point to enable laser trig? IMHO the fact that when you left the trigger button the laser goes off is a bug, otherwise there is no point in doing it :joystick:

[BarTzi]

Are you asking what's the point of manually lasing? Marking targets for another pilot is a good example.

Edited August 24, 2020 by BarTzi

[LordOrion]

Are you asking what's the point of manually lasing? Marking targets for another pilot is a good example.

 

 

right, indeed.

What I mean is what is the point of using that feature if I have to lase and shoot for myself?

[Swift.]

What do you mean, 'If I have to lase and shoot for myself'. The point of buddy lasing is so you don't lase for yourself, and can focus 100% on the delivery of the weapon without also having to worry about maintain a good pod track.

Edited August 24, 2020 by Swiftwin9s

[BarTzi]

right, indeed.

What I mean is what is the point of using that feature if I have to lase and shoot for myself?

 

You don't have to lase for yourself because the pod does that for you. You will almost never lase manually for yourself in DCS. Only for someone else.

 

And even if you don't buddy lase, it's another way help your wingman slew the pod to the correct target (LSS).

[LordOrion]

What do you mean, 'If I have to lase and shoot for myself'. The point of buddy lasing is so you don't lase for yourself, and can focus 100% on the delivery of the weapon without also having to worry about maintain a good pod track.

 

You don't have to lase for yourself because the pod does that for you. You will almost never lase manually for yourself in DCS. Only for someone else.

 

And even if you don't buddy lase, it's another way help your wingman slew the pod to the correct target (LSS).

 

 

Understood. So I guess the use of Laser Trig in Maverick employment is just wrong.

[Swift.]

Understood. So I guess the use of Laser Trig in Maverick employment is just wrong.

 

Its not wrong, its just cumbersome. The autolase is much nicer.

[LordOrion]

Its not wrong, its just cumbersome. The autolase is much nicer.

 

 

... and simpler.

[speed-of-heat]

Your problem is a collision between the alt space and space keys, remap them to dx buttons in target

[LordOrion]

Your problem is a collision between the alt space and space keys, remap them to dx buttons in target

 

???

Can you please elaborate this a little more?

[speed-of-heat]

By default each key on the joystick & throttle maps to a direct x button, what you have done is map the trigger to a key stroke, don’t do that... instead go into dcs and map the dx button for the trigger press on your joystick to the gun trigger ...

Edited August 25, 2020 by speed-of-heat

[Noluck]

When trigger is boxed, pulling the trigger will manually lase. No pull- no laser is fired.

 

However, when you launch a weapon - it will automatically lase for you. The steps to launch the AGM65E are as I explained above. Just press and hold the pickle. The pod will start lasing, and when the missile tracks it will leave the rail. Let go of the pickle and the pod will continue to lase until impact + 5/10 seconds. Read what I wrote above again.

 

Since day one, any AGM (65F/65E/88.) has priosity over the TGP when it comes to the HOTAS, doesn't matter which one has the sensor priority (diamond). So you can't use the FOV switch to control the TGP FOV if any AGM is displayed on any display.

 

The switch labeled in the NATOPS is the "RAID/FLIR FOV select button", the one I have mapped on the WH throttle, left side push button in front, pretty much same as the actual. Prior to the latest OB, it did perform that FOV select function with the SOI on the FLIR display. After the update, it does not. I'm confused, the switch is labled as above "RAID/FLIR FOV" but will not affect the FLIR display if a MAV is selected? Now I have to take my hands off HOTAS to change the FLIR FOV correct? I'd rather have it back the way it was.

 

 

 

If it's like that with MAV's in the real Hornet, then so be it.

 

Thanks for the information.

 

---

[rob10]

Prior to the latest OB, it did perform that FOV select function with the SOI on the FLIR display. After the update, it does not. I'm confused, the switch is labled as above "RAID/FLIR FOV" but will not affect the FLIR display if a MAV is selected? Now I have to take my hands off HOTAS to change the FLIR FOV correct? I'd rather have it back the way it was.

 

If it's like that with MAV's in the real Hornet, then so be it.

 

 

Sorry, but if you do a quick forum search on "MAV FOV" you'll see it's been this way since at least October of last year, it didn't start with the latest build.

The RAID/FLIR FOV will switch the FOV of the TPOD IF you don't have a MAV (and possibly other missiles, can't remember for sure) up on the other DDI. If you do have the MAV up this switch controls the MAV FOV regardless of which DDI has TDC priority. And yes, it apparently is that way in the real Hornet.