Problem starting the right engine since the last hot fix patch.

[Thunderchief2000]

Hi, is anyone else having a problem with starting the right engine?
 

since the mini patch (although it is a bit random so it might have been the patch before) both in my own missions and in the new Mad campaign. The right engine does not start.  However some times it does. 
 

my method, 

battery on

apu on

check throttles to cut off (I use a warthog throttle for the left and right engines)

Press the start on the left engine, engage idle at 20percent.  Engine starts fine

press the start on the right engine, engage idle at 20percent, engine rises to 50percent and the starter clicks off as normal, but then the engine just starts to die. Never getting above 55percent.  
 

however some times it works fine, at least in my own missions.

let me know if I’m doing some thing wrong.

 

cheers.

 

 

 

 

 

 

[sirrah]

I saw a similar report on the new Stone Sky campaign sub forum, with this "temporary" solution:

Please try the following: after starting engine 1, throttle it up to flight mode from idle.
Then start engine 2. It should start OK.

 

(Haven't been able to test/try for myself yet)

I'm sure ED will fix the issue soon.

 

[Thunderchief2000]

1 minute ago, sirrah said:

I saw a similar report on the new Stone Sky campaign sub forum, with this "temporary" solution:

Please try the following: after starting engine 1, throttle it up to flight mode from idle.
Then start engine 2. It should start OK.

 

(Haven't been able to test/try for myself yet)

I'm sure ED will fix the issue soon.

 

Thanks I will give it a try

 

[docWilly]

No you are not doing anything wrong. This issue is at least since latest big update (on Beta) - if you search the forum you will find older reports of that as well - it was cured and is now introduced again. What the older reports suggest (like collective is not detected as 0 seems not valid, so don´t fiddle around with setting axis or deadzone. Tested does not work.
What works is during the startup of Nr2: bring the power lever Nr 2 out of idle until ng passes the "magic" 52%. This of course is not per manual and clearly a bug.
Others raise the collective (which triggers warnings) until Ng passes 52%. Others do what sirrah posted.All is only a workaround to get it in the air.

I am surprised not to find more reports on that because we (on a MP server) have it regularily now. Maybe ppl mostly have hotstarted aircraft
And now.... no track dear ED stuff. Why.....it does not occur every time so it´s hard to track.
Hopefully someone has ist recorded...

 

Edited January 28, 2023 by docWilly

[kotor633]

So I haven't had this problem before. What I noticed yesterday when I started playing the MAD AH-64d campaign: I'm doing a cold start. And it doesn't matter whether I activate the battery or via ground current: When I press a button, the IHADSS is not activated. I'm following the startup procedure step-by-step as described in Chuck's Guide (Primary Cockpit Lights CTRL Knob is set to BRT). I finished the campaign and created a mission using the mission editor quick and dirty. And tried the same thing again as described above. With the same result. Then DCS terminated and restarted. After that, this phenomenon did not occur. Will keep watching.

[docWilly]

2 minutes ago, kotor633 said:

So I haven't had this problem before. What I noticed yesterday when I started playing the MAD AH-64d campaign: I'm doing a cold start. And it doesn't matter whether I activate the battery or via ground current: When I press a button, the IHADSS is not activated. I'm following the startup procedure step-by-step as described in Chuck's Guide (Primary Cockpit Lights CTRL Knob is set to BRT). I finished the campaign and created a mission using the mission editor quick and dirty. And tried the same thing again as described above. With the same result. Then DCS terminated and restarted. After that, this phenomenon did not occur. Will keep watching.

Now this is something else then the turbine Nr2 problem

[corbu1]

Doesn’t have problems starting the engines after recently OB Patch. Both engines start fine for me.

[Thunderchief2000]

16 minutes ago, sirrah said:

I saw a similar report on the new Stone Sky campaign sub forum, with this "temporary" solution:

Please try the following: after starting engine 1, throttle it up to flight mode from idle.
Then start engine 2. It should start OK.

 

(Haven't been able to test/try for myself yet)

I'm sure ED will fix the issue soon.

 

Just tried this and it works for the first mission of the mad campaign.

I noticed that I was wrong in my first post, in the mad campaign, when starting the right engine, the percent does not go above 45, so the starter never turns off.

well this work around will keep me going for now anyway.

cheers.

 

 

8 minutes ago, corbu1 said:

Doesn’t have problems starting the engines after recently OB Patch. Both engines start fine for me.

I think it might have to do with weather conditions of the mission, do you have the mad campaign?  If so try the first mission.

[docWilly]

Marked as solved??? Not really.  And it´s not dependent by weather.

 

[sirrah]

54 minutes ago, docWilly said:

Marked as solved??? Not really.  And it´s not dependent by weather.

 

The green forum "solved" mark, does not mean the bug is fixed, but only that the OP's question is answered (in this case with a temporary workaround) 

 

ED's official thread marks (e.g. "reported", "can't reproduce", "track file missing", etc.) look like this:

Edited January 28, 2023 by sirrah

[corbu1]

vor 7 Stunden schrieb Thunderchief2000:

 

I think it might have to do with weather conditions of the mission, do you have the mad campaign?  If so try the first mission.

Yes, I have the MAD AH64 campaign, but not played yet. Will check it tomorrow.

[admiki]

8 hours ago, Thunderchief2000 said:

Hi, is anyone else having a problem with starting the right engine?
 

since the mini patch (although it is a bit random so it might have been the patch before) both in my own missions and in the new Mad campaign. The right engine does not start.  However some times it does. 
 

my method, 

battery on

apu on

check throttles to cut off (I use a warthog throttle for the left and right engines)

Press the start on the left engine, engage idle at 20percent.  Engine starts fine

press the start on the right engine, engage idle at 20percent, engine rises to 50percent and the starter clicks off as normal, but then the engine just starts to die. Never getting above 55percent.  
 

however some times it works fine, at least in my own missions.

let me know if I’m doing some thing wrong.

 

cheers.

 

 

 

 

 

 

Can you post track file for your mission? I have tested it multiple times and had no issues. I even tried that old bug where left pedal would prevent engine start, but engine started just fine.

[sirrah]

16 minutes ago, admiki said:

Can you post track file for your mission? I have tested it multiple times and had no issues. I even tried that old bug where left pedal would prevent engine start, but engine started just fine.

Apparently it only happens under certain specific weather conditions.

(Haven't had the chance to test myself)

[Ourorborus]

Experienced this for the first time tonight. It had the added bug that in Multiplayer, the CPG got good indications of solid engine start while pilot couldn't start no2.

Then tried starting engines before CPG joined. Engine started (slowly) but CPG had Massive disconnect when joining after engine start. Indications of rotor brake on low rotr rpm, the works.

 

 

[FalcoGer]

Had this a couple of times. Also had a few instances of desync, even on self hosted hunting grounds. Pushing the throttles just slightly above idle during start seems to work, but might have been coincidence (small sample size). But that approach had the CPG's engine die while the PLT's engine did what was expected, leading to some massive desync issues, including power failure in flight due to over-torque (230%+) and subsequent INS reset, etc. I should have the track, but the issue happened during the second flight and that's like an hour in, and the track is huge anyway because it's hunting grounds with a lot of voice messages.

Also would be nice if this were moved to bugs.

[codyj007]

This bug is not fixed or solved in any way. Can ED mark this as reported please?

[sirrah]

1 hour ago, codyj007 said:

This bug is not fixed or solved in any way. Can ED mark this as reported please?

Ed is aware of the issue and it has been marked "reported" in this old thread:

 

[codyj007]

9 hours ago, sirrah said:

Ed is aware of the issue and it has been marked "reported" in this old thread:

 

thanks

[admiki]

On 1/28/2023 at 8:35 PM, sirrah said:

Apparently it only happens under certain specific weather conditions.

(Haven't had the chance to test myself)

that's why I would like track file

[Moxica]

7 minutes ago, admiki said:

that's why I would like track file

Try running "Mountain coin"

[Moxica]

Any news?
-Because, now it is affecting the MAD AH-64D Campaign by Stone Sky as well.

On 1/28/2023 at 11:44 AM, sirrah said:

I saw a similar report on the new Stone Sky campaign sub forum, with this "temporary" solution:

Please try the following: after starting engine 1, throttle it up to flight mode from idle.
Then start engine 2. It should start OK.

 

(Haven't been able to test/try for myself yet)

I'm sure ED will fix the issue soon.

 

Sounds like me trying to start my old Volvo 144 1974 model back in the 90's

[AdrianL]

1 hour ago, Moxica said:

Any news?

Next patch is only on 1 Match so you going to have to wait till then, at least.

[FalcoGer]

A work around is to ask your CPG if the engine is running or not. If either pilot gets a bad start then shut down and communicate that Ng is 0%, then try another start. Repeat until both pilots report a good start. It's fiddly, but at least you can get in the air.

Although officially not allowed, dual starting seems to also make a good start more likely, although again, sample size is somewhat small. Can't draw any conclusive data from a couple dozen start attempts.

Would really like a hotfix though, it is rather annoying and happens very frequently. Not being able to start your aircraft is kind of a big deal. Just my opinion though.

[Yurgon]

When I first saw this, I thought it might have to do with air temperature or wind, but since then I've seen a few failed engine start attempts at some of the most standard atmospheric conditions. Looks kind of random to me.

[Wizard1393]

I've had this issue multiple times recently. For me it has seemed to help to:

 

• Spawn into cockpit
• Move your collective axis up to max and then back down to 0/min
• Proceed with normal start procedure

EDIT: Doesn't seem to do it every time, so that's probably not it then.

Edited February 12, 2023 by Wizard1393