pilot87

No problems! Glad I could help.

Hi Greg, They're .ini files contained in the main installation location: [Main Simulator Install Directory - Prepar3D vX or FSX]\PMDG\PMDG 737 NGX\Aircraft You should find a list of .ini files with file names that match the aircraft registrations of those installed. I've not had a situation like yours before, but sometimes when things have updated, the OC has asked if I wanted to repair the installed liveries. In this case it appears to have created it's own backups. Have a look in the above folder - you may be lucky!

Haha as long as they model the engineers to come and fix it as well! Sloping runways would certainly be interesting. In any case, if you happen to do an update at some point it would be something I'd like to put in a request for. If not, then no big deal 🙂 Thanks Bryan.

Absolutely that's an option. In reality though, leaving flaps out for longer than necessary exposes them to stone damage (especially at regional airports). Doing that would also delay the start of the APU. Most regional airports in Australia don't have ground power, so the APU is the only option. Airline economics are built on speedy turn-around's so delaying the shut down for the APU spool up would not be desirable. Much to the frustration of most working pilots in Australia, we do things a little differently down here (including limited taxiways). A lot of regional airports too, will only strengthen the taxiways directly in front of the terminal meaning even though a taxiway may be available at the end of the runway, it's quite often weight limited to <5700kg (12,500lbs) MTOW. The only airports in Australia owned by the Federal Government are military, and the rest are either in the hands of local councils or private ownership. This generally restricts the infrastructure works to top priority or legislated items. 90% no backtrack may be accurate for the rest of the world but probably not in Australia. A quick look through my charts reveals that the capital cities are the only airports that don't require a backtrack. Even Canberra (YSCB) airport requires a backtrack for anything bigger than a 737. If you include a requirement to backtrack for departure I would say that figure would fall to as low as 50% (possibly lower) of cases where backtrack is not required. I know in the world of simulation it's a bit of a mute point as there's no stones, no repercussions for taking a taxiway not rated for the aircraft type and AI traffic doesn't react to strobe lights anyway so the fact of turning them on is in some cases just "eye-candy". I guess the question is always going to be how far do you want to take the realism whilst keeping the perspective that it's only a simulation on a desktop.

And this is what I normally do, unless they're not listening which is the case I had yesterday - I will need to investigate further. Completely understand. As I said it's in no way a big ticket item, but just thought it was worth a mention for any future updates for both aircraft types. Cheers,

Thanks Bryan - I don't think it was actually detecting my voice so I'll have to have a look into it. But handy to know regarding the conditional requirements. How about preventing the FO from switching them off in the after landing scan-action-flow in the case of a runway backtrack after landing? Using Ballina-Byron Gateway (YBNA) as an example (located on the far North coast of New South Wales, Australia). The airport is regularly visited by both 737's and A320's. Due to the location of the terminal and the landing distance required (LDR) both types will roll to the end of the runway, before backtracking to taxiway Bravo (preferred exit) or Alpha. In this case you would want to begin cleaning up the aircraft after landing but not turn the strobes off until clear of the runway. Currently all the SOP's for the A320 and NGX have the FO turning off the strobe lights in the after landing scan-action-flow. Whilst this is appropriate at most major airports, it wouldn't be in an airport such as the above.There would also be a preference to commence cleaning up the aircraft prior to exit (i.e. not backtracking the entire runway with flaps at full and spoilers deployed) and starting the APU during the backtrack as the alternative would be sitting on the bay for 3 mins waiting for the APU to come online. Departure is obviously not an issue as you can simply state "Set strobes on" (as per the manual) prior to entering the runway. Incidentally the above is not an issue with the Q400 as the Captain controls all the lights. Princess Juliana, St. Maarten (TNCM) is another that springs to mind where there is no taxiway at the end of the runway requiring heavy jets to backtrack to the airport terminal apron. As I said before, it's certainly not a show-stopper but I thought it was worth mentioning. I thought perhaps an option in the approach briefing section to leave strobes on after landing? Cheers,

Hi Bryan, Just had a query regarding strobe lights in the after-landing clean up phase. I'm not sure what it's like in other countries, but in Australia 737's and A320's are routinely used to operate to a number of airports that require backtracking the runway after landing. Currently the FO turns the strobe lights off as part of their after landing flow. Is there a way to prevent them from doing that? If not, is it possible to have added at some point in the future? It's by no means a show stopper/urgent and I simply turn them back on myself, but would be a "nice to have" feature. Perhaps an option as part of the APP brief data? (I do know you're super busy at the moment!) I noticed on a flight today that when the NGX is in "Lights and Doors" mode (SOP 1) it wasn't registering my request for "select strobes on" either. Perhaps I'm not doing something correctly? Cheers,

