I’m practically drooling with anticipation :-)

This could become one of the most interesting ATC robots around !

If only it could have an Xp12 port too 🥰

Edited yesterday at 08:59 AM1 day by jcomm

I'm also disappointed that there isn't a version of XP12. I use both simulators, and I hope it really does work better than the current alternatives, which have a lot of extra features but seem to fall short on the basics.

11 minutes ago, Aglos77 said:

I'm also disappointed that there isn't a version of XP12.

36 minutes ago, jcomm said:

If only it could have an Xp12 port too 🥰

Sorry, just not going to happen. Supporting one moving target with Asobo is challenging enough!

18 hours ago, kevinfirth said:

Interesting - those conditions are relatively calm, bit of fluctuating wind direction, good visibility, but nothing that would significantly affect flight operations at 7kts? My Claude research on which that ruleset is based included this....so its not surprising vox didnt include rw27. Wonder if there was some special case that the controllers used 27 for? Do we have any data on what/how many a/c landed using 27?

Strong crosswind (>15kt component) from SW/NW

09/27 brought into use

Well, from my own personal experience having visited EHAM many times is that, its usually operated when there's a strong, direct west wind when this becomes more preferable to operate than when the winds are in a NW or SW direction which is when the 18/36 runways are preferentially used.

So yes your summary of >15kts fits this scenario quite nicely I would say. By and large in contrast to other runways, it is not operated as frequently.
In terms of runway usage I have seen data for % used but I am not sure if I have seen volume in terms of actual aircraft movements.

16 minutes ago, 787flyer said:

In terms of runway usage I have seen data for % used but I am not sure if I have seen volume in terms of actual aircraft movements.

Latest EHAM rwy info ops from week 25May - 7 Jun:

36% for 06/24

32% for 18R/36L

13% for 18L/36R

12% for 09/27

7% for 18C/36C
0% for 04/22

Source: www.schiphol.nl

16 minutes ago, 787flyer said:

Latest EHAM rwy info ops from week 25May - 7 Jun:
36% for 06/24
32% for 18R/36L
13% for 18L/36R
12% for 09/27
7% for 18C/36C
0% for 04/22

While interesting, the numbers themselves don't have any bearing on which runways are usually allocated in any given conditions. I've updated my understanding of how things work at EHAM based on your and others input thanks!. I'll use that to create a more up to date ruleset that gets as close as reasonably possible to the real life restrictions and allocations. That will be over the coming weeks though. So for now, thankyou for everyone's input on EHAM - I think the discussion about the tool has shown how powerful it can be (and that there are improvements to it that can still be made).

• Tomorrow, I'll start to go into a little bit more detail on the interface and options you will find.

• After that, I'll look at an overview of some of the VFR capability.

• then we'll circle back round to consider some of the IFR, then VFR intricacies.

  Any questions on those - I'm happy to field them - pass your message!

All flight-ops are suspended during the daytime here. Temperatures are high enough to make my rig creak unfortunately. 40deg C doth not make a happy CPU! 😢

Here's the interface for VoxATC in-sim....

The panel display above can be displayed and interacted with in several different ways.

1. You can have the panel open in the simulator on screen as shown above.

• If you have a microphone connected you can speak instructions to Vox

• If you don't have a microphone connected, or don't wish to speak, you can use the prompt mode (as shown above.) When there's an input required from you as a pilot it will be shown in the prompt line, along with a 'Say it' button. Just click on the say it button and Vox will speak your input for you.

2. You can have the panel open in a second monitor so it doesnt take up any of your screen.

3. You can have the panel open in a networked device such as your phone or a tablet.

• the buttons that are clickable on screen are useable in touch sensitive devices.I often use the panel on an ipad and select any input with a finger.

It's also worth noting that the menu button allows you to quickly and easily change comms frequencies when needed.

• Vox will instruct you to change frequencies where required in the instruction/prompt line.

• You can do this manually in your aircraft, or you can just press the menu button to automatically change comms without having to look down and fiddle with cockpit systems.

• I find this incredibly useful when either in a high demand environment (for example on approach with busy vectors) where you are a single pilot managing everything, or where I'm using head tracking and it gets really awkward trying to keep the view centred on awkward little clickspots.

Edited 2 hours ago2 hr by kevinfirth

Do you have to speak exactly as the VoxAtc prompts display? Or, does VoxAtc recognize various ways of saying the same thing?

50 minutes ago, flyblueskies said:

Do you have to speak exactly as the VoxAtc prompts display? Or, does VoxAtc recognize various ways of saying the same thing?

You do not have to speak exactly as the prompts display, but they do contain all the necessary information and structured in a professional comprehensive manner. SO, treat them as a recommendation, something that would in most cases be real world acceptable.

As Ive covered before: Vox ATC uses a locally installed neural processor working in conjunction with windows speech recognition. VoxATC therefore takes two inputs, one from speech recognition and the other from the neural processor and determines the output it works with.

• This vastly improves accuracy over simple speech recognition alone.

• It requires no internet connection, no external AI and no subscription costs.

• It does require a little training by the user and some continued developer tweaking of the local neural processor rules to massage out edge cases - a process of continual improvement.

  (and last but not least, which specifically answers your question -->>> )

• The voice recognition system is also as a result much more flexible. It intelligently expects and looks for certain types of responses in different phases of flight. It recognises keywords independently, so for example, rather than having to read back a controller instruction strictly verbatim, you can successfully read it back correctly, but in any order. If you make one element of the readback improperly, VoxATC will repeat only that element back to you for correction.

In short, you don't have to speak exactly as the VoxATC prompts display, but get it wrong and you should expect the controller to pull you up on it.