I tried using the mouse click-drag method and got one engine to fire first time, then the other one wouldn't twice. I pulled the throttle back just out of idle (it was a bit more advanced than that at first) and the third time was a charm. Is there a specific throttle position to use?scott s..

No, but it does confirm that the problem is NOT with the aircraft, but with the users system, setup or configuration, and therefore hardly within the developers remit to solve. Whatever happened to personal responsibility? Besides, the configuration is only there as a sop to those who are unable to figure out how to create a cold'n'dark scenario in the sim, and there can't be many of those by now, with all the topics in all the forums available for research? If the config choice doesn't work, create one the `proper` way. It takes less than 19 seconds from start to finish...

Interesting reply Snave. The developer supplied a utility with the aircraft for a cold and dark start. Really simple Snave it either works or it doesn't. Obviously I know how to setup a cold and dark scenario because I replied back that I had setup exactly that. If you can't reply back with constructive data and help, please don't respond at at. Your bad attitude is NOT appreciated here. Anger councilingRealAir, glad to hear a new SP is coming out for the Duke. Looking forward to it. I have logged quite a few hours in the aircraft already and I love it. :)

I tried using the mouse click-drag method and got one engine to fire first time, then the other one wouldn't twice. I pulled the throttle back just out of idle (it was a bit more advanced than that at first) and the third time was a charm. Is there a specific throttle position to use?scott s..

I am using a registered version of FSUIPC (doesn't everybody?) and have set up the throttles to have no reverse zone and have closely sync'ed the lever positions (don't think that matters a whit but there it is). I find that setting the throttles in what would normally be the detent before going into beta range is all that is necessary. The lever movement between the detent and full closed has no effect on throttle position in the sim itself. The click and drag option for the mag switches has never worked for me. I set things up in the config manager to use right and left mouse clicks to move the switches.While I am not sure this has any bearing whatsoever on your question, this is how I have set things up and I get 100% reliable (well all except the time I fouled things up--but I digress :( ) throttle response and 100% trouble free starts. On another point: I set my cold and dark saved flight (basic start point for all later flights) the old fashioned way. Open the FSX default flight with that silly hang glider, change to a default Cessna 172, move the aircraft to parking at the airport of your choice, configure the 172 as you wish (I use 20% fuel load and all switches off), select the Duke and make any further changes you like, save the flight. While this does take a little more than 19 seconds, it doesn't take more than a minute. In addition, I set the Duke config manager to the cold and dark option. Setting things to the C & D option does not affect how you save your flight while in the air.

The advice given by Bill Leaming and Snave is tried and true and is as old as Flightsim itself.As Bill mentioned, the number of variables that are needed for proper sim initialization are set from a default aircraft in 2D cockpit view at a default runway.Attempts to bypass this basic FS "rule of thumb" often send folks off on "wild goose chases" related to starting issues. :(

.... The developer supplied a utility with the aircraft for a cold and dark start. ...RealAir, glad to hear a new SP is coming out for the Duke. Looking forward to it. I have logged quite a few hours in the aircraft already and I love it. :)

In retrospect, maybe we shouldn't have offered this as we did not anticipate the quite varied response of various systems to this feature. If you pop over to the RXP forums you'll see a thread there which appears to reveal there are at least two, if not more, versions of FSX SP2 library files according to how you updated FSX, or which version of FSX you purchased, including Acceleration and what is know as FSX "Gold".There are so many variables within FSX itself which can alter a wide range of what appear to be standard functions. There are also now so many variations in the way different people set up both their systems, graphics and cfg files in FSX and of course many many addons which also alter the way standard things work (for example lighting) that it becomes an increasing nightmare for aircraft developers to establish whether their own features are going to work.There is also increasing pressure on developers to offer ever more sophistication and innovation. For each innovation there is a risk which can lead to a feature offered in good faith giving rise to problems which would not have been there had the feature not been offered in the first place. Thus we are constantly negotiating a maze of variables which even with the most rigorous testing can never accomodate every potential for problems arising.Engine starting is another aspect which can have quite significant variations from system to sytem. Most standard prop aircraft start up far too easily in FSX. That is because the starter torque is set high so there is no possibility you would need two pushes of the starter button. But this makes the engine start too quickly and too easily, so we set the starter torque to as low as we could to give as realisitic as possible engine turning before firing up. But this has led to some systems being unable to start without two or three pushes of the start switch. Another variable is where exactly "zero" throttle is. In real prop aircraft there is not always a guarantee that you'll get a first time start on idle. So as with the real world, we tried to incorporate starting that is not always 100% reliable, except using the standard CTR E which guarantees starting in any FSX aircraft including ours.I use the above to illustrate the tension between the desire to provide realism, and the risks that doing so open up. The more complex a simulation is, the more scope there is for things to go wrong. We are constantly reviewing these things in order to arrive at a compromise between features and reliability.Rob - RealAir

Dont forget to turn on the fuel levers between the seats.

:( The one thing I was missing!!! This step does not appear in any of the manuals (Flying guide or POH) but does in the checklist on the kneeboard!!! Of course the engine will never start if there is no fuel flowing to it! Starts are now reasonably reliable (sometimes needs 2 or 3 very quick turns of the starter though). Thanks much!!!

In retrospect, maybe we shouldn't have offered this as we did not anticipate the quite varied response of various systems to this feature. If you pop over to the RXP forums you'll see a thread there which appears to reveal there are at least two, if not more, versions of FSX SP2 library files according to how you updated FSX, or which version of FSX you purchased, including Acceleration and what is know as FSX "Gold".There are so many variables within FSX itself which can alter a wide range of what appear to be standard functions. There are also now so many variations in the way different people set up both their systems, graphics and cfg files in FSX and of course many many addons which also alter the way standard things work (for example lighting) that it becomes an increasing nightmare for aircraft developers to establish whether their own features are going to work.There is also increasing pressure on developers to offer ever more sophistication and innovation. For each innovation there is a risk which can lead to a feature offered in good faith giving rise to problems which would not have been there had the feature not been offered in the first place. Thus we are constantly negotiating a maze of variables which even with the most rigorous testing can never accomodate every potential for problems arising.Engine starting is another aspect which can have quite significant variations from system to sytem. Most standard prop aircraft start up far too easily in FSX. That is because the starter torque is set high so there is no possibility you would need two pushes of the starter button. But this makes the engine start too quickly and too easily, so we set the starter torque to as low as we could to give as realisitic as possible engine turning before firing up. But this has led to some systems being unable to start without two or three pushes of the start switch. Another variable is where exactly "zero" throttle is. In real prop aircraft there is not always a guarantee that you'll get a first time start on idle. So as with the real world, we tried to incorporate starting that is not always 100% reliable, except using the standard CTR E which guarantees starting in any FSX aircraft including ours.I use the above to illustrate the tension between the desire to provide realism, and the risks that doing so open up. The more complex a simulation is, the more scope there is for things to go wrong. We are constantly reviewing these things in order to arrive at a compromise between features and reliability.Rob - RealAir

Exactly Rob. Seems we are all placed in the "darned if we do" or "darned if we don't" category".At any rate good luck on this and the Duke is an awesome aircraft. :(

On the "sp2 dll issue" I recall Phil Taylor writing that changes were made in Accel, what I remember is sim1.dll, in order to implement the hook/load capability for the helos in Accel.scott s..