Jump to content

Recommended Posts

Posted

I've been practicing comms with JTAC and so far I can get everything working (i.e., check in, 9-line, IP inbound, etc). BUT, I never get an option to have the drone lase. I've spent hours fiddling around with different settings in ME to try to fix this but not sure why it won't lase. Not sure how I can upload my .miz file here for anyone to take a look. 

Posted
9 hours ago, cypher04 said:

Not sure how I can upload my .miz file here for anyone to take a look. 

If you go into your Saved Games\DCS\Missions you should be able to find your .miz file - to attach it, you simply drag and drop the file into the box that appears below where you enter text.

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted
10 hours ago, Northstar98 said:

If you go into your Saved Games\DCS\Missions you should be able to find your .miz file - to attach it, you simply drag and drop the file into the box that appears below where you enter text.

Got it. Since my account was created < 24 hours ago I think it's preventing me from uploading any files. Will check back in a few hours (post 24 hour) and see if I can upload the .miz file then.

  • Like 1
Posted (edited)

Hmm, I've had a play around with it - I can't see anything wrong with how you've set the tasking up.

I was able to get success with the A-10C as an AFAC in my own mission (if you change the file extension to .miz from .trk you'll get the mission file), just using the FAC - Engage Group task, under "Start Enroute Task".

The MQ-1A and MQ-9 pretty much always seem to give "No Mark", even though LOS should exist, they should be in-range and the laser shouldn't be masked by anything. I was able to briefly get a "marked by laser" message from the MQ-1, but I haven't been successful in replicating this.

Personally, it looks like that there might be an issue with how the MQ-1 and 9s designator is defined - an identical tasking yields expected results with other units and as said above, the targets should be in-range, LOS to them should exist and the designator isn’t otherwise masked by anything.

HMMWV_FAC_Mark.trk MQ-9_AFAC_NoMark.trk A-10C_AFAC_NoMark.trk MQ-1A_AFAC_NoMark.trk

Edited by Northstar98
Added speculative conclusion

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

Posted
On 9/18/2024 at 2:15 AM, Northstar98 said:

Hmm, I've had a play around with it - I can't see anything wrong with how you've set the tasking up.

I was able to get success with the A-10C as an AFAC in my own mission (if you change the file extension to .miz from .trk you'll get the mission file), just using the FAC - Engage Group task, under "Start Enroute Task".

The MQ-1A and MQ-9 pretty much always seem to give "No Mark", even though LOS should exist, they should be in-range and the laser is masked by anything. I was able to briefly get a "marked by laser" message from the MQ-1, but I haven't been successful in replicating this.

Personally, it looks like that there might be an issue with how the MQ-1 and 9s designator is defined - an identical tasking yields expected results with other units and as said above, the targets should be in-range, LOS to them should exist and the designator isn’t otherwise masked by anything.

HMMWV_FAC_Mark.trk 685.71 kB · 0 downloads MQ-9_AFAC_NoMark.trk 285.9 kB · 0 downloads A-10C_AFAC_NoMark.trk 571.92 kB · 0 downloads MQ-1A_AFAC_NoMark.trk 493.8 kB · 0 downloads

 

Thanks for looking into this. It's somewhat reassuring that you weren't able to get the MQ-9/1 to mark laser consistently just like me. I guess this is why most just use the CTLD script w/ the JTAC autolaze feature haha. I've tried different placements of the MQ-9 to be 1000% sure it had LOS but was never able to get the "Marked by Laser" response. 

  • Like 1
  • 1 month later...
Posted
3 hours ago, NineLine said:

Trying this mission, I am not seeing an issue, is this still a problem?

Doesn't look like it - the missions I used to create the tracks here now consistently produce "marked by laser" callouts with lasers being fired.

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...