Amazing, thank you.
A bug I have noticed: when instructing an aircraft to leave a fix on a specified heading, if you then assign them a heading from present position as they are very close to that fix, their readback is "roger, we will enter the holding" or something similar, but then they just fly the heading.
Hey, really don't want to spam so I'll leave the updated link and let you work on your own time. Thanks so much for all your effort, and you did well addressing suggestions in the last update, so thank you for that!
https://docs.google.com/document/d/1ftVK9WEVSG6UAJRGRa8xA4mDEHpWCXFM2lF568iNil0/...
Hi! I think the solution to the issue of auto arrival clearances and all that stuff is simple:
Add a variable to [airspace] called [extension]. This applies whether a radius or a boundary is in use. [extension] would = a number, representing a number of nautical miles. The number sets how many miles before hitting the boundary line they contact the user.
This would solve so, so many issues and seems really simple to implement. Would be appreciated ASAP - personally I've stuck to creating simpler airports until this was fixed, and I think this may be the solution.
Let me know what you think!
Yep! I think in terms of separation, a specified value per localiser as a minima would be fantastic.
My experience with speed control is that if coming in faster than 250, it's difficult to control. If you reduce it, it jumps to 250, then continues down as normal. As soon as you give a speed of 250 or less, the option to give higher disappears. Even at FL130, the maximum I can give aircraft is 250 unless they come in faster. Especially since TMAs can reach very high (FL250 or so in some cases), 250 knots is incredibly slow.
The reason that early level offs are an issue is because the lack of automatic arrival clearances means that airspace has to be unrealistically extended to allow for the user to manually clear them. Something such as autoarr = true would work, unless the main airport has multiple arrival runways. If that were the case, possibly the player could be able to set arrival runway for arriving aircraft before they enter the airspace?
I understand your reluctancy to complicate things, but I think giving airport developers maximum freedom can only be a good thing. It has true potential to be a proper radar simulator - of course consider the path you take, but it's an incredible base at the moment that seems to be only getting better! :)
Thanks so much for the response.
(2) this is possible by overriding planetype properties but, as the game takes place in the vicinity of an aiport, most planes are below FL100 already so 250KT is the default limit
Controllers can generally give speeds higher (within aircraft limits) - I think 290 knots would be a reasonable cap.
(6) the distance will be reduced from 6 to 4 miles for more convenient waypoint selection
Could this be something customisable? It would be great to be able to set.
I'd like to specifically ask for your thoughts on 7, 9, 10, 16, and also 18 which I added as it's not an insignificant part of controlling a terminal area.
Thank you!
Hey! This is a suggestion list put together by the Endless ATC discord server. I'm sure you're aware of it but we have over 60 members, you're very welcome to join.: https://discord.gg/v4wDGh3.
The list of requested features is separated into easy and difficult to implement, and the most important ones have the number highlighted in red.
We appreciate all the work, and would love to see these features implemented!
https://docs.google.com/document/d/1ftVK9WEVSG6UAJRGRa8xA4mDEHpWCXFM2lF568iNil0/...
