Bryan,First, I have to say I'm impressed with the amount of detail included and the amount of integration in 4100 version. I'm having issues with a few commands and operations, but I think that's more on my end (I ran the voice tutorial, but haven't properly "taught" my machine to understand me). All that aside, there's one issue that has me stumped.Running through the tutorial/manual flight, I'm running into issues when I go to start an engine. My props are unfeathered and on the locks, but when I command the engine start, I get a response that the props are not unfeathered. Looking at them visually, I can ensure that they are (if I manually start, it goes off without a hitch), and I've even run the props through another cycle of the unfeather switch and I get nothing more from it. Any other attempts get the same unfeathered response. So the program is recognizing my command, but for some reason does not agree with what's going on. I'm guessing it might be Win7 permissions problems, but out of curiousity (and if you can share this), what is the trigger for FS2C to check between feathered and unfeathered?I'll read up on the PMDG info on the locks and see if I have anything wrong there, too.Thanks in advance,Kyle

Bryan,First, I have to say I'm impressed with the amount of detail included and the amount of integration in 4100 version. I'm having issues with a few commands and operations, but I think that's more on my end (I ran the voice tutorial, but haven't properly "taught" my machine to understand me). All that aside, there's one issue that has me stumped.Running through the tutorial/manual flight, I'm running into issues when I go to start an engine. My props are unfeathered and on the locks, but when I command the engine start, I get a response that the props are not unfeathered. Looking at them visually, I can ensure that they are (if I manually start, it goes off without a hitch), and I've even run the props through another cycle of the unfeather switch and I get nothing more from it. Any other attempts get the same unfeathered response. So the program is recognizing my command, but for some reason does not agree with what's going on. I'm guessing it might be Win7 permissions problems, but out of curiousity (and if you can share this), what is the trigger for FS2C to check between feathered and unfeathered?I'll read up on the PMDG info on the locks and see if I have anything wrong there, too.Thanks in advance,Kyle

Hi Kyle,Does your PMDG J41 have the latest PMDG Updates installed?You're 100 percent positive the props are unfeathered all the way?It should work for you.Are you running the Pre-Flight Events?

Bryan,The aircraft is the latest version, the props show unfeathered all the way and I ran it from the beginning. I've since restarted my computer and everything went okay tonight (my only issue came when I tried to remove the start locks - they set to off, but I got no confirmation from the FO). I also taught the voice rec for Win, so this flight's reactions were much better. The restart must've helped something. I could swear I followed the checklist to the letter the first couple times, but I must've been wrong.Any ideas on why I might not have gotten the verbal "locks off" message? Could just be user error.Thanks for the same-day reply. I'm impressed by the level of support you give in here (and on the PMDG boards alike),Kyle

Bryan,The aircraft is the latest version, the props show unfeathered all the way and I ran it from the beginning. I've since restarted my computer and everything went okay tonight (my only issue came when I tried to remove the start locks - they set to off, but I got no confirmation from the FO). I also taught the voice rec for Win, so this flight's reactions were much better. The restart must've helped something. I could swear I followed the checklist to the letter the first couple times, but I must've been wrong.Any ideas on why I might not have gotten the verbal "locks off" message? Could just be user error.Thanks for the same-day reply. I'm impressed by the level of support you give in here (and on the PMDG boards alike),Kyle

Hi Kyle,Glad you got it work.Off the locks: FS2Crew replaces that sound clip with its own sound clip. You should hear it... just try bring the throttles back a bit further to ensure they really are off the locks.Cheers,

To remove the start locks, bring the power levers back (one at a time) so the base of the lever aligns with the hatched area on the pedestal:(illustration from the PMDG J41 pilot tutorial, page 61)The easiest way to do this is to use the mouse to move the levers.

Tom,I'm getting the locks to come off, I'm just not getting a verbal confirmation. So far I haven't fried an engine on departure, so I know they're off (I checked they were on previously by advancing the throttles and noting that the torque hangs at 30-35%). I'll take a look tonight and make sure my throttle levers are ending up fully in the hatched area when I try to remove them.Takk skal du ha,Kyle

I'm getting the locks to come off, I'm just not getting a verbal confirmation.

Ah, OK. I was also having trouble getting the confirmation when using my hardware power levers without looking at the pedestal (I don't know if the start locks were in fact coming off, without the message playing). Using the mouse to pull back the levers and making sure they aligh with the hatched area works every time for me.Selv tak :(

Just as a confirmation for those happening upon this thread through a forum search who had the same problem.#1 - I had not unfeathered properly/completely (though, enough to start the engine without destroying it)Leave the throttles where they are when the FO sets cold and dark until you need to start the engines. At that point, hit F1 and call for the start.#2 - By teaching your computer, it will be better able to recognize your voice (run the tutorials after the intro through Win7/yourOS)#3 - The "locks off" confirmation happens when you bring the throttles slowly into the hatched range one at a timeI think I had been bringing them back into the full reverse range (which will also destroy your engine if not careful)Thanks to all who helped me fix my user errors,Kyle