When starting at Juliana, all textures go blurry within seconds. So after much tweaking, I gave up and started at Bradshaw. No problems. Performance was just about like FS9, with the exception of a little jerkiness that is probably due to the demo. Anyone else notice this?Thanks,Todd

What in any of that would make you suspect a "memory leak"? That term gets thrown around so often and hardly anyone understands what it means.A memory leak is when a program does not clear memory after it's done using it - it causes the memory to remain allocated as if its being used when it isn't. Thus the total memory the program is using keeps going up, eventually saturating the system.http://en.wikipedia.org/wiki/Memory_leakClearly this is not what you're describing here... not ever bug is a memory leak! If I had a dime for every time someone talked about one in PMDG's planes... ;)

Thanks for setting me straight there Ryan. Just trying to describe what I'm dealing with. I'm not a computer geek. Cheers,Todd

>Thanks for setting me straight there Ryan. Just trying to>describe what I'm dealing with. I'm not a computer geek. I'll>try elsewhere.>>Cheers,>ToddNo reason to go elsewhere.I think there is a valid reason for this.First, it seems that the St. Maarten area is more dense in terms of detail, i.e. scenery objects, boats, docks, placed buildings, etc.Secondly, the same area appears to have aerial or satellite photos as textures, as opposed to the default land textures. These specific detail textures could very well use more resources than other areas.I also notice better performance around the other islands.

I can use the airport in question, but turning up traffic be it General or Airline causes my memory usage to bring my pc to a dead stop. Using the task manager FSXdemo uses around 550mb out of 1gb on my pc, but after increasing traffic it uses every last bit of memory available. I'm not sure if this is due to textures or bugs but it may just happen around this airport and I believe it is the only major in the demo.Ian.

I've noticed that the demo is very prone to dynamic blurred textures (this was a very big issue back in the days of FS2002 - it was actually me who coined the term 'dynamic blurred textures'). This is probably what you're experiencing. It occurs because the system is unable to update the textures quickly enough as you fly along. I'm sure Microsoft are aware of this problem and hopefully the final version will be much better in this respect. One of the best fixes in FS2002 was to reduce the frame rate limit as much as possible. This makes more computer horsepower available for updating the textures. Best regards, Chris

Same here. I had the same symptoms in FS9 when I first used Rick Piper's fabulous HS.748 before he patched it. Blurry cockpit and scenery textures. He finally solved it with a patch. I assume it was related to one of the textures he used (Rick, are you here ?)It could be that one of the textures used on an object around TNCM causes this. It is a pity that this happens on the default airport which may explain why many users complain about blurries and are so disappointed.Jean-Paul

This is where Mike Gilbert has also mentioned that a dual-core processor will be most helpful.

I've done more flying around Bradshaw. No blurries. Frame rates suffered from the massive amount of trees, but that was it. There must be a texture or something else that is sucking the life out of my rig at Juliana. In FS9 I have autogen and traffic maxed with no problems for the most part. TNCM is not nearly as complex as other scenery in FS, so can't imagine why it would be so taxing.Cheers,Todd