Hey everyone,Unfortunately I have a problem with my 737NG. After loading the aircraft into FS2004 the battery is empty and I only get power to the cockpit via Standby Power. I neither can start the APU nor connect Ground Power to the aircraft. This happens for about two weeks now, maybe caused by installing the Captain Sim 757. The time before the 737 was all right.Do you know what I can do?

Hey everyone,Unfortunately I have a problem with my 737NG. After loading the aircraft into FS2004 the battery is empty and I only get power to the cockpit via Standby Power. I neither can start the APU nor connect Ground Power to the aircraft. This happens for about two weeks now, maybe caused by installing the Captain Sim 757. The time before the 737 was all right.Do you know what I can do?

Try Ctrl-E to autostart the engines and then see if the battery is charging. If so, then either you are missing something on the checklist or there is possibly a code conflict.I believe there is a setting in FSUIPC where you can give the planes unlimited battery, so you could try that.John

Hey John,Thanks for your support.

Try Ctrl-E to autostart the engines and then see if the battery is charging. If so, then either you are missing something on the checklist or there is possibly a code conflict. I believe there is a setting in FSUIPC where you can give the planes unlimited battery, so you could try that.

I tried to start engines by using CTRL+E. They fire and there's an indicated power supply by the generators, but I cannot switch the generators to the 'on' position, the switch simply does not come back to its initial position, it gets stuck at the lower position. Also the battery does NOT charge. This is definitely a code conflict. I bought the box legally at the Aerosoft store, so this is not a problem caused by piracy etc.Unfortunately I do not own a registered version of FSUIPC, because the battery worked fine before and there was no need for unlimited battery power. Do you think that there's another way of getting back the power to the battery? If not, I would buy a key for FSUIPC...

You state it worked before the Captain Sim install. If it uses FSUIPC and overwrote the current version with an older one, I suggest you update FSUIPC to 3.90 here:http://www.schiratti.com/dowson.htmlNext according top some postings installation of the CS aircraft can interfere with settings of other aircraft. I'd suggest going through all your FS and FSUIPC assignments to see what has changed. Also open up FS and then the PMDG menus from the FS menu bar and check assignments there. If you go to your FS9\modules folder and temporarily rename you FSUIPC.ini file to FSUIPX.INX it will be replaced with a default one the next time you start FS.A stuck switch can indicate a conflict of button and/or axis assignments. Another problem in some installers is that they go into FS9.cfg and directly change settings there. You could go into your folder where FS9.cfg is as an admin (mine for XP is "C:\Documents and Settings\Ron Ginsberg\Application Data\Microsoft\FS9\FS9.CFG"), and rename it (don't delete). (Make sure explorer is set to show hidden files.) Start FS9 and it will build a new default setting one. See if that helps with the 737. If it does you I think you need to either as stated above go through all of your FS settings.Another consideration for PMDG aircraft is the setting of your FS startup default flight. Make sure it is a default aircraft since it intializes the FS engine when FS starts, even in the menu pages. Set up the Baron parked somewhere as you like maybe cold and dark under a daytime clear weather theme theme and save it as the default flight. Restart FS and try the 737 to see if that helps.I have the Aerosoft CD of the 800/900 and applied their service packs. I also used their 600/700 (my preference).

You state it worked before the Captain Sim install. If it uses FSUIPC and overwrote the current version with an older one, I suggest you update FSUIPC to 3.90 here:http://www.schiratti.com/dowson.htmlNext according top some postings installation of the CS aircraft can interfere with settings of other aircraft. I'd suggest going through all your FS and FSUIPC assignments to see what has changed. Also open up FS and then the PMDG menus from the FS menu bar and check assignments there. If you go to your FS9\modules folder and temporarily rename you FSUIPC.ini file to FSUIPX.INX it will be replaced with a default one the next time you start FS.A stuck switch can indicate a conflict of button and/or axis assignments. Another problem in some installers is that they go into FS9.cfg and directly change settings there. You could go into your folder where FS9.cfg is as an admin (mine for XP is "C:\Documents and Settings\Ron Ginsberg\Application Data\Microsoft\FS9\FS9.CFG"), and rename it (don't delete). (Make sure explorer is set to show hidden files.) Start FS9 and it will build a new default setting one. See if that helps with the 737. If it does you I think you need to either as stated above go through all of your FS settings.Another consideration for PMDG aircraft is the setting of your FS startup default flight. Make sure it is a default aircraft since it intializes the FS engine when FS starts, even in the menu pages. Set up the Baron parked somewhere as you like maybe cold and dark under a daytime clear weather theme theme and save it as the default flight. Restart FS and try the 737 to see if that helps.I have the Aerosoft CD of the 800/900 and applied their service packs. I also used their 600/700 (my preference).

I had this same problem when I installed the captain sim C130.

Thanks for your cooperation. I indeed tried to replace FSUIPC before, but it didn't help. Now I removed the FSUIPC.key from the modules-folder and reinstalled FSUIPC. Now the PMDG 737 works fine! Thank you for your help!By the way, Dan, how did you solve the problem?

Sorry, I forgot to add the solution. I reinstalled FSUIPC the same as you, it was kind of funny because I was grasping at straws at that point and got lucky.