3 hours ago, AnkH said:

Proof or it did not happen with visible landing gear. Even Asobo devs claimed it fixed, one single startup from the sim showed how wrong this claim was 😉

I presume what's meant by the OP is that landing gear is visible as per Asobo's LOD management, i.e. within a certain range. I can't see how an ATC app would address that problem

On 6/10/2026 at 7:26 AM, anilcougar said:

WP-001: Aircraft Movement

https://youtu.be/_rmUFC5EmxA

Why is the plane moving so far from the taxi line sometimes? Even default ai traffic does better.

28 minutes ago, mrueedi said:

Why is the plane moving so far from the taxi line sometimes? Even default ai traffic does better.

As I told in the post, this video was taken while we were developing the movement engine, those movement bugs are mostly fixed. But thanks for the good question.

1 hour ago, MorrisMinor said:

I presume what's meant by the OP is that landing gear is visible as per Asobo's LOD management, i.e. within a certain range. I can't see how an ATC app would address that problem

Those can be controlled with the ATC software. MSFS doesn't care about if the landing gear is down or up, even the flaps and the lights. You have to scan the whole stack, find the aircraft and change the required variables to work properly.

Right now we're focused on only FSLTL models, but when the beta is ready, we will focus on other static aircraft models too.

Edited 19 hours ago19 hr by anilcougar

Hi Captains,

In this new WIP-003 video I would like to show you how, wide-bodies react to steering. As you know, they oversteer when lining up the runway or taxiing along the airport and you can now see how they move in the proper way. When this video was shot, I was like "Ok now we're creating something different" I really need your opinion about the smoothness off the AI Traffic that we move around. (and just a little note, mathematics always win)

I will be sharing WIP videos every or every other day. Because your comments are super important to us. But this is the last video of the movement engine, now we'll switch to a more serious stuff like the ATC radar and traffic handling.

And I'm pretty sure you will love them too.

As always, with love <3

https://www.youtube.com/watch?v=f5c6LY9-TpM

/Anil

7 hours ago, anilcougar said:

Those can be controlled with the ATC software. MSFS doesn't care about if the landing gear is down or up, even the flaps and the lights. You have to scan the whole stack, find the aircraft and change the required variables to work properly.

Right now we're focused on only FSLTL models, but when the beta is ready, we will focus on other static aircraft models too.

It would need to work with the full range of AIG models 😉

With respect to the WIP-003 video, I would prefer to see the AI planes line up with the centreline when they taxi out onto the runway. As most AVSIM users know by now, I have a bit of OCD where runway centreline alignment is concerned 😁

On 6/8/2026 at 12:24 PM, anilcougar said:

Sir yes sir! We have completely redesigned the movement engine of the simulator. We're not even using a single line of MSFS2024 code for moving the traffic around. The turns are smooth, aircrafts are flaring correctly even crosswinds are visible too.

The level of quality is our main purpose. No arcade stuff, real aviation stuff running on our computers.

Is it possible to get the fr24 live traffic data with your app? Just like how other developers already have like with fsltl.

4 hours ago, anilcougar said:

Hi Captains,

In this new WIP-003 video I would like to show you how, wide-bodies react to steering. As you know, they oversteer when lining up the runway or taxiing along the airport and you can now see how they move in the proper way. When this video was shot, I was like "Ok now we're creating something different" I really need your opinion about the smoothness off the AI Traffic that we move around. (and just a little note, mathematics always win)

I will be sharing WIP videos every or every other day. Because your comments are super important to us. But this is the last video of the movement engine, now we'll switch to a more serious stuff like the ATC radar and traffic handling.

And I'm pretty sure you will love them too.

As always, with love <3

https://www.youtube.com/watch?v=f5c6LY9-TpM

/Anil

Unless it's sped up, the turn into the runway seems a bit quick. But I know its still WIP.

Will there be inertia with these AI planes? In other words, they won't come to a complete stop instantly right?

8 hours ago, anilcougar said:

Those can be controlled with the ATC software. MSFS doesn't care about if the landing gear is down or up, even the flaps and the lights. You have to scan the whole stack, find the aircraft and change the required variables to work properly.

Right now we're focused on only FSLTL models, but when the beta is ready, we will focus on other static aircraft models too.

I guess you did not get the point about the landing gear... we are not talking about landing gear up or down, but about the annoying LOD culling by the sim resulting in landing gear no longer visible when looking from a certain distance...

On 6/11/2026 at 3:55 PM, anilcougar said:

https://www.youtube.com/watch?v=mpliMQSYhWg

Hi Caps,

Here comes the second WIP-002 video of the series.

Before the video, I want to say something very clearly.

I opened this topic because I wanted to share the development of this project with other simmers. Not with marketing words, not with a polished trailer, but with actual WIP videos. Step by step. Task by task.

The idea was simple: show what we are building, get feedback from people who actually care about ATC and AI traffic, and hopefully create something better with the help of AVSIM.

But honestly, some of the reactions here are becoming very hard to understand.

The first video was clearly about one thing: aircraft movement.

It was not the final product.
It was not the final UI.
It was not the final voice system.
It was not the full ATC logic.
It was not traffic density.
It was not a release trailer.

It was one WIP video about one task.

Still, some people replied as if I had claimed “this is the complete product”. Some people started talking about vaporware, subscriptions, company website, AI coding, developer background, maintainability, and almost everything else except the actual thing being shown.

That is not technical feedback.

That is noise.

And I will be very direct now. If this continues, if every WIP video turns into people judging a product they have not seen yet, then I will simply stop sharing WIP videos here until the final product is ready.

