Arnaud

Well in that case it is very unlikely that my trick will work. In my case of sudden CTD at one location, any aircraft was causing crash, defaut, Carenado and of course PMDGs. Try then silly things like changing ZFW and fuel from the load manager, perhaps something got corrupt in the acft.cfg during all the time you havent used the Queen. Also try to delete any saved panel if you use them, I personnaly never use any saved panels and never got any issue with the 744.

Benjamin,About the sudden crash at EHAM: I experience sometime those sudden CTDs for no obvious reason(often different DLLs implied in the CTD), at some specific scenery, the latest was at Overland's Narita. Here is a trick that works for me which I found myself and that I find pretty miraculous: just move the scenery that causes crash in the library up or down (along with its landclass folder if it's got one), save, quit, restart and try again. It has always worked for me, dont ask me why, I dont know, but it works. I had this issue with As Schipol after I installed the Frankfurt update. I was going nuts, then I changed the EDDF scenery layer and it solved the CTDs.In my case it isnt however linked with ANY aircraft, not one specific aircraft. If you get crashes only with the PMDG 744, then perhaps it has to do something with a recent navdata update, or some faulty SID/STAR you installed?

How weird fs9 can be! I've been reading the whole thread over at AS forum, and eventually posted about other issues, but I never encountered any performance problems with Münich.From the day it was released, it runs smoother than any other similar hubs on my rig. The only issue I had was the crashy bridges, and the aircraft's shadows 'falling' in the holes of the fake terrain modelled for the bridges.Glad that you guys have it sorted though, Aerosoft had been more efficient with Münich than with some other recent releases. Do you guys happen to have OrlyX as well? I lost my temper with the developper over their forum, because we're several people having major performance issue with Orly, and the only support we got so far was that we were asked to post screenshots to prove that our frame rate was low. I threw the line.

Are you talking of a complete computer lock up, or just the sim crashing and leaving an error in the application log?Might be two different problems here: the g2d.dl mixed with a pmdg gauge is most likely due to some faulty AFCAD in the area you're flying in,or a duplicate AFCAD somewhere in the area. It can also be caused by a scenery priority problem. Try to remember which scenery you've installed lately, and move it below in the scenery.cfg. It has solved some sim crashes I experienced around the HongKong area in China and Frankfurt in Germany.About the computer lockup, which is a different problem, I spent monthes to chase the cause and found the culprit to be some value I had changed in the fs9.cdg, the TEXTURE_BANDWIDTH_MULT (TBM) that I had set to 400, I lowered it to 200 and it solved the problem. The default value for this entry being 40 if I recall correctly.Hope this helps.

LFPG. I live 15km north of the field, and dont suffer the noise since the four runways are east/west only (two 09/27 and two 08/26, exactly like in Atlanta).Some years ago I used to live in a small city located just down the path of the runways, and man that was hell, even for me who like airplanes like we all do: you simply cant really live inside your home with your windows opened during summer, otherwise you cant hear a telephone call or the TV. I'm glad I moved from there after less than a year. When I was living in that small city, even the nights were noisy because of cargo flights and also Air France's Maintenance working all night testing engines.I wouldnt buy a house which is just under the path of jetliners, as far as 20kms from a major hub. Way too much traffic.Very interesting thread indeed. Reading that one guy is in Mosul, Irak... That's something :(

I still have uk2000 sceneries installed, Vic. I assume you can write those off your potential culprit list.I havent messed at all with duplicates textures.Myself, I lowered the audio DX acceleration one step, and lowered the TBM to 200.I flew a world tour two weeks ago: CDG-FRA-AMS-ORD-JFK-PDX-SFO-HNL-HKG(both new and old)-DXB-CDG without any problems, using only Aersoft's, FT and FSDT sceneries with PMDG 744 and MD11, full traffic and weather. I also suspected the nv drivers at some point, but I was obviously wrong as I havent changed the drivers, I use 190.45 and nHancer 2.5.7I'm glad we're all sorted :(

