Jump to content

Sign in to follow this  
dkohl

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

Recommended Posts

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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

I am going to try to increase the size of my AGP Aperture. I have it set at 128MB now (or it might be 256MB). I'll verify next time I get on my home PC. Someone once said it should be set to approx half of your system RAM - I have a GB of system RAM, so arguably, I can increase AGP to 512MB. I'm wondering if somehow I'm overloading the card and something inside WinXP is just shutting down the application to prevent damage to the card. I have no real basis for supposing this, but its worth a try. Anyone out there with XP knowledge enough to help diagnose the problem?-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.

Share this post


Link to post
Share on other sites
Guest tonyc

It's not your agp aperture size. It should be a lot lower than 128 because when fly needs more video memory it takes it from system ram, which is much slower than video ram, and your fps drop. It's a balance between your render.ini and your video memory. As for the ctd, is it happening only with PMDG's aircrafts? If so, try flying another aircraft. PMdg aircraft requires a funny installation relative to the fly2 pathches. Read the pMDG forum for instructions. tony

Share this post


Link to post
Share on other sites

Two things:1 - My aperture size was already 256 MB and couldn't be set higher. So as an experiment, I lowered it to 128 MB and will report back if this helps.2 - It is not ONLY with PMDG aircraft. It seems to happen more often with PMDG aircraft, but then again, I take longer flights with PMDG aircraft. But this has happened with the Pilatus at least once, and I am pretty sure I've had it crash with other aircraft.I just re-installed all my PMDG stuff from scratch following every step of the PMDG forum, but still having crashes since with the 777 and 757. -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.

Share this post


Link to post
Share on other sites
Guest tonyc

I used to have crashes on long flights, but his happened only as a result of some bad scenery installations and also memory leaks resulting from a bug in fly2. The last patch fixed it. I hope that you're patching properly.......tony

Share this post


Link to post
Share on other sites

Yes. As per my signature, I'm at 2.5.240. -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.

Share this post


Link to post
Share on other sites
Guest

Bonjour,I have exactly the same problem as you - and I noticed the following points:- the CTD happens more frenquently with big (and rapid) planes: frequent CTDs with TBM700 and Pilatus12, less frequent with Kodiak, and never happens with FlyHawk or Staggerwing (with long flights in every case). I don't have 777.- CTDs more frequent when flying above hilly landscapes.So I don't have any solution, except using Staggerwing - what I am currently doing, this plane is funny!have a nice day,Jeck

Share this post


Link to post
Share on other sites

Idea went nowhere. I CTD'd in the Staggerwing today on a flight over the San Francisco Bay. Was on the way from KOAK to HAF and about 3K feet over the bay I pressed the "down" arrow to check a gauge and BLAM - gone.This is getting worse, not better.-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.

Share this post


Link to post
Share on other sites

I'm gonna try flying without T&L for a while. I'll report back in a few days.-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.

Share this post


Link to post
Share on other sites

Hi David,Having the same problem just recently. Have the latest Omega drivers for the Nvidia. I have been making loads of Terrascene (so far about 15 gigs all of the US West Coast). This problem has been getting more frequent the more scenery I put in. I do think you have a point with WindowsXP protecting the video card from overloading. I get the same ctd with CFS3 if the resolotion is too high or 32 bit. Screen goes black and then the desktop is blue and you have to hit refresh to get the desktop background to show again. I'll give a try to the T&L also on flights that give me trouble and let you know. Don't have the 757/777 but the TBM700 and King Air both have ctd'd on me.ZaneFly!II 2.5.240WindowsXP HomeAthlon XP2000Asus GeForce4 Ti4200 128512 DDR 2100CH USB Yoke and Pedals

Share this post


Link to post
Share on other sites

I lowered my hi-res setting from 6 miles to 4 miles and no problems last night. Will post again if I get another ctd.Zane

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...