Airbus H225 engine refuses to stay on

User Support Hub Aircraft & Systems
, , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
When setting up for FLYING, either running on the tarmac or at altitude, the engine just shuts off. So if flying, the helicopter drops straight down.

If applicable, which aircraft is experiencing this issue:
Airbus H225

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Choose AIRBUS H225
  2. Either place in the air or running on the runway (i.e. FLY NOW with runway location)
  3. Watch the blades stop turning

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
Turtle Beach throttle and flight stick

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

Seeing as this doesn’t seem to be a widespread issue as others are successfully flying this a/c I’d suggest it’s either a control binding conflict or you’re doing something wrong. Very unlikely it’s a bug.

3

The H225 has a few known issues. Like pretty much all of the FS2024 plane developers HPG only had an incomplete SDK to work with in the run up to launch. They’ve said there is an update in the works which should hopefully fix some or all of the issues.

4

I can confirm this issue does not exists on my side.

I’m, like @CD0139, thinking that’s a binding issue.
My first reaction would be : are you using thrustmaster quadrant, and you happen to have or turn the engine buttons downs ? These two ones are mapped to a lot of different settings (fuel, starter, electricity, …).

If not, you may have something on one of your input controler that is shutting down something.

Have you tried to start Cold & Dark and try to see when, in the checklist, the aircraft refuses to start or maintain its status ?

Cheers,
K.

5

Moved to User Support Hub that is more appropriate for community support.

6

I used the checklist this time. Step by step. When I enabled the first engine to start, it began to spin up as normal. The N1% ran up to 105%. After about 10 seconds, it all goes quiet. Dead quiet. Like it shut off. The blades don’t spin. Go to the 2nd engine, same thing. It’s like it’s over-revving. I checked all my bindings and I can’t see a conflict. May be a setting is causing this. ?

7

Followed the checklist. Item by item. I enabled the first engine to start, it began to spin up as normal. The N1 ran up to 105%. After about 10 seconds, it all goes quiet. Dead quiet. Like it shut off. The blades don’t spin. Go to the 2nd engine, same thing. It’s like it’s over-revving. I checked all my bindings and I can’t see a conflict. May be a setting ? It’s over revving for some reason. I’m

1 Like
8

Hi @SlickBunny11200, thanks for the response :slight_smile:

I’m starting the H225, following the checklists (LEVEL STANDARD) step by step to see what I get on my side. I’ve gone through the whole “CHECK BEFORE STARTING ENGINE” and made the four first items of the Starting Engine Page :

  • Fuel Pump 1 : ON
  • Fuel Pump 2 : ON
  • Engine 1 Main : Flight
  • Engine 1 N1 : Greater than 50%

My engine 1 start, with the blade spinning. The engine will stay at 105% for 10/15 seconds, then will go back to a solid 76% without me touching anything else. I think this is where our stories differ.

Can you confirm :
1 - The N1 goes down to 0%, or is is just the sound that goes away ?
2 - Blade were spinning during the startup but stopped spinning ?
3 - The rotor brake is not engaged ? (all levers push forward)
4 - You’ve got fuel on board ?

As a reference, here are some photos so you can see what my panel looks like after I started Engine 1. Maybe you can spot a difference.

image
image1920×1140 236 KB

image
image1135×1307 173 KB

image
image1269×970 84 KB

1 Like
9

First- thank you so much for your very detailed response.

I went step by step again- matched your pics. So the pre-start was good as before. Then I set Engine 1 to FLIGHT. The process started.

Airbus H225 Stillshot
Airbus H225 Stillshot637×728 89.5 KB

Once N1 reached 105%- it locked there. It did not drop back. The engine sound stopped. The blades stopped. For fun, I hit SHIFT C to exit the aircraft and witness the blades while standing alongside. They were stopped, but then as I watched them, they began to rotate to full speed. Re-entering the cockpit, the blades stopped again. Same with Engine #2. If I move the Engine switch back from FLT to STOP, it’s dead silent as before, but then you hear the engine sound again as they power down. It’s as though once they hit a certain RPM, they go silent and the blades stop. Shut them off, and as the RPM drops, the sound starts again. This has to be some kind of a bug. That makes no sense.

1 Like
10

That’s definitely something strange, I agree.

Outside help

As I am running out of ideas, I posted a message on HPG’s discord (HPG is the developper of the H225), just to see if anyone as a clue of what’s happening there. Or an idea about what we should try.

I’ll let you know if we have something there :slight_smile:

Community empty ?

In the meantime, can you confirm that you made a try without anything in your community folder ? And with your joysticks / physical inputs disconnected ?

