user resolved what just happened?

[71st_Mastiff]

I'm flying to a point and the machine (Apache) just shut off and crashed?

Logs12142025.rar

 

https://www.mediafire.com/file/u8bl09m2un0wt7b/SYRIA_TPE_v1_RUN1-20250110-114542.rar/file

 

 

 

Edited January 11 by 71st_Mastiff

[MAXsenna]

I'm flying to a point and the machine just shut off and crashed?
Logs12142025.rar
 
https://www.mediafire.com/file/u8bl09m2un0wt7b/SYRIA_TPE_v1_RUN1-20250110-114542.rar/file
 
 
 

Tracks are better.

Sent from my SM-A536B using Tapatalk

[Floyd1212]

I think he is saying his computer crashed out of nowhere, and is asking (demanding?) for help interpreting the error logs?

If indeed his engines cut out and his Apache crashed into the ground, then yes, a track file would probably be better.

[MAXsenna]

I think he is saying his computer crashed out of nowhere, and is asking (demanding?) for help interpreting the error logs?
If indeed his engines cut out and his Apache crashed into the ground, then yes, a track file would probably be better.

I'm dumb. I read machine = Apache!

Sent from my SM-A536B using Tapatalk

[71st_Mastiff]

the apache crashed engines shut down and dropped out of the sky, the tracks are right there in the downloads.

 

2 hours ago, Floyd1212 said:

I think he is saying his computer crashed out of nowhere, and is asking (demanding?) for help interpreting the error logs?

If indeed his engines cut out and his Apache crashed into the ground, then yes, a track file would probably be better.

 

2 hours ago, MAXsenna said:

Tracks are better.

Sent from my SM-A536B using Tapatalk
 

well if you bothered to look at the media link that's where the trak is. 52mb; ED doesnt allow any bigger and Rar files really don't compress but 1bit.

2 hours ago, Floyd1212 said:

I think he is saying his computer crashed out of nowhere, and is asking (demanding?) for help interpreting the error logs?

If indeed his engines cut out and his Apache crashed into the ground, then yes, a track file would probably be better.

negative Max Sena was right the 1st time. Machine = Apache. 

I wouldn't have posted it here; if it was Computer related.

Edited January 11 by 71st_Mastiff

[Floyd1212]

Ok. It wasn’t clear, especially with the word “Logs” in the filename, but I get it.

How far into the flight does this happen?

[flanker0ne]

I tried to load the track twice. It gives me Mission Load Fail

[71st_Mastiff]

13 minutes ago, Floyd1212 said:

Ok. It wasn’t clear, especially with the word “Logs” in the filename, but I get it.

How far into the flight does this happen?

at the end.

12 minutes ago, flanker0ne said:

I tried to load the track twice. It gives me Mission Load Fail

not sure I'll try it and see if the same. try in VR. 

lol traks are broken in this version I guess non work for me. all show failed to load.

Edited January 11 by 71st_Mastiff

[flanker0ne]

Try to check the bindings, maybe the cutoffs off the throttles is not well set, like replicated ecc

Or if you use an analog axis, some dirt signals, aka spikes, are coming

[MAXsenna]

@71st_Mastiff Apologies! I'm on my cell and Tapatalk doesn't like/show complete links, while I should have understood it was a track.
Cheers!

Sent from my SM-A536B using Tapatalk
 

Edited January 11 by MAXsenna

[Lord Vader]

Hello @71st_Mastiff

Lots of things can happen to cause engine shutdown. A double engine shutdown sounds (just sounds) like a fuel problem. We've seen a lot of instances when, for example, users don't check the fuel and don't notice the AUX fuel tank isn't activated, for example. 

Of course, we would need to see it happening but your track fails to load.

We don't have any other recent reports of a sudden engine shutdown, unless caused by planning error (mostly fuel) or damage.
If you ever have this event again, please report it with just a track. 

[71st_Mastiff]

On 1/13/2025 at 4:00 AM, Lord Vader said:

Hello @71st_Mastiff

Lots of things can happen to cause engine shutdown. A double engine shutdown sounds (just sounds) like a fuel problem. We've seen a lot of instances when, for example, users don't check the fuel and don't notice the AUX fuel tank isn't activated, for example. 

Of course, we would need to see it happening but your track fails to load.

We don't have any other recent reports of a sudden engine shutdown, unless caused by planning error (mostly fuel) or damage.
If you ever have this event again, please report it with just a track. 

Well, it wasn't poor fuel, I just spawned in the throttles where spooled up for only 1 m/s; I cut back no other betty issues popped up or engines ill-sounds, I took off and with in 10 minutes of flight no warning no betty warnings and no system warnings; just shut off and fell. So I'm going to say engines over speed? even on micro seconds seems to be an issue with the module.

and needs to be looked at.

[Lord Vader]

Again, we don't have sudden engine shutdown out of the blue events being reported. Aside from the already mentioned fuel starving events, key bindings or "noisy" axis or even damage explains some of the engine loss issues we've seen. 

However, in order to actually see what's going on, we do need a working short track. Please try a simple mission, perhaps a Instant Action mission in Caucasus and if you reproduce it, send us that track and we will certainly look at it. 

[Leg2ion]

Hi All, @Lord Vader

Bizarrely read this and then had same happen to me in last mission. I was lined up on some training targets, and selected my modifier key and Switch 11 on my TM WH HOTAS grip (forgetting I had remapped the pilots sight select switches to elsewhere - so that key press combination is not in my current control configuration) - and had both engines cut with a pretty rapid nose dive as a result.

