Fly!2 Unexplicably Quits to Desktop - Cannot figure it out

[dkohl 0]

I am an NVidia user. And with the last few releases of the Detonator drivers, I've found that infrequently, but occassionally, I'll have an unexplained total quite to desktop. There will be no record of the error in GTFO.txt. While I'm not sure there is any relationship to the NVidia drivers, I cannot figure out anything else that has changed on my system other than the regular addition of TerraModels and TerraScenery areas. Note: I am using DirectX9.0a on a WinXP (Home Edition) machine. Other details are below in the .sig file.When going to desktop, my entire background screen is blank (default blue instead of a nice photo). Is there a way to better diagnose this. I am absolutely frustrated and canno figure this one out.Today, I just took the PMDG 757 for a spin from KSAN to KSFO. I was on my final - maybe 15 NM from landing on 28L and as I was doing a turn and looking out the window at the ground, boom -- gone. CTD.Ahhhhhhh.Any suggestions will be appreciated.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v41.09, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[Guest tonyc]

David,Pmdg 757/757 installation must be somewhat unique relative to all of the fly2 patches. So, if for some reason you have not installed the pmdg's planes EXACTLY as the instructions on their forum specify, you will get pleantly of CTD errors. I have been flying fl2 with pmdgs planes and the latest patches as well as many add ons and have not experience one CTD. I would get quite a few before the patch, and in one case, due to an erroneous installation of the pmdg's planes. The first or second thread in PMDG's forum provide the instructions.tony

[Avcomware 1]

Hi. Post your "render.ini" file here. Try to get the Options Scenery distance to a lower value, Hires and Med res. The file should look something like this:[Graphics]mipLevelCount=4vertexIndexFormat=0premultiplyColorAndAlpha=0allowAutoMipMapping=0directTextureFlag=0[Textures]maxTextures32=10maxTextures32_565=124maxTextures64_565=16maxTextures128=72maxTextures128_565=320maxTextures256=40maxTextures256_565=82maxTextures512=8maxTextures512_565=8maxTextures1024=1mipMapFlag=896maxTextures64=64[NonAGP]maxTextures256_565=0[AGP]maxTextures256_565=0TV

[dkohl 0]

Render is as follows....[Graphics]premultiplyColorAndAlpha=0allowAutoMipMapping=0directTextureFlag=0mipLevelCount=8vertexIndexFormat=0[Textures]maxTextures32=32maxTextures32_565=32maxTextures64=32maxTextures64_565=204maxTextures128=164maxTextures128_565=400maxTextures256=120maxTextures256_565=300maxTextures512=8maxTextures512_565=1maxTextures1024=2mipMapFlag=896[NonAGP]maxTextures256_565=0[AGP]maxTextures256_565=0But please note that up until the combination of DirectX 9 and two or three patches ago NVidia drivers (not sure exactly which) I had not had this problem.Thoughts on Render would help, but I'm not sure that is where I'm having trouble. Usually if this would be the trouble, I would have seen an error box and something written to the videoerr.txt file - this file contains no entries since March.-DK-DK ----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v41.09, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[dkohl 0]

I will re-check the PMDG installation, but I am quite certain I've done exactly what's instructed. That said, I will monitor whether this happens with other planes. Come to think of it, I think I've only had this problem in the 757.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v41.09, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[Avcomware 1]

Hi.I had a similar problem and always was due to the excessive Video memory allocation and the settings of the Hires. Your

[Guest andrewluck]

Another thing that's worth a try. Set your desktop res and colour depth to what you have in Fly! before entering the sim.Andrew Luck18 miles SW EGSH

[dkohl 0]

Desktop res and color depth are equal already. Hmm... good idea though.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v41.09, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[dkohl 0]

I still have not solved this. I re-installed both 757 and 777. But no luck. I had one CTD with the Pilatus, though, so I think its not a PMDG problem. That said, this tends to happen more often in PMDG planes. I changed my RENDER.ini a bit... Here is my latest, but still crashes:[Graphics]premultiplyColorAndAlpha=0allowAutoMipMapping=0directTextureFlag=0mipLevelCount=8vertexIndexFormat=0[Textures]maxTextures32=32maxTextures32_565=32maxTextures64=32maxTextures64_565=200maxTextures128=164maxTextures128_565=300maxTextures256=120maxTextures256_565=240maxTextures512=8maxTextures512_565=1maxTextures1024=2mipMapFlag=896[NonAGP]maxTextures256_565=0[AGP]maxTextures256_565=0The only thing I haven't done is roll back the drivers on my card. The added speed and performance are nice and I'm loath to try that. Anyone who might know if there is some kind of WinXP event log I can look at, I'm wondering if something is just clipping off my program from the OS? ----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[Guest Ken_Salter]

You might try deleting your .sit files. Look in the FAQ subforum for more info on this.http://saltydogfly2.avsim.net/images/avsim_sig.jpg

[dkohl 0]

Not the problem. I re-installed the 757 and 777 yesterday. I had deleted the SIT files for those planes prior to re-installing the aircraft. When I took my first flight with the 777, Fly!2 died about 2 hours into a 2:30 flight. I had initiated descent into EGKK on a plan from Rome. About 2 minutes after initiating the descent, Fly!2 quit. I wasn't even touching the controls... I was, in fact, in the bathroom and noticed the sudden silence. Hmmm... perhaps my PC detected what I was doing in the bathroom and quit in protest. :-)-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[Guest Steve Brown]

I must remember my "next" version of Gatwick should have in the readme file: NO TOILET STOPS! :-lol Steve.http://mysite.freeserve.com/fly2theuk/aragon.jpg][/divTHERE'S A BIG WAVE COMING!My United Kingdom Scenery.http://library.avsim.net/search.php?CatID=...&Go=Change+Viewhttp://mysite.freeserve.com/fly2theuk/avsim/bart.htm

[Guest spenik]

Oh Steve is such a ham! :-)But on the current subject, Did you try the "Video update" patch? It has a few updated video drivers expressly for us Nivida card people.As a last note, I used to get rather frequent CTDs, but after I downloaded the Staggerwing, I have not had one since. Can't say I know why but it's a thought.

[dkohl 0]

I have the Staggerwing. And on the Video update, I have installed patch 2.5.240 (final patch). Should I re-install the old video update (that's been out since 210 I think)? I can try that.-DK----David KohlFly! II v2.5.240Dell 8200 P4/1.8G, 1024MB RAM, Nvidia GF4 Ti4600 v44.03, WinXP Home Edition SP1.CH Pro Pedals and Yoke USB.

[Guest andrewluck]

DavidI don't think the video update should be reapplied after the 240 patch. The update was an interim fix for some problems was superceeded by subsequent patches.You're not alone in this. My system crashes very regularly on longer flights.Andrew Luck18 miles SW EGSH