The file is now up for download on the library for anyone that's interested. It can be found in the FSX Miscellaneous Files section. Here's hoping they work as well for everyone else as they do for Lucevan and myself (fingers crossed).Enjoy!-George

The file is now up for download on the library for anyone that's interested. It can be found in the FSX Miscellaneous Files section. Here's hoping they work as well for everyone else as they do for Lucevan and myself (fingers crossed).Enjoy!-George

This all sounds like very good news and thanks to all involved in the discovery and testing. I have never used DX10 because of all the different problems listed in this forum as well as others. My question now is exactly how should my system be set up. I currently use nick's tweaks and set up using Nhancer. Does Nhancer work with DX10. I have the I-920 and 8800 GTS (640) and windows 7.Sam

As for myself, I did the recipe for KORD and CYUL and it works. Please note starting to upload these the AVSIM and al can lead to some sort of scenery mayhem. The Florida FIX upload was done from stock airports right? I figure that many/most of us have got AFCAD tailored airports, like MyTraffic2010, etc.... So adding the "CONCRETE" scenery will reduce the ammount to AI traffic to those airports. I would suggest that any 'DX10' modification should be done on AFCAD improved airports. Others wise, it becomes another "1 step forward,1 step back" situation. But then, were have no real centralized AFCAD airport repository.Just a thought.../Vincent

Hi Sam,I don't use nhancer, so I can't answer that for you, sorry. Otherwise, my system is set up identically for DX9 or DX10 mode, personally I make no changes switching between the two. Perhaps someone who uses nhancer could answer this for you better than I.Hi Vincent,Yes, these are all based on stock airports. I don't use any traffic programs, so I can't say much about them, but I was under the impression that they only modified traffic files and not the airport files themselves. Does MyTraffic add things to airports like additional parking or something like that? I only ask because I'm curious why it cuts down traffic as the result of concrete. In any case, I don't change any of the default surfaces on any of the airports I try to fix. Instead, I add new surfaces and taxi links and hide them under buildings (usually a maintenace shed a good distance from the airport, as many default airports already have one out there) and none of the new surfaces or taxi links are attached to any existing airport surfaces. I only do this to maintain the original look of the airport, and to hopefully not mess with traffic or parking. As for fixing 'AFCAD improved' airports, many airports have had several versions done by different authors, and trying to fix each version of any given airport would be a logistical nightmare. The 'fix' is easy enough to implement, that once it has been confirmed to work 100%, I can't see authors not including it to ensure DX10 compatibility on their future projects. Since everyone has stock airports, and since many stock airports never get redone by third-parties, it seems that it would be best for me to just focus on the stock stuff, and leave the real airport improvements to the real designers. At the end of the day, I'm hoping that my 'fixed' airports do the job of 'filling in' the stock airports that haven't been improved by the real airport authors, so that flying in DX10 mode full-time could become a more reasonable prospect. That's why I've also given all my 'fixed' files an easy naming convention, so that they would be easy to find and delete when a user has an actual imroved airport that he or she wants to use instead of the stock ones. Once third-parties start incorporating the 'fix' into their airports, I don't think it will any longer be a case of one step forward, one step back, but rather a full shift to forward step after forward step after forward step etc. :) At least, that's what I hope happens. :)

Yes, these are all based on stock airports. I don't use any traffic programs, so I can't say much about them, but I was under the impression that they only modified traffic files and not the airport files themselves. Does MyTraffic add things to airports like additional parking or something like that? I only ask because I'm curious why it cuts down traffic as the result of concrete.

Default scenery have fewer gates and only for small planes. Default airport are modified by end user and 3rd party AI traffic producer to generate more AI traffic.

I can't see authors not including it to ensure DX10 compatibility on their future projects. Since everyone has stock airports, and since many stock airports never get redone by third-parties Once third-parties start incorporating the 'fix' into their airports, I don't think it will any longer be a case of one step forward, one step back, but rather a full shift to forward step after forward step after forward step etc. :) At least, that's what I hope happens. :)

Indeed, we should give feedback to commertial 3pp AI traffic product (UT2,Mytraffic) to implement this fix in there packages./Vincent

Indeed, we should give feedback to commertial 3pp AI traffic product (UT2,Mytraffic) to implement this fix in there packages.

Seeing as Ultimate Traffic II doesn't ship with any revised airport files, what is there for them to fix in their package?My Traffic does have revised airport files, but only a subset of what is in FSX. Should they "fix" all 24,000+ of the default airports for the DX10 Preview users? And how much more can they charge if they do?