[ED]Ben

Hi - this one was reported previously, and is fixed internally. Thanks

Hi - Just checked your track, and it looks like HRM OVRD was unboxed, so that part looks ok. The first missile goes for the ships as the AE is boxed in SP mode - as at the point of the first shot, it is regarded as the priority target. (HARM does not know friend/foe) Always ensure that the target you want to shoot at is boxed. I will investigate a little more however, as it may be that the priority should have been placed on the SA-15 sooner ( as it was for second shot).

Hi - i can not replicate this, and when i play your track it shows the missiles flying all the way to the target and impacting. Is it just the one time you saw this? or more? Thanks

Thanks - Reported. It seems it may only be one station affected - you can cycle stations using weapon select on HOTAS, and the other stations will operate.

reported - thanks

reported - Thank you for the detailed report - helps alot

Thanks Both - i will take another look. Appreciate the detailed responses

Hi - I may be totally misunderstanding this report, but as i understand it, you fly the FPM to the tadpole for steering to steerpoint. The tadpole would be offset to show any correction for wind. If no wind tadpole aligned with steerpoint marker. If you think it should operate differnetly, please could you supply some evidence? Thanks

As suggested above, we really need a track replay - i can not replicate either of those issues, so a track would help us see what may be causing it. Thanks

The additional TMS functions will follow in later patch. Thanks

Yes you are correct on the SOI - the auto SOI selection bug is reported, and we are working on it. Sorry i did not make that clear in my first reply.

HUD is the default SOI if the TGP or FCR are not tracking. HAD is not a valid source for mark mode, but you should be able to select as SOI - this is known issue. Thanks!

Can you list the steps to reproduce please? I can see the elev increase in your track, but if i take control, i can not replicate. Thanks

Yep we have this reported. Thanks

We have problems with beacons reported in MP - One thing to note is that if the client joins after the beacon starts transmitting, then the client will not hear it. Currently best practice to put any beacons on a timed trigger to restart every 5 mins or so, even if set to run on a loop.

quite right. i clearly need more coffee.

the DI in our mossie is the 6A/1298 model - so correct as is

replicated and reported - thanks

Airfield data visibility depends on mission editor view settings. Investigating to ensure they are consistant

Thanks - we caught this one internally. Should have been on the known issue list. Well spotted

Hi - we already have this reported. Thanks

Investigating this now.

Hi - please can somebody attach a recent log from when the incident happens? Ideally with an indication of the time the icons dis-appear. Thanks!

@Mike_Romeo thanks - I will have a look in the morning

reported - thanks