Dean33

Realair Turbine Duke - keep losing right engine!

Recommended Posts

I have the wonderful Duke installed in V4 using the latest installer.

I have the engine settings set to forgiving so expecting no engine failures.  I've confirmed the configurator is working by fiddling with radio layouts and of course open as Admin.

However carefully I manage the power I keep losing the right engine with a loud bang.  I'm nowhere near the engine limits.  

It is now happening straight after take off but a few days ago it happened three times during a one hour flight.  It does restart but that's not the point!

Can anyone give me any ideas what's going wrong please.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Posted (edited)

Do you have black oil on the engine? like below

07.%20Left%20engine%20out.jpgThe

Duke is very fragile if you let the temperature (ITT) climb too long.

Maybe you have only open the cowl flaps for the left engine.

Just try to check if the temperature of the engines are similar before the bang

 

 

Edited by orangina

Share this post


Link to post

You can turn the failures off.

Share this post


Link to post

I have the failures switched off.

I have changed P3D so engine stress does not cause damage.

I have the oil doors open.

I cannot get this aircraft above 1500 feet without BANG!

Here is screenshot a second before the latest failure. (Temps and oil pressure green).

 2018_3_30_15_49_56_219_2.jpg

Share this post


Link to post

Sorta looks like you are pushing that Duke a bit!  Just looking at the 3rd and 4th set of gauges down that column and the fact you are trying to climb at 2,000 fpm. Strange that only one engine is affected.

Looks like a really great aircraft!

Share this post


Link to post

It can climb at 3000-4000 fpm and I’ve got it throttled back!

Share this post


Link to post

My bet is either a spiking controller axis, or possibly a phantom axis input from another HID controller.  If the mixture axis goes to zero, even momentarily, it'll shut down the engine.  Check your axis assignments in P3D (and in FSUIPC if you use it) and make sure you don't have another controller assigned to the engine axes (throttle/prop/mixture).  If it's a spiking axis, you'll need to clean the contacts, or replace the transducer (usually a pot).

Regards

 

Share this post


Link to post
15 minutes ago, w6kd said:

My bet is either a spiking controller axis, or possibly a phantom axis input from another HID controller.  If the mixture axis goes to zero, even momentarily, it'll shut down the engine.  Check your axis assignments in P3D (and in FSUIPC if you use it) and make sure you don't have another controller assigned to the engine axes (throttle/prop/mixture).  If it's a spiking axis, you'll need to clean the contacts, or replace the transducer (usually a pot).

Regards

 

Oh!  

Next flight I’ll disable and disconnect joystick/throttle and uninstall FSUIPC and try flying with keyboard only - that should be fun!

I’ll check all P3D control assignments too but honestly after rotate and gear and flaps up I’m sat watching for it to fail - without actually doing anything- I think. 

Thanks I’ll report back. 

Share this post


Link to post

You can also use the FSUIPC logging feature to watch the raw values on the mixture axes (you can display them on the title bar, for example) and see if they're moving around when they shouldn't be.

Regards

 

Share this post


Link to post

I did what I planned but found two odd P3D commands. Mouse wheel rapid increase and decrease throttle!  Deleted those and it flew!

logging sounds good. Thanks. I’ll report back. 

Share this post


Link to post

HELP PLEASE  !!

It's not the joystick controller - I disconnected it and flew 'by mouse' and got the same error - right hand engine fails around 1000ft agl.

FSUIPC log shows:

3213828 *** EVENT: Cntrl= 66516 (0x000103d4), Param= 0 (0x00000000) FUEL_SELECTOR_2_OFF

It happens when I'm actually doing nothing - just after gear up generally and I'm watching it climb and waiting for the bang.

But I have no idea why - or what to do about it.

It only ever happens on this aircraft.

Thanks

 

Share this post


Link to post
Posted (edited)

I believe the engine failure is hard wired into the flight model if you exceed certain limits, so turning it off in P3D would have no effect. This us to happen to me when I first started flying the Duke. Are you flying her within these limits for all 3: Keep this values at or below these and see what happens. Also I would turn back on the damage engine mode in P3D. Make sure the oil doors are fully opened. Good luck!

ITT: 750-800° C

NG: 101.5%

Torque: 1250ft-lb

