Swift. Posted October 17, 2020 Share Posted October 17, 2020 AGM65E will not spot a laser if an AGM65F has been launched first. Tested on Caucasus and NTTR https://www.youtube.com/watch?v=1LftSTFZ3o8&feature=youtu.be It is untested whether this occurs after the launch of other weapons as well.65Ebug.trk65EbugCauc.trk 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2 Link to comment Share on other sites More sharing options...
Frederf Posted October 17, 2020 Share Posted October 17, 2020 https://forums.eagle.ru/showthread.php?t=287346 It seems to be a code issue (1111 regardless of what is displayed). Link to comment Share on other sites More sharing options...
oldcrusty Posted October 17, 2020 Share Posted October 17, 2020 AGM65E will not spot a laser if an AGM65F has been launched first. Tested on Caucasus and NTTR https://www.youtube.com/watch?v=1LftSTFZ3o8&feature=youtu.be It is untested whether this occurs after the launch of other weapons as well. 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? Link to comment Share on other sites More sharing options...
Swift. Posted October 17, 2020 Author Share Posted October 17, 2020 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 Link to comment Share on other sites More sharing options...
Swift. Posted October 17, 2020 Author Share Posted October 17, 2020 https://forums.eagle.ru/showthread.php?t=287346 It seems to be a code issue (1111 regardless of what is displayed). Very interesting, seems this bug has been known and unresolved for a while then. 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2 Link to comment Share on other sites More sharing options...
Predator-78 Posted October 18, 2020 Share Posted October 18, 2020 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. CPU: 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz - DDR4 32,0 GB - MSI RTX3080ti - Win 11 64bit Link to comment Share on other sites More sharing options...
oldcrusty Posted October 19, 2020 Share Posted October 19, 2020 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. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted October 19, 2020 ED Team Share Posted October 19, 2020 Already reported thanks, we do have a potential fix waiting to be merged. thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Recommended Posts