freded

I have been following this topic and wonder if regenerating my Prepar3d.cfg file will correct another problem that I have. Going into Scenery Library, I see that, in many entries in the Enable column, the box is greyed out. This only applies to entries that are enabled (and not all of them) and this means it is not possible to select these entries in order to Move, Edit, Add or Delete the area. Is this due to some fault in my setup or is it a 'feature' of P3D 4.5 HF1? If the former, what is the fault and how can I fix it? If the latter, why is it happening? Another 'feature' of P3D 4.5 is that there seems to be no correlation between Scenery Library and Scenery.cfg. It used to be possible to manually edit Scenery.cfg and the result would appear in Scenery Library. But if this is attempted now, P3D freezes and demands to be restarted. I assume LM must have had a good reason for making this change but it's very inconvenient! And some scenery programs, e.g. Orbx, have a nasty habit of forcing their entries to the top of Scenery Library - can this be stopped/corrected? I hope someone can answer my questions! Thanks for any help with these problems... Mark

Thanks, downscc, for your reply. To answer your points:- 1. "Auto Cruise" is the term used in Tutorial _1. 2, Yes, it's "AUTO TIME COMPRESSION" on the Auto Cruise page of the FMC. 3. I have selected the rate of x4. 4. Weather is stable with a tail jet stream of 167 knots. But I have found the answer... I went back to the Auto Cruise page and clicked on RESET and Hey Presto! Auto Cruise engaged. I have never encountered this before and I've used the process many times on other long flights. Sorry to have troubled you. Perhaps this thread will help someone else with the same problem. Regards, Mark

Up to yesterday, PMDG B-777 Auto Cruise was working perfectly, but now, in spite of flying straight and level at a constant speed, I cannot make it engage. I have tried using both the method of right-clicking on the clock and also setting AUTO TIME COMPRESSION to 'ON' in the FMC. Neither of these will turn on Auto Cruise. Any ideas, anyone?

During a long flight I had to change my destination to an alternate and now, approaching this airport, I cannot see how to tune the NAV radios to the ILS localizer frequency. When I press NAV RAD, the VOR L and VOR R have frequencies allocated to them, but ILS just says 'PARK'. How can I make the NAV show any ILS frequency? Mark

Hi Michael, Your suggestion of an auto-save program proved to be the answer to the pauses. I eliminated Avast as the cause by excluding all folders related to P3D. I then opened the FSUIPC window under Add-ons and changed the setting from 60 secs to 180 secs. I've just timed the interval between pauses and - guess what! - it's 3 minutes. Thank you for your help. I'd never have thought of that by myself. Cheers, Mark

Hi Dan, I'm sure you're right, that it isn't the FSDT version of Vancouver that is causing the pauses, because they are still appearing when the 777 is a long way away from CYVR. As for Windows Defender, it is not enabled on this computer at present, because AVAST Security is taking its place. Maybe that's what is causing the problem? I'll check... Thanks anyway! Cheers, Mark

Hi Andy, Many thanks for your very clear & concise reply. I'll have another go at it and try line-selecting the next waypoint and copying to the top of the plan. Are there in fact any ATC addons that are aware of SIDS and STARs? Cheers, Mark

I'd appreciate some advice on 'VECTORS'. I have set up a flight from Vancouver BC (CYVR) to Sydney Australia (YSSY) and the Route starts with three VECTORS waypoints. I have no idea how to deal with these. The flight starts at Runway 08L and the first Vector is on a heading of 083, which makes sense, but the aircraft simply heads in that direction for 'ever'. It does not switch to the next Vector or continue with the route set up in the FMC. I tried using ATC to direct me to Sydney but was unable to make the 777-300 capture the route, as I am used to doing with a FSX/P3D flight in other aircraft. Any suggestions?

I am suddenly encountering frequent pauses, lasting a few seconds, of the 777 in P3D version 3.142. This didn't happen originally with this aircraft. Could it be due simply to changing scenery from Dulles to Vancouver, BC? The frame rates have also declined. Both sceneries are enhanced above the default ones. Vancouver is by FSDreamTeam.

