Proposal for a client-side method of de-conflicting players on and around runways

[Moach6908]

This was posted on the highly related topic: Make it impossible to spawn on runway in Live mode - #67 by Moach6908

It is an alternative to enforcing any Do’s and Don’ts on players, which should nevertheless provide a satisfactory means to resolve runway incursions and air traffic problems.

To quote myself:

@Moach6908

I have given this some thought, and came up with a system that should make the problem go away.
It works entirely client-side so you don’t need to tell anyone what they can or cannot do.

Consider this:

The red zone is a bubble covering a runway, It is no more than 50~100 feet high.

The blue cone is the “approach zone”, it extends 5nm downwind of the runway and goes up to 3000ft AGL

Here’s how it works for each of those planes:

The Red plane is stopped on the runway (red zone). He is invisible to the Purple plane.
The Blue plane on the taxiway. He is visible to all and sees everyone.*
The Purple plane is inside the approach zone. He is invisible for Red.
The Green plane has departed the runway and can be seen by and sees everyone.

*If Blue taxies ahead of the hold-short line, he enters the red zone. He is now invisible to Red and Purple, who are also no longer visible to him. Once Blue takes off, he becomes visible and able to see everyone again.

You can make a binary truth table of plane visibilities for each other, it’d go like this:

This being all realized in each player’s own computer, there is no need to have new data going over the MP network. And more importantly, all players can configure the exact parameters however they like.

You could maybe select friends to be visible at all times, if you’re formation-flying with them, for instance. Or set different zone geometry rules for human or AI traffic. Many options exist and all are up to the individual player’s preference.

This may even be implemented as a mod.

Thus, people don’t need to bother anyone, and nobody should bother them. Everyone can spawn anywhere they like, and the poor guy on his third missed approach doesn’t have to do yet another go-around.

Conflict avoided.

So hereby I present this as a completely separate request.
It serves the same purpose of the thread in which it originated, but by entirely different non-intrusive means. Whether or not these requests should to be merged is left up to the forum staff.

I only hope that this makes its way to developers for due consideration.

[N316TS]

Hi,

You’re in luck, because it has already been considered by the development team and may get implemented some day. See this Developer Q&A transcript:

@N316TS

Runway Spawn Points at Hold Short Lines - Timestamp

Jayne – I know last time we talked about this, Martial, you mentioned you don’t know if we will take away the [runway] waiting point as a default spawning point because for newcomers, it might be hard to understand that you are not starting the flight in the alignment of the track. So it’s something we’re talking about. Is there anything you can clarify, here, about the original question?

Martial – Yes, everybody knows that now. So we followed the thread in the forums. And there’s plenty of good ideas there, and basically, putting by default a user at the waiting points, we could prevent those people from spawning when you’re about to land, but it’s not sufficient because we are talking about newcomers, we’re talking about beginners that don’t know that perhaps you should follow some procedures and rules not to go to the track before people are landed. So it won’t solve all solutions, so we are thinking about a solution in two steps:

1. Allow some users to be spawned onto the waiting point if they want to.
2. The other solution is another system to hide people on the track when you are about to land when you’re on final.

[Moach6908]

Here’s hoping!

[Hester40MT]

Several posts have been deleted from this wishlist.

Keep all replies related to this wish.