Chri

Before reinstalling your sim, you should take a look at this thread in the FSL Forum https://forums.flightsimlabs.com/index.php?/topic/16166-affinitymask-causing-stutters-and-underperformance/ and wait what the FSL support staff has to say about this. As you can see there are other people having perfomance issues with the latest update as well.

Another idea for a quick (and very dirty(!) workaround): Goto http://toolbar.netcraft.com/site_report?url=http://downloads.pmdg.com Copy the IP under Network. This is an IP from a cloudfront server which is most probably not located in germany. For me this is 54.192.29.41 at the moment Start Notepad with admin rights Open C:\Windows\System32\drivers\etc\hosts Insert a new line with [IP-Adress] downloads.pmdg.com ie: 54.192.29.41 downloads.pmdg.com Save the file Restart the PMDG OP Center and check. Important: Remove the Line from C:\Windows\System32\drivers\etc\hosts again!

The cache control header can be used in both directions - request and response, see https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Cache-Control Of course the cache server itself can have the ability to just ignore this header, but to my own surprise it did work for me. (Or all of this was a big coincidence) I had been a proxy administator myself for many years in a corporate network and had to do with this stuff on a regular basis. So I thought it was worth a try.

Hello there, I'm also from germany and had the same issue. By opening the URL that the Operation Center is using for checking for product updates, in Firefox debug mode (F12 Key) and setting the "Cache-Control: no-cache" header manually, seemed to have solved my issue with the download. The next time I loaded up the OP Center the new 777-Update was found. The "Cache-Control: no-cache" HTTP-Header most probably forced the cloudfront server to update its cache.

Someone at the LM forum posted an explanation a few minutes ago: http://www.prepar3d.com/forum-5/topic/optimize_parts-what-does-it-do/#post-102880

I did 2 full flights today with the NGX, each one about 2,5 hours long. So far I had not seen any unusual behavior in the sim with the tweak enabled. I don't run any overclock (yet). So it's 4.4 Ghz. (Eventually I will try this in the near future)

No, nothing unusual, just moderate settings. I have the bufferpools 0 tweak and my autogen is set to normal. LOD 4.5. Textures at 1024. The system is not overclocked. Btw, AI is off. I still need to get Ultimate Traffic to work.

The screenshots were taken at default ESGG. I don't have many P3D compatible airports so far. On Aerosoft EDDL I get around 43 FPS with OPTIMIZE_PARTS=1 and 36 with OPTIMIZE_PARTS=0

Intel Core i7 4790K GTX 980

Hello, today while inspecting my Prepar3D.cfg I came across the setting OPTIMIZE_PARTS under the [sIM] section. The default setting is OPTIMIZE_PARTS=0 and out of interest I canged this to OPTIMIZE_PARTS=1 to see what happens. To my surprise it really does optimize something in the sim. I have about 10 FPS more in the PMDG NGX afterwards. I did some testflights with this and couldn't see any other visual differences, but I haven't found any explanations on this option in the net. Does anyone know what it actually does? OPTIMIZE_PARTS=0 http://fs2.directupload.net/images/150314/yck5696m.jpg OPTIMIZE_PARTS=1 http://fs2.directupload.net/images/150314/g3xnlgrg.jpg Best regards Christian

Is there a VAS difference between the 200LR and the 300ER (I dont' have it yet) besides the taxi camera issue? On my system the VAS with the NGX is about 200 MB lower than with the 777-200LR. I'm not sure if VAS consumption has increased after SP1.

Robert, are you sure about this? I thought VAS is shown in the "Virtual Size" column.

Did you use any large fix page range rings for ETOPS alternates? On my last flight yesterday with the PMDG 777, after several hours, I was getting very poor performance when those rings were displayed on the ND. After removing them from the fix page, everything was fine again.

Maybe PMDG can convince Laminar some day that using the scrollwheel to rotate knobs in the VC, like in FSX, is not "Bad UI design". The X-Plane method of dragging to rotate a knob is so annoying if you're used to the easy and precise scrollwhell function in the NGX or 777X.

Those of you who don't want to mess with the rolling friction at all, but still want to have a better sliding friction: You can also just modify the Frictions.lua out of the Lua_Plugins_07July.zip and just keep the SLIDING-values in it. This is what I'm doing now. -- This sets frictions according to the resluts by Johan Lees, early December 2012 ipc.RestoreFriction() -- The original FSX values are shown in the comment at the end of each code line ipc.SetFriction(WHEEL, CONCRETE, SLIDING, DRY, 1.000) --0.640 ipc.SetFriction(WHEEL, GRASS, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, GRASS_BUMPY, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, ASPHALT, SLIDING, DRY, 0.950) --0.640 ipc.SetFriction(WHEEL, SHORT_GRASS, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, LONG_GRASS, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, DIRT, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, GRAVEL, SLIDING, DRY, 0.800) --0.640 ipc.SetFriction(WHEEL, BITUMINUS, SLIDING, DRY, 1.000) --0.640 ipc.SetFriction(WHEEL, MACADAM, SLIDING, DRY, 0.950) --0.550 ipc.SetFriction(WHEEL, TARMAC, SLIDING, DRY, 1.000) --0.640