phantomflyer81

And it works very well too! I need to correct something about the wing tip trailing edge white lights - they were longer when I did the "repair" function of the new full installer. Now they are exactly where they belong. Also, the landing lights at the wing roots were "doubled up" - now they are not. That could have been an indication that I did something wrong - and I do believe that runtime errors can be produced by visual things such as that, though I'm no expert in the area. I just wanted to clarify this in case anyone else installed using the repair function - if you notice these peculiarities, it's probably a indication that something is not quite right. Cheers folks! Bill

Not to worry John! These things happen - for my own future reference, I made note of the PMDG base pack folder's read me = it's the place to go if unsure about install/uninstall methodology. I did just as Kyle said (thanks again) and I saw that Direct X and, I think - because it was very quick, that runtime was also configured - I can assume that's where I got my problem and that it's now going to be fine . All my liveries are still intact and I did a short hand-flown flight around KSEA and all seems perfectly fine now. I did notice that the wing lights are a bit different in this latest version - the trailing edge white lights are extended further back pretty much like the B737NG ones are. I'm sure I will discover other changes as I fly. That said, I'm going flying! PS - I had to re-install the nav data - that's another area that didn't need updating when I just used the "repair" function of the new installer. That also tells me to always uninstall old when using a new full installer! Thanks to all for the input, Bill Alexander (out for now!)

Hi Kyle, Thank you for answering everything! I didn't do anything at all, but now I will simply do as you said. Liveries can stay and will do it simply with the installer. Best regards, Bill

Hi Kyle and John, I will, for now, first use the OC livery manager and get rid of all liveries, then I will use the installer's "remove" function. Then I will have a good look around to see what remains. Obviously, I don't want any unnecessary livery textures left, but I am loathe to mess with anything that wrecks my registry. I will wait until a PMDG rep posts here. Thanks to you both for your prompt replies Bill

Hello John, Thank you! Yes, I also remember reading instructions and was coming up blank too - until I just decided to look in FSX/PMDG/PMDG 777x folder! I found this in the "base pack" read me: INSTALL NOTES: ============== This installer will search for your flight simulator installation as it is reported by the registry on your machine. If you have moved your flight simulator installation, or if you deleted it and re-installed in a new location without updating the registry on your computer, you may be told by this installer that it cannot find your MSFS installation. If this message is displayed, you must manually navigate the installer so that it points to your default MSFS installation directory, or this airplane will not install correctly. UNINSTALL NOTES: ================ If you need to uninstall the PMDG 777-200LR/F or any other PMDG Simulations product, please run this installer again and select the REMOVE option. Also, you can use the ADD/REMOVE PROGRAMS item in your Windows Control Panel. DO NOT MANUALLY DELETE FILES FROM YOUR MACHINE. (we warned you!) What worries me somewhat is that this says "do not manually delete files..." with a terse warning - Seeing that beggars the question, do I or don't I delete any folder(s)? Cheers, Bill

Hello folks, I went into the OC 3 days ago to find several messages about updates I didn't have, so I let it update the OC 1st. Then I checked the other messages to find I needed to re-download full installers for the 777-200LR and 777-300ER which I did (always turn off AV during downloads) but after extracting, I found zero documentation on how to install these in the read me or on PMDG site. Frustrated by the lack of instructions, I simply ran the new January 2016 installers (as admin and with AV off) and used the "repair" option for both the T7-200LR and T7-300ER. Seemed to work until my OC said that I had corrupt liveries click to repair which I did. No more error messages and no more messages from OC - seemed good to me! Went for a flight in a T7-300ER and it worked fine for a 16 hour flight (never use time compression) The next day I used the T7-200LR and within an hour I got CTD of FSX with a 6025 runtime error. Something I never had experienced. I tried again 3 more times with the T7-200LR - same thing happened! The 300ER seems fine but not the 200. This has me in a quandary. 1)Why are there no instructions as to proper installation? 2)What did I do wrong? 3)How do I fix this? Sysytem specs i7 6700K @4.8Ghz Liquid cooled - PC is only 5 months old Nvidia GTX 970 latest drivers 16Gb DDR4 system Ram Win7 pro 64 updated regularly UAC off installed in 250Gb SSD C:\ everything FSX related is run as administrator and fully updated FSX (Not SE!)Sp1 and Sp2 installed in 2Tb mechanical HD - D:\FSX ASN in D:\ UTX and GEX - covering the world and fully updated REX TD4 with Soft Clouds fully updated Can anyone please assist here. I'm tempted to repair again or do a fresh install (only if I really must) but need advice on how to do either of these first, Best regards Bill Alexander