Yes, a typo seems very likely, although it says: "... The ANOR2A approach ends at MIQ, which is a transition for Runway 26L. In order to provide a more complete picture, though, we have requested and have been approved for 27L." So who knows?! I don't know which AIRAC was used when the Tutorial was made. I am using an up to date version from Navigraph. Thanks again for your help.

Hi Romain, Thanks for replying so quickly! So I guessed correctly about the STAR renaming. But still don't understand why both 26L and 27L are mentioned on the same page. I see that the magnetic variation would result in the runway denomination changing over time and it's probable that this had happened since AeroSoft created their version of EDDM (in 2015). But this still doesn't explain why Kyle used both codings! So I'll use ANOR3A and ignore '27L'.

Tutorial 1.5, pages 53 & 54, mentions ANOR2A approach for EDDM, but there is no ANOR2A in the EDDM ARRIVALS on the CDUs. There are 32 STARS on the 7 pages but the only ANOR** approach is ANOR3A, which shows up twice - once for NDM08L Approach and once for NDM08R. Is this because the latest Navaid has changed the name? The other problem, also on Page 54, is the mention of "Runway 27L". No such runway exists at EDDM, according to the 'AeroSoft Mega Airport Munich' Charts.pdf, which shows only Rwys 08L, 08R, 26L & 26R. Should I therefore choose ANOR3A for the approach and ignore the mention of '27L' ?

Thanks Michael, I thought PFPX sounded familiar... I found it on my computer - I had installed it last September ! I'll give it a go. Thanks also for the method of creating routes in the FMC. I must get down to reading FCOM 2.

