Dux1

I've never noticed that before Neil, how on earth did you discover it? I assume that you couldn't see the AI because it's all on a VFR flight plan (unless you happened to switch the optional IFR file).John

The other thing you can try Neil, is to switch off (uncheck) all 3rd-party scenery in the scenery library except for Duxford and see if the AI appears. Remember to re-launch FS9 though. If it does appear, that will tell you that there is a conflict. You can then switch on half the 3rd- party scenery and test again and use a process of divide and conquer to get to the offending scenery area.

I deleted my default FS9 traffic years ago too by removing traffic30528.bgl Neil, but no other files. No problem there if that's all you have removed. The historic aircraft should display at 100%, the only reason I suggested for not doing that is because it will let through some unrepresentative default aircraft, if you have 30528 present.Have you ensured that there are no other EGSU.bgl files in other add-on scenery taking precedence, especially AF2 files? UK2000 scenery is often the cause of conflicts. Try a Windows search as per the Duxford manual.

Neil, the white texture you mention is due to a large sheet that some graphics cards don't like - it's fine on mine, Stevo's and the testers, but it seems to be affecting a small number of people from the large numbers of people who have downloaded so far. If you drop me or Stevo and e-mail, we can send you a smaller texture that will solve the problem.There is nothing wrong with the supplied AI packages. Have you enabled both the main scenery and the air show add-on in the scenery library and does the air show area sit above the main area as illustrated in the manual? Don't tamper with the AFX files, there is nothing wrong with them. AFX files have the same format as AF2 files but they are produced with Flight 1's AFX payware program that has many more facilities than AFCAD2, including the ability to convert between FS9 and FSX formats, something that AFCAD2 can't do.Simple check list for you:1. Both scenery areas enabled in the library and stacked correctly,2. Aircraft in FS9aircraft3. Duxford1.bgl traffic file in FS9sceneryworldscenery4. AI traffic set to on (at least 10%) but see the AI manual for the 3 different levels of visibilityHope that helps.John

As one of the two developers of the Duxford scenery, can I just say a big thank you on behalf of us both for all your kind words. It's really made the project worthwhile. We are so glad you like the scenery.Joe's question is really relevant to good designing. It's not easy to answer unless you are familiar with Gmax, but in our case we did quite a bit of research into what makes FS9 and FSX tick, performance-wise. There are a couple of quite technical Microsoft documents around that give some clues and with a bit of experimentation, we began to understand. It's based on the premise that "polygons don't matter, texture vertices do". What it really means is that you can build complex items with many polygons, but you need a technique to share all the common texture vertex points (the dots that map the texture shapes to the faces of the modesl) to minimise their number and the number of draw calls. Repeated objects like trees are a prime example and benefit enormously from the technique. If any designer wants more information, go to the tutorial section of the ACG website or drop me an e-mail (addresess in the Duxford manual). There's a tutorial there that I wrote on the subject written in simple terms that might help.John