Just found this: http://forum.simflight.com/topic/71348-oom-warning-given-by-fsuipc/ From way back in 2012 as well! I have brought back my TML to 1024 and un-ticked the box in the FSDT and FlightBeam "Virtuali" addon manger to not force textures at all. Also I noticed that I have UT2 installed and the AI traffic percentage is too high sitting at 35% for airlines and GA. So I brought that down and will probably reduce my water effects to 2x Low per Nick's (and many other's) strong suggestion! If I'm getting this bell at RPLL, surely I will get it at FlightBeam's KSFOHD after a long haul. Mind you, I did fly in and out of the SFO bay area after installing it, but with the default Cessna 172! I'm sure there are many other areas I can save a lot more memory...As for P3D, I haven't taken the plunge yet but certainly considering it over the next year or so.

You'd be correct about FSUIPC warning of impending OOM. It happened today landing the PMDG T7 at PIS's RPLL which is quite an intensive scenery. I just built this PC too - i7 6700K running stock 4Ghz on a Corsair H75 liquid cooling, I have 32Gb DR4 and GTX 970. WIndows 7 pro is on my Samsung 850Evo SSD and FSX on my HDD (space reasons - lots of add-ons). My last PC ran it without this warning, but I had FSX exe patched with the 4Gb patch. Perhaps that is needed? Or I'm being a bit too hard on my new system by expecting it to be able to handle sliders full on and/or the Virtuali addon manager keeps setting my FSX config to 4096 textures! I have to keep editing it down to 2048 (though I cannot see why 1024 isn't good enough). Time to go through Flight1's "Nick M's Bible" and get this new machine optimized. It was the one thing (aside from hardware) I haven't touched yet - today's flight was my 1st long haul test flight since building this baby. I knew it had to be something FSX related because the "bell" stopped when I hit P or if I went into the cockpit. SO I did some research to find that the latest FSUIPC gives us a warning. Great idea.

I noticed that it was reduced to only 1 pixel in a later service pack (and also in PMDG 777 models) If you touch it (try to move or re-size it with your mouse cursor) it will enlarge (especially in the 777LR model) from 1 pixel (tiny) to many more and become annoying - then it will be impossible to re-size it down to only 1 pixel again unless you re-start the flight. I just leave it alone at 1 pixel and hardly notice it's even there. Cheers, Bill Alexander

My pleasure Dan. If you browse the sections (go to the main page) there are also magnetic deviation updates. The ones from stock FSX are way out of date (many years). Aerosoft also do the 28 day cycle AIRAC data (supplied from Lufthansa Technic) at a reasonable cost, but not sure if they provide the automatic installer that Navigraph now use. Best regards, Bill A

Good point Peter. Without the highmemfix, the plane won't show up. Josais - you will have to renew your account with Navigraph to get monthly AIRAC updates. Personally, I buy 13 cycles at a time and always keep my FMS (for all add-ons) up to date. When you look at your FMS "init" page, it shows the date of the AIRAC. You can also update all the FSX nav data (free) here http://www.aero.sors.fr/navaids.html so they match the nav data on your FMS. They do it 3 monthly though and you can donate to the cause.

I has to do with the way the Earth is shaped in FSX. It is not round. Here is an explanation from no one other than Nick from Flight 1. Most, if not all, folks here should know Nick not only from his FSX "Bilble" posted in the Flight 1 sim forums but as a major scenery developer and amazing IT technician. He talks about the lights here, but this discussion started with the drifting eyepoint and now includes the drifting lights bug (per Hooks post above). This bug is also prevalent in P3D as Lockheed Martin have not toyed with that area (yet). Anyway, here's what Nick had to say: "It is most likely associated with the earth curve math and yes locating lights can be a PITA based on where the aircraft is on the earth.. you set their aircraft location precisely based on lets say Seattle and in Florida they are off, farther south off more I'm sure its in Adams original calculations for the curvature of the earth bleeding into the math for the aircraft lights. If you go into say Norway or Greenland during the day you will notice the ground textures are stretched bad.. this is because the earth in FSX is not round it become conical shaped as you get closer to the poles nothing you can do about it unless someone hacks the code and separates the association between the earth shape and the lights with respect to aircraft I am sure" So, it's something I (we) have to live with for now. I tried everything from EZCA to Opus with zero results. The closer to the equator, the worse the effect. The further away from the VC the CG is, the more the magnitude of the effect. Best regards, Bill A

Sorry to say that neither EZDOK nor OPUS can cure this problem at all. I still don't know if P3D got rid of it but it is extremely annoying. I am trying to find a solution elsewhere and will keep you posted. Regards, Bill

I wonder if the LM team did something about this FSX bug before releasing P3D? If so, I wish I could see the code so I could apply it in FSX! Someone out there surely would know what to do with this bug. I have often wondered if Microsoft ESP (some have it and some don't - I don't) has the tweak somewhere... Cheers, Bill