NO AI Traffic in a Custom X-Life ATC Routes (Page 1 of 2)

Hi,

I've looked at your files and found the runway line missing, yes the main runway line is there on the editor RUNWAY tab but there needs to be one on the LINES tab too. I've taken the liberty of modifying your .xlf and cleaning up taxiways in some areas, avoid short runway offshoot lines along the runway as AI planes will head towards the end of the offshoot line away from the centre line before the turnoff point.
Obviously taxiways need naming so ATC taxi instructions can be issued and understood. It's not easy to tell without objects but you may need to revise maximum plane size at some gates, clearance on taxiways, overhanging service roads etc.
If you've not already seen it I produced an editor manual for JAR which is on a 'Sticky' at the top of the Custom ATC routes forum.

Happy editing, Phil

It is not possible to draw lines from the RUNWAY tab, with a new airport like this which has no previous X-Life taxiway files when the editor is first run it picks up the runway end marker coordinates from your apt.dat file and places a line automatically. This is how the line was placed in the .xlf I uploaded and in your original.
If you place your original .xlf in the X-Life/Airports folder and start the editor you'll see the RUNWAY tab line in place but runway lines are missing with the LINES tab selected.

The key question is, how do I make the runway appear in both the LINES tab and the RUNWAYS tab ?.

That's the main problem that I think I have and that's why I do not connect the gates with the runway and it gives me the error of impossible to connect the gates with the runway.

Don't you think so?

Yes, I modified later. I included in my last post MDST files as xlf and zip. Just look the prior post. Don't you see the files?

OK, I've created a scenery folder structure with the apt.dat file you posted. When I load the airport with your MDST.xlf the runway line is missing as you said, this may be down to a glitch when you did the original .xlf file. I removed your MDST.xlf from the X-Life/Airport folder and re-started the editor and the RUNWAY tab is showing the runway line as expected, as this is a small airport it is easy for you to start again, after removing your first .xlf file and checking your scenery folder structure is correct - Custom Scenery/MDST/Earth nav data/apt.dat - start the editor, check the RUNWAY tab has the imported runway line, and then add the taxi lines etc.

MDSD - change short segment marked as runway at each end of runway to 'Hold area'. Taxiways need naming for ATC purposes.

MDST - presents additional problems due to being a runway with no taxiways to the end points.
You need to include turnaround lines at each end, see example file which I made for testing purposes.
Consider enlarging turnaround aprons and taxi area, large arriving aircraft seem to be missing the nodes and taxiing on grass back to nearest runway exit.
Settings need to be chosen to reduce missed approach occurrences, as it's a small airport traffic density and stands busy can both be at max, but runway operation interval from my short time watching needs to be at least 2.5 minutes because nearly all arriving aircraft taxi to the turnaround before returning to the exit.
Consider the start ramps you make available, it's not unusual for available start ramps to be less than the number of gate positions at an airport but it would be nice to cover all sizes of aircraft at start positions.
Gate B5 is set back from the X-Life gate B5 position, not sure which is correct.
If you decide to publish the airport and .xlf specify the settings needed for correct operation.

Hope this helps, Phil

Hi,
1. The example file is MDST.xlf attached to my last post
a.- Yes if you decide to do it you would have to do this in WED

Heli gates just need to be connected to a taxiway, just like any other gate/stand. Parking layout shouldn't matter and taxiway directions can be left as 2-way. I would imagine most helicopters fit into the A & B categories, something like a Chinook would be size C.

Phil

X-Life v2.1r1 is out now and works well, see details here http://jardesign.org/forum/viewtopic.php?id=3747
Gates have Jetways to protect passengers from the weather, these can be animated by using the Autogate system by Marginal, this also provides a docking guidance system, see here https://forums.x-plane.org/index.php?/f … te-plugin/

Phil

Phil, I don't know if I am doing something wrong but installed ver 2.1 R1 and look what is happening.

You can check real arrivals to MDSD in the pictures I attached and look at the actual load of X-Life. No corresponding liveries and no arrivals programmed.

First I replaced the new X-Life folder but almost all the work done was lost, gates settings and no taxiways that were included in previous versions, then I again replace the old folder and only replaced the new .xpl file and you can see what happened.

Any comments?

Regards, Juan

Juan,

Do you have the Bluebell AI traffic installed? If not go to the v2.1 post again, links and instructions are there.

Regards, Phil

Hi Juan,

I don't think this can be fixed in the .xlf file or WED, it's probably more an issue with X-Life now real schedules are used, I have seen this problem at other airports. Only thing I can suggest is try increasing the number of Cargo gates in .xlf if you have room on the apron, other than that try asking the question on the Updates / X-Life V2.1 R1 forum, but JAR are focused on the A330 v3 update at the moment.

Regards, Phil

Hi Juan,

Not sure, X-Life stops following traffic at departing airport around 50+ miles and loads in arrival airport traffic about 50 miles before, you can monitor this on X-Life tower display. As the flight route is 200 miles there is enough distance between airports. I was going to try and re-create this but X-Plane crashes when I try to load the editor at TJSJ so I can't create ground routes.

Phil