Discussion in 'Airport Design Editor' started by jvile, 3 Dec 2007.
see post below
Thanx for the info. Didn't mean to start an aisort question,but...I'd created an airport with FSXplanner. I made some gates for a 737 which worked at first. After adding some GA parking,GA flight plans worked great but the 737 gates did not. Ramps and gates show up in FSX, but after compiling flightplans, aisort says it can't find parking for the 737. Probably something simple I missed. I did lots of airports and flightplans in FS9. FSX sure is a different beast.
Adding Airport parking for AI Planes is one of the fundamentals that ADE is designed for. I see no reason why we cannot discuss it here.
Jon may break this thread into 2 different ones (altitude and AI Parking) so Topics stay on track.
Reggie is the leading FS9/FSX expert on all plane parking and will probably post here when he reads your behavior parking concerns.
Reggie did have post on parking rules based on 4 years of continuous study but some of those were accidently deleted under new management at PAI. We are working on new Tutorials for all the rules that FSX plays by and will be added to the ADE web site eventually.
The ADE team (as seen in the ADE Documentation) is made up of the most knowledgeable people in the Aircraft/Airport, Visual/non-Visual behavior of FS9/FSX. We are here to expand the Users knowledge base also.
Aisort just presents created flight plans to Traffic Trafficdatabasebuilder (traffic tool box), The file "TBldr.txt" is created by TDBB .
The error can't find parking for ** at ** has multiple meanings.
Here are some I have found While developing Aisort.
Gates have a 10 mtr range,gaparking has a 5 mtr range,Flightsim might park a 737 in a 36 Mtr(heavy) parking spot BUT TrafficDatabasebuilder will not accept any gate larger than Medium gate (23 mtrs) for the 737.
If the runwaylength is shorter than the min runwaylength for an aircraft, can't find parking will be gennerated.
In some cases I have only one air craft useing an airport but TDBB requires three parking spots of the required size at that airport,(workaround = have one space at the airport then lie to TDBB ie manualy add more more parking spaces in the "AirportList.txt" under the ICAO of the airport then compile ,TBBD will accept it.
I have been procrastinating over have Aisort read the TBBD log file then creating a file with possible solutions to the errors created but at the moment it's bigger than me.
Hope I have cleared the air a bit.
Thanks for chiming in on this Frank
I got confused on AISort vs AI Seperation in my post above so I did a edit.
AI Sort is a good program to create TDBB FP's but I think it only fair to warn Users that it plays by the rules of FS9/FSX and takes Lee Swordy's TTools that developed major airline flightplans and destroys them.
If a large AI Airline like Southwest or Delta has FP's made with TTools and AIsort converts these to TDBB FP's then most of the original FP's are deleted and a Airport like Houston or Atlanta loose many many arrivals and departures. That is not just based on parking available on parking size restrictions, turn around time restrictions but also the exposed throttle valve that FSX now has that was not exposed in FS9.
There are 2 schools of thought.
Build FP's using all the rules that TDBB applies which does not allow for realistic Airline Flightplans
build Flightplans with TTools and then convert those with a Utility such as AIFPC to fit into the FSX flightplan scheme.
I personally prefer the second rule and then use Reggie's FSX GA Traffic bgl flightplans so the FSX GA planes and default FP's are used in FSX rather then porting over FS9/FP's and GA Planes.
Everybody has their own preference but the pro's and con's must also be weighted.
What would be a nice feature is if AISort could weed out all the rules applied in a TDBB FP and allow the FP Developer to choose the option of rules. Maybe AISort is doing this now and I missed it because I have not used in sometime now. Please correct me if I have said something here that is no longer true and it is a pleasure to see you over here on this forum.
Some time back I used Aisort to sort out my flightplans but when compiling came up against the brick wall of parking spaces. I started adding parking spaces to the AirportsList.txt and the file grew and grew. By accident I unrecoverably deleted it and mentally groaned at my stupidity. Then I discovered AIFPC and this has completely solved the problem. Using it to compile flightplans in the Ttools format is as easy as pressing the compile button.
I have compared the filesize generated with the original by WOAI or PAI and they are identical so it appears to lose nothing in the compiling process. I wondered why Aisort didn't do this as I had become accustomed to using it(my thanks for your program). Perhaps this could be a guide to how best to develop your own version.
I use FS9 format traffic files especially when developing AFD files since one can fill every parking spot.
If I receive any FSX format traffic files, I convert them to FS9 format using AIFPC.
I developed Aisort to work with TBBD to follow the rules FsX wants us to follow and my programing ability is nowhere good enough to build a compiler,
as TBBD produces a log file I restricted error checking in the sort routine to things that Aisort can fix without user intervention.
In very large files Ie Flight1 Traffic I split the TTools source file into 295Kb lots then run them through Aisort and combined with ScruffyDucks ADE I got all aircraft flying ,Done the same with World ga,.
I found that All the errors that TBBD throws up MUST be attended to if a plan is to work.
Its a lot of work but when done all aircft fly.
Thanks for your update. I'll revisit Aisort in the near future to see how it now works.
Thanks for your input on AISort. I used it because it seemed to be the most like ttools, which I was able to understand. I have AIFPC and don't seem to be bright enough to get to work. Maybe I'm making it too difficult. I'm one of those lucky Vista users. It's hard to get anything to work. Took two weeks, or so, to get simconnect up and running. I was aware of the parking radius and runway length rules, but had not heard the extra space idea. I'll keep at it.
You are amoung a bunch of beta guys here that use Vista 32 and Vista 64 on SP1a, SP2, DX9 and DX10 modes.
Of course we also have other team members using XP2 with different FSX version so we should have all those bases covered.
We also have tons of AI running with many various FP programs from payware to freeware.
Adding more of the same size parking did the trick. Now the 737 is happy. Now on to fuel trucks and airport vehicles. Those ought to be good for a few more gray hairs. Oh yes, and getting voicepak to call my airport by name and...
Separate names with a comma.