Restarted a new mission, and pressed same whilst hot on the ground, same effect. As I was on the ground re-accelerated the engines, and then could not repeat with same key presses?

Both tracks attached.

Eng Off.trk Eng Off2.trk

[BIGNEWY]

Hi 

We've analysed your tracks and indeed it seems you cut-off your engines while flying in the first track. On the second one, the cut-off levers are pulled all the way back right on the start.
Both instances seem to indicate that you may have an axis or button in conflict. 
Can you confirm you don't have any more axis or buttons assigned to cut-off? If so, can you try to move your controls lua file in Saved Games\DCS World\Config\Input\AH-64D_BLK_II_PLT\joystick and rebind your keys? You can then move the file back if the problem persists.

thank you 

[Leg2ion]

Hi @BIGNEWY

Think I've got to the bottom of it. I have the pinky lever on the cyclic grip assigned as a modifier, and the increase/decrease slider on the throttle unit assigned as the throttle power control coupled with the modifier (to prevent unwanted throttle inputs - doh!). The button 11 is a red herring, and was purely co-incidental as I selected that at the same time I pulled the pinky lever.

When I flew a previous mission, I did a shutdown etc, with the power levers (increase/decrease slider) left in the off position. This mission - I started hot, so in game the power levers are forward, on my WH throttle the slider is in the aft position. When then I select the modifier button, and the slider is aft, the in game throttle then moves to adopt the position of the slider, regardless of any input to the slider itself. Created a new joystick file and exactly the same happens.

Question is - is there any way of preventing that happening, as in mind the throttle should stay where it is as I am not creating any input into the slider, just depressing the pinky lever modifier? That would also explain why I couldn't repeat it, as to recover I throttled up using the slider, so then were synched with both being forward. Not insurmountable if not - just make sure I check the position from now on...

 

[MAXsenna]

54 minutes ago, Leg2ion said:

ncrease/decrease slider on the throttle unit assigned as the throttle power control coupled with the modifier (to prevent unwanted throttle inputs -

Have you set it up as a slider in the axis tuning? 

Never mind, I see what's happening now. And that's how it's supposed to be. 

56 minutes ago, Leg2ion said:

This mission - I started hot, so in game the power levers are forward, on my WH throttle the slider is in the aft position. When then I select the modifier button, and the slider is aft, the in game throttle then moves to adopt the position of the slider, regardless of any input to the slider itself. Created a new joystick file and exactly the same happens.

I'm sorry, I don't intend to sound harsh. Why do you expect a different result? Your physical controllers controls the virtual controls in the sim. I'd be seriously frustrated if it didn't work like this. Check the "sync HOTAS at mission start" checkbox in the General Settings, and make hot start checklist for your physical peripherals. That's the answer to your last paragraph. To prevent it happening, make sure physical positions are set correctly.

Cheers! 

[ShuRugal]

1 hour ago, Leg2ion said:

is there any way of preventing that happening, as in mind the throttle should stay where it is as I am not creating any input into the slider, just depressing the pinky lever modifier?

Check your control bindings, and unbind the pinky lever axis from the throttles.

[Leg2ion]

1 hour ago, MAXsenna said:

I'm sorry, I don't intend to sound harsh.

I asked a question - bignewy was kind enough to give a steer, which then set me in the right track to replicate it and then suss out what was happening and why. What I don't like is the 'what do you expect' kinda answer like I should have known (that is why I asked for help and asked the question!) - as a lot of strange things happen in DCS due to the variety and complexity of individuals differing hardware and software set ups. 

I guess I was thinking that regardless of where the slider was, it would stay unaltered until I interacted with it, also coupled with the fact I (purely by co-incidence) made a button press at the same time. Sorry but where I have some switches mapped to say lights or similar - when I fire the aircraft up, if they are in the on position they don't automatically turn the lights on, having to cycle off then back to the on position - so would it be unreasonable to think similar in this instance?

But thanks anyway! Cheers!

1 hour ago, ShuRugal said:

Check your control bindings, and unbind the pinky lever axis from the throttles.

Yep - done! Quickest way - and TBH not sure why I added a modifier to it in the first place - must have been a good idea at the time!

Edited March 10 by Leg2ion

[Leg2ion]

On 3/10/2025 at 8:38 PM, MAXsenna said:

Your physical controllers controls the virtual controls in the sim. I'd be seriously frustrated if it didn't work like this.

Hi @MAXsenna - one final update. I have just swapped my original TM Warthog stick base for an Ava base. With the new base I do not get the same issues - so all key binds and modifiers the same - no issues - so whether there was some sort of conflict - or my new base is now not working as it should...? 

[MAXsenna]

4 minutes ago, Leg2ion said:

Hi @MAXsenna - one final update. I have just swapped my original TM Warthog stick base for an Ava base. With the new base I do not get the same issues - so all key binds and modifiers the same - no issues - so whether there was some sort of conflict - or my new base is now not working as it should...? 

Ah, the marvelous wonders of computer tech!
Happy for you!
Now, start saving for an FFB base!  

Sent from my SM-A536B using Tapatalk
 

Edited March 22 by MAXsenna

[Leg2ion]

Just now, MAXsenna said:

Ah, the marvelous wonders of computer tech!

Got a few other 'choice words'!!