in development and testing What happened to the new MSI functionality?

[amalahama]

I expected it in the next patch but according to newspaper it doesn't seem to be the case anymore...

I really love ED putting some care and attention to the hornet, because it's lagging behind the F16 and the Apache in realism

[rob10]

TA radar should be in next patch (fingers crossed for this week), MSI has always been "planned" for August patch.

[Fresh]

I noticed recently I could L&S and DT2 onboard trackfiles via the SA page.. is this new, or did I just not try it in the past?

[Muchocracker]

It was added a long time ago i dont even remember when. 

[Zarma]

It's in the patchnote. But no clue how to use it.

[Muchocracker]

find a SURV track on the RDR ATTK page, and TDC depress to designate as Launch and Steering

[falcon_120]

find a SURV track on the RDR ATTK page, and TDC depress to designate as Launch and Steering

Is it correctly working along the TWS auto mode? So good bye to having to go AUTo>MAN>AUTO again to L&S target outside current AUTO rdr coverage?

I'm away on vacation and we'll be unable to test for at least 1 week :(

Enviado desde mi RMX5011 mediante Tapatalk

[AndrewDCS2005]

@Muchocracker L&S designation is fine, do you have info if current implementation (which is stated as WIP) already allows to launch, guide and hit MSI-only track by AIM-120 without locking the target with onboard radar? I've tried few times but no success so far.

[Muchocracker]

1 hour ago, falcon_120 said:

Is it correctly working along the TWS auto mode? So good bye to having to go AUTo>MAN>AUTO again to L&S target outside current AUTO rdr coverage?

I'm away on vacation and we'll be unable to test for at least 1 week

Enviado desde mi RMX5011 mediante Tapatalk
 

AUTO should be centering the volume on the L&S At all times, no matter if the trackfile has radar contribution or not. 

 

31 minutes ago, AndrewDCS2005 said:

@Muchocracker L&S designation is fine, do you have info if current implementation (which is stated as WIP) already allows to launch, guide and hit MSI-only track by AIM-120 without locking the target with onboard radar? I've tried few times but no success so far.

As long as the radar is on and transmitting (not in SILENT) it should still provide command link's to the amraam. If it's not it needs to be reported what conditions is causing it not to. 

Edited 18 hours ago by Muchocracker

[Coyle]

1 hour ago, Muchocracker said:

AUTO should be centering the volume on the L&S At all times, no matter if the trackfile has radar contribution or not. 

AUTO will prioritize keeping the L&S in radar coverage at all times, but will in fact actively work to keep as many track files in the radar as possible with the help of MSI tracks. So 'keeping it centred' is a bit of a mischaracterization.

Attached image has the L&S on the far left while AUTO is engaged, keeping as many things in the box as it can (basically all but one)

Edited 17 hours ago by Coyle

[Muchocracker]

4 hours ago, Coyle said:

AUTO will prioritize keeping the L&S in radar coverage at all times, but will in fact actively work to keep as many track files in the radar as possible with the help of MSI tracks. So 'keeping it centred' is a bit of a mischaracterization.

Attached image has the L&S on the far left while AUTO is engaged, keeping as many things in the box as it can (basically all but one)

i am well aware of TWS centroiding. His question was specifically in the context of the SURV tracks which you can only have 2 at maximum designated at this time. 

[ramyad]

13 hours ago, AndrewDCS2005 said:

@Muchocracker L&S designation is fine, do you have info if current implementation (which is stated as WIP) already allows to launch, guide and hit MSI-only track by AIM-120 without locking the target with onboard radar? I've tried few times but no success so far.

Hi there i have done some extensive testing yesterday with a buddy and i can confirm the following:

It is to note that in all the testing mentioned below we i had my radar on silent ensuring that the input of the target is coming from datalink.

You can lock and launch an Aim120 on a MSI only track however as mentioned in the changelog you might visualize some desync pretty regularly. We have tested using both tracks coming from AWACS and in other instances we have tried using only fighter to fighter datalink and in both cases it works meaning good launch good track and a good hit.

However there are plenty of issues that have been caused in the radar for example now by using NWS in the TWS mode i have verified that it appears like the target switch happens but immediately snaps back meaning you can go from target with priority as 1 to 2 but it kinda glitches and throws you back to the 1. Other isssue i have noted for example when you perform soft/SAM lock on a target in RWS mode you cant proceed to unlock it with NWS.

And this issue is very evident when you try to for example perform a msi lock on a target that is located outside your radar sweep you get a successful lock but when you proceed to unlock it you can't which is pretty annoying.

But overall its a very cool feature added and in near future the issues will be resolved most likely.

Edited 5 hours ago by ramyad

[Tholozor]

2 hours ago, ramyad said:

Other isssue i have noted for example when you perform soft/SAM lock on a target in RWS mode you cant proceed to unlock it with NWS.

This is correct, as the NWS button shouldn't drop L&S designation. Pressing NWS should:

- command return to search (RTS) if the radar is in STT.

- step the L&S designation through valid, ranked trackfiles.

- swap L&S and DT2 designations if both are present.

If you want to remove the L&S in RWS, press RSET.

[Muchocracker]

There is a known bug with the undesignate logic in MP. It effects RSET as well effectively paralyizing you from switching targets