Thanks Michael, for the congrats! Yes, I do persevere - though my wife calls it stubbornness! I think when I've completed Tutorial 1.5's flight (she's off the ground now & heading fo SWANN), that I'll try a different route, using Tut. 1.5 as a guide. But how do you import/create a flight plan for the 777? Can you import one from FSX/P3D? Or make one complete with SID & STAR from inside the FMC? I can't find anything describing this in the Tutorials or in the Introduction.

Hooray! I've got her on Runway 30 at last! Now to actually fly the Triple-Seven...

OK. Panic over! I looked in the Introduction.pdf, on Pages 157/8 and played about with various LSKs on the RTE page of the FMC. I had already filled out the ORIGIN & DESTINATION fields, so I entered '30' in LSK 2L and pressed ACTIVATE, then EXEC lit up, so I pressed that. Now I have the Flight showing on the ND and can continue with the Tutorial... What exactly I did to achieve this is a mystery! :smile:

Hi, yet again, For the nth time, when CAREFULLY working through Tutorial 1.5 I have managed to evoke that dreaded 'NO ROUTES AVAILABLE' error message in RTE 1 1/2. This is at Page 31 of the Tutorial, where it says: "Go to the RTE page, enter PFO103 (PMDG Flight Ops 103) in the Flight Number field, and then press <REQUEST.". I have checked that PFO103.RTE is present in folder ...\Prepar3D 3.4.18\PMDG\FLIGHTPLANS\777, and I have not got that disastrous 'Estonia' program on my computer. So it must be something else. All steps prior to the ROUTE REQUEST had been completed exactly as the Tutorial instructs and I had successfully completed (also on Page 31):- "-Turn on the ADIRU. "-Line select the GPS position and place it into the SET INERTIAL POS field of the INIT REF page." So why is my REQUEST for the Flight not working? Forum members may remember my posting this same query several months ago, to which there was a number of suggestions - none of which worked for me... Perhaps I'll be luckier this time?! By the way, I notice that there is a possible mistake in the screenshot of RTE 1 on Page 31 of Tutorial 1.5. Under FLT NO it shows "PFO13", although the name of the Flight Number is actually 'PFO103'. Probably an insignificant thing but I mention it in case it's relevant to my problem.

Hi Pete, Thanks for that! I'll give it a whirl. I'm in the middle of working through Tutorial 1.5 again and hopefully I shan't have the same problem this time. But if I do I'll try Capt Myron's method. Hi Dan, The error happened on page 28: "Set the chocks, release the parking brake, and connect the GPU and air conditioning unit." When I was up to Page 37, I noticed that the refuelling was losing ground to the APU , so I turned it off not realising that the GPU was off-line and so all power was off... Restoring power with GPU brought all gauges back to life except for the ones I mentioned.

I must admit not having even glanced at the two FCOMs. It seemed a bit like overkill and FCOMv2 has over 1200 pages! However I'll now bear them in mind if I can't find what I want elsewhere. As there seems no way to simply correct the problem I have, I guess I've no alternative but to start Tutorial 1.5 again from the beginning with the Cold&Dark state, as mentioned in that Tutorial, Page 9, 'Arriving at the Hangar'. Thank you everybody for your invaluable input on this subject. If anyone happens to come up with a way to re-energize the DSP and FO's EFIS, please let me know. :smile:

Yes, the DSP is apparently the correct name for the panel containing the selection buttons for the ECL display, and the FO's EFIS panel for the other one. But I was unable to find (by doing a Search in them) mention of these names in either the Introduction or the two Tutorials hence my long-winded descriptions! The Panel State was originally the Default one and then I saved the Scenario at the point where I ran into this problem so the State is now named 'PMDG B777-200 at Dulles KIAD 2.fxml.sav'. I have since used a 777 CLDDRK.sav state for the next time I start with Tutorial 1.5.

Jim, I kept a record of what exactly I did as I worked through Tutorial 1.5 and I see that I did NOT select the APU before disconnecting Ground Power! This was because I was concerned that UPLIFT FUEL up was losing ground to the APU's thirst for fuel, so I turned it off. As Ground Power was already disconnected, I saw that ALL the FO's panel displays had blacked out so immediately re-established Ground Power, which caused the PFD and ND to turn on. Obviously, in hind sight, this was what caused the two panels on the FO's side to lose their functions. BTW, you say '747' and talk about 'at least one APU generator'. Only one APU generator is shown on the 777's Overhead Lower Panel... Is there another one that I haven't found? It was my mistake not to have connected the Ground Power before starting the APU and its generator. Is there some way I can now restore the function of the two panels that have gone off-line? To make it quite clear which are the non-functioning panels: They are the two at the extreme right-hand end of the glare shield, above the FO's ND & PFD. One includes the selection buttons for the ECL display and the other the Barometer, Minimums and Range knobs, etc.

Dan, EFIS CTL is OFF, but there is no entry for DSP CTL on the MENU screen.

Well, That didn't work. If it's any help, Fault Messages are showing:- ENGINE SHUTDOWN INSUFFICIENT FUEL FMC MESSAGE DISPLAY SELECT PANEL EFIS CONTROL PANEL R TCAS OFF Is any of these relevant to my problem?

Thanks Dan, for your suggestion, but I can't get the synoptic to change from FUEL to ELECTRIC because it's not responding! In any case, as it happens, I've just been presented with a VAS error and have had to close P3D. I'll try reloading the saved scenario and see if restoring Ground Power will fix it.

Hi, I am working through Tutorial 1.5 (yet again!) and have got to Page #38, with more success than ever before. But now I have encountered a serious problem. Here's where I am at:- Page 38:- - Remove CHOCKS, this disconnects AIR and GPU. (APU is running) - Run the BEFORE START checklist. But I cannot change anything on the ECL, because the control panel on the FO’s side of the glareshield has become inoperable - so have all the knobs and buttons to the right of it... Nothing I have tried will fix it. So it's stuck at FUEL. I've tried closing P3D v.3.4.18 after saving the 'Scenario' and then reloading P3D and then that Scenario again, but the two panels are still frozen. If I close P3D and reload it and select the 777 in the same location (Dulles KIAD Gate C2), everything works perfectly. But, of course, I've lost where I had got to in the Tutorial! Any ideas as to why this is happening? The affected instruments were working OK until they suddenly failed. Better still, has anyone met this problem before and found a solution?