Speed and angels mission 12 LGB part

[NicolasDf]

LS,

After eliminating the air threat the next step in the mission is to go and bomb a couple of ships close to WP1. 
This part of the mission does not work for me:

I don’t have a LANTIRN video image in the front cockpit, only the Lantirn bezel. Also, the LGB12s don’t fall. I have tried by keyboard command and joystick but no joy. Jester does give guidance. I didn’t have this problem during the Nevada RAG AG training mission. 

Next step was to run a DCS repair which didn’t solve the problem.

Any suggestions?

And yes: all switches are set correctly in both cockpits as are the contrast and brightness for the VDI. I have trained extensively DCS AG missions for the F14 with the Lantirn and LGBs both as pilot and RIO. From my side this is a bug of sorts but nobody else seems to have this problem… so must be doing something wrong.

N.

 

 

[Reflected]

Hi,

if it worked at the RAG it should work in mission 12 as well. Here’s what I can think of:

- make sure you don’t have the spacebar assigned to anything

- make sure you have no unofficial mods installed  

if this doesn’t work, better ask the Heatblur guys because it’s definitely not mission related. And not a switchology  problem either if it worked at the RAG

PS: there is a Tomcat bug, sometimes I get a black screen with a crosshair instead of the TCS image. Maybe it’s related?

Edited January 19, 2024 by Reflected

[NicolasDf]

LS,

I’ve found a solution. Apparently some players had a similar issue on DCS MT and their workaround fixes the TCS and LANTIRN image problem on the VDI. I have this issue on the standard DCS but the same solution works too:

Starting the mission from the mission editor gives a normal functionality for the imagery of the LANTIRN in the front cockpit.

To get the bombs drop I jumped in to the rear cockpit and although on the armament panel all the switches were set correctly, I switched them all off and back on again as a reset and this worked.

The strange thing is I only have had this issue in mission 12 of S&A. For all other missions the F14 works as advertised. 

In any case, problem solved.

Thanks for your input,

N.

 

[Reflected]

Thanks, good to hear that!