Just to be clear.......I want to be able to load the Turbine Duke with the engines running in P3D v2.4. I assume that I can do this, even if I have to switch the engines on first, and then save?

Robert,

Had my right engine go down today, with out writing a book about, simply amazing at the work you have put into this, this would only show up when on one engine, the wind over the air frame the pulling and pushing, the plane sliping.

I got her down and it left me with a huge grim on my face and felt like a beer having got though it. YD was the main culprit, how you moulded all that in is amazing.

 

Thank you for an amazing aircraft.

 

Our pleasure.

Just to be clear.......I want to be able to load the Turbine Duke with the engines running in P3D v2.4. I assume that I can do this, even if I have to switch the engines on first, and then save?

I think this is so. What I do know is that P3d 2.4 loads all turbo prop aircraft with the impression that the engines are working if the previous aircraft was running, but in fact the engines die. This has been fixed by LM in P3d 2.5. I do recall saving a flight with the Duke and other turbo props in 2.4 and this seems to overcome the bug if you reload the saved flights, but I am not absolutely sure.

Robert,

Í had a chance later this evening to review your post (#118):

"Well, it works for me and I just tested it:
Loaded P3d. Selected the Piper Cub. Started engine. Place it at a small airfield in the UK. Then loaded the Duke having selected the cold and dark option. The Duke loads and the engines die."

 

"I don't know why it is not working for you. Maybe your options are not being saved (best to run the config app as administrator). Yes you did report what you think is a bug, but also complained that we should explain in detail about the cold and dark setting. There's nothing much to explain though. It is a simple setting, either engines running or engines/system not running. I can't see what extra explanation is needed!"

***********************

That also works for me.

When I start P3Dv2.5 (default P3D program start situation) then load the Duke its engines do shut down ok.


********

But that was not what I seen as a problem with the Duke's cold and dark Option.


The problem I am talking about here and initially posted (post #97) is:

"I notice:
If the RealAir DukeV2 in P3Dv2.5 (hot fix) is cold and dark .. then BAT ON .. both engines do an autostart.
This does not happen in FSX .. there I get to manually start each engine .... which is what to do.

****

It is the entire aircraft (including the panels engine start switches / landing light e.g.) that are not in the cold and dark cockpit state.

Thus, when the BAT switch is turned on, both engines immediately do an autostart (spool up start sequence).

 

 

I use the Trike in FSX engines running and the DukeV2 loads up cold and dark just fine.

 

 

Hi - Not a good idea to use the trike for default saved flight.  This is because it lacks some standard FSX features (such as a fuel selector) which means that when you load a complex aircraft after the trike, some of those features may not be set correctly.  Something like the C172 (for FSX) or the A36 or Maule (for P3D) are better to use as a safe, default saved flight.    Cheers.

Craig,
"Hi - Not a good idea to use the trike for default saved flight."



Yes, I do know what you mean.

I had a different FSX startup situation aircraft until ... there were problems reported by pilots using FSX addon aircraft.

Anyway, Flight One came up with a solution at some point in time.


So, years ago I started using "The Safe Startup for Complex Aircraft" for FSX.

Available here:
http://www.flight1software.com/files/FSXSafeStartup.exe


I have never had any problems with any addon aircraft.
And, I have not heard of pilots complaints about using it.
So, maybe I should not have mentioned Trike but rather the FSX Safe Startup for Complex Aircraft by Flight One.

Thanks for the follow up.

Have a good day.




 

 

The problem I am talking about here and initially posted (post #97) is:

 

"I notice:

If the RealAir DukeV2 in P3Dv2.5 (hot fix) is cold and dark .. then BAT ON .. both engines do an autostart.

This does not happen in FSX .. there I get to manually start each engine .... which is what to do.

 

 

Thanks for your demonstration video. This is most definitely a bug in P3d, not in the Duke. The battery on switch does not provoke a false engine start after loading it with other piston prop aircraft. But it does happen if the last aircraft you loaded was the F22, and for all I know other jets. That means the F22 and possibly other P3d aircraft are adding variables unknown to us, and which we cannot reset unless we know what they are.

 

When you load the Duke cold and dark, as I described earlier, it attempts to reset all known variables to zero in order to provide a clean variable state so the Duke can implement its own variables. It doesn't do this once, but many times repeatedly, so as to give the maximum chance of clearing whatever is in memory. The SDK gives no clues as to why the variables are differing between prop aircraft and jet aircraft, so we can only work with what we know.

 

I have no doubt that in time LM will gradually iron out this, and many other anomalies which cause minor inconvenience or minor problems for the user.

 

We will be gathering a list of other minor issues and suggestions and sending them to the P3d team, but we are giving them a chance to address some of their own known problems with 2.5 and the hotfixes issued so far. But from my feedback so far, LM are well aware that things are not perfect and I am very impressed by the way their team is steadily and openly working on them, in a way that MS never did.

 

As I said before, the F22 is not a "default" aircraft. It just happens to be the one that LM chooses to load, but as you know you can choose any aircraft you wish as the start up vehicle. At least from what I am looking at, simply loading as your "default" a prop aeroplane like the cub, which is a good choice because it is light on resources, you should find the battery switch on the Duke does not cause a turbine start up.

 

Please also note that a lot of anomolies in P3d, going back since 2.4 and possibly before, seem to be exclusively affecting turbo prop aircraft. We have done our best to overcome these. 

 

A guaranteed way of loading the Duke in the state you wish, in the meantime, is to simply save whatever state you wish to be reloaded at any time later. It takes about 5 seconds to save.

 

I hope that, for the time being, finally answers all of your posts about this subject, and you can enjoy the Duke for the other 99% of trouble free qualities that it possesses.

Thanks for your demonstration video. This is most definitely a bug in P3d, not in the Duke. The battery on switch does not provoke a false engine start after loading it with other piston prop aircraft. 

 

Thanks for confirming a bug in P3Dv2.5 (with hotfix-1).

 

I initially thought you tested with a default P3Dv2.5 installation. That was the reason for my first post.

 

I am doing all my scenery and new addon aircraft(s) installations / setups with the default P3Dv2.5 installation.

 

I have found problems with other aircraft as well .. Like the Lionheart LJ24B e.g. .. has no Night time VC lighting .. The developer also told me the next P3D hot fix should correct it.

 

It will take a while for P3D to shake out all their bug.

 

We just need to find them all (the bugs) and report them back to LM P3D for them to fix.

 

The Dukes .. I have several ... really enjoy them all.

Hi Robert

 

Could you please answer this Q of mine?

 

I want to move the VC Wood panel from Duke Turbine V2 N710DS to another. to DNSYR

 

How do I do that?

 

I managed to do this for the regular Duke. I don't believe I could do the same here. for the Turbine Duke V2.

Neil,

 

Thanks for confirming that the P3Dv2.5 settings are ok.

 

"My understanding is that for 'cold and dark' the duke loads and repeatedly 'spams' the simulator (fsx or P3D) with the 'cold and dark' state"

 

I do not know anything about that .. how it is done by developer.

 

Like I said .... just reporting the problem I seen ... The DukeV2 P3Dv2 cold and dark start up configuration option does not work.

 

Ryan,

Thanks for the information.

 

Do you know which aircraft the DukeTurbinev2 (P3D) was tested with?

Well I know of this one guy who tested it with the default retro mooney lol

Hi Robert

 

Could you please answer this Q of mine?

 

I want to move the VC Wood panel from Duke Turbine V2 N710DS to another. to DNSYR

 

How do I do that?

 

I managed to do this for the regular Duke. I don't believe I could do the same here. for the Turbine Duke V2.

 

Please can you email Sean at RealAir support for this, quoting your order number. It is too involved to discuss in a forum. Thank you.

Hi - Not a good idea to use the trike for default saved flight. This is because it lacks some standard FSX features (such as a fuel selector) which means that when you load a complex aircraft after the trike, some of those features may not be set correctly. Something like the C172 (for FSX) or the A36 or Maule (for P3D) are better to use as a safe, default saved flight. Cheers.

Like you I use the Maule in P3d set everything up for cold and dark. Save and make default.

It really is that simple. An F22 is never a good idea as a Default just like the trike was a bad one(C172 for me was the perfect one).

A huge fuse over nothing that a simple common sense cold are dark set up sorts out.

I apologize if this is the wrong thread; I don't see an "unofficial Duke Turbine" forum.

Purchased the Duke a few days ago. I haven't tested the aircraft fully and with the numerous hotfix from P3D, this may be a premature inquiry.

 

On startup, when I click the battery on, I get a quick series of beeps, the "wait blue circle" and thrown out of the active sim window. The sim window is still there, but in the background. I then click back in and can proceed as normal.

 

Just not sure what that is.

Hi Mario,

 

We offer email support and reply very quickly. Please email me with your order number for support. Meantime, the bleeps should be there and are standard engine warnings on the Duke T. However I doubt the "wait blue circle" is a Duke-specific issue. It doesn't happen here in P3d 2.5 and maybe the hotfixes are not quite perfect yet..

Thanks for the fast response!

I will email you from home when able.

I love my new turbine Duke v2 for P3d, but as soon as I patched P3d to xx44, I have my two GTNs but no ADF OR AUTOPILOT.

Reset Duke config and moved things around the put the GNSs and AP/ADF combo where I wanted them (same as before) and saved.

 

...rebooted...reloaded P3d..

 

therrrrre hearrrrrrrrr...grin

 

Thanks

Chas