Because there is no point in sharing unfinished development footage if some people are going to treat every unfinished part as final evidence against the whole project.

If the movement looks wrong, say it.

If the aircraft turns badly, say it.

If the taxi behaviour does not look realistic, say it.

If something in the video is technically weak, say it.

That kind of feedback is useful. I can respect that. Actually, I want that.

But if the point is only to ignore what is being shown, not read what I wrote, and then create a negative story around the project, the company, the team or the final product, then I am not going to feed that anymore.

There are many seperate tasks in this project. Movement, traffic injection, airport graph handling, runway logic, voice, CPDLC, AI brain, ground operations, emergency handling, handoffs and more. Some of those parts are already in testing. Some are still being built. Some will be shown later.

We are showing them one by one because that is how development works.

[nerd data incoming]

We are not building this as one giant fragile script where everything is hardwired together.

The system is being built in a modular way. The ATC brain, simulator adapter, movement engine, voice layer, traffic layer and other parts are separated as much as possible. That matters because if something breaks, the goal is not to rewrite the whole product. The goal is to fix the responsible part.

So no, this is not “AI made a magic addon”.

This is software development.

And software development means building one layer, testing it, finding ugly edge cases, fixing them, and moving to the next layer.

[/nerd data incoming]

The first movement engine video was made using our own movement logic, not the simulator's default AI movement. That was one of the first big challenges.

You have to deal with taxiway geometry, turn radius, elevation changes, aircraft size, speed, braking, smooth acceleration, and a lot of boring things that users should never have to think about, but the system has to handle.

Not all airports are flat.

Not all taxiways are clean.

Not all scenery data is perfect.

For example, when this product is ready, take your favorite aircraft to VNLK and just watch how AI traffic behaves there. That is the kind of airport where you really understand why movement is not a small detail.

This is the level of behaviour we are trying to build towards.

And that is also why I started with movement. Because without believable ground movement, nothing else matters. You can have the best voice system in the world, but if the aircraft moves like a toy, the immersion is gone.

The first video I shared was older footage. This one is also not from today. There is a reason for that. I want to show the progress in a sequence, not just throw random clips and call it a day.

This next video is still WIP.

It is still not the full ATC product.

The focus is aircraft ground movement and the next step of airport flow.

Bigger aircraft.

Smoother turns.

Better ground behaviour.

More believable movement.

And yes, I want feedback about this. Real feedback. Good-will feedback. Technical feedback. The kind of feedback that can make the product beter for all of us.

But I am not interested in defending myself against assumptions every two pages.

I am a simmer too. I am one of you. I am not standing outside this community trying to sell some random hype to you. I want this product because I want to use it myself. I want better ATC in the sim. I want better traffic. I want airports to feel alive.

About subscription, I already explained this before, but I will say it again shortly.

I know many people do not like subscriptions. I am not in love with them either. My other product, SimPassengers, is a one-time payment product because that product can work that way.

This one is different because there are ongoing systems behind it, and those systems cost real money to run. A lot of money, actually.

But even there, I already said we are thinking about lighter options for people who do not fly very often. Nothing is final yet. When it is final, I will explain it clearly. I am not hiding that.

What I do not accept is people turning every unfinished WIP video into a full judgement about the whole project, the company, the team, the business model, and even who is or is not a “real developer”.

That is not fair criticism.

That is deciding the conclusion first, then looking for something to attach it to.

So from this point, I will keep sharing selected WIP videos only if the discussion stays useful.

If you want to give technical feedback, I will read it.

If you want to point out something wrong in the video, I will read it.

If you want to ask a real technical question, I will try to answer it.

But if this turns into constant negativity and criticism of things that have not even been shown yet, then I will stop sharing WIP updates here and simply come back when the final product is ready.

That is not a threat. It is just the only healthy way to continue building without wasting development time on assumptions.

Anyway, this is WIP-002.

It is not final UI.
It is not final voice.
It is not final traffic density.
It is not the full product.

It is another step in showing how the movement and airport behaviour layer is developing.

Please judge the video for what it actually shows.

With <3
/Anil

"Because without believable ground movement, nothing else matters. You can have the best voice system in the world, but if the aircraft moves like a toy, the immersion is gone."

YES! FINALLY! This is something that none of the other ATC solutions seem to understand at all.

On 6/11/2026 at 6:09 PM, vonduck said:

This sounds very good Anil!

I was thinking too (probably a pipe dream!!) but how cool would it be to have live traffic (however you get that) and at the same time have Live ATC comms injected form the actual feed (liveatc.net) at that airport so you could hear Ground, Tower, Control, Centre etc if you tuned to those freq's!

Also, there is a distinctive lack of people around AI aircraft.. wonder if that is addressable?

Looking forward to what you have in store!

This already exists. It's called PSXT

22 minutes ago, simsuper80 said:

This already exists. It's called PSXT

I use that program bro too! Awesome! How do you activate the ATC within the program settings? I must have missed that... cheers!

23 minutes ago, vonduck said:

I use that program bro too! Awesome! How do you activate the ATC within the program settings? I must have missed that... cheers!

Well. The thing about live traffic is that you can't interact with it. Injecting live traffic based on live ADSB data means that it is you that is not real, where as everything else actually is. The best you can do with PSXT is to block the flight that you are flying and just taxi and fly based on the flight you are looking at on FR24. Maybe even listen to live ATC too.

With beyondatc for example, they get live data from flightradar, BUT beyondatc still controls the traffic movements. So in that case, it's live data information, but not literally live from ADSB.

Edited 10 hours ago10 hr by simsuper80

The traffic seems to be moving in lockstep. They all start moving simultaneously, which seems artificial. Is this something you have looked into?