Have you tried to move Brussel scenery in the library as I suggested? For instance, set it on top of everything. Use the FS library menu. And make one more test flight.

I agree, dont point to the 3GB switch so quick, Ehasanov.I use WinXP 32 Home and both the 3GB switch and fs9.ewe 2gb aware. No OOMs nor CTDs.I recently encountered those g3d.dll crashes though, and I was fortunate enough to find the culprit: it was the latest Aerosoft frankfurt update. What I did? I moved it under all my other sceneries in the library, and that solved the problem. So it's not only crappy sceneries who cause problems, sometime it's nice famous ones.I've been lucky to find the cause of my g3d.dll, but that was easy: the g3d.dll crashes started right after I installed the new scenery.Have you always had those crashes or did it start recently? If so, check what you have last installed and try stpe by step, doing always the same flight that causes FS to crash.That's what I did, flew 3 times an EDDF-EHAM flight, had 3 times g3d.dll crash. When I found the solution, to make sure I had it sorted, I flew again EDDF-EHAM flights without any problems.FS is definitely not en exact science. So many different setups, different PCs etc.

Hey Vic and all,Since my last posts I've been doing a lots of flights, always using heavy sceneries, heavy traffic, heavy weather and heavy aircrafts (PMDGs), and so far I did not have a single freeze.I am near to believe I had it sorted then. Would be interesting to know what other people who also had freezes get now. That could be a relief for all of us miserable frozen simmers.

Heh, Victor, so you're planning on going to a 64 OS then. I hope it will solve your issues. I understand about the textures, I didnt know, as you say if FSmanager looks for duplicate texture then there must be a good reason. I simply never heard about it.Now, about the freezes...oookay... I am on small vacation so I could spend some time on FS (well, all the afternoon actually :( ). So far, no more freeze nor lockups nor stutters. I dont hold my breath, but I am confident, and I am confident because after the three changes I made I have the clear impression that the sim is even smoother than it had never been.Been punching the sim in the face during hours, in the most heavy scneeries (including the latest Mega Amsterdam) with the most heavy PMDGs, full AI, weather etc...Switching views, panning 360 degrees like hell etc...the 3 changes I made are: - I loweredd the TBM steps by steps, ended at 200 with framerate locked at 29.- I deactivated the WinXP screen saver I had totally forgot about.- I lowered the dxdiag audio acceleration, one step.I suspect the last one to be the winner, so far.

