reported Request Repair - Can't

[Caldera]

Hey All,

I got a little sloppy today and lost #1 engine due to ground fire.  I limped back to my FARP an attempted a repair.  I had no luck, it kept telling me that I needed to shut down my engines.  Both engines were shut off and #1 was, of course, dead.  Funny thing is the sound kept playing as if an engine was still running and the oil pressure on #1 engine was initially at 29, but crept up to 43 psi.  I connected to ground power and did not start the APU.

It says failure --> #1 engine failure

At the FARP when I tried to repair.

 

Because I was on ground power I tried to re-start both engines, but only #2 would start.  Notice the oil pressure with #1 engine off and #2 engine at idle.

I am thinking something is not right.  Anyone else have this happen to them?

Caldera

PS: The track file is 34MB.

Edited June 17, 2022 by Caldera

[Varry007]

I've had the EXACT same thing happen yesterday. one engine out (shot).

Landed; shut the bird down; all is of, yet there remains oil pressure in the shot engine; ground crew refuse to repair.

 

 

[Caldera]

Varry,

Thanks for responding.  This sounds like a glitch.

Caldera

[Caldera]

Another one to mull over...

After engine 1 was knocked out I had managed to make it back to my FARP.  This time however I could not get the Chief to hook up ground power, get the ground crew to re-arm or refuel or repair.  Every time I tried I was ignored.

This picture shows engines off, APU off and battery off. 

There is certainly a glitch.  I hope ED takes a look at it before bringing the AH-64D to OpenBeta.

Caldera

Edited June 27, 2022 by Caldera

[ApoNOOB]

Haven't tried this a while, but in previous patches repairs only worked for me after turning off everything including the battery.

Edited June 28, 2022 by ApoNOOB

[104th_Money]

I use the auto stop feature so I dont have to shut everything down manually. I have had issues not shutting down properly when I used a joystick/key bind to move the power levers forward. Using the mouse and doing them individually allows me to use the auto stop. Only then am I able to repair.

I was able to do it by using the joystick/key bind for power levers forward smoothly and even though they were forward I used joystick/key bind to move again then was able to auto stop.

[Caldera]

Same FARP and but a different day.  I had already rearmed / refueled 3 times for the mission.  On the 4th try the ground crew just ignored me.

Caldera

[Scaley]

At present it look like there are a variety of failure modes where one the engines fail but when shutdown does not shutdown cleanly (presumably due to the way the damage is modelled). This leads the DCS crew chief to refuse to do the repair because the engine is still, in some way, "running". Variations have been reported several times, but it seems pretty hard to reliably reproduce. 

[BIGNEWY]

are you running exported displays?

please include a short as possible track replay to show the issue. 

thanks

[Caldera]

Big,

It happened to me again this evening, On the third refuel / rearm attempt the ground crew just ignored me.  To my knowledge I had taken no damage.

12 hours ago, BIGNEWY said:

are you running exported displays?

please include a short as possible track replay to show the issue. 

thanks

If you mean by "exported displays" that I am running more than monitor, then yes I am running two monitors.  I am running the main game one and one for the gunner MPD's.  There are no  mods being used.

As to including a track file... 

I can only recommend that ED changes it maximum file size for *.trk files.  Many times the mission track file is many times greater than 5mb.  I think that it would benefit ED to do so as they are missing out on allot of good information that can not be passed along through this web site.

Is there another way to pass large *.trk files to ED?

Caldera

[BIGNEWY]

4 hours ago, Caldera said:

I am running the main game one and one for the gunner MPD's.  There are no  mods being used.

It is a known issue with exported displays, the team are working on the issue. 

Larger track replays dont tend to be very useful for us, if a longer track needs to be shared using a cloud link like google drive or drop box can be used however. 

thanks

[Caldera]

Big,

OK Thanks!

I tried running the same mission this morning with the same results.  On the third attempt to refuel / rearm the ground crew ignored me.  I then shut down both engines and turned off DC power.  The screen shot below is what things looked like after I did so.  This is the second time I have noticed that the MPD's do not go black and at the same time the ground crew ignores me.

Kind of ruined the mission I had been working so long on...

Caldera

Edited July 2, 2022 by Caldera

[Rabies]

I was unable to run a repair yesterday whilst flying on the Rotorheads server. I lost number two engine. Returned to base and shut down. Ground crew refused to repair, telling me to shut down the engines. I restarted the apu and engine 2 oil psi was showing 20, and there was a faint engine sound that would disappear for a second or two then return. 

I’d been flying for a number of hours so I haven’t even considered uploading the track file.

I’ve also noticed that my Warthog throttles disconnect from their throttle bindings post repair. Prior to restarting the engines, I use the key commands to move the throttles forward which then re syncs my warthog throttles. Any suggestions on how to resolve this?

[FalcoGer]

I don't see what this has to do with display exports. I'm not running display exports and had my engine shot out twice today, both times the status bar on the bottom said 46% RPM even after shutdown. This is an old bug, and I thought it had been fixed. I guess it's a regression.

[al531246]

Still having this issue with the Apache. Had my engine 1 shot out, flew back to FARP. Once I landed and shutdown it said in F2 view the engine was still running! Screenshots below.

[CervO]

The bug exists since like sept 2022. I have had it so many times.

It is systematic when you lost one engine by enemy fire, the engine will not shut down whatever you try to do (all systems off and you can still hear engine running in F2 view) and so the ground crew will refuse to repair asking you to shut down your engines.

To me the most frustrating bug of the Apache, you are glad to make it back to the FARP with one engine and there is no repair possible ... awful  

[Ditch]

I just had this occur. I shut down Gen 1 and 2 and turned off the CMWS and repair worked. Perhaps a fluke idk.

For reference. Needs verification

[Ditch]

OK so even after that, the repair didn't seem to work and Gen1 still out. APU then died and I couldn't get any repair dialog appear, even though ground crew said "Copy" upon request. Massive track here as well sorry so not much help.

Edited June 6, 2024 by Ditch