R/H engine keeps shutting down!!

[bart]

Ok I have this weird problem. I first noticed it when playing online over the weekend. The right engine keeps shutting down. I first thought it was enemy fire but when it kept happening it was more than a coincidence.

 

I have just been playing a single player mission start on the runway so all systems are as they should be ruling out finger trouble by not switching fuel pumps on etc. which I'm absolutely sure I didn't miss when online. Same thing happened, so I reloaded the mission and started again, same thing!!! shutdown, even when invunrability is switched on so that got rid of the enemy fire thing.

 

Could this have something to do with using a headset? This is the only common factor in this. If I have the sound out of the TV then this doesn't happen, but if I use the headset it occurs.

 

Also you can't do a restart in flight, I tried. Even motoring the engine then going for a restart. You get the engine start sequence caption but nothing else.

 

Anyone else had this happen?

 

My headset is a Creative Fatal1ty.

[Kaiza]

Is it the same mission? It may be triggered as part of the design?

[Tizid]

Which headset? Do you use Makro Buttons?

[bart]

The headset is a Creative FATAL1TY.

 

It happens in different missions. First time was playing online with the 74th vfs, second time was in an offline single player mission, JATAC practice i think.

 

I repeated the missions using the headset and it happens every time. If I dont use the headset all is ok!!!!

[Tizid]

Hmm... no idea. Headset driver already up to date? USB? Try another USB Slot.

[Oznerol256]

What about the positions of the switches and throttles ingame? Are they shown as they should be or is something strange happening e.g. the throttles arent going from off to idle?

[Kaiza]

Can you provide a track file?

[Cedaway]

Are your 'fuel shutoff' switch in good position on your TM Warthog?

[Comrade Vodka]

Sounds like nothing else for it. Drag it in the shed and do a starboard engine change....lol (couldn't resist)

[ENO]

Probably something to do with using an Alienware system. ;)

 

Kidding aside- are you actually saying that you have the right engine running properly, and then it just shuts down? Or that you can't get it to completely start up?

 

 

I may be inclined to go and check your key bindings in the options menu to see if there are some overlaps. For example we started to have this weird bug where hitting the laze / wheel disengage button on the HOTAS was opening our mic switch... perhaps something equally flunkie is happening with whatever software you have running in the background.

 

I've had issues with the APU being stuck at 80 and I can't get my right engine started... but that's its own thing provided your engine starts and then consistently shuts down afterwards.

Edited April 16, 2013 by ENO

[Datajack]

Are you using any voice control software? If so it could be something you're saying is sending a command to the sim that causes an engine shutdown. I had a similar problem some time back and had to go into the voice command profile and correct the issue.

 

Probably not your issue but I thought I'd mention it and cover all the bases.

[Tizid]

Yeah... of course. It also could be your headset itself. Maybe it is too heavy that your head is lying on the throttle of the right engine. :D

 

As said a track file would help.

[bart]

Probably something to do with using an Alienware system. ;)

 

Kidding aside- are you actually saying that you have the right engine running properly, and then it just shuts down? Or that you can't get it to completely start up?

 

 

I may be inclined to go and check your key bindings in the options menu to see if there are some overlaps. For example we started to have this weird bug where hitting the laze / wheel disengage button on the HOTAS was opening our mic switch... perhaps something equally flunkie is happening with whatever software you have running in the background.

 

I've had issues with the APU being stuck at 80 and I can't get my right engine started... but that's its own thing provided your engine starts and then consistently shuts down afterwards.

 

Could be this.....but does the game recognise the headset or is it just your rig that does that?

 

My headset isn't USB, it has the standard green and pink jacks.

 

My headset is left plugged into the computer all the time, when it happens I have enabled the headset to be the Primary playback device by right clicking on the speaker icon bottom right of taskbar and disabling the HDMI output to the tv and enabling the headset. If I then play the game the engine shuts down after say 10 mins airbourne. If I use the TV for the sound and just use the headset as a trackir support.....no problem. This is the only thing I can think of that is causing it as I had no problems up until I got the headset last weekend.

 

Weird huh.......

[mjeh]

Try with a different headset, only way I can think of to rule in or out

[Oznerol256]

This could be some sound driver related problem.

[fmpflyer]

Look in your settings to see if you have birds turned on.

 

