fixed internally Helmet ACM functionality seems to be incorrect

[ColinM9991]

1 hour ago, NineLine said:

I cant answer why it might not make sense or anything else, but this doesn't match the MLU documents according to the team, sorry.

So you're saying the 4.2+ handbook has a different process than 3 & 5.1 (which was previously shared here, but now deleted)?

Edited November 6, 2022 by ColinM9991

[SparxOne]

2 hours ago, NineLine said:

I cant answer why it might not make sense or anything else, but this doesn't match the MLU documents according to the team, sorry.

Totally understandable, i am not going against you ED trying to replicate as accuratly what the 16 should be like, as much as i appreciate your precise work on the plane, reality feels weird thinking the guys that created that logic felt it was adequate.
That is all i'm trying to express in this thread

Edited November 6, 2022 by SparxOne

[bukizzzz]

8 hours ago, NineLine said:

I cant answer why it might not make sense or anything else, but this doesn't match the MLU documents according to the team, sorry.

Is there a way we could see the document in question? Considering that people have posted proof of the contrary, you can't just expect from us to take your word for it, no?

 

[hooti]

16 hours ago, NineLine said:

I cant answer why it might not make sense or anything else, but this doesn't match the MLU documents according to the team, sorry.

Hi NineLine, your point is totally understandable, and i can only hope that the people stop discussing based on only a feeling or if something makes sense or not. That is normally not helpful for such evidence based discussions (and this does not only apply for this topic).

The problem in this specific case is, based on publicily available documents (MLU Manuals), we can see how the behavior should look like. We also mentioned the specific page where you can find the description. And this is the reason why its hard to understand that the team refers to MLU manuals and claims that it should look differently. Hopefully this is also understandable from your side. Nevertheless, I also have to admit there is still a small chance that they really changed the behavior from M3 to M4.2 and then back to M5 but to be honest, this time I have a gut feeling here  

Maybe you have the chance to talk to the team again about this topic and have a second look into the manuals or even better, short question to a SME what will happen if you release TMS and there is nothing to lock. Will the ellipse stay slaved to the LOS? 

Thank you!

 

 

 

Edited November 7, 2022 by hooti

[ColinM9991]

40 minutes ago, hooti said:

Maybe you have the chance to talk to the team again about this topic and have a second look into the manuals or even better, short question to a SME what will happen if you release TMS and there is nothing to lock. Will the ellipse stay slaved to the LOS? 

Wags viewed the thread last night and it is now set to "Investigating".

So, fingers crossed that the team is looking at this now.

I agree with your sentiment. It is difficult to believe that 4.2 introduced a very different behavior than what is described in 3 & 5.

[Burt]

Is anybody having issues locking the bandit up in a tight dogfight. I have rebind and used the keyboard command also but it seems that it’s unable to lock for the gun and found myself last night shooting without the computer/target lock which is not a bad thing. It’s not like it’s not working but I don’t remember the Viper having any problem locking on command.

[Tholozor]

If you're using the helmet to try and lock, you now have to hold TMS Up over the target, and the radar will attempt to lock once TMS Up is released.

Edited November 8, 2022 by Tholozor

[Burt]

Ah okay so you must hold TMS up now gotcha I’ll give it a try this evening. Thanks !

[Burt]

Oh my god ! I’m sorry I have been so busy the last few weeks I really haven’t had a chance to go over the new updates. I just looked at the recent one and found this. 
How embrassing. My apologies and thanks again. 
 

geeez
 

[Burt]

Solution solved by Tholozor not me.

Edited November 8, 2022 by Burt

[BIGNEWY]

Hi all

Thank you for your patience here, we do have some changes coming in a future update for this. 

Things did get confusing as we had different people with different sources which were conflicting and reporting parts as broken when they were correct. On the other hand, there were also some valid errors. It’s a good example of why one issue per report is always better. 

The change will be as follows:

You will still need to hold TMS forward to slave the FCR to the HMD LOS (ellipse visible) and release to start acquisition. What was incorrect is that the FCR should have been following the HMD when TMS was held forward, and once released, the FCR should have stayed in acquisition, even if no target was locked.

 

thank you

 

 

 

[609_Relentov]

Also see BIGNEWY's post in the bugs section: 

 

[Sile]

 

[Burt]

Gotcha thanks. Checked it out last night and there seems to be a delay locking but I know it will get fixed.

[LowGlow]

Interesting, a complete new way to acquire a target lock, and nobody has made a video about it yet.

[Reusenfisch]

Still confused…

 

I need to hold TMS to slew the radar to the HMCS. Ok. Is it slewed only for the time I hold TMS?What happens when I release it without a lock? Will it be synced back to the radar boreline indicated in the HUD?
 

Thanks for any further info…