AeroDan90 Posted July 16, 2021 Posted July 16, 2021 (edited) So me and a friend have been practicing LANTIRN bombing with GBU's in the Tomcat (14B) for almost a week and after this most recent update i can no longer see the LANTIRN pod in the front pit, only the TCS will display and i also cannot see any ordinance (GBU 16's in this case) being selected by my RIO, all other functionality is there, he can set waypoints and can lock air targets, he can also use the full radar suite and the LANTIRN himself but it still only displays the TCS for me in the front, other things are also synced such as switch sounds, TID and the tape player are all working fine but without being able to see the LANTIRN and not having bombs being selected for the pilot this removes all A2G functionality for multicrew as dumb bombs are boring for RIO's. (or so I'm told, I always fly the thing) We had ran 20+ successful guided bombing missions in the Tomcat during the week leading up to the update and barring minor issues (desync) and my RIO forgetting to lase the first few bombs.. we have been issue free but after this update we have attempted several times to get this to work but so far we have had no luck. Things we have tried. - Consulting the manual as well as numerous tutorials in case we missed something obvious. - Multiple restarts/reconnects for any possible desync issues. - Starting both from the Ramp (hot and cold), from air starts and from the runway directly. - Multiple missions created by myself in case of file corruption, basic missions, no scripts, no MOOSE. - Having Jester set up everything first. - Having me jump in the back and set everything up (my RIO is new to DCS) and then having him jump in. - Loading in and then removing the LANTIRN with 'rearm' and then replacing it to force it to reset. - Loading in clean and then installing the LANTIRN fresh from 'rearm'. - Setting up the LANTIRN both on the ground and in the air. - Both of us re-installing the F14. At this point we are at a loss, the only thing that is different from when it worked is the new update and after reading through the patch notes nothing obvious seems to stand out dealing with the 14 or the LANTIRN that would cause such an issue, so now I'm here to see if anyone else is experiencing this issue as it's kind of annoying having my friend who is using a trial license for the F14 being unable to actually do anything useful, we both prefer A2G over A2A and right now other than the Hind or the Gazelle (both of which he does not own so more trials needed) we cant really do much together. Hopefully we are just missing something simple but im 98% certain this is a bug caused by the update otherwise the timing of it is ridiculously coincidental. Edited July 16, 2021 by AeroDan90 PC Specs Owned Modules Wishlist Ryzen 7 3700X F-18 - F-14 - FC3 AC-130 - Su-47 - Avro Vulcan - B-2 Spirit ASUS ROG STRIX X570-F Super Carrier - Persian Gulf F/A-18E/F Super Hornet - F-35 - B1/B Lancer EVGA GTX 1080Ti 11GB Syria - KA-50 - Gazelle E2-D - AH-64D (soon!) 32GB HyperX Predator DDR4@3200 A-10C II F-4E - Tornado GR4
IronMike Posted July 19, 2021 Posted July 19, 2021 Thank you for the great report, we are currently looking into it. We will have a MP test this week, where we will give it specific focus. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
QuiGon Posted July 19, 2021 Posted July 19, 2021 (edited) Hmm, I've done quiet a bit of multicrew LANTIRN work last week as a RIO with two different pilots and it all worked fine. We were running the current OB and were both clients on the Buddyspike BlueFlag server. Edited July 19, 2021 by QuiGon Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Recommended Posts