correct as is Delay enabling/Disabling IHADSS after today's update

[Turd Ferguson]

Since the update today there is a delay of a few seconds when I press the button I have mapped to lower/raise the monacle. I was flying the Apache this morning and it was instant as it's been since launch back in March.

 

I didn't see anything in the patch notes for the AH64 relating to this. It's quite annoying now having to wait for it  I've realised since the update how often I did raise and lower it.

[Zarma]

it simulates the movement of the ihdass from the helmet. was already there in VR

[Turd Ferguson]

You're right t was there, but prior to todays update when I pressed the button it would immediately raise/lower the IHADSS now there is a delay of around 2 seconds from the button press to the monacle raising or lowering.

[shagrat]

vor 15 Minuten schrieb Turd Ferguson:

You're right t was there, but prior to todays update when I pressed the button it would immediately raise/lower the IHADSS now there is a delay of around 2 seconds from the button press to the monacle raising or lowering.

Seems they fixed the instantaneous movement and made it more realistic and in line with the action you see in the external view. Raise the hand, move the monocle, Instead of the monocle simply switching on and off instantly.

Edited September 21, 2022 by shagrat

[Turd Ferguson]

Maybe there'll be an animation when the Pilot bodies are introduced of the hand moving it although I tend not to use the pilot bodies tbh.

It was always something I used without even thinking about it whereas now I press the button then am waiting, Albeit only a couple of seconds but it's now something I'm consciously waiting for.

hopefully there'll a least be an option to say if you want the animation/ delay or not.

[Turd Ferguson]

13 hours ago, shagrat said:

Seems they fixed the instantaneous movement and made it more realistic and in line with the action you see in the external view. Raise the hand, move the monocle, Instead of the monocle simply switching on and off instantly.

 

You could also argue that an animation of the pilot/CPG hitting the WAS button would be more "realistic" or that an animation of the Pilot/CPG tapping the buttons on the MPD's is more "realistic" however it would get old pretty quickly if every time a guy with an AK started firing at you, you had to wait for a couple of seconds for a hypothetical animation of the Pilot reaching over and tapping the WAS button to complete before you could use the gun for example. If it was an intentional change and not a bug at least.

This is the only function I've ever come across in any simulator I've played where there is a delay between activating something and it actually happening.

Hopefully something that ED will fix soon

[Floyd1212]

It's a little bit different than your two examples since those require you as the pilot to take a moment to press a button on your joystick, or to look down and use the mouse to press a button in the MPD (or if you have a screen in front of you, for you to reach your finger out and press a button).

Think of it like opening and closing the canopy door; you can map that function to a button on your HOTAS, but it still takes a moment for it to execute in the game.

[BIGNEWY]

Hi, 

the delay matches the animation for enabling or disabling IHADSS, it looks correct to me. 

I will pass on your feedback however

[admiki]

5 hours ago, Turd Ferguson said:

You could also argue that an animation of the pilot/CPG hitting the WAS button would be more "realistic" or that an animation of the Pilot/CPG tapping the buttons on the MPD's is more "realistic" however it would get old pretty quickly if every time a guy with an AK started firing at you, you had to wait for a couple of seconds for a hypothetical animation of the Pilot reaching over and tapping the WAS button to complete before you could use the gun for example. If it was an intentional change and not a bug at least.

This is the only function I've ever come across in any simulator I've played where there is a delay between activating something and it actually happening.

Hopefully something that ED will fix soon

Easy, don't fly with IHADSS up and you won't have any delays.

[Turd Ferguson]

3 hours ago, BIGNEWY said:

Hi, 

the delay matches the animation for enabling or disabling IHADSS, it looks correct to me. 

I will pass on your feedback however

Thanks @BIGNEWY. I'd appreciate you passing it on to the relevant team even an option to enable/disable the sync with the animation would be great.

I see that it matches the animation however when you're flying in the cockpit without a pilots body you're not looking at the animation from the outside.

2 hours ago, admiki said:

Easy, don't fly with IHADSS up and you won't have any delays.

Thank you for your input

[admiki]

33 minutes ago, Turd Ferguson said:

Thank you for your input

You're welcome

[shagrat]

Am 22.9.2022 um 12:41 schrieb Turd Ferguson:

You could also argue that an animation of the pilot/CPG hitting the WAS button would be more "realistic" or that an animation of the Pilot/CPG tapping the buttons on the MPD's is more "realistic" however it would get old pretty quickly if every time a guy with an AK started firing at you, you had to wait for a couple of seconds for a hypothetical animation of the Pilot reaching over and tapping the WAS button to complete before you could use the gun for example. If it was an intentional change and not a bug at least.

This is the only function I've ever come across in any simulator I've played where there is a delay between activating something and it actually happening.

Hopefully something that ED will fix soon

I am not arguing, more describing.

 My guess is, it is a deliberate addition, not a "bug".

George actually does exactly what you describe, for the exact same reason.

You "tell him" (press button via George Menu), to WAS the gun or Hellfires and it takes a second for him to switch and answer.

As for the animation, actually the CPG TEDAC buttons are animated. Just in sync with you touching them.

The difference between buttons on the controls and the IHADSS tube is the motion necessary to let go of the Cyclic, raise your right arm and move the monocle aside.

Edited September 23, 2022 by shagrat

[Turd Ferguson]

8 minutes ago, shagrat said:

I am not arguing, more describing.

 My guess is, it is a deliberate addition, not a "bug".

George actually does exactly what you describe, for the exact same reason.

You "tell him" (press button via George Menu), to WAS the gun or Hellfires and it takes a second for him to switch and answer.

As for the animation, actually the CPG TEDAC buttons are animated. Just in sync with you touching them.

The difference between buttons on the controls and the IHADSS tube is the motion necessary to let go of the Cyclic, raise your right arm and move the monocle aside.

 

From BIGNEWY's reply above it does seem that it was an intentional change and I fully understand that the reason it's been done is to tie in with the animation, however from my perspective i'm not looking at the helicopter from the outside when i'm flying it, I won't enable the piliot's body when that is implemented so an animation is no use whatsoever. I also already move my hand to press the button to raise/lower the Monacle. Not a huge issue just an annoyance that appeared to be a bug tied to the update.

On a positive note though the Apache does seem a lot more stable since the update, my takeoffs are a lot smoother and I've found it a lot easier to transition in an out of a hover which makes my flying appear more skilled than it actually is.

Thanks for taking the time to reply anyway @shagrat

[Swift.]

20 minutes ago, shagrat said:

 

The difference between buttons on the controls and the IHADSS tube is the motion necessary to let go of the Cyclic, raise your right arm and move the monocle aside.

 

I wonder what one should do if they have a button on their own headset for the hiding of the IHADSS? In that case, the motion of letting go of the cyclic and raising your arm is already accounted for by real life. Which means you'll have double the delay ingame!

Obviously I'm deliberately picking a ridiculous point. But hopefully my meaning is clear: extra features like this are fantastic and very much appreciated, but the control over their implementation should be down to the user. If ED can't dictate everyone's physical cockpit set ups, then why should they dictate the way the physical setup interacts with the digital world. It would as if DCS didn't have a way to bind your controls other than the defaults, or if there was no way to tune an axis.

[Turd Ferguson]

On 9/23/2022 at 3:18 PM, Swift. said:

extra features like this are fantastic and very much appreciated, but the control over their implementation should be down to the user.

Exactly this, I am hoping that the ability to disable this hypothetical animation will be implemented. Or someone can tell me if there's a file I can edit to get rid of any delay.