10 hours ago, Balint Szarka said:

Hi

Since updating to V5 HF1 I am experiencing CTD's due to the program. It can be easily reproduced if you select a different time upon loading up the sim at any airport then changing time to any time you wish or just placing yourself somewhere else on the planet. 

 

Kind regards,

Balint

With 5.1 HF 1 I can confirm the issue that Balint describes. However, the features themselves work nicely and as intended. 

I've been spotting at the new EDDB for a while now. For some reason the "Enable Roll then takeoff" doesn't work anymore. So aircraft keep waiting until the landing aircraft has fully vacated the runway. 

6 minutes ago, fclaass said:

I've been spotting at the new EDDB for a while now. For some reason the "Enable Roll then takeoff" doesn't work anymore. So aircraft keep waiting until the landing aircraft has fully vacated the runway. 

Can you show me your config file?

Edited November 21, 20205 yr by fs1

<?xml version='1.0' encoding='utf-8' ?>
<Parameters>
    <Airport>
    <ICAO>EDDB</ICAO>
    <ActiveTakeOffRunway>
        <Runway>R25L</Runway>
    </ActiveTakeOffRunway>
    <ActiveTakeOffRunway>
        <Runway>R25R</Runway>
    </ActiveTakeOffRunway>
    <ActiveLandingRunway>
        <Runway>R25L</Runway>
    </ActiveLandingRunway>
    <ActiveLandingRunway>
        <Runway>R25R</Runway>
    </ActiveLandingRunway>
    </Airport>
    <enableFastTakeOffs>1</EnableFastTakeOffs>
    <enableRollthenTakeOff>1</enableRollthenTakeOff>
    <allowTakeOffDistance>9000</AllowTakeOffDistance>
    <taxiSpeedLimiter>30</TaxiSpeedLimiter>
    <nonBlockingUserAircraft>1</nonBlockingUserAircraft>
    <minCrossingRny>2000</minCrossingRny>
    <isGUIVisible>1</isGUIVisible>
    <deployEarlyFlaps>0</deployEarlyFlaps>
</Parameters>

The issue here is that if there is an AI landing and it is less than 6000 meters(see <allowTakeOffDistance>6000</AllowTakeOffDistance>) the min take off is not set to permit the new AI take off, so the AI will wait for the landing AI to land. Can you check this that there are no AIs trying to land on that runway? Thanks 

Edited November 21, 20205 yr by fs1

Yes usually there's already another AI on final, but I think it's further than 6000m away.  I have now set this one to 9000 though. Do you think that should be lower?

Try setting <allowTakeOffDistance>1000</AllowTakeOffDistance>)  to 1000, a smaller value and check if the AI takes off

3 minutes ago, fclaass said:

Yes usually there's already another AI on final, but I think it's further than 6000m away.  I have now set this one to 9000 though. Do you think that should be lower?

Correct. Try a smaller value just for testing purposes. In your XML you have 9000 which is quite high

Edited November 21, 20205 yr by fs1

Ok that worked, thank you. However, 6000 is a little tight in my opinion. I get some go-arounds because aircraft are still taking off when another aircraft is quite close with landing.

Great. I am working on a spacing algorithm so landings will be more separated to each other.

Edited November 21, 20205 yr by fs1

I can confirm 6000 leads to many go arounds. Trying to find a happy medium right now. Will try with 8000-10000 and see if that is better. 

2 minutes ago, DChockey08 said:

I can confirm 6000 leads to many go arounds. Trying to find a happy medium right now. Will try with 8000-10000 and see if that is better. 

This will be resolved once I space out the landing arriving AIs. This will be done in next builds, and will be able to keep lower values 

I have update the links with a new build that fixes CTD. Thanks

15 hours ago, DChockey08 said:

I can confirm 6000 leads to many go arounds. Trying to find a happy medium right now. Will try with 8000-10000 and see if that is better. 

The flight dynamics of the AI aircraft and the runway layout do also influence the traffic flow. Most AI aircraft have a too short and too slow rollout phase, which will let them not reach the suitable runway exits. Back with FS2004 there was a FDE set by Jan Martin that improved the values of all AI. Sadly, P3D had some changes to the Flight dynamics that made the old AI FDE sets unsuitable. The user Urmel has done a significant work to improve it for AIG OCI. But it is a difficult task to find a balanced setting for approach speeds and landing distance that works at various airport configurations. 

Great work!

Tested on RJTT with the xml entrrence below:

	<Airport>
	<ICAO>RJTT</ICAO>
	<ActiveTakeOffRunway>
		<Runway>R05</Runway>
	</ActiveTakeOffRunway>
	<ActiveTakeOffRunway>
		<Runway>R34R</Runway>
	</ActiveTakeOffRunway>
	<ActiveTakeOffRunway>
		<Runway>R16L</Runway>
	</ActiveTakeOffRunway>
	<ActiveTakeOffRunway>
		<Runway>R16R</Runway>
	</ActiveTakeOffRunway>
	<ActiveLandingRunway>
		<Runway>R23</Runway>
	</ActiveLandingRunway>
	<ActiveLandingRunway>
		<Runway>R22</Runway>
	</ActiveLandingRunway>
	<ActiveLandingRunway>
		<Runway>R16L</Runway>
	</ActiveLandingRunway>
		<ActiveLandingRunway>
		<Runway>R16R</Runway>
	</ActiveLandingRunway>
	</Airport>

What I noticed:

AI pick only the listied runway as well, no more 04/05 landing and 22/23 Take off!

I see one instance ATC tells AI to go 35L which is for "crosswind runway" trick, I guess the crosswind runway trick in ADE/AFCAD is nolonger needed?

Despite I set wind 020/16, AI still picks runway all over the airport, and even head-on takeoff with landing on like 34L/16R or 05/23.

I didn't noticed the "probability based on the number of entries", it seems 22 is the most used rwy for landing and followed by 16L/R, with them low on the entries (and north wind). And I only see one T/O on Rwy05 when it's listed on the top (it's far from apron, compare to default, it's good that any flight actually use it)

Edited November 22, 20205 yr by C2615