Chri

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

While reading through that boeing patent ( https://www.google.com/patents/US6158695 ) that someone posted earlier (I'm not sure which thread it was) I've found something interesting Figure 1: https://patentimages.storage.googleapis.com/pages/US6158695-2.png Might this be the answer to what we are experiencing regarding "autotrimming" while pushing or pulling the control column?

I had the same problem with the popup displays first. Unlike in the NGX you have to click on the outer edge of the display (the thin pitch black line that sourrounds the whole display) to move it.

I'm getting slightly better frames in the 777 now than in the NGX after I've set the PFD and ND refreshrate for the VC to "15" just like I have it set in the NGX (which I think is also the default setting). The default refreshrate for PFD and ND in the 777 was (at least for me) set to unlimited which gave me a 5 - 10 FPS performance hit. So I have now between 30 - 40 FPS at the cargo gate in Aerosoft EDDK and around 50 FPS high in the air.

Hello Rich, I had the same problem with the popup displays first. Unlike in the NGX you have to click on the outer edge of the display (the thin pitch black line that sourrounds the whole display) to move it. I hope that helps