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

Maybe the plane gets dirty (from the outside) after several hours of use...

I had this problem a couple of times in the past. It's not the result of a hard landing and no custom PMDG failure. It always happened to me when the NGX was loaded twice, i.e by changing the livery or selecting the plane in the startup screen first, and then loading up a saved flight with the same NGX model. You can also check if something is faulty with the plane by looking at the engines. If the engine fanblades look strange, then something has gone wrong when loading the plane, and the problem with the landing gear might occur. I hope that helps.

In germany we have some airports where visual approaches are not even permitted to fly, according to the information in the aerodrome charts. I guess the reason for this is noise abatement, but I'm not sure. Here are some examples that I've found by a quick search in my charts: EDDK TRAFFIC NOTE Visual approaches will not be granted to arriving flights EDDL VISUAL APCH NA. EDDW TRAFFIC NOTE Visual APCH are not permitted.

Well, mine is set like that. Maybe it's just me and I've flown the Airsimmer for too long which flightcontrols do feel more direct to me. Thanks anyway

I agree that the real sidestick feels different in terms of force to a usual PC joystick. When I did a flight in a full motion sim at Lufthansa Flight Training center some time ago, at first I was very surprised what amount of force you had to use to move the stick or the rudder pedals. (At that time I was using a Saitek X52 at home.Now I'm using a Thrustmaster Hotas Warthog, which I think in terms of force comes close to the feel of the real sidestick.) On the other hand I was impressed how precise you could handle the plane with just some very small sidestick inputs. And in this regard the AXE feels a bit weird in my opinion. It seems to me that especially roll feels somewhat lacking behind my actual sidestick commands. You can also see this when doing the flightcontrol check as rob suggested. There is a noticable delay between the movement of the white cross on the PFD and the movement of the control surface. Comparing this to the Airsimmer A320 I don't see and feel the same behavior. Am I the only one with this impression?

1) The future of flight simming 2) PMDGs future regarding simulations of Airbus aircraft :Thinking: :smile:

I have exactly the same problem with the APU when loading another panel state. My workaround is to save the entire flight in FSX and load that one up on my next flight. Of course this only works if you want to take off from the airport where you landed before

In the NGX I normally fly manual till 10000 ft after takeoff. On approach I turn off the AP after landing checklist is complete and the runway is in sight.

Wonderful video! Thanks for posting!

This are my own observations. No one told me to do that. I noticed this effect while experimenting with FSX in the past when I renamed the fsx.exe to something else and got worse performance. Now with prepar3d.exe it's the other way around. This probably won't have any effect on Nvidia cards, and I'm not even sure if it affects all ATI Cards. But at least on my setup I'm seeing better fps when running Prepar3d.exe as fsx.exe. My only guess is, that it's a driver optimization specifically for FSX, that only takes place when the application is named fsx.exe.