Finally resolves #551. Really sorry it took so long to get around to this one; it was an issue that was rather detrimental to gameplay... Anyway, this will fix it.
At the beginning of a new game, you will no longer have to wait for arrivals to reach the boundary if their spawn point is a long way away. Depending on the frequency set in the arrival stream, if there is enough room to add plane(s) between the spawn point and the airspace boundary, the game will now do so.
An example is at Miami, where we put in the full STARs, including entry points hundreds of miles from the airspace boundary. Used to be that it would take as much as 10-15 minutes to get the stream spawning the furthest away to actually reach the airspace. Below I've provided a screenshot that shows the aircraft that are spawned beyond the spawn point, up to the airspace boundary. As indicated in the console, this screenshot was taken about 4 seconds into a new simulation session.
Finally resolves #551. Really sorry it took so long to get around to this one; it was an issue that was rather detrimental to gameplay... Anyway, this will fix it.
At the beginning of a new game, you will no longer have to wait for arrivals to reach the boundary if their spawn point is a long way away. Depending on the
frequencyset in the arrival stream, if there is enough room to add plane(s) between the spawn point and the airspace boundary, the game will now do so.An example is at Miami, where we put in the full STARs, including entry points hundreds of miles from the airspace boundary. Used to be that it would take as much as 10-15 minutes to get the stream spawning the furthest away to actually reach the airspace. Below I've provided a screenshot that shows the aircraft that are spawned beyond the spawn point, up to the airspace boundary. As indicated in the console, this screenshot was taken about 4 seconds into a new simulation session.