Jd_jay

Kyle thanks to your pointers i managed to narrow down the problem and find the cause. It was neither a hardware or PMDG problem. Im very new to transitioning to P3D so still fine tuning settings, and what i didn't notice was that P3D had automatically assigned two different controller axis to my throttles. Once i cleared the one that wasn't assigned to my hotas throttle it stopped. I didn't think to check this sooner as the throttle was PMDG 737 exclusive, didn't happen with other well known payware or freeware. Thanks again.

Kyle Purchased and installed the P3D version, referenced FSX as I don't have the problem in FSX so find it hard to believe that it would be any sort of hardware or calibration problem.

Just putting this out there today just incase I'm making a silly mistake somewhere. I've recently crossed over to P3D and installed PMDG 737 and fs2crew reboot. I'm not sure what's causing it but I have the throttles in idle and run through the start procedure and everything's fine. I can sit on the ramp for ages at engine idle and everything is ok. When I then go to taxi I accelerate and when I pick up speed I reduce back to idle. Then randomly the throttles keep jumping forward, I have to slam on the breaks and move my manual throttles forward and backwards. I need to do more testing but I'm sure it doesn't do it if I'm set just off of idle. I don't have the problem in FSX with everything set up the same and I have a null zone of 5 on my throttles axis to try and stop it.

You sir, hit the nail on the head. Thank you so much, that was the last setting i had out of place on my new install. Have done a complete flight with it all working smoothly and your right, its so much better than the legacy version and was worth the purchase. Would you mind answering my post about the PM and panel lights at some point please. or give me a brief outline here of what the PM is actually programmed to do with regards to panel lights?. Mine currently doesnt switch on the overhead panel light or dome lights when starting out, lso should he switch at least his panel lights on at dusk and dawn transitions. Thanks again Bryan

so i did another flight and the same things happened. PM seems to have no contact or awareness of anything that is to do with altitude. For example this time, did no do anything when passing transition altitude which was set for 6000, so randomly at 12000, PM replied standard set, passing 0500 altitude.... no light operations at roughly 32000 i see briefly up in the menu bar an orange message saying something about 10k.... Pm said 1000 to go after i gave decent briefing asked to release the cabin several times through out flight.

Did my first full flight last night and had many problems with the PM and altitudes. I need to do another flight to see what happens but I'll list my observation, all information in the FMC was correct. I'll make a list. Pressurisation cruise altitude was set at 36500, cruise level in FMC was 37000 Transition level was 6000 in FMC, PM did nothing at 6000 and when he did the altitude was well out PM did nothing with the lights at 10000 PM did not say 1000 to go until I started defending PM told cabin crew to prepare for landing at around 18000 PM said the message about 5000 at around 12000 Any ideas?

Thanks for the reply. I guess it comes down to personal preference. Would be nice to find out what should happen though, when and if I should switch on the overhead panel lights, or I have a bad installation at present.

Just getting to grips with reboot after switching over. Im using SOP2. My question is when and what lights should the PM switch on at night internally?? The reason i ask is that I've noticed the PM doesn't switch on the dome lights to start with, and also when he's switching on the panel lights he's never at any point switching on the overhead panel lights or circuit breaker lights? Is this now my job? i can't find any mention about the internal lights in the tutorial apart from that at night the PM will switch off the dome light. Im currently typing up my own flow list and would like to add in the necessary or is it a bug? Many thanks in advance for any info.

Hi Bryan, thanks for the reply and advice. I tried everything you said but still couldn't get it to work. Knowing that it technically isn't supported in P3D I didn't want to bother you with the issue any more so I decided to bite the bullet and purchase reboot instead. Looking forward to testing it out I can see the vast improvement already from just quickly toying with it.

