_SteelFalcon_

while i do agree with this statement, the current FLIR is less than satisfying and may make the module less attractive driving people away from it. this will make using the LANTIRN even harder since IR is all it can do. the issue will not be the TGP, the issue is that even a nicely modeled LANTIRN will not fix the FLIR issues that are widely reported, ultimately frustrating the user and making this aspect of the F-16, and let's face it, a very large portion of A-G weapon employment in this module, a bad experience further frustrating the user. i'd rather have the pod as it is for the time being (as it did at least make employment of any sort of TGP in the years since the modules release possible) and the LANTIRN additionally.

I‘d like to see it added additionally, and then removed when the Sniper pod is available, so we don’t miss out on the LSS function we got to use for the last years. Not to speak of the useful TV mode as FLIR currently is rather unsatisfying or leaves some things to desire.

Thanks for the clarification, that‘s good news No TV mode and current FLIR images will definitely make it challenging…

What‘s the reason in removing the litening and replacing it with the lantirn? does this affect other modules that use the litening pod too? Or do they keep it?

pretty sure Viper Pilot is by Dan Hampton, but yes, there's a part in that book with exactly this scenario

If you fly the stable version, it is still bugged. They do work fine in the recent Open Beta version.

mav_auto_bsgt.trk no issues on latest OB. keep in mind, auto handoff might not be the most accurate, as you can see in the track, the first mav constantly tries to lock up another tank close to the tpod spi, not the exact one due to proximity. and at 8nm it's damn near max range. as i get closer, the missile has less of an issue locking the exact target my pod is looking at. and to bsgt them initially, you obviously have to slew the mav manually to the correct place as initially entering point track with non-boresighted mavs results in break-lock on the mav page keep in mind, bsgt at 4nm will look off when the target is at 8nm or vice versa

Is it also correct, that friendly contacts turn from green to white when they enter the radar scan? Seems hard to believe and very risky

ED answered the question a couple days ago, check the tag on the post:

Personally I dont really agree with boring weapon loadout, however, since most of the weapons currently have some annoying bug to them or a system related to its use, it‘s somewhat frustrating to use / fly. And that‘s what gets boring for me.

This sounds like the issue here:

Since when do you have to re-boresight? It used to not be the case for as long as i remember (excluded the part of when it was completely broken)

Currently you dont need to re-boresight after rearming. Although i‘m not sure if that‘s correct.

I see it has been reported here too, and its affecting MT and ST: And here:

Correct. I switched to ST and flew on Grayflag Syria. Then got hit out of the blue by the SA5 without any audible warning that a missile had even been fired. then i tried to replicate it in Single Player but in Single Player the launch warnings do appear.

Yeah but MT or ST doesnt matter, no Sam is generating launch warnings in multiplayer. Dcs is currently a horror game

I had no issue with helmet markpoints when I tried today. Can you replicate?

Same in the F-16

yep, seen the same issue. no launch warnings in MP

Had the same happening in the f-16 with an SA5. No launch warning at all in MP. when testing in SP, the warning did appear tho.

TGP point track on moving target established, maverick does not follow the point track. can only be temporarily set to the TGP point track with TMS right on TGP page MAV_moving_target.trk

Spi is the correct answer. It sends the current spi.

As stated before, I am not having any issues boresighting both stations at all with the current OB patch. I am well aware that the prior one was broken. The current one works perfectly fine. Unless you fly the stable version OR your process in boresighting is faulty, you should not have any issues getting them boresighted. Your assumption of me not flying the viper lately is pretty far off and you‘d know this if you‘d actually follow the bug reports section here at least a little bit. If you‘d provide some actual info about which version of dcs you use and what weapon loadout, this crap could be avoided. (Track replays do help with that ) if you are 100% sure you do it right and it doesnt work in the OB version, try repairing your game.

Relax mate, it might be user error and it‘s more often than not a valid assumption. I dont have issues boresighting them at all, i‘d also guess you do something wrong in the whole process. good luck

this!