J737NGX

I will try. Just please add notes about it into your Quick Troubleshooting.txt also temporary meanwhile for new users

byork I found the root cause of this problem. Every user who have FSUIPC 7 for MSFS installed as auto-start with MSFS have the similar problem. I also get the Application Error popup window with: Exception EDOMParseError in module fs2crew_fbwa32nx_autostart.exe at 001E2CF6 A name contained an invalid character. Line: 2 <SimBAse.DocumentType="Launch"version="1. That is caused by FSUIPC7 not use CR+LF on end of each line. Here is how looks like in Visual Studio Code (my xml editor). I try to format as visible the original EXE.xml after FSUIPC installed 1 <?xml version="1.0" encoding="Windows-1252"?> 2 <SimBase.DocumentType="Launch"version="1,0"><Descr>Launch</Descr><Filename>EXE.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Name>FSUIPC7</Name><Path>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole></Launch.Addon></SimBase.Document> 3 The 2nd line without any tabulator or CR+LFs on end of the each closed blocks. Mytragina fresh line correct for FS2CREW autostart, but not the FSUIPC7 due those autostart missing from that. Here is my correction. I deleted the EXE.xml recreated with FS2CREW how you wrote above and simple added the FSUIPC Addon part with tabulators and CR+LF end of each line. That is started correctly error free. Here is the screen from my Visual Studio Code in temporary format mode: 1 <?xml version="1.0" encoding="Windows-1252"?> 2 <SimBase.Document Type="Launch" version="1,0"> 3 <Descr>Launch</Descr> 4 <Filename>exe.xml</Filename> 5 <Disabled>False</Disabled> 6 <Launch.ManualLoad>False</Launch.ManualLoad> 7 <Launch.Addon> 8 <Name>FS2Crew Command Center</Name> 9 <Disabled>False</Disabled> 10 <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path> 11 <CommandLine></CommandLine> 12 </Launch.Addon> 13 <Launch.Addon> 14 <Disabled>False</Disabled> 15 <ManualLoad>False</ManualLoad> 16 <Name>FSUIPC7</Name> 17 <Path>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path> 18 <CommandLine>-auto</CommandLine> 19 <NewConsole>False</NewConsole> 20 </Launch.Addon> 21 </SimBase.Document> And in plain text for Ctrl-C/V <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FS2Crew Command Center</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path> <CommandLine></CommandLine> </Launch.Addon> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> </SimBase.Document> At MSFS boot time when the bottom blue progress bar somewhere in middle the the screen change for black (just the blue progress bar visible) that is when FS2CREW loads and I get the FSUIPC7 popup window. You can test and reproducer it easily just download FSUIPC7 for MSFS before install FS2CREW http://www.fsuipc.com/

I can confirm same problems with FS2Crew and EFB (old version 1.3.1).I have test flight between LHBP>LOWW after start landing (samewhere before G/S alive) my EFB Dataprovider collapsed and closed (my EFB never performed before). No problem in middle of landing minimize FSX to find icon on desktop and restart Dataprovider. But be care problem can be related to PMDG SP1c also.Second issue (can be not fully related to EFB) after I park and cutoff my FSX due .NET error also collapsed (happy Microsoft question try to find online solution). That is happend two times.Do I have more add ons (example: REX 2.0OD, EFB, but PMDG base airplane) I am unable to determine problem just with several tests. Example upgrade to new 1.3.2.

Thanks byrok. My problem solved. My SP1c was wrongly installed generate my problem.If I try to install SP1c again not allow they say same version number. But if I follow your instructions works well.The only point what I see difference after install done: FMC/PMDG Simulation just see one FO callouts before and three V1,VR,V2 after that.So my cause was PMDG SP1c not installed succefully. Reinstall solve issue.From another happy FS2Crew customer :(

1) OK I wait for T+0 and then check doors/before start check list3) How can I announce the start sequence in button control version?Airwolfe: Don't worry about ezdok. I dont have ezdok, but I have same problem (unable to start engine 2) as yours. I don't have automatic switch to VC problem.If I understand clearly nobody know what is behind original problem? (in 2D mode also unable to start engine 2)

