Crash with 737 and fs9 patch

[kerosene31]

I did a complete uninstall of all addons and fs9. I also uninstalled the PMDG 737 using the downloadable uninstaller. (I also manually deleted everything from the old fs9 dir)I reinstalled everything clean, including fs9. Installed the new patch. I have been reinstalling my addons, and I reinstalled the 737s (600-900s). My install order was:737 6/700 version 1.21.3 patch 737 8/900737 8/9 patch 1.1Now when I start up fs9, if I immediately pick a 737, the sim crashes. It loads all the fixes in the menu, then I click "Fly now". Next the fs9 status bar loads to 100%. Once it hits 100%, the screen goes black, and then I get the generic crash message. Fs9 has encountered an error. I have the option to restart the program. When this happens, the error below appears in the event log. Now I noticed that if I start up the sim with any other plane, then load the 737 after, everything seems to load fine. I haven't tested a flight, but the 2d panel loads up and looks normal. Any ideas? Are there any fixes I should be adding to the default install that I am forgetting about? I am running WinXP SP2. Thanks in advance for any help. At least I should be ok as long as I remember to start up another plane first before flying. The error from the log:The description for Event ID ( 1000 ) in Source ( Microsoft Flight Simulator 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: fs9.exe, 9.1.0.40901, pmdg_737ng_main.gau, 1.0.0.0, 00105362.

[Hakkie]

Hi Craig, first of all I don't know if this is relevant in your case. I had a almost similar error which seemed to be caused by 'render to texture' being ON. I turned it OFF and all was fine. In my case I am to blame myself, as I played around with some settings after installing the patch. But again, it's worth a try. Change your setting and see if it matters..Henk-Jan

[Hakkie]

Edit: Sorry, got impatient an hit the post button twice :-shy Hi Craig, first of all I don't know if this is relevant in your case. I had a almost similar error which seemed to be caused by 'render to texture' being ON. I turned it OFF and all was fine. In my case I am to blame myself, as I played around with some settings after installing the patch. But again, it's worth a try. Change your setting and see if it matters..Henk-Jan

[Guest BBrooks]

Something I would try is to load the base 737 program, and then run FS9 to see if it works. Then I would load the subsequent updates and run FS9 after each one of them. Then you can isolate which program the actual problem is coming from. When I reinstalled my Windows program I had to do something similar to get the add-ons to work correctly. It seems one version has to be "initialized" before the updates can be applied.Brooks

[Guest proflight20002000]

Uninstall the update, it is not compatable with certain versions of fuicp, the list of issues in the microsoft documentation leaves me to feel i just dont want it.

[Guest Philip Olson]

Uh, why don't you just update FSUIPC? Kind of silly to tell someone to uninstall the patch when all they have to do is update one program. It seems to work great for me, I'll take the improvements any day!Philip OlsonI'm the luckiest man in the world, my girl friend has a yoke and rudder pedals! Eat your hearts out!http://www.precisionmanuals.com/images/forum/supporter.jpg

[Shaka]

>Uh, why don't you just update FSUIPC? Kind of silly to tell>someone to uninstall the patch when all they have to do is>update one program. It seems to work great for me, I'll take>the improvements any day!Actually, I'm having the exact same problems, and I have updated FSUIPC. I was having a similar problem a few weeks ago, where my PMDG aircraft were crashing FS in the exact same way. I narrowed it down to a memory problem - my hard disks were too full to support an adequate swap file. A larger hard disk solved the problem that time, but I have no idea why it is happening again.The fact that we are all using the same PMDG aircraft and the same 9.1 update tells me that there is a problem for only a few of us. But for me, this problem only appeared after installing the 9.1 update. So, besides the FSUIPC update, has anyone else had any problems?- Martin

[kerosene31]

I updated my FSUIPC right away, so that isn't my problem either. I think the render to texture has something to do with it. For the 737 it is recommended to be off, but if you use the FSW dxt3 clouds, they will crash unless you have it on. I don't know how I fixed it before, but I had both working. I can't remember if I had render to texture on of off. Does anyone know where this setting is in the config files? I backed up all my .cfg files, but I can't seem to find the display variables.

[kerosene31]

>I think the render to texture has something to do with it. >For the 737 it is recommended to be off, but if you use the>FSW dxt3 clouds, they will crash unless you have it on. ^ This was it. Render to texture must be off, plus if you are using the FSW clouds, you have to use the 32 bit ones, not the dxt3 versions.

[Hakkie]

Hi Craig, glad I could point you in the right direction. Nice to hear you're up in the air again! :-jumpy Henk-Jan