Pease_W

An object placed within FSX/P3D won't be excluded by higher-priority work if there is no exclusion area that covers the object's placement point. XML-based exclusions are rectangular and at times are drawn only to take out a certain object. Making a large rectangle that encloses an irregular shaped airport can take out more than what might be intended. It all depends upon the person making the work, as to how they anticipate what else might be there besides what they happen to see. So unless the UK2000 scenery was predicting that another object could appear in an area and applied the exclusions appropriately, it's to be expected that another object could and should appear from lower-priority scenery.

UTX uses commercial grade data, the other uses Open Street Map (enhanced?) data. UTX pays a royalty for the sale, Open Street Map expects any changed data to be shared back with the community. I think OSM is still waiting for the shared data? UTX offers a 30 day money-back option if you are not happy.

While it is not a true indicator of system capabilities, this line can be useful as an indicator of what FSX sees; ProcSpeed=7881 My 2.5 year old i3570 yields a rating of over 16,000. So your reading indicates to me that your system is not at full performance and I would look to see that any power saving options in Windows was turned off to let your system work at full speed.

Mountain out of a molehill. Each region can call it's own version of a land classification texture, if it has it's own landclass.bgl file. So any texture can and should appear more than once, ideally each time a region is installed. Add in that FSX/P3D will have it's own World-based set of the same textures and you will add up many instances of the same file name.

Why is it there are times when "something" just sparks a curious nature.... http://forum.avsim.net/topic/359863-fsxcfg-check/

The nature of the large texture sheet should be understood before adjusting. If a sheet is 4096x, but set up to replace 16 1024x sheets, then you are seriously hindering proper display qualities. If the 4096x sheet is just a larger version of a 1024x sheet you won't lose too much. But I believe FSDT is a proponent of 4096x sheets to reduce the number of file calls for displaying an airport. One 4096x sheet replaces 16 1024x sheets and 16 file calls.

It's not a satellite, but generally a twin engine airplane. And in the U.S. they try to fly after winter, but before the growing season gets too far along. If you ever notice any banding in the scenery it is because the camera's view is not limitless. So the plane goes north, turns around and goes south on an adjacent path and repeats over and over. The imagery get's "stitched" together to make up larger areas.

Did you install the latest libraries after Vector?

Downloading both the P3D and FSX versions. Thanks for the heads-up!

You need to extract both files into the same folder and start installation from there. You cannot attempt an install trying to run the file(s) from the archive you downloaded.

They have changed to a single .DLL approach for most of the airports. There are some that have not been updated and would still have their own .DLL file. I've not seen much of any commenting about overload from the old way of doing things and doubt I'd worry about the few stragglers waiting to be updated.

You have other files for this airport, somewhere? That is why you see the problems with the terrain. Stock KMRY is at 257 feet elevation. Checking in the trike would bring the Shift-Z reading to 263.4'. Some other file is changing the ground elevation, which would not apply to most elements of the airport infrastructure. But it sounds like you bought the NorCal package, which is a good product. Required? No, but it will still serve some good. You might still want to find where that stray file(s) is that's messing up the airport area.

Let's see, you are flying with afterburners ablaze and wondering why an object doesn't have time to fully render? :huh: Find something slower and enjoy the journey, plus the scenery.

You could make your own land class file to override what might be there. That would require having the SDKs installed before starting anything.

There is no region for Palm Springs, so I guess it blows that "must" out of the water? Certainly the airports will look better with a regional package,but will function stand alone as well.