Hey, thanks for the explanation Vic.There is only one thing that bugs me with the duplicates textures theory: as any PC programm, it is my understanding that FS deals more with pathes than file names. Otherwise, how the hell could AI work properly? Must of us have gigabytes of textures for our AI aircrafts, meaning thousands of 'duplicated' texture, yet it works very well. Because, FS looks for a texture with a path to it, not simply a filename. I fear that if you remove some of what you think are duplicate textures for some of your sceneries, you will end in finding some sceneries with textures missing here and there on the display.I will all let you know how it turns out for me, I made some hard testing (at heavy sceneries with tons of AI and chasing views) and so far no freezes, only thing i did was lower the texture_bandwidth-multi and lowered the audio acceleration setting in dxdiag.oh, and I for one totally trust FSUIPC too. Never used AI smooth.Will keep you guys posted :(

Thanks Victor,Perhaps I misunderstood what you meant by 'lockups'. By lockups I certainly understood your second case: dead PC, hard reboot being the only solution.I have never heard of duplicates texture though. I've ran fs9 since its release in 2003 on 3 different machine without looking for dupes and never had issues.What are you refering to as duplicates textures?About OOMs, they always happen near airports. The first OOMs were approaching aerosofts great hubs. I bought some uk2000 sceneries not later that last month and didnt have OOMs but most likely because in the meanwhile I had installed the 3gb switch.What's really of interest to me in what you write is the trick to allow fs9 on one CPU core only. I've had read few posts about it in the past but never paid more attention because by then I did run an old single core p4. That sounds like making sense to me.CTDs: the original CTDs were just what they mean: crash to desktop! FS closes without warning and without a single error message and you're on the desltop.I sometime had FS crashes, normal crash with some errror message and an entry in the eventlog, those crashes caused by duplicate AFCADs, 32bit texure without alpha channel etc...I can clearly see the graphic corruption on your screenshot, I dont have that particular problem. On the other hand I do have some problems with sounds too sometime.Anyhow, I will continue to investigate and try to keep track of what I'm doing and report when I get rid of the problem.And, Desertwinds, you're absolutely right, it IS frustrating. As you say, except those freeze, my new PC also FLIES :(

Well, thanks for your reply Victor, although I'm a bit disppointed since getting rid of the 3Gb switch is out of the question for me, as it frees me from OOMs (as I fly mainly heavies to major hubs).More importantly, I did have lockups way before I added the 3Gb switch. The freezes started just after I got my new computer, much more powerful than my previous one.I tend to think that some fs9.cfg settings I had on the old PC dont suit the new one, so I am searching.The freezes or total lockups cannot be due to textures or duplicates AFCADs, faulty textures will eventually cause CTDs, same for AFCADs , but not total random freezes. A while ago I had to chase some duplicated AFCADS that gave me consistent CTDs near HongKong. But that was only CTDs, I am more concerned about my hardware lockups.Only once I had the chance to get back to the desktop after a freeze, and although the OS was kinda dead (nothing functionning), I could see the cause of the problem, 'nv' as nvidia in the evnent log. Doesnt mean necessarily that my drivers are corrupted, but 'something' that the video drivers couldnt cope with caused the lockup. I suspect my texture_bandwidth_multi entry that I had set to 400 to be a possible cause of the freeze, I lowered it to 80 with a max frame rate at 27, and am still testing. I also just found in my fs9.cfg, and dont understand how it is, I have the texture_maxload set at 1024 which is non sense I believe.Since you removed the 3GB switch have you ever had OOMs?About your stutters, does these happen everywhere? I dont have stutters, except in places where are some textures mipped out of imagetool (there is a famous scenery designer on the market known for that). And I solved the stutters by reworking the faulty textures with DXTBmp.

hey Victor,Sorry to bump that thread, but I've been reading and searching forums about freeze problem part of the night, and this morning I saw you active in the flytampa thread,so I thought I'd ask if you sorted your freeze issues? Because I havent, I still have lockups from time to time, and I cant stand it anylonger I think.I have a similar PC as yours, GTX260 and 4GB RAM using the 3GB switch and userva2560.I am starting to doubt the GTX260 even non OC - Asus branded.Have you lowered the TBM entry finally? I'm going to try this out, sounds interesting. I had it set to 300.

Sure it does, if you follow an aircraft all the way to its destination, you will see it flies the planned leg. That is, depending if you use @ or not in the flightplan.I dont use @ (fixed arrivals), and let TTools computes arrivals with the speeds for each aircraft, so the aircrafts dont vanish in-flight.I witnessed vanishing crafts in fs2002 though.Several times I 'intercepted' and followed AI to their final destination. The most crazy was a flight from Paris to Shanghai: I followed an AI 744 cargo from LFPG to ZSPD (10 hours flight)and kept visual with the traffic all the time: it never disappeared, and landed in Shanghai Pudong at the planned time.

Paul might be right with the F12 key, however I must say I gave up with Active Camera long time ago and trashed it: too many issues on the long run, so I moved to DBS Walk and Follow, much better and much more stable, even if it's a bit more expensive. I strongly recommand it.

thank you very much indeed Vololiberista :( I replaced the cirrus_overcast03 file with the defaut one, at first, and it definitely solves the problem. Moreover, I emailed the author, Pablo Diaz, and he was so kind and repliedwith some texture of his own which also solves the problem (I tried the haze layers from bluesky, but honnestly wasnt much convinced).How nice is that? he shares with us his awesome work, and he even takes time to reply to emails. Quite rare these days.

Thank you guys,I understand that is a common problem with HDE clouds then. Too bad :( ChinookWind, thanks for the tip, but I can hardly imagine a sky without cirruses. Did you mean stratus? I might give REX a try though, I've been reluctant to buy it since the many issues people experience with its GUI so far.

Hi,Something which never happened before started to annoy me in fs9 since a while. I dont use any addon weather program yet, no ActiveSky, no REX, nothing, at the moment.However I have downloaded and installed the nice HDE clouds from Pablo Diaz recently, and I wonder if these cloud textures could be the cuplrit. I noticed they arent mipped.Here's the problem: when setting up a layer of stratus, at let's say 3000feets AGL, and some cirrus at FL600, when flying at FL150 for instance, I noticed that there were an uncommanded cloud layer following my plane. That looks really idiotic, and I have no idea where that cloud layer come from: I checked my registered version of FSUIPC which can sometime add clouds layers, but it's not there.That cloud layer which follow my plane seems to appear only with stratus, not with cumulus. Under that ghost layer, I can see the layer I did set myself.Are there any known issues with HDE clouds such as this one?Or does this have anything to do with the cloudimpostor value set in fs9.cfg?Hope someone can help.Regards

:( You're just hilarious, Jim! gee wiz...

Look, Jim, no need to post a screenie of that page here, because the one you're refering to is exactly the setting I am talking about, in the general settings. Simple.You say that it is not what that option does, that it only serves to boot the sim at the date/time taken from the PC clock: OK, that is what you say, perhaps you're right, or partly right, but all I can say it that it solved the problem for me, and for good. From memory, the choice is 'PC timer' or 'flight time'. Correct, flight time, says it all no?You know time fuses, right? You know you change a time fuse each 15 degrees east-west or the other way round from the Greenwich meridian (360/24=15), right? If you cross one of those time fuse at 12.00GMT, the sim will recalculate the sim time accoding to the pc clock and the meridian you're over, to stay tuned with it, and thus reload both AI, textures, etc according to the new time of the day/location it has just computed.That is how it work. Perhaps it's not written nowhere but that's how I fixed that annoying thing, and I found that fix because it is nothing but logical. One more thing: FS9 time is wrong: you loose few seconds per hour, so on a 10 hours time the ellapsed time in FS will not be the same than on your watch, there's always some missing minutes.

heh. you are a funny person Jim :( Of course FS does that. Period. Why do you think I have that unchecked? Simply because I had the same issue when flying transpacific flights. And I got rid of the problem by unchecking.That being said, I dont use Active Sky, unlike Steve. There could lie the difference.

Steve,You must uncheck, in the FS general option menu, sync time with PC time. Otherwise, especially on long haul flight, every 15 degrees(longitude) the sim will recalculate the time difference between your PC time and the UTC time according to where your are on the globe.That's not an FSUIPC issue, it's a defaut FS option that must be unchecked.

I use FSgenesis worldwide mesh, and the more i fly over the globe the more I find issues with FSG mesh, mostly with addon sceneries, but also on many default location. Lakes in deep holes, gigantic wrong straight canyons in Saudi Arabia desert, plateau effects in Spain etc...Would any FSGlobal users who also know FSGenesis give a hint as to which one is better? I am considenring trashing FSGenesis one day or later.

hehe, for some reason, I've had the feeling it was going to be released today when I got up. I bought it less than one hour after it was released, downloaded but did not have time to install it yet. Paul's post makes me feel impatient tho, and smiling, as I trust his taste for good scenery. I never had any other EHAM than the default one, never bothered with the C9 scenery since when it had been released a few years ago I had read many people dispappointed.So today is a good day.