I assumed the RADuke V2 (P3Dv2) was tested using the default P3D startup flight (situation).

 

 

I believe you can make any flight the default start up in P3d. You choose the flight and I think you can tick the "make default" box. You can save the Duke in any situation and make that the default flight too. P3d 2.4 handles turbo prop loading differently from 2.5. You can also save a cold and dark flight then reload if you have any problems. Hope you enjoy the many features the Duke offers and which work flawlessly.

You are correct, Robert. In addition (as I have already pointed out), you can make P3D load the setup menu on startup. My suggestion to Vaughan is to try one of these options.

I believe you can make any flight the default start up in P3d. You choose the flight and I think you can tick the "make default" box. You can save the Duke in any situation and make that the default flight too. P3d 2.4 handles turbo prop loading differently from 2.5. You can also save a cold and dark flight then reload if you have any problems. Hope you enjoy the many features the Duke offers and which work flawlessly.

 

At first I had to take time to re-check my P3D setup ... why am I getting an auto-start by turning the BAT switch on?

What was I doing wrong .. check the manual .. check the Duke's  options, go check FSUIPC ...

 

I assumed the Duke was beta tested using the default P3D flight and other parameters (SDK etc) used by developers..

 

I do not want the Duke as my default flight in P3Dv2,5.

 

Problems with other aircraft could happen if you start messing around with the default flight. Doing custom saved flights etc.

As soon as there is a problem the question asked is what's your default flight ....

 

IMO, it would be better to have the Duke load as selected in the Dukes Options selections, cold and dark .. engines off / all switches off ... cold and dark panel.

 

Lastly, the options selections and manual should explain the cold and dark startup considerations and other special must knows for the Duke as it was designed to operate in P3Dv2.

For years all I've done is use a default GA aircraft like 172 in fsx and now in p3d the maul. Turn engines off set lights, parking break on etc, then save as default.

 

It's no big deal so stop making a big deal out of nothing. Just sent 2 mins and set a default to your liking

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

.. noticed that the RA Duke v2 (P3Dv2.5 hotfix) cold and dark option leaves the Ignition switches in AUTO and the START switches ON after shutdown.

 

So, BAT ON gives a two engine autostart.

 

This doesn't sound right and doesn't work like that for me.

Granted, the Ignition switches are set to 'AUTO' which I believe is a bit strange for a Cold and Dark setup, but the starters are both set to off so, even if you switch the battery on straight away, you shouldn't get an immediate engine start.

 

Sounds like something isn't right in your config or something? I'm sure it's something simple that we can figure out.

Could it be your P3D realism settings?

For years all I've done is use a default GA aircraft like 172 in fsx and now in p3d the maul. Turn engines off set lights, parking break on etc, then save as default.

 

It's no big deal so stop making a big deal out of nothing. Just sent 2 mins and set a default to your liking

 

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

 

With the DukeV2 for P3DV2 I was simply reporting a problem I noticed.

It does not load up cold and dark when selected in the options.

Many panel switches are in the wrong position.

 

With all my sim aircraft ... if they have a special flight situation that they provided that must be loaded first .. fine, no problem.

If they say it only starts with a specific setup ... like Cessna loaded first .... fine, no problem.

Whatever is ok with me.

I am easy going .... been flying sims a long time. I go with the flow.

 

Now, for this auto-engines starting up from a could and dark options selection by turning on the BAT switch ...

I was only reporting a problem that I noticed with a new sim P3Dv2.5 (with its own Hot fix) and an newly developed Duke for P3dV2.

 

No big deal ...

Just reporting something the Duke beta testers may have missed when checking the Duke out with the new P3dv2.5 default startup situation.

This doesn't sound right and doesn't work like that for me.

Granted, the Ignition switches are set to 'AUTO' which I believe is a bit strange for a Cold and Dark setup, but the starters are both set to off so, even if you switch the battery on straight away, you shouldn't get an immediate engine start.

 

Sounds like something isn't right in your config or something? I'm sure it's something simple that we can figure out.

Could it be your P3D realism settings?

 

That is what I was wondering about .. had other pilots had the same problem with the Duke's engines doing an autostart from cold and dark simply by turning on the BAT switch.

 

 

"Sounds like something isn't right in your config or something? I'm sure it's something simple that we can figure out.

Could it be your P3D realism settings?"

 

Sounds good to me:

What in specific should I look for ?

 

Are you using the P3D default F22 at startup?

 

Did you have other switches ON .. like Landing lights or other switches in wrong position e.g. in cold and dark?

 

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

Follow up example:

 

I just recently got the Lionheart LJ24B for FSx/P3dv2

 

Hear is their cold and dark flght info an a warning ... again .. just an example .. Each developer does their own thing ....

 