One small detail on your screenshot

There is also something that I see on your screenshot. Your warning leds (at the top of the main cockpit) seems quite different than mine.

This is what I have before I put the engine 1 to FLIGHT

image
image642×444 24 KB

This is what I have during the startup, when N1 = 105%

image
image831×629 47 KB

No changes after normal start (my N1 is back at 76%)

image
image664×398 19.8 KB

This is what I have after I manually stopped the engine 1 after a successful start

image
image544×371 21.8 KB

On your screenshot, both engines are on with a lot of warnings. This is what I have when both engines have started norrmally, without any intervention on button or axises :

image
image582×1094 62.9 KB

So, while your two engine are started, the warning system seems to complain about :

Am I right ?

11

The warning lights were on (and matched your engine off pic) because I took that pic when the engine ‘died’, even though it is showing 105%. I just did this sequence again. It started up fine, and my board matched your board. The blades were turning. All was good. Got to 105%, and sat there running. It did not drop to a lower %. Then I toggled to an outside view, using the external cam, and the blades stopped. I toggled back into the cockpit view, and the engine is dead, but still shows 105%. Now, when I hit SHIFT C, and am standing outside, the blades begin to turn again. SHIFT C back into the cockpit, and they shut down. So this is clearly a conflict somewhere. If I move the engine switch back to STOP, the engine sound returns as it winds down, as if it was running but there was no sound or the blades had stopped.

New experiment. This time I stayed in the cockpit view, and unplugged the throttle (Turtle Beach). Moving it back to FLT, it spins up, sound is good, goes to 105%. I plugged the throttle back in and voila, now it’s dropping back to 76%. The blades are spinning. Both engines. So far so good…

So I toggled to the external cam. Boom. The blades STOP!. This is clearly a conflict with something.

Experiment #2: Setup on a runway already RUNNING. That should eliminate any errors on starting it myself. So I did that- it’s on and running. As soon as I hit Ready to FLY and I am in the cockpit, it shuts off. It immediately dies.

Experiment #3: I unplugged the joystick (Turtle Beach) and just used the mouse. HA!! the engine stayed on, and I went to an external view and it also stayed on. SOOOOO… the culprit is a binding conflict with the joystick. When I plugged it back in, the engine immediately died… Now I need to start defining these bindings. I will let you know what I found.

1 Like
12

An extensive research, I like it. Congratz for your patience, many would have give up a long time ago (and I could’nt blame them).

I hope you’re finding something soon. Please come back if you put your finger on it, I’m curious now (but I can’t afford to buy the TurtleBeach just to dig it myself :stuck_out_tongue: :stuck_out_tongue: :stuck_out_tongue: )

Cheers,
Seb

13

Narrowed it down: With the Turtle Beach -joystick assigned as follows: General controls: VelocityOne Flightdeck Stick 2024 Transversal , Helicopter controls: None and Specific H225-None, the engine WILL run with the joy stick plugged in. It’s all good.

If I leave the General controls unchanged, but change Helicopter controls from None to: VelocityOne Flightdeck Stick 2024 Helicopters, the engines die in 2 seconds. Dead silent. Blades stopped. Go back to None, the blades fire back up, engine fires back up. So the culprit is a binding in that secondary level assignment. There are 16 bindings in that setup. So I am going to start deleting each one and see where the conflict lies…

FOUND IT! There is a wheel on the joystick (Button 25 and Button 26) that has an assignment of ROTOR BRAKE ON and OFF, resp. My wheel was turned to Button 25…hence the engines shut off and the blades stopped. I braked the rotors. Rotating the wheel to 26, ROTOR Brake OFF, it fires right back up.

There is a bust here in the H225 model. Rotating this wheel on and off does NOT move the brake lever in the cockpit. For that matter, with the blades running, pulling the brake towards myself does nothing. So that lever may move but is non-functional, but my assignment wheel dang sure brakes the rotors. The other bug is exiting to walk around. If I enable Button 25, and stop the blades, hit Shift C and am standing outside, the blades begin to spin up. Reentering they spin down again. Rotating back to Button 26, they spin up.

So there it is. Thank for all your help…

1 Like
14

I use the TB FlightStick. I’m on Xbox X so the H225 usually causes a CTD after a few minutes (known Xbox H225 issue) but I have managed one 30 minute flight with no issues and a few shorter flights before the inevitable CTD.

15

Wow. Congratz for your extensive research and your findings. I’m going to pass the good news over to HPG.

Enjoy flying the H225, it’s still in its early phase (updates will be pushed later, I’ve been told) but so far I loved flying it :slight_smile: