tbarker1989

Bryan, Will we be seeing an update to the 777 interface anytime to bring it in line with the NGXu and QOTS II? Thanks, Tim

That tool was very powerful in my opinion Kyle.

The 5Y is the company code/AIRLINE ID. That would be the code you would put in the PREFLIGHT page in the ACARS. This doesn't do anything now but later I believe this will have greater implementation with GFO and with certain dispatches and what not but I may be mistaken.

okay, I figured I would ask. Thanks for the help. If you need some help beta testing. I can be of assistance. I have assisted Byork with FS2Crew Products.

write it up in the log and fly that bad boy!!!

In the Flysimware LJ35, This is the lights section from the aircraft.cfg screen. [LIGHTS] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logo, 10=cabin light.1 = 10, 10.80, 0.00, 1.4, fx_vclight light.2 = 10, 6.80, 0.00, 1.4, fx_vclight light.3 = 10, 3.00, 0.00, 1.4, fx_vclight light.4 = 8, -1.00, 0.00, 1.4, fx_vclight light.5 = 9, 11.70, -3.70, -0.9, fx_vclight light.6 = 1, 0.0, 0.0, 0.0, fx_NONE light.7 = 2, 0.0, 0.0, 0.0, fx_NONE light.8 = 3, 0.0, 0.0, 0.0, fx_NONE light.9 = 4, 0.0, 0.0, 0.0, fx_NONE light.10 = 5, -0.00, 3.95, -1.2, fx_landing_3D_FSW light.11 = 5, -0.00, -3.95, -1.2, fx_landing_3D_FSW light.12 = 6, -0.00, 3.95, -1.2, fx_landing_3D_FSW light.13 = 6, -0.00, -3.95, -1.2, fx_landing_3D_FSW light.14 = 7, 6.00, 17.80, 0.4, fx_landing_3D_FSW light.15 = 7, 6.00, -17.80, 0.4, fx_landing_3D_FSW

Is this typical to have FSReborn lights on my aircraft? I get this on default aircraft and a couple of payware aircraft like the TFDI 717, Flysimware LJ35, Flysimware FA50. Thanks

Robert, That is understandable. I can agree with your conclusion. I wasn't saying it "must be" in the installer. I said "may be". I can agree to your animosity that most users on here have. I wasn't intending to throw blame or anything like that. I can agree that something did mess it up but I cannot tell you with 100% what did. I am a PMDG Fan. Hopefully, all is well.

I just ran across this issue as I do not fly the NGX much anymore. Mine was caused by missing a <Launch.Addon> for the PMDG HUD Interface. I believe this to be a bug in the most recent installer. Mine was this. <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> </SimBase.Document> <Launch.Addon> <Name>PMDG Interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <---------This was missing!!!!! <Name>PMDG HUD Interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> This was causing the rest of my entries to not be started due to this error. I added the <Launch.Addon> entry after the </Launch.Addon> and it loaded correctly.

Converting to use the updater was a great idea! Not having to download the installer every time for a new update is great!

That is true and only time will tell.

That is understandable Marc but due to limitations and such that is the best that could be came up with. Is it an inconvenience? Slightly, does it get the job done? Yes.

I have flown it with the 747-8 and in fact tested it for Bryan, it isn't much of a hassle to go through the ECL during the time you are going through the checklist with the FO. it is an easy click click click and you are done with it for that checklist.

Pauly, you my man are a real G and you know what you are wanting out of your 747. Attempt to taxi a little slower and attempt to use little to no braking this should help with your overheating issue. Yes, it is possible I taxi with little to no braking but I am also not taxiing like southwest. That is if you want to not cook them but hey, you do you and have fun doing it. 🙂

That is some kind of installation issue, maybe a bug. I have had that and once I do a reinstall it works fine after.

Sounds like to me that Pauly is a real G. Hahahaha

The FMS did eventually right itself when I was no longer speed restricted. After the inital climb I was speed restricted to like M.865 or so with an increase in speed every so often. I was set for M.88, once the aircraft was able to do M.88 it righted itself and showed FL430 instead of FL400.

Kyle, I am following what you are saying! About the releasing information, I will take all the updates you have to offer. Heck slide me a few under the table too (I won't say a word to anyone). More information in my opinion is better than no information. I understand development takes time and kinks come in the way. I was just testing a piece of software recently and I cannot tell you how many times I tested 1 minor thing for it to execute as expected.

I put that in trying to diagnose the problem. It was set to RVSM before. I changed that after I got up the FL430.

I took off from KEDW to PHNL. My initial altitude was FL380. I had an initial step climb planned to FL400 and a later step climb to FL430 along the flight. I stepped up to FL400 with no problem. I then step climbed up to FL430 when it said to but when I dialed FL430 into the MCP it changed to showing this. Later after I was no longer speed limited it corrected itself to showing correctly. Is this proper operation of the FMC?

With global flight operations, I understand that with persistent aircraft that a person may fly an aircraft for instance with an INOP APU. Will this and similar situations be displayed in the Panel with a MEL sticker?

Check the FS2Crew FB Page. www.facebook.com/fs2crew/

Sounds good. Thanks for the update.

I did some further testing in an attempt to assist with the issue. I tested these aircraft with the following results: 747-400 & 747-8 - OUTBD L and R, INBD L, Beacon, and Nav provided updates. INBD R, rwy turnoff L & R, taxi, strobe, wing and logo provided no updates. The wing and rwy turnoff lights aren't an issue 777-300 & 777-200 - Landing L, N, and R, Beacon, and Nav provided updates. Rwy turnoff L & R, taxi, strobe, wing, and logo provided no updates. The wing and rwy turnoff lights aren't an issue just like in the 747. 737-800 - Fixed landing gear, taxi, logo, anti collision, and position all provided updates. I was by myself so I could not verify that the Position light on steady was nav lights only and on strobe and steady that it was nav lights and strobes. Retractable landing, runway turnoff, wing and wheel well lights provided no update which isn't an issue for the application. Based on previous aircraft tests being the same I only tested one version of 737. Based on my results I believe the 737 is fine where it is at. It could be added to the retractable if you wanted it to be symmetrical. I know some of the information that I provided is not needed but might as well be thorough. All aircraft are the current release versions. I hope this is beneficial to the process Thanks,

Per PMDG Forum rules, you are supposed to sign your post with first and last name. I believe the AUTOLAND option is like a logbook entry which will be later further expanded upon in Global Flight Ops.