No problems at all!

Hi Zoran, Navigraph changed the mappings slightly so you may need to check that. From Navigraph's support forum they suggest the following: Open "Navigraph FMS Data Manager" Delete all PMDG entries from the "Addon Mappings" tab Click "Save" Once saving is complete, press "scan" All PMDG entries should be back. Once they are, select "save" again (result should be <P3[Version Number]>\PMDG\ or <FSX>\PMDG\) Return to "Addon List" Tab and try the NavData update again. You can also check if the correct AIRAC is installed by going to the PMDG folder in the main simulator directory --> NavData and open the "cycle_info" text document. As at 18JUL18 0310z, it should state: There's a new cycle due shortly so the above information will obviously change when that occurs. Hope that helps!

Hi Dorian, You will need to submit a support ticket. The official support system can be found at https://support.precisionmanuals.com If you have not used the portal before, you will need to register (registration is separate and independent to any store account you may have). Even though PMDG staff do post here, the forum is aimed mostly at user-to-user support. Kind Regards

Hi Larry, I do not speak on PMDG's behalf, however based on my time in the forum and other similar posts my recommendation would be to submit a ticket within their support portal. That can be found at https://support.precisionmanuals.com/Main/ If you have not used the portal before, you will need to register (registration is separate and independent to any store account you may have). This forum is mostly for user-to-user support, whereas the support portal is their official contact line so you'll be more likely to get the attention of someone who can assist. You may not be aware of PMDG's forum rules requesting that all users sign all their posts with their first and last name. It's highly encouraged to set up a signature block in your Avsim profile. Best of luck - always worth asking the question as you won't know if you don't ask.

Under Australian flight rules, an Air Traffic Controller can descend an aircraft below an MVA by use of the term "visual" appended to the end of the instruction (i.e. "descend 2,100 visual"). They can only do it if the pilot has previously reported "visual" and terrain separation then becomes pilot responsibility. So in that circumstance it's always a good idea to have a quick look out of the window before reading it back to make sure you're happy to accept that clearance. As a side note, I've got in the habit of checking the turn even before spinning the heading bug on a radar vector. ATC can't see where the clouds are and are usually accommodating to adjust a radar heading if required. Obviously thunderstorms are a different matter but summer fair weather cumulus will give you a bit of a kick under the wings as you go through them so I generally try to avoid them if I can. A smooth ride is as much a part of an airline pilot's job as getting the passengers to the destination safely!

If you are asking about PMDG products, then no. The statement made by Jonathan above is correct. If you are asking only about FS2Crew then there was a small discount available - I'm not sure whether it's still active, Bryan will have to answer that. But you can find the relevant information for the NGX here (under topic "discount code") and the 777 here (note number 3). Note: These discounts only apply to FS2Crew purchases and do not apply to the actual aircraft built by PMDG. FS2Crew build products that integrate with PMDG aircraft but are not affiliated with PMDG other than being a recognised "Partner Product."

Thanks Bryan! As I said I knew I had to be missing something! I knew I'd updated as that was required for the latest NGX install anyway, but I must have missed an update. I gather the 777 and NGX use different infrastructure if the 777 was working ok? Thanks as always for your speedy support! Cheers,

Hi Brian and all, I purchased and installed the FS2Crew NGX Reboot today for P3Dv4 along with the 777. Both installers run as administrator and P3Dv4 also run as administrator, with the 777 working as advertised. The NGX will accept voice commands and respond, however the FO will not actually action any items (neither physically or any sounds of levers/switches moving). The log within the manager confirms that the commands have been received. I have the latest version of P3Dv4 and have attempted to repair the installation of both the NGX and FS2Crew. I have also tried completely removing and reinstalling FS2Crew. I have also confirmed that SDK broadcast setting is correct and the FS2Crew NGX panel entries are correct. System check results are as follows: I have had FS2Crew for FSX, FSX:SE and P3D v2 and v3 and never had any issues to date so I am positive I must have missed something somewhere. Any thoughts or suggestions? Cheers, Haydn