I had this setting enabled when I first started playing and nearly everytime I rotated on takeoff one of my engines failed on me. When I put birds down to zero it stopped happening.

[shagrat]

Do you fly straight and level or are you in a dive when this happens? I had some problems with a flameout when diving and quickly decreasing the Throttle to idle! ...and, hmmm, a track file would be helpful :smartass:

[bart]

Do you fly straight and level or are you in a dive when this happens? I had some problems with a flameout when diving and quickly decreasing the Throttle to idle! ...and, hmmm, a track file would be helpful :smartass:

 

Flying straight and level, cruise speed say around 240kts.

 

First indication it's happened is when the attention getter starts flashing and you look at the CWP and the low oil press light is on. Check the engine gauges and its dead!

 

I'll try and get a track file next time it happens but not sure how to save it or upload it here.....not done it before.

 

Update.....

 

Ok It's just happened again. I saved the track at the mission debfief and I now have a .TRK file.

 

Now what?

Edited April 18, 2013 by bart

[shagrat]

if the file is not too big you can attach the file to your post. Look for the usual paper clip symbol. It will open an upload dialog. I know it's annoying to get the trk file and upload it, but it is the best way to check what is going on e.g. clicking wrong buttons, settings, or whatever.

[Hamblue]

you could also get a free file hosting account and post a link here.

One good one is dropbox

[bart]

Ok, the track file is too big to attach to a post....its 7MB so I've uploaded it to mediafire.

 

Hope this helps someone to help me out! The problem occured near the end of the flight.

 

BTW, how do you access .trk files?

 

 

http://www.mediafire.com/download.php?jy38vfj3b0wje9r

[shagrat]

You put them into your Tracks folder in <your profile>/Saved Games/DCS.

Then you can choose replay in the DCS main menu...

Actually it feeds all inputs, into the sim in realtime so ideally the treack reproduces every thing that happened in your mission.

 

Sometimes, especially when fast forwarding, or if there where changes to the sim especially the flight model, it gets out of sync.;)

[shagrat]

Ok, checked your track and it happens for me also. The bad or good news is you do not throwing any weird switches, it is nothing that has to do with cutting the throttle or getting hit (we would have an event in the debriefing for that).

Since we can pretty much rule out errors during start up procedure, as well. Everything by the book!

 

That left me with little left to check... and guess what it seems you got a bird strike! I'm not 100% sure but in the trk file (which is a Zip Archive by the way) there is a /scripts/bird.lua and it seems this is active... I know you DID deactivate birds, deactivate random failures and enforce these settings.

 

But it seems the only reasonable idea.:dunno:

 

I've attached the mission and edited the settings, so the mission enforces 0% birds and deactivates random failures, now.

I know it is boring, but can you try that one and see if it happens again?

 

Right Hand Engine ShutdownTEST.miz

[bart]

Ok, checked your track and it happens for me also. The bad or good news is you do not throwing any weird switches, it is nothing that has to do with cutting the throttle or getting hit (we would have an event in the debriefing for that).

Since we can pretty much rule out errors during start up procedure, as well. Everything by the book!

 

That left me with little left to check... and guess what it seems you got a bird strike! I'm not 100% sure but in the trk file (which is a Zip Archive by the way) there is a /scripts/bird.lua and it seems this is active... I know you DID deactivate birds, deactivate random failures and enforce these settings.

 

But it seems the only reasonable idea.:dunno:

 

 

 

I've attached the mission and edited the settings, so the mission enforces 0% birds and deactivates random failures, now.

I know it is boring, but can you try that one and see if it happens again?

 

[ATTACH]79905[/ATTACH]

 

Thanks for that shagrat :thumbup:

 

 

I've downloaded your test mission and will give it a try.

 

 

I tried something new yesterday which may have worked or it may be a coincidence, I will have to test further but, I tried to do an axis tune within the game on the warthog throttle. I did it on both of them and didn't have a recurrence of the problem, it was just one mission though so more testing is required. I will give your test mission a try and post the results later.

 

Thanks again for your time and help......

[Hamblue]

You should rule out the possibility it's the throttle sending a shutdown command. Try re-mapping so that both engines run off of the left throttle lever. Done in the Axis section. Assign throttle both to the left throttle and unassign the left and right.

 

If it is happening you should also be able to look at the throttle on screen around the time it happens to see if it moves on it's own.