September 6, 201213 yr I had the 737 NG working for about a year, then I recently had a hard disk crash and had to reload FS9 and the 737. I set the default Cessna to have the avionics switch on, battery on, and engine off, then loaded the PMDG 737. With the battery switch on, the main panel is dark but the switches work. Even after starting the APU and turning on the APU generators, the main panel is still dark. This keeps me from starting the engines as I can't see N1/N2 to know when to move the throttle levers on. Should the main panel be on with just the battery switch on? I can't remember. Is this a known bug?
September 8, 201213 yr Author I had the 737 NG working for about a year, then I recently had a hard disk crash and had to reload FS9 and the 737. I set the default Cessna to have the avionics switch on, battery on, and engine off, then loaded the PMDG 737. With the battery switch on, the main panel is dark but the switches work. Even after starting the APU and turning on the APU generators, the main panel is still dark. This keeps me from starting the engines as I can't see N1/N2 to know when to move the throttle levers on. Should the main panel be on with just the battery switch on? I can't remember. Is this a known bug? I am reposting this because I forgot to mention that this is a Windows 7 system. Has anyone had problems with the legacy 737 on FS9 under Windows 7?
September 9, 201213 yr Author I am reposting this because I forgot to mention that this is a Windows 7 system. Has anyone had problems with the legacy 737 on FS9 under Windows 7? For anyone who has this problem in the future, I solved it by reinstalling the latest version (3.999) of FSUIPC. The version that I had installed (3.50) was either corrupted or incompatible. The PMDG support web site does list this as a solution to the blank screens I encountered.
Create an account or sign in to comment