XCLTM3

I saw someone post on a 3rd party FB page and the news regarding FSLabs and the work they're doing. The post read: "Malware Labs is back". I thought that was hilarious tbh. It indicates that some persons have remarkably good memories in this day and age of speed read and move on. Another Airbus though........market is saturated.

For any painters out there who will be undertaking the task of painting liveries for the new iFly737 Max. Could you please seriously consider "Freedom One" for Southwest. I understand it would be fictional and not realistic. Could be a Paypal tip for it too. Much Obliged. PS: I have posted this on the discord for Flight 1 and iFly. Cheers!

747SP FTW!!!!!

This is why I consider PMDG the best of the best in software development - particularly in terms of flightsim aircraft. To revisit an older software title and rework/revamp it due to discovering reduced memory usage during development of a new aircraft - that commitment walks the talk. Many thanks PMDG team.

For those who may be interested in the latest Boeing 737 release - MAX. http://airwaysnews.com/blog/2015/12/08/first-737-max/

Giddy Up!

Hi Mark, +1 - for the ability to stretch the CDU app. Also, Andre Blossfeld - how did you get the Frameless App to work for the CDU? I tried but was unsuccessful.

Yes, I had the same issue with v 1.0 I'm not running pre-flight events. This issue is occurring when I arrive at a destination gate - once the engines are cut, FS2Crew hooks up the GPU & A/C. FS2Crew then opens the Cargo Doors automatically - but within a short amount of time the doors then close rather then remain open. I observed the FMC/CDU Door Menu and saw it engage and close the doors seconds after opening them. If I choose to NOT have FS2Crew open the doors automatically - and I do it manually, then the cargo doors open and will not close until I prompt them via the FMC/CDU. This is why I suspect that this is a possible scripting issue with FS2Crew which is opening and then closing the doors quickly thereafter. I mean, it's not a huge deal breaker by any means Bryan - but if I can have this resolved it would sure help. Thanks,

1. I'm using SOP1. In future, I'll just set the Weather radar on my side. 2. I don't believe I have any other addon that would be affecting the Cargo Door operation. I guess I could just go back to manually operating the doors - although having FS2Crew carry out the op would be handy. Any chance you can double check the script in FS2Crew just to make sure it's not the culprit?

Hi Bryan, 1. I'm not using a voice command for the prompt - I'm selecting "Weather" under the "Concerns" section of the "Approach Brief". If I select "Terrain" as the concern for either Departure or Approach the FO will display the Terrain radar on his display. However, if I choose "Weather" as the concern the FO still displays Terrain instead of Weather. 2. As I understand it, GSX does not play with the Cargo Door opening or closing script. GSX waits for the user to open or close the doors and then commences it's operations. (ie Cargo loading/unloading, Passenger embarking/disembarking, Catering, etc) Thanks & Regards,

Hi Bryan, thanks for the 1.1 update. I just have 2 issues that require assistance. 1. I've tested this twice now, and it appears that when I request the FO to turn on his Weather Radar via the Approach Brief page, he turns on his Terrain Radar instead. This was the same in Version 1.0. 2. Also, when FS2Crew controls the Cargo Doors, the doors are opened only momentarily (ie several seconds) and then the doors are closed again. This becomes an issue when using GSX.

I just purchased Mark's NGX CDU app and it's wonderful. +1 if he can do the PMDG 777 also.

Thanks for the explanation.

I understand. I guess I could map the resets around my joystick device. From a logical perspective - if we are able to command the PM to reset the Master Caution why not the others? Also, with Emergency NGX at some point to be coupled with Reboot - I wonder if there will be occasions whereby the PM as part of an emergency SOP will be responsible for silencing the various alarms and warning horns including the abovementioned Auto-Pilot and Auto-Throttle?

For example, when I'm shooting an approach going onto final using the HGS, and I've instructed the PM to disengage the auto-pilot and the auto throttle, I don't want to be distracted having to look away from the HGS and push the buttons and silence the warning horns. Why wouldn't the PM do this to assist the PF? What else would the PM be doing at this stage that would be more important? Besides, if the PM can be commanded to silence the Master Caution button, why not these others?

Hi Bryan, congrats once again on reboot - enjoying it immensely! Just wanted to ask you if it's at all feasible to add a few voice commands for the PM? These relate to the 3 warning annunciators located above the ND. I know we can command the PM to RESET MASTER CAUTION - but it would also be helpful to have the PM do the following: RESET AUTOPILOT RESET AUTO THROTTLE RESET FMC Many thanks.

Damn! Andy, you were on the right track. I only checked to see that the VOR 1 on Captains EFIS was "ON" and it was. However, I just started another flight and decided to cycle both VOR 1 and VOR 2 radio switches from ON to OFF to On again and presto! VOR1 started to work again. It may have something to do with the fact that I saved my own panel state and auto start up on that? Perhaps? Lesson learned here....

Thanks Andy, but I did check that prior to posting this.

Hi Romain, I don't use the failure system. To be clearer about the radio - I punch in a VOR or ILS frequency into Nav1 and it is not being recognised at all. No identifier name is displaying, nor any DME. NAV 2 radio is working properly - punch in a VOR frequency, and the identifier and DME displays accordingly.

Hi all, I tried a forum search on this in addition to looking through the manuals but could not locate an answer. For an unknown reason, I can't get NAV1 radio to operate. Whether I input a VOR station frequency or an ILS frequency - it is not responding / working. NAV 2 is fine. Anyone have a clue as to what's going on? I've looked at the Radio Stack and the Overhead Panel and all looks ok.....I'm obviously missing something. Appreciate any assistance.

You're welcome Alan.

Craig & Rafal, the purpose behind my intention was simply that I don't peruse the avsim site throughout. A friend emailed me the thread Tom Allensworth posted, otherwise I wouldn't have known. Ergo, I thought it was quite possible that others here may not know of Tom's predicament if they, like me, only peruse certain avsim sections. eg: I only visit FS2Crew, PMDG 777 & PMDG 737NGX. I usually don't bother with the rest. I hope this has clarified the issue.

http://forum.avsim.net/page/index.html/_/pri-news/words-i-need-to-share-with-our-community-r2864

Brilliant Bryan! Looking forward to it.

Thanks Bryan. 1. Can I ask if you can try to ensure that the commands we give the FO in the NGX mirror those in the PMDG 777? There are subtle differences in text between them relating to the same actions. Would be good to streamline them so that those of us hovering between both the NGX & 777 have a smoother transition. eg: PMDG 777 - Flight Directors ON (OFF) NGX - Select Flight Director ON (OFF) PMDG 777 - Strobes ON (OFF) NGX - Select Strobes ON (OFF) 2. If we could ask to have the increased FO functionality from the PMDG 777 brought across to the NGX - eg: Display Weather on my side, Display Stations on my side. 3. Have the FO calibrate the barometers according to region just like you did with the PMDG 777 (ie USA = inches, Australia = Hectopascals)