1 hour ago, vadriver said:

Indeed ..... I notice similar behaviour using these tweaks at some of my airports though I struggle a tad as to which weight is used.

At Haneda for example, I used lighter max gross for domestic widebodies but they still used the longer runway as the heavier internationals rather than 05 as seen on FR24.

I'm doing Haneda now and I am puzzled how to make them use the island runway (at least in 30% of cases) and not the 35R

 

 

 

Is there someone here who can fix my ADE?
I need crosswind configuration, so I can force them to use both long 35 and island runway.

I tried adding x-wind, but it doesn't work.

https://drive.google.com/file/d/1IdmoV33a1dQxHDUBKzcJaKp_rjFrpZpc/view?usp=sharing

 

I am very grateful!

Edited December 13, 20241 yr by vl1

Presuming this is for Technobrain's RJTT, feel free to use my personal xwind files as a base. They're a couple years old and could do with a refresh; they also incorporate Oli from AIG's JALD/ANAD domestic assignments.

I have two files: one for North flow & one for South flow. Separate directional files are necessary for realistic behavior when using the runway length mod. If you build for one direction, and try to use it in the opposite, you will see funny things like landings occurring half way down the runway.

North Flow: Takeoffs on 05 (tier 1/2 aircraft only) with heavies/tier 3 using 34R. Landings on 34L (tier 1/2 only) with heavies/tier 3 using 34R. RWY04/22 is removed completely from this file to prevent rogue landings on 04.

South Flow: Takeoffs on 16R (tier 1/2 aircraft only) with heavies/tier 3 using 16L. Landings on both 22 (all aircraft) and 23 (all aircraft).

https://www.dropbox.com/scl/fi/6zhfw0yrehtqa2iji6wao/Rjtt2_adex_tb_dr.zip?rlkey=wv35xsfl5xgj9yvt77c6m35l3&dl=0

To install, first make backup copies of your current afcad/ade. Then paste both files in the zip above into your RJTT scenery folder, and remove the ".new.[north/south].off" suffix from the file/direction you want to use. Switch directions by reapplying the suffix to the active file and removing the suffix from the inactive file, and so on.

Edited December 14, 20241 yr by drobinho

30 minutes ago, drobinho said:

Presuming this is for Technobrain's RJTT, feel free to use my personal xwind files as a base.

 

Ok, Drobinhito))

I will do the magic, update the stands and we can put it to AIG forum

Edited December 14, 20241 yr by vl1

 

33 minutes ago, drobinho said:

North Flow: Takeoffs on 05 (tier 1/2 aircraft only) with heavies/tier 3 using 34R.

Rwy 34R is closed for takeoff in your file. Says NO
Is this the way it should be?

Another question. I saw this in SEA, why would you disconnect speedy taxiways to the left?

They ARE used in real life...

So I copied the runways from your file to the letter, I deleted the northern runway, they still use only RWY5. Landing and dept. ONLY #5

 

Please take a look

https://drive.google.com/file/d/1IdmoV33a1dQxHDUBKzcJaKp_rjFrpZpc/view?usp=sharing

6 minutes ago, vl1 said:

Rwy 34R is closed for takeoff in your file. Says NO
Is this the way it should be?

Yes, this is intentional and should be left as is. Essentially, it's the only runway that is long enough to accommodate tier 3 aircraft, as all other runways are "not long enough" so the heavies will be directed onto 34R at all times. There are some nuances there, but - for the most part - you can trick tier 3 aircraft onto using a 'closed' runway for takeoff as long as there are no other longer runways around *AND* that the runway in question is *ALSO* set to Y for landings. At least, that's how it works in my sim (v4.5); maybe they patched that out with later releases.

Taxiways to the left of 34L were disabled a) because 99% of tier 1/2 aircraft (the only ones that qualify for using the runway) want parking spots to the right; and b) to force the heavies/tier 3 flights taxiing twd 34R for departures to use TWY L10 as the dedicated runway crossing. If you have runway exits on both sides of a runway, it opens up the possibility that ATC will direct an AI to use unintended runway-exits to cross a runway instead of your intended pathway.

3 minutes ago, vl1 said:

Please take a look

Sorry I'm really pressed for time at the moment (literally on my way out the door to a holiday party that I'm dragging my feet on...!). I might be able to sometime this weekend, but recommend you just take the parking assignments from your original work and copy those into my base files.

7 minutes ago, drobinho said:

Taxiways to the left of 34L were disabled a) because 99% of tier 1/2 aircraft (the only ones that qualify for using the runway) want parking spots to the right; and b) to force the heavies/tier 3 flights taxiing twd 34R for departures to use TWY L10 as the dedicated runway crossing. If you have runway exits on both sides of a runway, it opens up the possibility that ATC will direct an AI to use unintended runway-exits to cross a runway instead of your intended pathway.

That's crazy complicated!

5 minutes ago, drobinho said:

Sorry I'm really pressed for time at the moment

So you DO enjoy the partyyyy )

1 hour ago, drobinho said:

Presuming this is for Technobrain's RJTT, feel free to use my personal xwind files as a base.

Thanks

7 hours ago, drobinho said:

Sorry I'm really pressed for time at the moment (literally on my way out the door to a holiday party that I'm dragging my feet on...!). I might be able to sometime this weekend, but recommend you just take the parking assignments from your original work and copy those into my base files.

Your file still triggers landings to RWY 5

Maybe also needs further Xwind adjustment

On 12/14/2024 at 4:17 AM, drobinho said:

 you just take the parking assignments from your original work and copy those into my base files.

Not gonna work, because remaking stands is much harder then adding 10 runways.

Even more, because of GSX I think, you removed jetways, a lot of them...

On 12/14/2024 at 1:52 AM, vl1 said:

Your file still triggers landings to RWY 5

So that is probably the 'rogue landings' bug/limitation that you're seeing, which is where AI land on runways that are set to NO for Landings. My understanding of this bug is that if the flight path of the approaching AI is within a couple of degrees of any runway at the airport, ATC will direct that AI to use the runway regardless of the YES/NO settings. This would also apply to the opposite-end of the runway (example: say you have rwy27 set for takeoffs-only, you might see flights from both hdgs 270 and 090 get directed onto 27). So this can essentially be attributed to the right combination of both the AI's and the runway's hdg. From my experience, when you see AI landing on a closed runway, it's an indication that all flights from that destination will be directed onto that runway (fwiw I use bgl files and not aigfp). I've seen this bug in numerous places, such as RJTT, PHLI, KBOS, EHAM, EKCH.

 

9 hours ago, vl1 said:

you removed jetways, a lot of them

Oh yeah, ha, whoops. Yes I did, for my own custom SODE file using jetways from other sceneries.

Here's an updated version that includes all the original jetway objects contained in the original TB RJTT ADE file.

https://www.dropbox.com/scl/fi/o274l0av5new2o8j5nib6/Rjtt2_adex_tb_dr_jetways.zip?rlkey=n6pmkiabuxgcjqpdomeg59sqb&dl=0