Moonshine

id also like to keep the boresight mechanic. as long as it doesnt break every time a bigger update happens

dear ED, this was a question about the functionality, not a bug report. Just slapping „correct as is“ wont answer the question as to why everyone else can lock on jamming targets but not the viper. thanks

seems to also apply to the viper. seen the same, mostly after manually entering the STN

currently it seems to be impossible to get a radar lock on a jamming target unless you reach burnthrough range (around 27nm) shouldnt it be possible to get a lock but not get range info? after all, the ECM use would increase a contacts RCS. shouldnt we be able to fire missiles with their home on jam capability at the expense of losing their loft mechanics (aim-120)? now even within burnthrough range the amraam doesnt loft - but thats a different topic in the past (about 2-3 updates ago) it was possible to get a lock on something thats jamming, this no longer is the case. is this intended to be that way? Cannot-lock-jamming-tgts.trk

add the mav boresighting thing to that hotfix too

a minor thing but since the april 24 patch the RWR BIT no longer works RWR-BIT_not-working.trk

OP is right. boresight does not work. upon boresighting the MAV LOS is nowhere near the TGP location (even worse than its non-boresighted original offset from the TGP), not stabilized and the LOS indicator in the HUD does not match the actual picture on the MAV screen. MAV-boresight-not-functional.trk

+1 for hotfix. it impacts MP gameplay quite a bit. and i dont even know if its a viper only issue

seeing the same Drift-CO-off-the-HUD.trk

- set up a jet in the ME with laser code other than 1688 (in my test 1511) - set up the laser codes in the DED accordingly and arm the laser - drop bomb -> bomb will miss. - change TGP laser to 1688 -> drop next bomb -> hit track attached so since the patch, the laser guided bombs do not care about the laser code set up via ME or via kneeboard prior to adding power to the jet GBU-12_not-tracking-laser.trk

thanks. removed my comment. looking forward to see more info

seems to be related to this: check if at the time you switched to VRP you were already in CCRP mode

it does not when you have no weapons on board. and you can also not select it on the MFD itself.

they denied the things with the maverick EO VIS modes too. took years to get them to acknowledge it. lots of prior denial. still we have it now and the community was right about it. wouldnt be surprised if that repeats itself here (and with the RWR)

apparently marked as "planned" in this post

@BIGNEWY why is this a wishlist item and not a bug? it was working before you guys remodeled the RWR..

Sams in DCS are rather simplistic. Only by using scripts like Mantis or skynet you can make them behave less stupid. Until ED comes up with some more in-depth modelling of an actual IADS, thats sadly how it is.

the higher and faster something is, the faster his missile will be and hence will cover the distance from pitbull to impact more quickly. thats why at very high altitude, just defending when you hear the RWR wont suffice. you have to anticipate that the enemy has fired on you already. not even mentioning thin air and hence less drag for the missile but also slower control response for any defensive maneuvers. The Amraam has some guidance capability with Datalink, so if you lose lock, it will continue to fly to the anticipated location of the contact, and, with some luck, pick it up on its own radar once active. however this is not as reliable as if you continue to feed the missile info by holding the lock until she goes active

might be related: dont think its the bombs fault but the CCIP post designate

i support that point. an option to choose would be beneficial. having switched from a "conventional" stick - that was great all around - to a FSSB did improve the "feel" of flying the viper in ways i cant explain. i just feels so much better, more agile and more responsive.

i tried to get a track from a MP server (as they save automatically) yet so far i can never open them (most likely corrupted due to the crash). @BIGNEWY could you please take a look? the "missing trackfile" tag like on this post (merge, same thing) wont help solve the problem.

indeed you are correct. you can type in all the data, as soon as you switch the release mode to CCRP (or even PRE for MAVs) the game crashes. and no, Track cant be produced as of course the game crashes before a track can be saved... here, a video: https://drive.google.com/file/d/1cNypCukWXB6bu0auxKXXw1Rf1iS1rbUp/view?usp=sharing

Yes this is also why i observed in my test, lat long was fine but elevation was couple feet off every time.

As already raised and explained by @Sadhu, the WPT data shifts when pressing TMS aft to CZ. while the coordinates stayed consistent in my test, the elevation data after pressing CZ was off compared to what the DED WPT entry says. i understand this to be the case when area track or point track is commanded as it measures true elevation, however not when the pod is just slaved to the steerpoint. Sadly the previous post was locked, so i made a new one. TGP_TMSaft_shift.trk