NBouc

Thanks guys but it's all OFF (Game Bar OFF, Game DVR Recording OFF, Game Mode not activated, TruePlay OFF) @João Alfredo: The spanish forum you referenced seems to deal with the problem with 32-bit FSX and P3D, which is different than what I am having. I don't have the option to select a rendering device in my Nvidia CP, my GTX1070 is automatically used. Thank you anyway.

Vineguy, that is an option I am considering, but I would prefer to try and correct the problem on 1709 if I can. If nothing can be done, I will rollback to Windows 10 1703. Being on the Home version, 1709 might be forced back on me later down the road :-(

Hi simmers, Last night I updated to Windows 10 Fall Creator Update 1709 (from an up-to-date 1703) and ever since my FPS in P3Dv4.1 are 50% lower than what they were on Windows 1703. I tried to solve the issue by removing the current Nvidia drivers (385.28) using DDU in safe mode, and installing the latest available version (388.13) but the result is the same. I even tried a fresh re-install of drivers 385.28 and still no improvement. Doing a google search reveals a few posts outside the Avsim forums talking about that problem with other games, but none that offers any real solution (apart from suggesting to update the video drivers). Are any of you facing the same issue ?

Martin, this is good information and something I did not know regarding MCE. His Mobo is an Asus Prime Z-270 and we indeed kept MCE enable, mainly for the simplicity of getting a reasonable overclock without having to figure out the proper voltage to apply. I might try with disabling MCE to see what difference it will make, or eventually look for a better cooling solution such as the NH-D15 (He doesn't want any water-cooling solution for some reason). Reducing the CPU temperature might give it a longer life, even though my son does not seem to be too concerned about that since he replaces his computer every 4 or 5 years no matter what. Anyway, thank you for the information you provided me.

Hi Martin, thanks for the comparison with your daughter's setup. The ambient temp is around 21C when his computer is iddle, but rises to 25-26 after a few hours of gaming (the computer is heating the room). His CPU Cooler is a Master Cooler Hyper 212 with 2 x 120mm fans (push-pull) and the CPU turbo is overclocked to 4.5 GHz on all cores. I wonder if his high temps could be caused by the location of his case which is on the floor under his desk, in the corner of a small room (6 inches clearance from the back and side walls). May be the intake fans are re-injecting a portion of the exhausted warm air. Even with a good airflow in the case, may be the airflow "in that corner of the room" is not optimum.

For regular gaming, I agree. My son, who is a "gamer" and not a flight simmer, replaced his i5 2500K with a new system build around a i7 7700K (the 8700K was not yet available at the time) and for the type of games he plays, the additional threads seem to be utilized by most of his recent games. Performance wise, it was a huge leap forward for him. But despite a very good air flow with multiple fans well balanced and a good CPU Cooler, his CPU temperature is often in the 80°-85°C range (while my i5 6600K under stress never goes above 60°C).

Hi fr3dm, 2 years ago, I replaced my aging i5 2500K@4.5 GHz, 16GB DDR3-1600, GTX970 4GB VRAM with a i5 6600K@4.5 GHz, 16GB DDR4-3000, GTX 1070 8GB VRAM and saw a big big improvement. So I figure that going to a i7 8700K or even i5 8600K will be for you even better. I cannot comment about the benefit of a i7 8700K over an i5 8600K for lack of knowledge of those new CPUs performance in regards to P3D, but the i7 will surely produce more heat than the i5 thus require better cooling. I've always use the i5 variant because they are easy to keep cool on air, even when overclocked (no water cooling required), and also because I am not convinced that P3D can properly use the additional logical cores of a HT CPU, but I might change my mind in the future if I see reports of the contrary. I've seen too many reports about people running their i7 with HT OFF for better performance/stability with FSX or P3D. Disclaimer: My opinion of a i7 vs i5 is purely personal and I have no technical background to backup my point of view. I am not a CPU expert. I simply follow my guts feeling based on what I read. I would recommend going the SSD route though. No need to buy the expensive M.2 drives, I have 2 Samsung 850 EVO SATA SSD drives (500GB for OS and 1 TB for P3D) and would never go back to mechanical drives. It does not make P3D perform better, but the shorter load time is well worth it. Best regards,

Hi Luke, Just make sure that you also have the files "cont1.cab" and "cont2.cab" in the same folder as your "Install_Content.msi". All 3 parts are needed for a proper installation of the content.

Same here with the PMDG 737-700 in P3D V4.1.7.22841 on Windows 10 1703 Build 15063.674 I don't usually use the 2D panel, but today, while wanting to return to the VC using Shift-S, I hit the key one time too many and got to the 2D panel. The mouse cursor changed to a rotating circle for a few seconds then P3D crashed, CTD with no error message and nothing in the Event Viewer. P3D4 simply closes. Very annoying.

Update for those who followed this topic: Problem solved ! Problem solved after installing the 777's micro update to v1.10.8443 (12SEP17). I flew many test flights to destinations where I was having the "Invalid entry" problem all the time but with this update, I am now able to change STAR and approach at will way past T/D.

Thank you Mats for the link. I've bookmarked it in case I ever need to revert to a 32-bit Office for some reason.

Lucky you Skywolf, because on my system, the installation of the 64-bit version of "Microsoft Access Database engine 2010 (Spanish)" caused my Office 2010 applications (32-bit version of Office 2010 Pro, even though I am running Windows 10 Home x64) to start with an error message saying "One of your object libraries is missing or damaged. Please run Setup to install it", which I did and was able to work on my Office documents but only for that session. That same error message would come up again every time I launched an Office application. A search on Internet took me to a Microsoft Support page stating that the problem is caused by having a 64-bit version of the Access Database engine running along a 32-bit version of Office and recommended to remove the 64-bit version of Access Database engine. I looked at my installed APPS in Windows and I saw the entry for the Access Database engine in the list with the same install date as my PMDG airccarfts. Since I never installed MS Access and don't need it, and I did not see any relevance between it and PMDG (not mentionned in any document I read) I followed Microsoft's recommendation and removed it, which corrected my problem with the 32-bit Office applications. All the uninstall dialogs were in spanish, despite my OS being in US English. I did not know it was needed by RAAS. But then, Prepa3D v4 would no longer start and I could not figure out why, except that I knew that the only thing installed that day was the PMDG aircafts (NGX+777). So I uninstalled my PMDG aircrafts and Prepar3D v4 completely and re-installed them while monitoring the installed applications window and I then realized that installing the PMDG aircrafts triggered a silent install of the 64-bit "Microsoft Access Database engine 2010 (Spanish)". At that point, it seemed that I had to choose between using Office or using PMDG in Prepa3D v4, but not both :-( Well, I finally solved the whole problem by uninstalling my 32-bit version of Office 2010 Pro and installing the 64-bit version of Office. I took the time to write all this not so much as a reply to your own post, but more as additional information in case some other users are having the same problem I had and are still scratching their head off trying to understand what is going on. Best regards,

Hi Chris, we can rule out the navdata. I first had the problem while using the cycle that came with the aircraft (I think it is 1509, not 100% sure but it was old). I then installed cycle 1707 and had the same problem. Tonight, I installed the latest version of the PMDG 777-200 LR/F for Prepar3Dv4 (v1.10.8378.0), re-installed cycle 1707 just in case, and the problem is still there.

I tried with and without loading a scenario and had the problem in both cases. Entering the route manually or loading a saved flight plan also has no impact on the end result.

Hi David, good to know I am not the only one with this problem. What simulator are you using with the 777 (I am on Prepar3Dv4) ? PMDG has confirmed to me that the 777 should allow this. They are already analyzing the problem and I have full confidence in them to either fix the issue (if there really is a bug with the aircraft system) or to provide a solution if the problem lies somewhere else. I just have to be patient. Later tonight, I will install the latest 777 version made available yesterday (1.10.8378), but I don't expect any change (too soon after I opened a ticket on the subject). Cheers,

I sure will Dan.

Thank you Chris, I finally opened a support ticket with PMDG with a link to this thread.

Thanks for the idea Andy, but I already tried it and it doesn't help :-(

Hi Dan, I was in flight on that KMSY to KIAH leg when you posted and since I was approaching AEX, it was a perfect timing to try your suggestions, but unfortunately it did not work. I could select VFR runway 08L, but got an "Invalid entry" as soon as I tried to select GESNER.08L I changed the destination to KLAX and Exec, changed it back to KIAH and Exec (The FMC lost all waypoints but the current active one which was FERNY). I was not able to select any STAR at all at that point (not even DOOBI), they all resulted in an Invalid entry message. My NavData is current, AIRAC cycle 1707.

Thank you very much Andy for that video. I really appreciate the effort. The way you do it is how I have always done it, but it still does not work for me with the 777. I flew the route again (KMSY to KIAH) with your video on my second computer just to compare and replicate your actions at the same moment and order. We are doing the same thing in the same order but with different results. I was setup the same as you with DOOBI and ILS08L active before passing AEX, I initiated the change of approach and STAR at the same location you did (10nm from JERNY while in descent) making sure that my indications on the PFD, MFD and MCP were the same (they were except VNAV put my AT in SPD mode instead of HOLD like yours - but that should not be a factor). In the DEP/ARR page, I was able to select ILS08L but as soon as I clicked the LSK for GESNR1.08L, I got an "Invalid entry" message on the FMC. The FMC did not update with that STAR since it cannot be selected as a result of the invalid entry. I tried again with a different Livery, just in case (PMDG House instead of my usual Air Canada one) and got the exact same problem. At least, your video shows me that it should work. I am running Prepar3Dv4 with the latest Hot Fixes for both P3D and the 777, but the problem was already present before those updates. To add to the puzzle, I have the same problem with the 777 in Prepar3Dv3 (but not with the NGX). I initially used AIRAC cycle 1509 and recently installed 1707 and encountered the problem with each one, so I can probably discard the AIRAC content as a possible cause. My conclusion is that there must be something in my setup that is creating the problem. I am tempted to uninstall and re-install the 777, but having read Kyle often say to others that it is not the best way to try and correct a problem because it may sometimes introduce new problems makes me hesitate. So I am back to the drawing board, but have no clue as to what causes the problem. Hi Dan, I initially had DOOBI and ILS26L selected. When I tried to change for GESNER and ILS08L, I selected ILS08L first (which was added to the LEGS page) then tried to select GESNER but got an (Invalid entry). Being unable to select GESNER, I end up with DOOBI.26L and ILS08L in the FMC, with a DISCO in between (the DISCO is normal and expected at that point). Since I cannot change the STAR, the most logical step is to re-select ILS26L and carry on with the DOOBI arrival and ILS26L. At this point, I don't know what else I can try to solve the problem. I want to thank you all for the time spent at trying to help me, I really appreciate it. In my 32 years of FlightSims, including many years with PMDG aircrafts, this is the first time I just "don't know what's going on". I will come back to this tread if I find the solution. Best regards and appreciations.

Hi Andy, doing it before reaching TOD works as intended indeed. I can change STAR and approach at will until TOD. But past TOD, the 777 won't let me (Invalid Entry when selecting a different STAR, even with the same entry point and even if the next 4 waypoints are common to both STARs). What I am trying to simulate is a sudden change of active runway occurring during the descent (which I often saw happen in real life), requiring me to select a different STAR and approach (Lets say I am some 30 nm out at about 10,0000 ft when that occurs, already setup with a STAR and approach, but must change it). At that point, I am way past TOD. I can select any other approach I want, but cannot select the STAR connecting to that approach (= Invalid entry). I am stocked with the STAR I selected before TOD. I know I should not compare the 777 to the NGX, but just for the sake of the discussion, I can do it in the NGX, so I figure there must be a way with the 777 also. I just haven't found it yet. It does not matter if I select the new approach or the new STAR first. The result is the same (Invalid entry). Dan, I tried that route to KIAH and encountered the same problem as anywhere else. I flew from New Orleans (KMSY FL300 J58 AEX DOOBI arrival for ILS 26L at KIAH). I was able to change the STAR and approach at will, back and forth many times (having to rearrange the route of course to remove the DISCO) until reaching TOD (which was past AEX). At TOD, I was setup on the DOOBI for ILS26L but once past the TOD, no way it would accept the GESNER for ILS08L (or any other STAR), but it accepted the ILS08L approach which I activated. So I ended up with the DOOBI arrival (for runway 26L), and the ILS 08L selected. I opted to reselect ILS 26L and land on 26L. Flying on HDG and FLCH while I try to make the change (vs remaining on LNAV/VNAV) did not change the result. If you have the chance to try it as I did, I would be curious to know if you succeed or not (don't risk scrapping an important flight for this though). If you succeed, then I'll know for sure that the problem is ME. Best regards to both of you.

Hi Chris, Based on the way I explained it, you understood correctly. But I found out I was not 100% correct in what I wrote. I initially thought that by not being able to change the STAR, I was committed to that runway. It did not occurred to me to try and change the approach instead of the STAR. Here's what I discovered tonight. I just flew into CYUL on the OMBRE4.24L STAR with ILS 24L selected. Past TOD, I tried to change the STAR to OMBRE4.24R and got an "Invalid entry" (So, cannot change the STAR). But if in the ARR/DEP page I leave the STAR OMBRE4.24L alone and instead select the approach ILS 24R, it is accepted with a "route discontinuity". The fixes for the ILS 24R replace those for ILS 24L in the LEGS page (they are added at the end of the STAR itself, following the discontinuity). At that moment, I must simply decide when to leave the STAR leading to runway 24L and proceed direct the IAF for the ILS 24R (correcting the discontinuity by making the first fix for the ILS 24R active). Edit: Forgot to mention that even after activating the ILS 24R approach, it is still impossible to change the STAR leading to 24L (Invalid entry). It is not too bad when changing from the left side to the right side of parallel approaches, but it might be a bit more inconvenient when changing from lets say, 06L to 24R (opposite sides of the same runway). Then I need to be vectored because my only valid waypoint reference becomes the IAF for 24R. I hope I explained myself better this time. Nonetheless, I really enjoy flying the 777. It keeps my "grey matter" active. Cheers,

Hi Chris, That is a possibility I haven't thought of. I'll experiment with it to see what can be achieved. I've noticed so far that as long as I enter a STAR before reaching TOD, I can later (past TOD) change the approach if it is part of the choices for that STAR, but I cannot change the STAR itself. For example, on a HABBS3.24B STAR, I can initially set the approach to be ILS 24R, and later change it for RNAV 24R or even ILS 24L (because of B for Both), but if the STAR says HABBS3.06L, I cannot cannot change it for HABBS3.06R. I am committed to an approach on 06L if I want the FMC to do the job. Thank you for the idea, I'll try different things that will surely better my understanding of the 777 systems. Best regards,

Dan, I appreciate your point of view and the normal procedure you describe is pretty much what I normally do too. But when I feel comfortable enough with the aircraft’s systems in performing normal and well planned flights with no surprises, I like to add unexpected changes to the experience such as route change, weather avoidance deviation and last minute runway change, especially at airports I am very familiar with (things I have seen very often during my ATC career). Doing this brings me a deeper understanding of the aircraft possibilities and limitations that I don’t necessarily grab after reading the FCOMs and other manuals. What motivated me to post on the subject is simply my surprise of not being able to modify some aspects of the automated flight past a certain point. I was not expecting that limitation and I wanted to know is it was normal with the 777 or if it was me who missed something important in my reading, because as an ATC, I never heard a 777 pilot say something like “We need radar vectors then” after I issued a modification to the runway in use just before handing him over to the approach controller, forcing him to select a different branch of the STAR (HABBS3.06L vs HABBS3.24B for example). The reference I made in my initial post regarding the lack of speed/altitude prediction after T/D might give a wrong impression. It was the result of a test I made by voluntarily delaying the data entry in the FMC, just to see what the result would be (I was expecting a different result, obviously). I guess I’ll just have to keep doing normal, well planned in advance and uneventful flights with the 777 ;-) Thank you again for your point of view. Best regards,

Hi, After flying several flights with the PMDG B777-200 LR, I have noticed that if I don't have yet selected a STAR when reaching T/D, I am unable to do so afterwards because it results in an Invalid Entry message on the FMC. There is also no speed/altitude prediction displayed on the LEGS page for any FIX remaining past the T/D (true in both P3Dv3 and P3Dv4, on both B777 v1.10.8333.0 and v1.10.8363.0). In the NGX with P3Dv3 (Patiently awaiting the NGX 64-bit version), I can fly past the T/D and even fly past the last FIX on the route (no STAR pre-selected and flying on HDG mode once past the last FIX), and still be able to select a STAR, set the next waypoint ahead as active, re-engage VNAV / LNAV and resume navigation on the STAR. But not so with the B777. Is it an intended limitation on the 777 or is there something I am missing ? I am interested in knowing if I can change this behavior on the 777 because before departure, I prefer to enter the route up to the first STAR transition fix only, and wait closer to the airport to select the STAR since there are many destinations where the STAR starts so far out and selecting the right one is runway dependent but you are not yet in range of the ATIS to confirm what runway is in use (I know, I could guess it by looking at the last Wx report, but ...) Thank you in advance to anyone having an idea on this.