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.
iMac5K 27” (2015), i7 4GHz, OSX 10.14.6, 32GB, AMD M395X 4096MB, Saitek X52, TPM, Radio, Switch & Multi, TM MFD, XP11.35r1, FFA320v0.11.2-2305, ToLiSs A319 v1.3.3, JDA320 v3.4r1, JDA330 v3.2r1, XL v4_250719, FM v2.6r2, GndHdg v.4.010719, Air Plugin v4.8.3, FWL 2.7.19, 3jFPS-wizard, PI v2.73.06, NOAA v2.4.4, XSPs v2.75, XCL v1.37, BPB v0.47, SAM 1.1.0