Firstly I fully appreciate the NGX legacy isn't supported technically for P3D but I've seen posts about numureos people that have had no problems using it in P3D so as I have just forked out for P3D, the P3D version of PMDG 737, I thought I'd just use the legacy of FS2Crew for now. The problem I'm having is I just can't get it to show up when I'm sitting on the Tarmac and ready to use. I installed it using the migration tool, I have the SDK edit in the options.ini, all the entries are in the panel.cfg, I have it enabled. I even have a key assigned to auto feather. When I use the key it doesn't show, there is also no click spot available in the cockpit. What am I missing? Any thoughts would be most appreciated. Many thanks.

FSX Steam addition not available to you?

The answer to your problem is with fs2crew not PMDG, the answer is also on the fs2crew forum. All you have to do is do a reinstall of fs2crew, when it warns you about which service pack you require, just click ok and activate voice or button version, whichever you choose to use.

I wasn't going to make up a new thread until I tested it by doing another flight, but I'll mention here beens you have if you don't mind, the FO didn't turn the dome light back off before push back on my flight either.

Yes, your supposed to assign a key to auto feather, and not alternate static, here's the text straight from the manual: Create a joystick or keyboard button assignment for 'AUTOFEATHER (ARM/OFF)' in the FSX 'SETTINGS - CONTROLS' menu. You can select any Joystick or Keyboard assignment (or both). If using a keyboard assignment, we recommend using a single key, like the letter "C", instead of a complex combination.

If you have followed the tutorial from the manual or correct flows from +54 minutes, from the cold and dark state, you would of powered up the aircraft correctly anyway, so none of that will be a problem. Some paragraphs in the manual are just giving explanations as to why things have to be how they are.

Your not the only one that has fell fowl of that, glad you got it sorted

What's a stuck mode? Does it freeze? Or does it not allow you to enter manually? Or are you stuck because you've not entered manually before? Have you tried this more than once? With full pc shut downs inbetween? Hopefully we can help get to the bottom of it

It does what they said it would do, its a big performance hit. Took 15 FPS off as soon as i clicked the cam button, as soon as i clicked it off the FPS went back to normal. Going to leave that one alone i think.

I actually copied my reply to many posts that have asked the same thing, and have since upgraded to ASN, couldn't agree with you more about the upgrade, quick question, when you say does it all automatically, do you mean you don't have to load a flight plan into ASN, for it to work now?

Im currently running AS2012 with SP3 Beta, i have no problems what so ever with importing the winds, for anybody who wishes to update or is using AS2012 SP3 beta, this is what i do. the first bit is for what i do and may not be relevent to some. So i create my flightplan in EFB, and save it into my PMDG flighplans folder, and also as a standard FSX.pln. 1: i load the flighplan into AS2012 (you should be aware how to do that using the standard .pln file) 2: run FSX from AS2012 3: start flight as normal, loading the same flight in PMDG format into the FMC. thats it, after i have done my FMC setup the winds are automatically in there. (providing you have clicked RTE DATA>WIND DATA REQUEST) click the LSK key next to the W and you will see the winds for that waypoint.

Unfortunatly i cant help you with a fix, but can give you some info. I had airbus extended with locked RAAS, and then installed PMDG 777 with Locked RAAS, after install both worked fine. Then i unistalled Airbus extended to install the new versian, after reinstalling the airbus extended with Locked RAAS, they both still worked. i was actually worried about that side of things, but all is well. Best person and place to ask would be the developer on the FS2Crew RAAS forum.

Out of interest why are you setting it to 250kts rather than your V2 speed for take off?

you should do that with the flight you was on about and we will be able to help you better, make sure you have a 2D view of your FMC showing and all the autopilot buttons, you can PM me if you dont want to keep filling up this post.

some screen shots might help when this is happening so we can see what configuration you have the aircraft in, but when you are on approach and coming onto final, are you arming the localiser and then approach button whilst you are still below the glideslope, do you have ILS active. You maybe programming the FMC right with regards to STAR, but are you flying the aircraft properly in the correct config?

Have you used process explorer to monitor your VAS usage on this flight yet? You will be shocked at how much it jumps up as soon as flytampa Dubai loads up, don't forget it's not just the airport that loads with this scenery it's the whole area of Dubai. Also is your OOM error message from FSX or is it a windows OOM error?