hero93

It works with the hotfix. Thank you!

There is quite a lot of negative feedback here, but I want to emphasize how grateful I am for this application, and many of your recent changes are very nice! Keep on!

I use PSXT/RT the same way as you do. 1. I would also wish for a more versatile block feature (maybe Regex-based) because often RT shows a "_" suffix that is removed just after takeoff, which is quite a painful moment to change the blocked aircraft. 2. Is there a way to remove the newly introduced timelag in RT? Because I really like the ability to look ahead.

Yeah, you are right. I see those.

I don't have any elevation issues, though I haven't tested the ILS yet. Be sure to clear your scenery cache and scenery index.

I don't really see myself as a commercial member of the community. Developing AFDs is like another hobby for me, that I get occasionally payed for. I am not part of any company and I don't make money by selling Add-On Products.

Ray, as the developer of the Flightbeam and some other payware AFDs I want to comment this briefly: First of all: Did you experience any real problems with the AFD while simming, or did you just run the fault finder? Those errors you mentioned are relative, when we produce the AFD for an airport with custom ground poly we don't use the links as intended. We add way more nodes to ensure the AI aircraft are taxiing on the centerline, thus there are overlapping nodes at some complex intersections. But those are not errors, as otherwise the AI would taxi via shortcuts or off the centerline. The maximum holdshort distance has some tolerance. The fault finder will of course use the minimum, but its sometimes necessary to nearly reach the limits. And as others already wrote, this is only important at the runway ends, as the AI won't get the takeoff clearance if they are too far from the runway. At the middle runway intersections, those errors are irrelevant and at a large airport like IAD with four runways you might get a large number but it doesn't say anything. There are sadly lots of limitations and problems with FSX (i.e. runway usage). Be sure those faults are the smallest concern in AFD design. When I am in the progress of developing the AFD. I run the fault finder every 30 minutes and fix the real mistakes. I spend hours simply monitoring the AI movement, searching for the important problems and trying to increase the traffic flow. At all Flightbeam airports also the service roads are traced in the AFD so GSX works as intended, this sometimes produces more node related error messages which are irrelevant. About Aircraft Parking and Gate description: By using specific gate types we prevent displaying of the default service vehicles independently from the user settings. There is a big limitation on gate identifier. All Traffic Add-Ons use different aircraft properties (wing span, Airline Codes,...). It is impossible to match every users AI. Our priority in parking distance is the user aircraft, as there is less variety and to ensure you don't start your flight inside the terminal. I have to agree with you all, that there are a lot of bad AFDs even from the "big players", but a lot of problems you adressed are because of limitations we sadly can't change. If you have any other specific questions I am glad to answer them. Sorry for my bad English and grammar, it's late...

I use a lot of traffic and recognized no loss on framerates with FTX Global. They just changed textures!

N60JB, The default AFCAD of RKSI is stored at Scenery/1002/scenery/AP81180.bgl and when something went wrong while compiling or if Ken used an unusual way to import it, it is possible, that the default AFCAD is still somehow dominant. So Ken: What AFCAD have you used to edit with ADE and how did you open it? Have you MyTraffic installed? Because then there will be a duplicate AFCAD in the MyTraffic Folder which can "overwrite" your custom AFCAD.

Well, now you will have a duplicate AFCAD. What AFCAD have you started with? The default one? You can either try to add an exclusion rectangle in ADEX and excluce all, or deactivate the default AFCAD, by changing the *.bgl extension in something like *.off or *.bkp.

Great Video, indeed! You can watch it here.

Hi, first of all I want to thank all those talented painters who contribute so much to our community, but: Every time I add a new livery to one of my aircraft I have to add the parking codes myself to the aircraft.cfg. Of course it is no big deal, but I wonder why the painters don't add the codes, as they release all the other cfg entries? It is so simple, just add the line: atc_parking_codes=*ICAO code of the airline*

There is a new video on youtube. It makes me hope, that it will be released very soon. It is in german, but maybe you want to take a look at it:

<br /><br />Just use FSX ATC. When it wants to vector you to the airport, use the ATC Menu to choose another Approach.<br />Don't choose an ILS Approach as it is bugged and only supports transitions from VORs.<br /><br />Choose a RNAV or GPS Approach and then you can choose a proper transition for your STAR.<br />ATC gives you an direct to your selected Transition, and when you arrive there it hands you over to the Tower.<br />You can still fly an ILS Approach, ATC just doesn't use the phrase.<br /><br />That is maybe not very real, but it gives you all needed freedom to fly your Approach and STAR and lets you use your AI Traffic and Schedules.<br /><br />This, of course, works only when the Approaches and Transitions are listed in the AFCAD, otherwise you could add them yourself with ADEX.<br />Airports which support this method are e.g. all airports by Flightbeam, Montreal by FlyTampa or Helsinki by A-Flight.<br />(There are surely a lot more but I don't know exactly as I edit all AFCADs myself)

It is currently on ice, because the developer also creates professional GFX for television etc. and it looks like he has too much work to continue the A380 right now.