ATC UI Wheel (For speed and safety!)

[EchoFiveWhiskey]

ATC User Interface Wheel

 

Short description: Add a wheel for ATC Comms

Detailed description: See below

Commands to add:

Items to add: User Interface Wheel same as animations

How would your suggestion improve the server?: Would improve flying safety and user experience overall

Additional information:

 

Aviation RP has really "taken off" as of late and one issue I've run into while flying is that I just don't have the ability to type fast enough to get a long ATC message over the comms while maintaining control of my aircraft! Other, faster typers may not have as much of an issue with this but I know it would be a welcomed change if we could revamp the ATC/Comm system to a faster and safer method. 

First and foremost I'd request that we make an exception to the "no bind" rule for pilots (anyone in an aircraft, really, so that you could be a pilot in training or a co-pilot). This would be the fastest and safest way to communicate, I believe. 

However, if this weren't possible (and, even if it were, really) there's another alternative that could serve as a neat and effective middle ground: The ATC UI Wheel. 

The wheel would be exactly like the wheel you use for animations, and just as customizable, but for the purpose of constructing a message quickly and safely, minimizing the time away from the controls. Let me explain:

https://imgur.com/CTOM5Pq

So, looking at the picture we can see how this would work (don't think to much about the specifics of the example, it's just for proof of concept)

1. You'd choose if you're taking off, landing, or performing some other maneuver, perhaps ascending or descending, etc.

2. Say you choose to take off, the second wheel would come up with the list of airports and helipads (that you could customize based on your preferences, just like animations), in this example, LSIA.

3. The third wheel would come up listing the possible runways or helipads that are available for takeoff (or landing if you'd be landing) So on until you have constructed the full message as required. The code required to implement this would look at the information about the aircraft itself (like the N number) and add that into the message appropriately. At each step you'd have a 'back' option and at the end of an acceptable message you'd have a 'send' option where the code would construct the message based off your input and send it off. It sounds complicated perhaps but really it's just clicking through a small number options like a flowchart instead of having to type it all out and lose control.

This would conceivably be able to handle most of the common calls one would perform while flying, with only a small number of outliers remaining. Once the pilot gets familiar with their own personalized layout they'd be able to use it much more effectively, safely, and quickly than typing it all out. Plus it would guarantee they don't forget information and that it's all in the right order. 


EDIT: Added the template that I forgot (sorry!)

Edited June 29, 2020 by EchoFiveWhiskey
Add Template

[St3fan[NL]]

Seems like ALOT of work for Devs while little to 1% of the community use ATC.

 

You can use /atc, making this you might aswell use keybinds..