I have a simple but important question regarding the operations of this program: before turning ON the engines and the beacon lights there is no way to force take-offs and landings according on what I set in the AIForceTaxiOutRunway and landing preferences?

Simple because if I'm at the gate preparing my A320, I need time before turning on the engines.

Thanks
Stefano

Edited August 17, 20241 yr by ilpagaia

21 minutes ago, ilpagaia said:

I have a simple but important question regarding the operations of this program: before turning ON the engines and the beacon lights there is no way to force take-offs and landings according on what I set in the AIForceTaxiOutRunway and landing preferences?

Simple because if I'm at the gate preparing my A320, I need time before turning on the engines.

Thanks
Stefano

Yes of course. AIFlow and AIGround have nothing to do with whether your engines are on. As soon as you set a forced runway, AI will use it.

I'm not sure because the AIGround log messages reports that according with the OFF status of Engines and Beacons of the User Aircraft (my aircraft), the default FS2020 AI Traffic rules is active.

Specific runways setted in the .ini file are not taken into account by AI traffic with Engines and Beacons OFF.

Any idea?

38 minutes ago, ilpagaia said:

I'm not sure because the AIGround log messages reports that according with the OFF status of Engines and Beacons of the User Aircraft (my aircraft), the default FS2020 AI Traffic rules is active.

Specific runways setted in the .ini file are not taken into account by AI traffic with Engines and Beacons OFF.

Any idea?

I think you misunderstood something there in the logs. Anyway just check it: Load a flight with engines off, set a runway for forced Takeoff that should not be active via MSFS and see what the AI does.

I did ... and is exactly what I don't expect.

With my engine OFF the takeoff runway for AI aircrafts is not what I set in my AIGround config. 

1 hour ago, ilpagaia said:

I did ... and is exactly what I don't expect.

With my engine OFF the takeoff runway for AI aircrafts is not what I set in my AIGround config. 

But what do you see? Do they taxi to the runway you specified?

29 minutes ago, Fiorentoni said:

But what do you see? Do they taxi to the runway you specified?

No, the AI traffic (with my engine OFF) use different runways instead of what I setted in .ini file.

6 hours ago, ilpagaia said:

No, the AI traffic (with my engine OFF) use different runways instead of what I setted in .ini file.

Hi!  If using for the first time, make sure to use the new, included config utility (Config_Utility_AIFlowAIGround.exe) rather than editing the .ini files manually.

Check out this video playlist:  Config Utility for AIFlow and AIGround Youtube Video Playlist 

First video is the basics.  Forcing takeoff and landing runways is a more advanced topic that begins with the second video.  

The engine and beacon lights do not affect forced takeoff.  Rather, an engine and beacons off signals to AIGround that the user aircraft is parked and AI can pass closely behind the user aircraft in a cramped parking or gate area.  Starting an engine or turning beacons on signals to AIGround that the user aircraft is ready for pushback or taxi.  AIGround then starts enforcing normal user-AI ground separation (if that option is enabled) for the taxi out/in including preventing AI from passing too closely behind the user's aircraft during pushback.

Edited August 18, 20241 yr by Clipper Ocean Spray

8 hours ago, ilpagaia said:

No, the AI traffic (with my engine OFF) use different runways instead of what I setted in .ini file.

What Clipper said (the creator of the mod), use the config tool. I think you might have left the comment symbols in the .ini (//) and that's why it does not work.

Thank you all for the suggestions ... I'll try to setup AIGround via config utility.

Regards

8 hours ago, Clipper Ocean Spray said:

Hi!  If using for the first time, make sure to use the new, included config utility (Config_Utility_AIFlowAIGround.exe) rather than editing the .ini files manually.

Check out this video playlist:  Config Utility for AIFlow and AIGround Youtube Video Playlist 

First video is the basics.  Forcing takeoff and landing runways is a more advanced topic that begins with the second video.  

The engine and beacon lights do not affect forced takeoff.  Rather, an engine and beacons off signals to AIGround that the user aircraft is parked and AI can pass closely behind the user aircraft in a cramped parking or gate area.  Starting an engine or turning beacons on signals to AIGround that the user aircraft is ready for pushback or taxi.  AIGround then starts enforcing normal user-AI ground separation (if that option is enabled) for the taxi out/in including preventing AI from passing too closely behind the user's aircraft during pushback.

Thanks for creating the videos. I've watched them and I'm still unable to get MSFS ATC to give me the appropriate landing runway. Sometimes it does, and sometimes it assigns the opposite runway. I only use the FSLTS injector and FSLTL fleet and the models work great. I tried all others and settled on FSLTL. I'm waiting for BATC to add AI Traffic control, but for now I was hoping to AI Ground working.

Is there an ATC setting that I need to check or any advice on how to always get the landing and takeoff runways to stick? I've even used the advice given in the flightim.to forum.

Thanks.

Jose

On 8/18/2024 at 7:54 PM, CFIJose said:

Thanks for creating the videos. I've watched them and I'm still unable to get MSFS ATC to give me the appropriate landing runway. Sometimes it does, and sometimes it assigns the opposite runway. I only use the FSLTS injector and FSLTL fleet and the models work great. I tried all others and settled on FSLTL. I'm waiting for BATC to add AI Traffic control, but for now I was hoping to AI Ground working.

Is there an ATC setting that I need to check or any advice on how to always get the landing and takeoff runways to stick? I've even used the advice given in the flightim.to forum.

Thanks.

Jose

Thanks!

Re: MSFS ATC communication with the user aircraft, AIFlow/AIGround does not affect any ATC communications with the user aircraft.  Have you tried MSFS Assistance Options -> ATC enforce flight plan ON (favor user's flight plan or world map flight settings over the current conditions)? 

Re: MSFS ATC communication with AI, there will be no MSFS ATC communication with AI in an AIFlow/AIGround "Forced" mode (AIFlow/AIGround is doing the vectoring, spacing, etc) except in situations where an AI was switched over from MSFS default mode to a Forced mode while an MSFS ATC instruction was pending (in which case you may hear the MSFS ATC repeating instructions to that AI for a bit).  

Apologies for hijacking this with another issue, but using AiGround in grass strips with ForcedTaxiOut mode, I have noticed that AI disappear if they have to cross a runway to get to the assigned runway using ForcedTaxiOut. A lot of good third party scenery have intersecting grass runways so if this could be looked at it would be amazing.

Thanks!

 

On 8/18/2024 at 11:42 AM, Clipper Ocean Spray said:

Hi!  If using for the first time, make sure to use the new, included config utility (Config_Utility_AIFlowAIGround.exe) rather than editing the .ini files manually.

Check out this video playlist:  Config Utility for AIFlow and AIGround Youtube Video Playlist 

First video is the basics.  Forcing takeoff and landing runways is a more advanced topic that begins with the second video.  

The engine and beacon lights do not affect forced takeoff.  Rather, an engine and beacons off signals to AIGround that the user aircraft is parked and AI can pass closely behind the user aircraft in a cramped parking or gate area.  Starting an engine or turning beacons on signals to AIGround that the user aircraft is ready for pushback or taxi.  AIGround then starts enforcing normal user-AI ground separation (if that option is enabled) for the taxi out/in including preventing AI from passing too closely behind the user's aircraft during pushback.

The new ATC setting is MSFS has had little effect on aircraft landing on opposite runways. I thought that AIFlow/Ground solved that by forcing aircraft to land in the specified runway. It's probably another unfixed bug ignored by ASOBO. Thanks.