I dont know if my problem is ADE,AIFP,or me.I can not get AI traffic to start at the last 20 airfields I have created.If I write a plan from a working airfield to one of my working airfields,the aircraft appears and flies the first leg.If I fly with it,and when it lands park alongside,and wait until it is time for the return leg,the aircraft takes off normally.But if I fast forward to the take off time there is no aircraft there.If I restart FSX and go to my destination airfield just before time for the return leg,there is no aircraft there.I have drawn a very basic airfield and written a plan for it,but it also does not work.and I dont think I can have any faults on the airfield.If I write a plan for one of my older,working airfields,it works which seems to suggest that AIFP is not at fault.
-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
problem
- Thread starter collltip
- Start date
- Messages
- 8,893
Adding to Sandra'a request there is a timing code built into FS9/FSX.
If you want to see the AI Plane before it departs you should set the time 5-15 minutes before departure.
If you want to see the plane at its destination airport you should set the time 5-15 minutes after arrival time.
If you want to watch the plane approach the airport and land you should set the time 15-20 minutes before the FP arrival time. This gives the AI Plane time to transition the visual zone sectors.
Your FP does not have the final say of when a plane leaves or arrives but that comes from the AI Engine once the FP gets processed. Additional troubleshooting requires the TrafficToolBox .dll SDK utility loaded so you can call up and see where the AI Plane is located.
Last edited:
Problems
Thanks for the replies.Sorry if all the following appears as one paragraph.I am using FSX and for the second of these plans,v1.37.05. for the two airfields.The first plan uses airfields made some months ago,and was probably made with an earlier version.I have just written and tested these plans using the same aircraft.
AC#1,1135,1%,24HR,VFR,12:00,12:19,30,R,717,A146,12:30,12:49,30,R,718,AF45
AC#1,1136,1%,24HR,VFR,12:00,12:19,30,R,719,AF72,12:30,12:49,30,R,720,AF71
The first plan using older airfields works normally.The second, using recently made airfields,does not produce any traffic.
If I write a third plan from AF45,which works OK,or from a stock airport,to AF71,the traffic works.But if I go directly to AF71, at any time,nothing appears.
I have 20 recently made airfields,none of which produce traffic when I write plans for them.
Thanks for the replies.Sorry if all the following appears as one paragraph.I am using FSX and for the second of these plans,v1.37.05. for the two airfields.The first plan uses airfields made some months ago,and was probably made with an earlier version.I have just written and tested these plans using the same aircraft.
AC#1,1135,1%,24HR,VFR,12:00,12:19,30,R,717,A146,12:30,12:49,30,R,718,AF45
AC#1,1136,1%,24HR,VFR,12:00,12:19,30,R,719,AF72,12:30,12:49,30,R,720,AF71
The first plan using older airfields works normally.The second, using recently made airfields,does not produce any traffic.
If I write a third plan from AF45,which works OK,or from a stock airport,to AF71,the traffic works.But if I go directly to AF71, at any time,nothing appears.
I have 20 recently made airfields,none of which produce traffic when I write plans for them.
- Messages
- 34,981
- Country
What won't? ADE?
- Messages
- 8,893
collltip
Your FP does not have the last say and when passed to the dll FSX may not show this FP.
Several things you can do as a test.
Find out what the highest terrain is between the 2 airports. If it is 2500 ft then set your Altitude higher such as 3500 ft. FSX has a matrix in the dll files for terrian.
Another test is to set the FP IFR when 2 airports are very close to each other. Let ATC instruct the plane to fly the approach vectors to the airport runway instead of using the FS VFR rule. If airports overlap the VFR circuit away form one airport can be too close to the VFR circuit rule of another airport as per the dll files.
Be sure you are placing your compiled FP's into the FS\Scenery\World\Scenery folder.
I see many post on forums where Users and Designer/Developers say it is ok to place FP's in a Addon Scenery folder. This is a shortcut and a No-No.
FS specifically placed compiled FP's into the FS\Scenery\World\scenery folder. The first algorithm for setting the AI/User plane on a Apron RAMP elevation must load before AFRICA.
A second algorithm then reads the runway elevation at the default APXnnnnn.bgl or the enhanced airport at a higher priority such as the Addon scenery folder. This blocks the runway value in the APXnnnn.bgl. The second algorithm is for AI/User Planes that materialize in the AI Zone sectors. It's purpose is so each landing plane knows what the runway elevation is which differs from the ramp elevation (even though they should always be the same).
Short Cutting how FS uses multiple algorithms to load AI Planes may work fine for some Users. When you create FP's that use airports very close to each other or 3rd party scenery (both Freeware and Payware) the plane may not materialize on the ramp or if it does may be sunk up to it wheels in asphalt.
Last edited:
- Messages
- 12,244
- Country
What
- Messages
- 34,981
- Country
I thought the basic user allowance was 5Mb but maybe I am wrong. If you mail it to me I will post it.
- Messages
- 8,893
- Messages
- 42
- Country
It is only 1 MB. We cannot upload a total of more than 1 MB, including previous files we uploaded. If we uploaded, say a 250-kilobyte file before, then we can only upload 750 kilobytes now, unless we delete the 250-kilobyte attachment, removing it from any messages we attached the file to.
- Messages
- 8,893
Thanks everyone.
Jon,
I tried to post AF71 in reply to bobbyjacks'offer.But I now have 25 newly created airfields,none of which show traffic.My older and stock airports still show older created and newly created traffic.
I suspect some thing went beserk when I installed a later version of ADE or AIFP.I thought it was most likely ADE because I can still produce working traffic for my older airfields,but perhaps it is AIFP.
George,
The AF71_ADE_PC.BGL is only 39K but the ...ade and...ade.bak are both 5.6MB before zipping.I am not at my own computer,but the figures for AF72 are 882K before zipping
Jon,
I tried to post AF71 in reply to bobbyjacks'offer.But I now have 25 newly created airfields,none of which show traffic.My older and stock airports still show older created and newly created traffic.
I suspect some thing went beserk when I installed a later version of ADE or AIFP.I thought it was most likely ADE because I can still produce working traffic for my older airfields,but perhaps it is AIFP.
George,
The AF71_ADE_PC.BGL is only 39K but the ...ade and...ade.bak are both 5.6MB before zipping.I am not at my own computer,but the figures for AF72 are 882K before zipping