P3D crosswind runways

[DuduGuimaraes]

Hello. I´m trying to set up some crosswind runways in SBVT in P3D, and I´m not sure if I´m doing it right.

The runways are 02-20 and 06-24. When the winds are coming from the south/southwest, runway 20 is used for takeoff and 24 for landing. So I set up the crosswind runways as it follows: https://www.img91.com/en/l5QhayAJsvHPfcO

As for the patterns settings, I did the following:

Runway 06 - CLOSED for both takeoff and landing

Runway 24 - CLOSED for takeoff and OPEN for landing

Runway 02 - CLOSED for both takeoff and landing

Runway 20 - OPEN for takeoff and CLOSED for landing

However, when I fire up P3D, traffic still lands on runway 20, which is closed for landing. When requesting to land using the ATC window, I can select both 20 and 24. Is that supposed to happen ? How do I prevent traffic from landing on runway 20 ?

Thank you

Eduardo

 

[Luis Hernandez]

Have you tried checking out FSDeveloper? Possibly someone there has faced this issue already.

[G-RFRY]

Have you put the ADE bgl in the airport scenery and tuned off the default.

Edited May 27, 2024 by G-RFRY

[drobinho]

Getting AI to behave correctly around xwind configs can be really tricky. Everything below is with respect to default ATC behavior, but you might find third-party ATC mods helpful. I personally haven't gotten around to using it, but I understand ATCAPI is quite good at managing runway selection (https://www.avsim.com/forums/topic/589642-new-atc-and-airport-operations-application-testing/).

I think your issue is Runway Length. For runway selection, P3D tends to use three weight categories (based on the values in each aircraft.cfg).

Cat 1 = GA/prop planes only = No longer than 1828.7m (aka it must be shorter than 6,000ft).
Cat 2 = 737/A320-sized acft only (+ cat 1 acft) = No longer than 2103.1m (aka it must be shorter than 6900ft)
Cat 3 = All traffic = [Any value greater than 2103.1m] (aka 6900+ ft)

If you have an airport with really short runways - that don't conform to P3D's coding/categories - then ATC logic can get a bit wonky and may start deferring to its own "best available" logic. Notice that your landing runway is below the cat 1 value above, which means it's probably only available to small aircraft, while your takeoff runway is within the cat 2 value range, which means ATC is probably sending all 737-sized flights onto runway 20 for both landing and takeoff.

You can address this by changing the runway distance values, but you're introducing even more factors to consider (and make sure you have a backup copy of your project file before you start making changes!). For example, let's say you want to extend RWY06/24 by 200m. P3D will add 100m to EACH rwy06 AND rwy24. This means the start of both runways is now 100m into the grass, and AI will now land 100m earlier than before. So to fix this, you slide the runway along by about 100m so the start of your new rwy24 matches the original position. You've now fixed the behavior for rwy24, and in doing so, you've made rwy06 start 200m too early which would look crazy if ATC were to try and use it. The only way I know how to address this is by having two separate files: one file specifically for rwy20/24 and a separate file specifically for rwy02/06.

Unfortunately, there is also the "straight-in approach" bug, which is controlled by both the geography of the airport and the AI's direction of flight. In my experience, certain airports are prone to this more than others (based on runway layouts & direction of most traffic flows). When these conditions are met, ATC/AI will completely disregard the category logic and pick their own runway. So there's a chance you're seeing a combination of *both* runway distance limitations *and* the straight-in approach bug, but it's hard to know first without understanding the behavior around runway lengths.

[Swiss2259]

could it be that you have two active airport .bgl files for this airport?

[DuduGuimaraes]

Hello, thanks for the answers.

I have checked, there is only one .bgl airport file active. I will play around the runway lengths and report back.

Thanks

Eduardo

[Ray Proudfoot]

Eduardo, where have you placed the new BGL?

[DuduGuimaraes]

44 minutes ago, Ray Proudfoot said:

Eduardo, where have you placed the new BGL?

In the airport’s scenery folder.

[Ray Proudfoot]

1 hour ago, DuduGuimaraes said:

In the airport’s scenery folder.

Ah so you’re modifying a third party airport. Have you disabled the default AFCAD?

Try running MakeRwys.exe and search for SBVT. See how many entries it finds.

[DuduGuimaraes]

19 minutes ago, Ray Proudfoot said:

Ah so you’re modifying a third party airport. Have you disabled the default AFCAD?

Try running MakeRwys.exe and search for SBVT. See how many entries it finds.

Good point ! Will do that. Thanks Ray

[Ray Proudfoot]

19 minutes ago, DuduGuimaraes said:

Good point ! Will do that. Thanks Ray

It should only find the default in a scenery folder with a four digit number plus yours. 

[Grzegorz]

Try this. It works very well for me. 

https://www.avsim.com/forums/topic/589642-new-atc-and-airport-operations-application-testing/

 

 

[G-RFRY]

In ADE open tools and click on file priority, then in the open window check all boxs and click scan, you then see the BGLs for that airport and which is active highest priority. If you have two BGLs active you can disable one in that window.

[Ray Proudfoot]

@G-RFRY, I’ve used ADE for ages but never spotted that, thanks. 👍

[G-RFRY]

https://www.flickr.com/photos/154944674@N05/53751369602/in/dateposted-public

This KDEN scenery file showing my custom BGL at the bottom, and the original BGL switched off edited with .OFF I use uppercase showing it`s my edit. You do not need to touch the base scenery BGL as the sim will load the BGL with highest priority. which is why your addons are placed above the base scenery. And if it`s a small airfield you edited place above your ORBX scenery.

DO not delete the original BGL then you can revert back if your custom BGL is not working to your liking.