Jump to content

Recommended Posts

Posted

Hey,  anyone else having issues self-lasing a -65E on anything other than 1688? I tried on 1776 (both stores and tpod setup correctly) but no joy.. mav searches but cannot find the laser.

Callsign: "Milkman"

I7-8700k@4.8--Corsair H115i pro--EVGA FTW3 1080ti--GB Aorus Z370--256GB M.2 SSD--16GB ram--Win10--1000wGold Rate PSU--CV1 Rift--TIR5--X55 HOTAS--TM pedals--TM MFDs--Custom UFC

Posted

Hello.

I m afraid  that the code you are using is non acceptable. This are the laser codes availble

Laser codes

    1    2    3    4
    1    5    1    1
         6    2    2
              3    3
              4    4    
              5    5
              6    6
              7    7
              8    8

 

Saludos

Saca111
 

Posted (edited)

Umm, I use 1776 all the time. Might not have tried since the LATEST little OB patch, but I didn't see anything there about laser code changes.

 

Is this not still correct:

 

1st Digit: 1
2nd Digit:5-7
3rd Digit: 1-8
4th Digit: 1-8

 

Edited by Recluse
Posted

There's been a discussion about this in the bugs channel. Try to put the TDC to the FLIR page and you will see the Maverick capturing the laser in a dime.

Posted (edited)
3 hours ago, Recluse said:

Umm, I use 1776 all the time. Might not have tried since the LATEST little OB patch, but I didn't see anything there about laser code changes.

 

Is this not still correct:

 

1st Digit: 1
2nd Digit:5-7
3rd Digit: 1-8
4th Digit: 1-8

 

 

AFAIK that's still correct for the Hornet.  On the A-10 2nd digit can only be 5+6 (no 7).

 

EDIT: just tried it with 1776 and it worked for me.  Any chance you're just changing the LST to 1776 rather than the laser itself (laser option won't show in UFC until LASER is ARMED)?  Barring that, check the thread becas22 suggested.

Edited by rob10
added info
Posted
30 minutes ago, Swiftwin9s said:

Seems you guys might be confused with gbu-12. Mavs and the pod can do 1, 1-8, 1-8, 1-8 iirc. It's paveways that are limited to the 5,7,8 at the start.

 

Nope.  Just tried it on the Hornet, you can't use "8" as the 2nd number.  Strictly 5,6 or 7.  3rd or 4th 1-8 is fine.  That's for both GBU and MAV.  If you use 8 as the 2nd digit on either you get a flashing ERROR when trying to assign it to the weapon.

Posted
19 hours ago, rob10 said:

Nope.  Just tried it on the Hornet, you can't use "8" as the 2nd number.  Strictly 5,6 or 7.  3rd or 4th 1-8 is fine.  That's for both GBU and MAV.  If you use 8 as the 2nd digit on either you get a flashing ERROR when trying to assign it to the weapon.

Yeah sorry, my mistake the 2nd digit can't be 8 it's 1-7. 

 

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.globalsecurity.org/military/library/policy/usmc/mcwp/3-16/appk.pdf&ved=2ahUKEwjUi7nQ-OvtAhWgQxUIHc69BqoQFjALegQIDBAB&usg=AOvVaw1uvqpM6WwgotDtFPMmTIRO

476th Discord   |    476th Website    |    Swift Youtube
Ryzen 5800x, RTX 4070ti, 64GB, Quest 2

Posted
On 12/25/2020 at 9:16 AM, becas22 said:

There's been a discussion about this in the bugs channel. Try to put the TDC to the FLIR page and you will see the Maverick capturing the laser in a dime.

This seems to be my issue, thanks!

Callsign: "Milkman"

I7-8700k@4.8--Corsair H115i pro--EVGA FTW3 1080ti--GB Aorus Z370--256GB M.2 SSD--16GB ram--Win10--1000wGold Rate PSU--CV1 Rift--TIR5--X55 HOTAS--TM pedals--TM MFDs--Custom UFC

Posted

 

1 hour ago, Recluse said:

...and still marked CANNOT REPRODUCE and doesn't seem to be any clarity on the TRUE switchology for this 😞

 

Guess just do what works!

I can sympathize with ED on this one, because I've never seen the issue 🤔

Posted

Yeah it affects different people different ways.

 

For me, it seems to work fine with MAV SOI for any Stationary target, but if I am targeting a mover (vehicle or ship) I HAVE to move the TDC away from the MAV page.

  • 2 weeks later...
Posted

So, just thought I would post this observation:

 

Did a bunch of AGM-65E attacks. Previously I had been doing it sequentially. One press of the pickle..wait for the solid box and fire the missile. It was under these conditions that the "no lock with TDC in MAV page" issue arose.  After the latest patches, I have been doing the HOLD THE PICKLE DOWN method. What I noticed was (with TDC in MAV page) the Missile actually came off the rails BEFORE I saw the solid laser lock, but the solid box and lock appeared very shortly after the missile left the rails. Previously it would NOT come off before a MAV LKED indication.

 

Kind of odd. Wondering if others are seeing this behavior now??

 

 

  • Recently Browsing   0 members

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