Dean19

Lifelong Asus junkie here. Always had great reliability and fantastic performance with Asus MB's. My last build on a Asus MB lasted over 6 years on a OC'd system that was on 24/7 for most of that time. On my most recent build I went with a Asus Z170A but the board came DOA. Took it back to Micro Center to exchange but they were sold out of the Z170A's. Was gonna go with the Hero but I got a fantastic deal on a ASRock Extreme6. I've been quite impressed with this board so far. Coupled with GSkill DDR3400 ram it's humming along very nicely and stable at 4.7ghz. Still an Asus fan but nice to find success with other brands too.

Thanks everyone for the suggestions. I will go with 2 x 8 (16gb) memory and when or if I need to upgrade, hopefully won't have any problems matching the set.

Hi all, I'm looking into finally upgrading my [email protected] rig. This CPU has lasted me over 6 great years but alas the time has come to jump on the 6700k/Z170 band wagon. I want to go with 32GB memory primarily for (future proofing) X-Plane and P3D and gaming. Looking to go with DDR3400 just for the added overclocking headroom. Would I be better off going with 2 dimms or 4 dimms? 32GB (4 X 8GB) DDR4 3400 - http://www.newegg.com/Product/Product.aspx?Item=N82E16820231917&ignorebbr=1 or 32GB (2 X 16GB) DDR4 3333 - http://www.newegg.com/Product/Product.aspx?Item=N82E16820232295 Will be using one of the Asus motherboards, haven't decided which one yet. Micro Center currently has a great deal on the Asus Z170-AR for $109.99 with CPU Combo, but the GSkill QVL doesn't show official support for compatibility with that particular MB. Thanks for any opinions!

Google Earth is also pretty good at finding some weather.

I have the same problem. When I load up cold and dark the CDU is blank. Holding down the MENU button will not turn it on. The only way to turn it on is to bring up the 2D version by using shift-3 or clicking the CDU screen itself. But it's ok, I can deal with it...as long as it works!

I think the whole point of this thread(and the other threads on this issue) is the desire to fly the aircraft by the official Boeing numbers and have it react accordingly during this important phase of flight(approach/landing) I'm surprised this wasn't caught during the beta period. Also surprised at the lack of comments by the PMDG team about this.

Watch the aircraft in outside view as you switch between 2-class and single class configuration. You will see the nose gear compress slightly in the single class config...due to the added weight up front

I tend to have similar results(0 degree attitude) when I fly the approach by the official numbers. Could possibly try coming in at 5 to 7 kts slower and compare the results.

I just did this flight. IGS RWY 25 approach into LSGS. I couldn't get the ISI 108.35 offset LOC to come up at all. I had to use the SIO VOR without glidescope guidance on a 6 degree approach descent from 16000' down to 3000' was an awesome approach. Will definitely be doing this one again!

That worked, thanks. Have to save the random failures state with the panel state or else it will default back to off.

I'll give that a try, thanks!

Is anyone having problems saving the random failures state? I turn on random failures, choose the number of failures(3) then execute. I exit out of FSX then restart in the same livery but random failures has defaulted back to off. Jeez, I was wondering why I haven't been getting any failures after hours and hours of flying!

Did you check for any route discontinuities in the legs page after you made the change?

+1 I know it was mentioned here but I can't seem to find that post!

This is important! I was losing my mind trying to figure out why I wasn't able to manually add Along-Track Place-Bearing/Distance waypoints . I was manually typing the waypoint names in the scratch pad and getting the "invalid" error. Finally figured it out that you have to use the line select key to place the waypoint name into the scratch pad then manually type out the parameters.

Thanks Zach! I've been looking for this. I have ENB and Antilag running together on my system now.

Made me chuckle, thanks for the reads!

You can actually see the aileron deflection on the lower DU if you set it up to watch.It instantly deflects full range for a second when the heading select button is pushed. Doesn't seem normal.

Thanks for the suggestions. I exited out of FSX completely before each livery change. I did this 4 or 5 times loading different liveries and even threw in a system reboot but they were all still loading with idle fan blades. Only the PMDG House livery would load with the fans spinning. When I changed airport to KLAX the problem was gone and all liveries loaded fine. Will have to load up at KTPA again and investigate further. Edit: I just loaded up again at KTPA and all is fine...fan blades and cone working. The only thing I can think of is that it was raining heavy at KTPA when the fan blades were not working. When I load up in clear weather the fan blades work fine. Maybe the weather has something to do with it?

Scenery is FlyTampa rebooted KTPA I just tried reloading at a different airport and all is working fine. Strange! Thanks for the suggestion.

I had to uninstall and reinstall the NGX after I messed up trying to resolve the livery manager issues. Then I downloaded some liveries and tried to install them. Had to delete all the old livery folders before I could install the new ones. Now the fan blades are not spinning at all on all my add on liveries. The engines are running but the fan blades are not moving at all. And also the fan cone looks like it's gone. But the PMDG house livery looks fine and spinning as it should. Anyone have any idea on what could be wrong? Thanks

Try turning off the landing lights and it will show correctly. I think Ryan said this is one of those FSX limitations for some reason...

The few panel freezes and out of memory issues I had came when I started FSX after running other programs such as internet browser, office applications, games, etc. I don't have any issues at all when I start FSX right after a fresh reboot.

My default pilots view zoom factor is at .65 as the manual recommends .60 to .70 I tried .70 for a while but enjoy the bit wider aspect of .65 for ease of view But yeah, TrackIR is definitely on my list!

This is my default Cockpit view made with Ezdok Zoomed in HUGS view