Quickmarch 488 Posted October 10, 2013 Report Share Posted October 10, 2013 I mentioned elsewhere (Kaspers latest ATWC post) that I had been having a bit of fun with the PMDG 737 NGX lately. What I didn't mention there is that it has been giving me fits with FSX. I'm going to lay the blame solidly on PMDG's doorstep because nothing else, none of the other planes in my hangar (that I've flown lately) experience the same problems.Problem #1: Many "not responding" error messages. Fortunately, always on startup. Sometimes takes two or three attempts to get the 737 stable enough to start a flight process. Never crashed during a flight. All of the PMDG suggestions for proper setup have been followed to the letter.Problem #2: I normally run FSX in the standard screen mode, ie: not full screen. I do this because I often pop out to other programs to do things pertinent to the flight. Eg: read sids, stars, approach plates, etc. while flying. In the 737, if I do this, I cannot recover FSX by clicking on the FSX icon on the lower task bar in Win7. To get the sim back, I've got to load Task Manager and recover FSX by "bringing it to the front". This one is real strange because it's absolutely the first time this has ever happened.Problem #3: I'm using a Gamepad, because I'm travelling, instead of my usual joystick. This required some changes to the default.cfg file in the controls setup menu. All other planes that I've flown using this Gamepad operate as advertised. The PMDG 737, on the other hand, occasionally scrambles the button assignments. Picture the throttle increasing during taxi when I press the decrease button. First, I increase rpm, to about 30%, to get the plane rolling, then immediately decrease to idle. The plane rolls along quite nicely at very low throttle settings. Last night, I ran across this problem where the rpm increased despite hitting the decrease button. The solution was to use the keyboard commands F1 - F4 to control the throttle. At the same time as the throttle inputs were scrambled, the brakes (assigned to the two "shoulder" buttons) ceased to work. This requires the application of the period to slow or stop the plane. Loading the default Cessna 172 without exiting FSX yields normal responses to these inputs. PMDG specifically mentions NOT to use FSUIPC to assign button commands, so I have not done so.In fairness to PMDG, I'm using two different pieces of software/hardware than I have used in the past when flying the 737 back at home. The first is the Gameboy. I'm NOT convinced this is a problem because it is using exactly the same software (FSX default control menu) as I use with the Logitech Joystick.The second is a piece of software called "VAInterface Lite" which links the iPad "Virtual CDU" to FSX over a TCP/IP connection. I have not tried testing the PMDG 737 without this software and link. Easy enough to do and if it yields results, I'll report back, here. Don't hold your breath.I have been very careful NOT to load one session with the PMDG software over another. This is specifically noted as being a no - no by PMDG. They remark that lots of instability will be your reward if you make this mistake. Sequence is: Finish flight, Exit FSX, Restart FSX, Load new PMDG session.I'm not put out by these issues. I know I'll eventually find the solutions. I am, otherwise, very happy with the PMDG product and have been planning on adding the 777 as soon as I get back to Canada.That's my $0.02. YMMV Quote Link to post Share on other sites
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.