cmckjodi wrote: pwalchester wrote:
Did'nt see any lockups earlier but had lockups with 2.0 and 2.1b7 now, plus the flight timings with 2.1b7 are out of step. I've come to the point where maybe spending too much time firefighting while we're in the current 2.1 beta phase is a waste of resources.
I think what JAR really needs to do is have better traffic logic. No need for planes downfield or waiting to take off to be waiting so long for a planes on approach. I think 5 to 3.5 miles out is the limit depending upon weather and visibility. I'm sure having the right traffic timings is a huge challenge, but the main thing IMO would be to have more efficient departure clearances and also a way for a user to define departure and arrival runways I think would really help. For instance 4R for departures, 4L arrivals at xxxx airport. Busy airports are often setup this way as in real life. But still some nice improvements have already been made. We keep testing for JAR.
You can define runway take off and landing restrictions in airport editor.
iMac Retina 5K 27” (2015), Core i7 4GHz, OSX 10.13.3, 32GB RAM, AMD Radeon R9 M395X 4096MB, Saitek X52, Saitek TPM, Radio, Switch & Multi Panel, 2xThrustMaster Cougar MFD, XP 11.11r2, A320v3.2r1, A330v3.00b2, XL v2.1b4, FM v2.6r1, GndHdg v040118, SMP4.5, RWCv1.1, FlyWithLua v2.6.5, 3jFPS-wizard, PythonInterface v2.73.06, NOAA Weather v2.4.1, XSaitekpanels v2.70, Xchecklist v1.28