james008

Thank you very much.. First I tried to deal with an update installation (since either way was supposed to give the same results) but I had to reinstall from the beggining as you suggested to solve this issue Marcelo Monteiro

I updated my FSX 737 base + expansion products to this new version, but the WX RDR is not working... and the WXRDR panel on pedestal section remains fully unclickable.. mouse arrow does not turn into a "hand" when passing over WXRDR pedestal panel knobs and switches does anybody have any idea? Thanks Marcelo Monteiro

resuming my point of view, after compiling historical PMDG comments in this forum and paying attention to PMDG historical market way of thiking (except for punctual releases that, for specific reasons, was not foccused on high sales, like DC-6)... Too early to be developed, but to be expected in the future = 787-8, 787-9, 737-MAX Not to be expected, due to prognosis of poor sales = 707, 717, 727, 737 (classics and jurassics), 747 (classics), 747-8, 767-400, DC-10 (and older DCs), MD11v2, L-1011, F-100 Not to be expected, due to market focus = any Airbus, any Business Jet TO BE EXPECTED (in the order I think it would make business sense) = 1) 757-200, 767-300 (757-300 and 767-200 would be target to a possible later expansion that I think will not really come) 2) Embraer regional jets, ATR-72 3) Bombardier regional jets ("globally" I think Embraer regional jets would open a wide market to PMDG, but maybe PMDG thinks different) Regards, Marcelo Monteiro

hardware axis assigned, via FSUIPC, to tiller option does not move PMDG aircrafts rudders hardware axis assigned, via FSX menu or FSUIPC, to rudder will also move tiller due to FSX limitations

first of all, you're not saving the file as a real .wx extension.. you're saving it as a .txt extension... you're saving as xxxxx.wx.TXT while on notepad, you have to "save as" and, while typing the archive name, you have to change the archive type to "all archives" then, on the aircraft, yYou have to type into scratchpad the same name of the file, without the extension part, before click on wind data request LSK key; for example: if you named your archive as KMEMOMDB01.wx, you have to type on FMC KMEMOMDB01 and then pull the wind data request LSK key Regards, Marcelo Monteiro

Here with the 737NGX I can press brake pedals and set parking braking while pressing them, as in the real life, without any problems related to immediate release of parking brake; I only release the brake pedals after confirming parking brakes on; by the way, I use a rudder/brake pedals hardware.. maybe this problem should be experienced by those who have to use keyboard to command manual brakes and parking brake Regards, Marcelo Monteiro

probably a departing traffic from Galeão International Airport, just taken off from runway 10 with right turn inbound to São Paulo terminal or inbound to Brazil south region...

Does the .ini configuration files from version SP1b works correctly with SP1c, allowing us to backup them and paste on the appropriate folder after install this update, os do we have to reconfigure mannualy our aircrafts via FMC?Thanks!Marcelo Monteiro

I don't know if I understood correctly what you are trying to say, but let's go...1) if you load the aircraft that comes with engines on, and you want to change the panel state to "cold & dark" you should NOT select the option called "save", but the another called "load";2) if you get the aircraft with engines running and make a SAVE over the "cold & dark" state, you will definitively overwrite the "cold & dark" state to a state in wich the aircraft is almost ready to fly;3) the minnor issue that the FMC denotes, when leaving indefinitely the words "loading panel state" on its screen, can be solved by clicking on the FMC to zoom it to a 2d popup and clicking again to close the popup;Regards, Marcelo Monteiro

The flap indication on the left speed bar on PFD is an optional config, variable from airline to airline...You can activate it via FMC, on the aircraft/display settings.. It's something like "show landing flaps"Some airlines use it, some don't useRegards,Marcelo Monteiro

I noticed it too, and I solved this problem just like Tejon said above.. simple!Regards,Marcelo Monteiro

I saw it too; and I found that the reason was really due to the coincidence between the T/D and the waipoint displayed.. I think that always the T/D varies a little due to wind, ground speed or another factors, something like decimals of a mile, always; in every flight, even when you think the T/D is fixed on an specific position, it is varying a little, something not visible to our eyes; but, in this case, the waypoint was, by coincidence, located just in the middle of this small variance, forcing the T/D to move ahead and move after the waypoint; if that waypoint was not present, it should vary decimals of a mile too, but should not be noted by the pilot; Regards Marcelo Monteiro

Trying to help people, I will repeat a suggestion of a brazilian sim pilot, posted on a brazilian forum: uninstalling java should improve the FPS and the smoothing of your FSX... I tried here, and it really improved the smoothness of my 737ngx virtual cockpit... and improved a lot! trully, I was not having low frame rates, I was having 20-30 fps on VC, but my VC was not paning and running smoothly.. after this, all became perfect It did not gave me much more frames, but it gave me only the perfect smoothness! from now to the future, probably I will install java when visiting a website that requires it, and I will uninstall before fly again! this will be my routine Regards, Marcelo Monteiro

the other is there, on the first officer side of the pedestal, "below" the engine 2 fire extinguisher;on first sight, we mismatch it with the standby first officer VHF COMM frequency, but with attention you can note that the FO COMM radio doesn't have standby frequency like the one on the captain's side... there's only an active COMM frequency and an active NAV frequency, no standby ones to the first officerRegards,Marcelo Monteiro

Patrick,Here the default panel state is engines running, but, in your situation, if there isn't another bigger problem, you can simple access the PMDG menu and load another panel state, choosing one of the others except the Cold & Dark one.Did you changed your default FSX flight to make all aircrafts always start with its panel in cold & dark state?Regards,Marcelo Monteiro