Hi Byork,I can confirm same problem as reported by airwolfe."Fs2crew for PMDG 737NGX" hmmmmm I am long waited for this add-on. Thanks fs2crew for this development. I am pleasured to buy :Peace:My config:HW: close to nuclear power plan counting capacity :( and controll: Speedlink Black Widow joke+thrust comboi7-2600k 3,4Ghz with 16GB RAM, OCZ Vertex-3 SSD for OS and FSX.SW: OS Win7x64FSX Gold Edition SP1cPMDG 737NGX example 800Winglet modelOther special add-ons:Budapest airport scenery (LHBP) V2 by Andras Kozma, remember for MALEVAivlaSoft EFB not used hereREX 2.0 OV not use hereSteps:- load FS2CREW first, select button control, enable fw2crew button control. OK on confirm screen- click on FSX icon. Win7 inform about back to basic theme (from aero desktop).- Start screen show Trike airplane/Friday Harbor as part of original configuration- My setting contain 2D mode (as already configured for PMDG double checked)- All authorize questions answered (can be two of them at first time after install, not asked any more)- Select PMDG 800Winglet, LHBP as airport Gate 32, and reset to current time.- Push Fly Now.- 2D screen appear- wait for pmdg green boot counter- switch by button "A" to VC mode.- Click on yoke to down and on FMC Load NGX CLDDRK config (original I think never modified), Exec- wait for next pmdg green boot counter.- click on ISFD space to open Fs2crew panel,- right click on hide menu bar (I must to perform two times mouse menu command just after second executed, can be fsx bug?)- fw2crew PWR and LT (because after 20:00LT night) I arrived to PREFLIGHT CHECKLIST- open CFG panel,- change TAIL to RIGHT (instead of LEFT)other settings:onborad speakers, region EU, T+30, APU, AES NO, DOORS YES, GATE DEP/ARR YES both, ASDE-X YESPB YES, dist 80ft, TAIL RIGHT, ANGLE 00 (I know that is will be corrected)- RUN PF clickFO start to work.- close CFGAfter APU power enabled to both bus:- panel light enabled for overhead, main and pedesral panels- both IRS to NAV ( I use button A to scroll for upper overhead panel, due I don't have TrackIR)- back to pilot screen, open via ISFD Fs2crew again (yes I click now on LK to lock panel good future:)- park brake set- FMC init position LHBP and gate 32, route load from Company route active and exec- also config FMC perf init, N1 limit CLB-1 26k thrust, flaps 5, CG by pmdg and all 3 speed ok.- Fligh director ON (just captain)- Load flight plan (use FSX flight plan load, not via EFB)T+19: FO back from walk aroundT+18: Start boarding YESFSX ask IFR clearance and confirm (setT+12: at FO finish preliminary procPrefligh check list COMPLETE until T+11T+10: BR button, Play Brief, NADP1, SID, flaps 5, DRY, A-ICE not req, bleeds on, close BR screen under talkT+9 BR completeT+8 LSheet Thank you.T+3: BEFORE START PROCEDURENormaly AFT and FWD cargo door open and unable to start BEFORE START PROCEDURE. So I close manualy via PMDG FSX action menu.T+2: what is this siren sound after close samething.so start BEFORE START PROCEDUREarm auto thr, MCP IAS=V2, set MCP course 309 on both side (FO not set if I see correctly) and heading also 309, set altitude to 6000 as asked by ATC before), arm LNAV and VNAVUnable to perform Taxi and takeoff brefing (where is this function???)T+1: cabin ready thanksBefore start checklist complettedT (T+1 disappear):CTC ground P/Bready for pushback- release brakes and report backfs2crew show (white START ENGINE 2 and yelow BREKAS SET)From here until plane fully stopped after pushback done (I confirm back BREAK SET) unable to start Engine 2 via same error message by FO. I checked many times in VC mode same issue. I also try to idle-cutoff swap many times but not help.I will check with later on with 2D mode (under all process) and cfg setting IF needed.Do you have any more idea? Can you have any debuging tools to check which config is not acceptable by fs2crew? Any more help can I give you to solve this problem? (I am back at 18 of march from holiday)I am able to start both engine manualy and perform any other steps (until arrive and secure) without any major problem.Jackson, an airplan technician and IT engineer