12 hours ago, JYW said:

Could anyone kindly advise if there has been a video featuring ATC / voices in this thread yet?

I don't want to read all 9 pages of marketing 101, unless I know there's a video worth watching in there.

How do you know if it’s 9 pages of marketing 101 when you haven’t even read it ?

14 hours ago, blueshark747 said:

let the developer cook in his thread

What's all this talking about cooking? Is this a new young person's saying?

I thought cooking was something you did to make food.

8 hours ago, Simicro said:

Looks like some posts here are written with AI.

Baseless allegation so far as the OPS's posts are concerned. Most of his posts return zero confidence in AI generation while those that do are within the human written 20% or less AI confidence score (many 0% or with 1 -5%).

But perhaps your allegation is related to someone else's posts?

40 minutes ago, Ianrivaldosmith said:

I thought cooking was something you did to make food.

As an accountant I couldn't possibly comment

8 hours ago, Ianrivaldosmith said:

What's all this talking about cooking? Is this a new young person's saying?

I thought cooking was something you did to make food.

In slang, "let him cook" means to let someone do their thing, share their ideas, or work on a task without interrupting them. It is typically used when someone is displaying a specific talent or formulating a brilliant plan, and you want others to give them space to finish what they are doing.

24 minutes ago, simsuper80 said:

In slang, "let him cook" means to let someone do their thing, share their ideas, or work on a task without interrupting them. It is typically used when someone is displaying a specific talent or formulating a brilliant plan, and you want others to give them space to finish what they are doing.

Ding... ding.... dong we have a winner!🏆

Now let's get back on topic, let OP have his thread back and stop with the AI slop accusations.💡

Edited June 16Jun 16 by blueshark747

Anything new?

1 hour ago, simsuper80 said:

Anything new?

Yes we're c00king (:

Hello Captains, Long time no see (:

I know we've been quiet for a little while but today's update is the main reason for that. I will show a video today that displays the main reason why we were quiet. In this WIP video, you will be seeing the 3 main decision making layers of ACE of ATCs which are

1. The brain layer

2. The AMAN layer

3. The Director layer.

The scenario starts with 20 arrs into LTBJ 34R. 10 aircraft coming from north and the other 10 are coming from west. All 20 are flying the STAR based arrival procs. The ones coming from the north are following BERG1E and the ones coming from west are following VEXO1F. The director finally merges both streams nto one runway squence. The most important part is that this is fully automated after the scenario starts. There is no manual sequencing, no hand-placed arrival path, and no scripted landing order.

The system reads the procedure environment from navdata, keeps the surrounding fixes visible, builds the arrival picture, predicts threshold timing, applies wake-aware spacing, and then lets the Director manage the merge into a single RWY 34R landing flow.

This is also why the video is a raw radar/debug view rather than a cinematic edit. We intentionally kept the fixes visible around LTBJ so the procedure geometry can be followed. It is best viewed full screen. And remember the speeds are 5x increased. Didn't want to take to much of your time. Because landing 20 airplanes seriously takes time.

A few notes about what is shown here:

- Two independent STAR arrival feeders are active at the same time
- The AMAN layer builds the arrival sequence
- The Director layer protects the runway flow
- Wake category is considered while building the spacing
- The flow is data-driven, not airport-scripted

Around 2:50, both feeder streams are clearly visible converging toward the RWY 34R sequence.

Around 3:50, the traffic density increases around the merge area, while the Director continues feeding one runway sequence.

Right now this video shows aircraft following STAR-based flows. We will also share the fully vectored version, where the Director has more freedom to build and manage the arrival flow with vectors instead of simply following the published procedure structure.

The same scheduling logic is also the foundation for DMAN. Soon, we will show the departure management side, and after that, the more interesting version: arrivals and departures sharing the same runway/resource picture.

In other words, this is not just “arrival traffic”. This is the beginning of the common traffic-flow layer that will support both AMAN and DMAN and operated by the Director.

About voice: we know we have been quiet on that side as well. We are deliberately playing that part by the book. The business terms are agreed in principle, and at this point we are waiting for the signature process before we share more details publicly.

As always, with love and blue skies.

/Anil

Video:

For those interested AMAN (and DMAN) were developed at Eurocontrol in the late 90s

https://skybrary.aero/articles/arrival-manager-aman

4 hours ago, SierraDelta said:

For those interested AMAN (and DMAN) were developed at Eurocontrol in the late 90s

https://skybrary.aero/articles/arrival-manager-aman

Thanks Søren.

Yes, that is the conceptual direction we are working from. The sim implementation is our own, but the idea behind it is the same: do not just react when traffic is already on top of the runway. Build the traffic picture earlier, predict the merge, and manage the flow before it becomes a last-minute problem.

That is why we are treating AMAN and DMAN as part of the same traffic-flow layer, not as separate gimmicks.

DMAN is next, then we will start showing arrivals and departures sharing the same runway/resource picture.

And also, one final note. If you guys know what SWIM is (Systemwide Information Management System) the system communication service is also based on the brand-new shiny SWIM protocol.

/Anil

Hi Captains,

Here comes our new WIP video showcase.

In this video, you will see three operational layers working together: AMAN, DMAN, and the Director.

AMAN is responsible for arrivals.

DMAN is responsible for departures.

The Director is responsible for coordinating the overall traffic flow and making the runway-resource decisions between them.

As you can see on the ATC radar screen, there are two arrival streams coming in: one from the north and one from the west. The system sequences the arrivals, manages departure opportunities, and the Director decides when departures can line up, take off, or hold based on the live arrival gaps.

There is one small issue in the middle of the video: you will see a rogue 737 moving through some traffic holding short. That one is completely on me. I accidentally tapped the “Spawn puppet” button during the live test, and that caused it. It is only a development/debug feature, of course; there will be no “Spawn puppet” button in the final release.

And just not to forget: we have completed the voice-related paperwork, and a very BIG surprise is coming in the next 1–2 days.

As always, with love and blue skies.

ps: The video playback rate was increased x5 just to keep it short. It's actually a 22min video.

/Anil

Edited Wednesday at 04:37 PM1 day by anilcougar

Two points I would like to make after watching that video....

• The waiting aircraft need to be on the taxiway centreline

• Would it be possible to get a waiting aircraft to start the taxi out to the runway before the landing plane has exited the runway (assuming that there are no other aircraft on short final)?

47 minutes ago, Christopher Low said:

The waiting aircraft need to be on the taxiway centreline

And, even more importantly, behind the hold short line. 😱

In terms of traffic flow, this is already looking pretty good though!

Two things. One, at around 2:50 traffic comes close on the radar display to a collision. Two, management in the air overall appears to be pretty good maintaining spacing on arrival, but for the departures, traffic is not lining up after the landing traffic crosses the threshold. You could increase departure rate by getting traffic to line up earlier.

The threshold crossing is obviously a bug in early development, so easy to let go. The voice thing will be interesting to learn about. Waiting with cautious optimism.