zlsa / atc

https://openscope.co/
342 stars 107 forks source link

Arrivals always spawn at FL100 #633

Closed Fechulo closed 7 years ago

Fechulo commented 8 years ago

The title says it all... All arrival aircraft are ignoring the altitude stated in the airport file. They spawn at FL100 and climb back up to meet the necessary restrictions.

erikquinn commented 8 years ago

Yeah, it's actually hard coded at 10. And if you notice, it won't be ALL arrivals, just all "pre-spawned" aircraft. In other words, aircraft who spawn at the starting fix of their route, not immediately at the start of the game. Was a workaround for it being really hard to get them to look through the altitude restrictions in the STARs and find the appropriate altitude to spawn at along the descent path. It should be fixed though, just wasn't a high priority when fixing the original issue of long wait times on getting arrivals.

Fechulo commented 8 years ago

That makes sense. They probably don't need to spawn at an exact altitude along the glidepath (Option A), I think it's easier if they spawn at the altitude of the next restriction (Option B): spawning

erikquinn commented 8 years ago

Right. Honestly though, it will already have to step through each fix in the star, and find the altitudes, and it's hardly any more effort to spawn them in accordance with option A as opposed to doing option B. After all, if I have to find the next altitude, it's usually just as easy to find the previous one as well, and interpolate to an appropriate altitude.

Fechulo commented 8 years ago

True, I hadn't thought of that. Option A is clearly more realistic but I initially thought it would be harder to code. If you think they're pretty much the same, then I suggest going for A.

erikquinn commented 7 years ago

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope, and thus, all issues are being closed. If this is still an issue with the latest version of the sim (accessible at http://www.openscope.co), or is a feature you still think we are lacking, please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.