Jump to content

Recommended Posts

Posted
This could also be related to another bug. There are issues with getting a launch solution when you put SOI on the MavE page. Do you get the same problem with SOI on Tpod?

 

I am tempted to say it's not that issue, because I also tested 65E on their own and they worked fine, I didn't take note of where my TDC was assigned but I am willing to assume it would be the Mav screen aswell.

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

Posted

I also have a problem with the LST mode of the TGP, the maverick does not lock onto the target illuminated by an external laser source.

 

Firma DCS.png

CPU: 12th Gen Intel(R) Core(TM) i7-12700K   3.60 GHz - DDR4 64,0 GB - MSI RTX3080ti - Win 11 64bit

Posted
https://forums.eagle.ru/showthread.php?t=287346

It seems to be a code issue (1111 regardless of what is displayed).

 

I've just ran into this myself. With Lmavs laser code set at the start of the mission, before switching to Imavs and using the the Imavs on the first 2 targets, I wasn't able to launch Lmavs.

 

On the second run, I set the laser code after launching the Imavs and no problems with Lmav launches. Both fired and tracked.

So... it seems like you're onto something here.

  • Recently Browsing   0 members

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