"These are two different 'Cold and Dark' saved flight files for the LHC LJ24B Learjet.

These are 'Pure' Cold and Dark start files, cold state, all systems off except *Hydraulics.

With these in your sim, you can 'load' these up and your LJ24B will be 'off'.

You can then turn all systems on and fly without issues, with Avionics being 'on', AP able to come on, mixtures proper.

This is because the 'cold and dark' states were created from a 'pure' Running Learjet LJ24B.

If you use a cold and dark from another plane, you will have countless issues with the LJ24B because many of the other planes systems are transferred to the Lear, messing up all of its logic settings and syncs.

Use Pure C/D's only from running flights. Always!"

 

 

Are you using the P3D default F22 at startup?

 

 

OK, I loaded the F22, then immediately the TDuke V2 and the left starter is set to 'on'. This combined with the Auto ignition causes an engine start when the battery is switched on. You're right.

 

I personally have a "Duke" flight saved which is cold and dark and I just load this when I want to fly the duke.

 

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'm sure this has it's own quirks from time to time. The best thing to do is to just have a separate save ready to go. Nothing's ever perfect when it comes to fsx/p3d (...but the TDuke V2 is close )

It's never a good idea to have an addon as your default flight (F22).

 

Use something default like the mooney retro no g1000. It has basic variables much like the default cessna in FSX.

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.

It's never a good idea to have an addon as your default flight (F22).

Use something default like the mooney retro no g1000. It has basic variables much like the default cessna in FSX.

Ryan,

Thanks for the information.

 

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

HI Vonmar,

 

For now we had to make a compromise between P3d 2.4, which lots of people still have, and 2.5.

 

P3d 2.4 has a bug which loads every turbo prop aircraft with the engines off and this happens whatever setting you make and whatever the developer does, so it is not really relevant to compare with a pure jet. In 2.5 you can load turbo props with the engines running and in the same state a previously loaded aircraft is in.

 

I'm guessing that LM have not yet quite sorted this out so it is 100% reliable. I'm not blaming them. I'm just saying that P3d is a constantly developing sim and I don't think it is too bad that we have managed to make 99% of things work perfectly.

 

Regarding what you describe as the "default" flight, there is no such thing in P3d. I guess LM decided, due to many of their clients possibly being military or related organisations, that they felt they wanted to load a military jet by default. That doesn't make it the "default" flight and if anything it probably taxes your system less to load a simpler piston prop aircraft.

 

The Trike or C172 are regarded as "default" flights in FSX but that isn't really true either. In the days when more complex addons took up acres of computer resources it was considered wise to first load up a simple aircraft so as to keep processor load as low as possible. That is not really the case now.

 

What Ebs refers to is that when the Duke loads it tries repeatedly to reset all variables in the sim in an effort to wipe away any preloaded settings. On some systems this works every time and on others it doesn't so well. I apologise if this one aspect is giving you frustration. As another poster points out, you can in a few seconds simply save a flight of your own and the job is done.

 

If you find that you cannot accept this, or enjoy the many hundreds of other features of the Duke that work perfectly, please email me at RealAir and I will try to accommodate you. Thanks.

"I apologise if this one aspect is giving you frustration."

 

You know .. for some reason I cannot get the main point across .. with a new sim and new aircraft .. the cold and dark option is not working.

 

Just reporting the problem.

Nothing more.

I had not seen it reported so I did a post.

 

I (we) do that on all forums with all vendors.

 

That way other pilots will now their setup is not at fault.

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

 

How do I do that? Anyone?

"I apologise if this one aspect is giving you frustration."

 

You know .. for some reason I cannot get the main point across .. with a new sim and new aircraft .. the cold and dark option is not working.

 

Just reporting the problem.

Nothing more.

I had not seen it reported so I did a post.

 

I (we) do that on all forums with all vendors.

 

That way other pilots will now their setup is not at fault.

 

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. Again in Turbo props, in P3d 2.5, and because turbo props take a long time to wind down, you will hear the engines shut down and the props decelerate. Please note BTW that because the cub is a tail dragger the Duke will first load in the same attitude as the cub. A quick press of the slew key twice puts it back where it should be with the nose wheel on the ground.

 

Next I loaded the P38 and started the engines then loaded the Duke with cold and dark set. The Duke loads and the engines and systems are off.

 

Next I loaded the F38 lightning and started the engines. I then loaded the Duke with cold and dark set. It loaded and the engines switched off as did the systems.

 

So on my system it works, and has always worked since we started testing.

 

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!

Robert,

 

"Loaded P3d. Selected the Piper Cub."

 

Ok,

 

Thanks for the information.

 

That is what I failed to do.

 

I just started P3D and selected the Duke.

 

Have a good day.

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.