Vielen Dank ( Many thanks ) from Aachen, GermanyHans LauerCore I5, WIN 7 – 64, RAM 8 GB, Grafik GTX 260 Dual Monitor GLOBAL 2010, UTX EUROPE, VFR GERMANY 1-3-4, VFR London, Mega AP EDDF, EHAM, LEMD, LSZH, Stuttgart X, Approaching Innsbruck, Switzerland X, NordlichterPMDG MD11, Jetstream 4100, 737 NGXFSX.CFG by ******* ´Bojote´ AltuveExept of the activating issue, which was solved by the great support of Paul and Ryan this environment never caused any problem

I waited for the release of SP1 to purchase the aircraft and I did it right after it was announced. I'm really enjoying this magnificent aircraft and the PMDG team deserves a very loud applause.That being said, I have a small problem and I am curious about the details. One of the SP1 improvements notes: "Added more robust support for custom FMC waypoints that are created as the result of downselecting already existing LEGS, RTE or FIX page waypoints". Well, that really does not seem to work for me. For example, when I tap in let's say BIG/-2 it creates a custom waypoint as BIG001, thus seem to work as intended. But when I try to create another waypoint using this new custom waypoint like BIG001270/10, it says "Not in Database". The note clearly states SP1 should allow this to be done, but it simply does not work.Not that it is a huge issue, still it would be very nice to have especially for visual/custom approaches. I wonder if this is scheduled to be fixed/improved.Anyways, thank you for this excellent aircraft once again.Doruk Selçuk

Is this thread any help?http://forum.avsim.net/topic/347242-making-waypoints-tutorial/page__hl__waypoints

Unfortunately, no. I have no problem creating the first custom waypoint as described in that thread. Further, I can create as many 'unrelated' custom waypoints as I like. The problem occurs when I try to create another custom waypoint, originating from the first one. Like;I create XYZ001 , then say I need to create another custom waypoint 5 nm east of that new waypoint, normally 'XYZ001090/5' should do the trick, but it does not. :)Doruk Selçuk

Is this thread any help?http://forum.avsim.n...__hl__waypoints

Joao-Yes- this is an indication that you need to adjust your FSX.CFG settings to correctly match your monitor.For instructions, take a look in the Simobjects/Airplanes/PMDG 737-800NGX/Panel folder.We put a README there to guide you through the correct change. It's contents read as follows:===============Failure to use the correct fsx.cfg WideViewAspect setting can result in strange views that don't match what we designed:-For widescreen 2D panel use, you must have WideViewAspect set to TRUE in your FSX.cfg [Display] section.-For 4:3 2D panel use, you must have WideViewAspect set to FALSE in your FSX.cfg [Display] section.The FSX.cfg file is located at:Windows Vista/7:C:Users(Your Windows User Name)AppDataRoamingMicrosofFSXWindows XP:C:Documents and Settings(Your Windows User NameApplication DataMicrosoftFSXYou may need to change two Windows settings to be able to see these locations and the file - set "Show Hidden Files and Folders" and uncheck "Hide extensions for known file types" in the Windows folder options in the Control Panel.====================================Hope that helps!

Okay Now I am confused as well lol. I read above but I already had WideViewAspect=True in FSX.CFG Normally the panel.cfg would be used so when I adjusted the numbers from 10 to 3.1 that worked fine. But now I see there is another .cfg in there named panel_wide.cfg and the numbers 10.0 are still in there.So I wonder which one I am actually using. Logic would say I should be using the panel_wide.cfg and not the panel.cfg where I changed the numbers and it fixed my view. So whats the deal here with the 2 .cfgs and how do you know which one your using?

I have one quick question - what is the order of installation? Is it...1. 737NGX 800/9002. SP13. 737NGX 600/700

I have one quick question - what is the order of installation? Is it...1. 737NGX 800/9002. SP13. 737NGX 600/700

Yes!

Thanks, any chance a PMDG repainter could do the RAAF VIP jet? Also, just wondering if PMDG can update us on whether we will see a Wedgetail variant?

Which file to save the download into? Sorry guys I'm not to technical.Regards,Woody

Which file to save the download into? Sorry guys I'm not to technical.Regards,Woody

Save the SP1 file anywhere you like - I save mine to a folder called "PMDG Downloads - FSX". Then when it has finished downloading, unzip the file and just double click on it to run it. Follow the instructions on-screen and presto! You've installed the SP1 update.

Save the SP1 file anywhere you like - I save mine to a folder called "PMDG Downloads - FSX". Then when it has finished downloading, unzip the file and just double click on it to run it. Follow the instructions on-screen and presto! You've installed the SP1 update.

Thanks a lot!!!!Regards,Woody

Would be nice to have a solution to the skeleton effect, where in the outside view the plane slowly constructs itself from skeleton upwards. This is definately a SP1 problem for me.

This happened to me until I turned OFF the low res cockpit model and textures. Haven't yet checked which one of the two was responsible for the effect, however.

Would be nice to have a solution to the skeleton effect, where in the outside view the plane slowly constructs itself from skeleton upwards. This is definately a SP1 problem for me.

What kind of storage do you have?

What do you mean with storage?FSX is on another partition as my OS and I have 4gb Ram.But it can´t be my hardware, because this effect wasn´t there before SP1.

Hello PMDG,First of all: Many thanks for this update!!! It's a real improvement on my computer (more stable). Now, I van fly from LSZH (Zurich) nach EHAM (Amsterdam), without getting an OOM-CTD anymore. Perhaps there is stil a short freeze above the Netherlands, but that sure has everything to do with the NL-2000 scenery that is installed. NL-2000 is really demanding scenery.Still, I should like it, if the pedestal/throttle quadrant should be accessible from the 2D Panel (perhaps in a future update????).Kind regards,Henk Altena