Moonshine

While i welcome the improvements going into the Q&A part (hope to see more of it), as a customer, the current quality of the module is not acceptable. Yes it is early access, however the decline in quality, the constant issues with systems being broken is not okay. While i dont know the very process after which testing is done prior to releasing a patch, it is questionable how, after 2 minutes of installing the patch and starting the jet in an effort to do an integrated systems test (cold start, align, takeoff, employment of systems and weapons) some major bugs like the boresight and the laser code can be immediately found. „Just enjoy it as it is“ is reeeeally difficult that way and the frustration is noticeable throughout the viper community by the looks of it. This is what i want to see changed and it would be appreciated to hear something about the efforts ED intends to take in this direction

there is a lot of things wrong with the HARM POS modes, might be related:

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