Edited by MartinRex007

Share this post


Link to post

Do you have fuel in the right tank?  Is the right fuel selector on the floor between the seats set to "On"?

Something is sending a command to shut off the right fuel selector...probably code in the panel.  Also, make sure that no key or axis is mis-assigned to the fuel transfer controls in P3D.

Regards

 

Share this post


Link to post
Posted (edited)

Still same problem.

3213828 *** EVENT: Cntrl= 66516 (0x000103d4), Param= 0 (0x00000000) FUEL_SELECTOR_2_OFF

Right engine blows at about 1000 feet.

Yes I have fuel. No there are no commands or keys tied. I am literally sitting on my hands when it blows.

Power is well below minimums. I've reset configuration to Realistic and very low random.

I've watched fuel switches and they don't move.

I've even uninstalled and reinstalled the aircraft.

Any other suggestions how to identify cause of this command? (Please)

Edited by Dean33

Share this post


Link to post

I don't think that this is the same problem, but the TD has previously been reported to also spontaneously lose flight control for no apparent reason. The supposed cause was starting a flight with a previously saved non-default scenario. Doing so may overwrite one or more of the initial values of the aircraft's internal variables.

As a test of your problem, try starting P3d with the default sim scenario and then change the aircraft to the TD.

Share this post


Link to post
Posted (edited)

I'm getting the same problem with the right engine constantly failing without warning. I thought it was me but clearly there is something else going on. I've tried it with an ROC of no more than 700fpm and throttle and rpm well below redlines. I've tried uninstalling and re-installing the updated installer and I have failure switched off yet still it happens.

Not looked into any possible joystick issues and I'm working now until Monday but any advice from the assembled masses on here would be welcome.

"As a test of your problem, try starting P3d with the default sim scenario and then change the aircraft to the TD."

Thanks Jay, I'll try that just as soon as work gets out of the way :angry:

Edited by BrianT

Share this post


Link to post
Posted (edited)

I'm delighted to say I have found a temporary way around this!

1     Start default P3DV4 flight (Raptor at Eglin). 

2     Change aircraft then change location to desired departure point.

Just completed 70 minute flight without problem.

Edited by Dean33
  • Upvote 1

Share this post


Link to post

Yeah, if one starts with a saved scenario, especially one that has been modified by flying the Duke to different airports and saved several times, the initialzation process of key TD variables becomes corrupted.

Unfortunately, the RealAir TD is "out of production" and unless some XML expert can track down the conflict between the P3d scenario file format and the TD gauge coding, this issue is going to persist. I've tried to do so, but so far with no success.

  • Upvote 1

Share this post


Link to post
7 hours ago, Dean33 said:

1     Start default P3DV4 flight (Raptor at Eglin). 

2     Change aircraft then change location to desired departure point.

That's what I always do with every flight any aircraft with the exception of PMDG. My default start scenario has all systems off. I load desired aircraft and then departure location.

Share this post


Link to post

Yeah I always start with a built-in P3D plane at teh airport and spot I want to fly from, then switch to the plane I want to fly after the scenario loads.  A2A recommends that too.

Share this post


Link to post

I’m learning that but I currently believe there is an advantage to actually loading the default Raptor/Eglin flight rather than loading up the Raptor at designed location. 

I may be wrong but having spent 24 hrs frustrated with this problem this is my conclusion.

Share this post


Link to post

Load the default Raptor at Eglin. Then load an existing flight plan that has the desired departure airport. Then answer yes to the  "Move the aircraft ..." question. Flight plan files do not preserve the aircraft state.

I've found that it also works if you load the default scenario, change the aircraft to the TD and save that scenario (still at Eglin) as the new default scenario. Then  just use the flight plan approach described above. 

Share this post


Link to post
Posted (edited)

Well 'm having no luck at all here I loading the default Raptor/Elgin and then switching to the TD and now the left engine blows complete with oil and smoke stain on start up even though I've got failures turned off in the TD config panel. I give up :angry:

 

 

edit....So after a restart of P3d and the loading the default raptor/Elgin and then switching to the TD I am now flying again.a bit too much faffing around if I'm honest but what the hell it's working again yay! thanks for all the tips and advice one and all.

Edited by BrianT

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now