FSX-MS AI Controller 1.4 (SID, Jet Route, STAR and Final Approach) (New) Beta

[Mr_LoL 10]

Out of interest Roland why does this program take over ground operations? It really doesn't work well at all..

planes simpy aren't arriving in a timely manner. I have one plane circling at 38000 ft.

[Clipper Ocean Spray 189]

It would appear AI Controller is relinquishing AI control to FSX after exiting the STAR, so I'm not getting any managed approaches. 

 

Possible causes:  (1) enhanced mode off (2) preferred landing runway set (is there a  "AIEnhancedLandingRunwayPref=XXX" entry in your AIController.ini), and (3) taxi data incomplete, which AIController will warn you about at startup.  Choose reset path and options to default, apply, force update, and give it another try.

 

 

The application was unable to start correctly (0xc000007b). Click OK to close the application.

 

You don't have the correct 32-bit VC 2013 runtime installed.  Check the instructions in the readme.1st file.

 

 

Out of interest Roland why does this program take over ground operations? It really doesn't work well at all..

planes simpy aren't arriving in a timely manner. I have one plane circling at 38000 ft.

 

It works better than you write, I assure you that.  I have no idea what your problem is and I'm not going to fill in the blanks if you can't write something cogent.

 

 

Also my Norton antivirus kept annoying me because it would delete every .exe file and i would have to restore and exclude them so they wouldnt be deleted again.

 

I've had issues with Avast scanning AIMonitor when it is first loaded, which then causes AIMonitor to crash.  If I restart AIMonitor after Avast completes the scan, everything runs normally.

[Mr_LoL 10]

OMG lol I wasn't having a go at you or your programme Roland.

FSX does a far better job of controlling planes on the ground than this program. For example at LAX planes land on 24R and 25L with fsdreams scenery like it is in real life.. With this they land on all four runways which isn't how it is in real life.

When the planes do land off they go to random gates making your airport messy. They also turn slower than an oil tanker when taxiing. IMHO the program should just control sids and stars that should be it. On final approach, control should be handed over to fsx.

 

Ok so someone who has it working well what are your settings because with default setting planes aren't arriving.

[Clipper Ocean Spray 189]

FSX does a far better job of controlling planes on the ground than this program.

 

Then use it, please.

 

 

 

IMHO the program should just control sids and stars that should be

 

Ummm...that is a prominent option called turning enhanced mode off.  I frankly don't see how you could have missed this even with a brief, cursory inspection of the program (say, for example, the time it took you to write your original message).

 

 

 

With this they land on all four runways which isn't how it is in real life.

 

That's load balancing...you can turn that off too.  You can also manually select what runways you want the AI to land on...up to three parallel or crosswind runways.  I have that particular option bolded and in blue highlighting on the download page.  Do you read anything before using a program?

 

 

When the planes do land off they go to random gates making your airport messy.

 

Random?  Really..you think that?  I just "randomly" assign gates?  The program looks at gate radius first based on aircraft.cfg in the order listed in ADE.  If the AI is smaller than the gate, it looks for a matching airline code in the gate order listed in ADE.  If no code is found, it assigns the first "blank" gate of sufficient size in the order listed in ADE.  This is the standard method many scenery designers use when coding gates in ADE.  The only extra twist I add is I look ahead three gates to try to find the best matching radius gate to try to minimize AI using oversized gates.

 

 

 

They also turn slower than an oil tanker when taxiing.

 

This is incorrect, they will make fast turns but not fast sharp turns.  There are a lot of taxi options you can change to affect taxi-in behavior, but that would require reading and tweaking.  I think your best bet is to go back to stock FSX.

[JSkorna 137]

Let's suggest that  Mr LoL go and LoL somewhere else unless he has a change of something or another, LoL.

[hero93 12]

Do you know a workaround when the aircraft all stay too long to high and start the final approach too late so they land way too far at the middle of the runway. I tried it with custom Approaches (via the Converter) and the files you provide (My Problem is at SFO).

[Chris Zoepound 0]

Quick question Roland. So when this program is running, does default ATC still give out orders?.. for example "turn right heading etc etc etc" "airport is -- miles, turn etc etc report runway in sight"? Or is ATC just silent?

[Chris Zoepound 0]

Thank you for your help so far Roland. AI controller now uses the pmdg sids and stars at my customized airports.

But..I was watching an ai aircraft perform its approach to one of the airports and the command keeps saying this just before final:

"Jamaica Express Flight 361 (6Y-JED) UNABLE to assign final approach (Enhanced Mode).

 This typically occurs when the sim session has just been started at the monitored airport.

 As time passes, final approaches can be more readily assigned due to accumulating wind and landing data."

 

My aircraft just begins to circle the area as if in a holding pattern...Always unable to assign the final approach.

 

Thing is i started ai controller well into my sim session.. Also I turned off Enhanced mode after seeing this issue and in final approach options set FSX to take over final approaches and its the same..it flies towards the airport waiting for fsx to give final approach vectors, and at a point it circles again.

 

I know this doesnt happen with your samples so i wonder if something is wrong with my custom files. i took them from the PMDG airac as specified and used ai converter.

Could anybody give me a clue to fix this please?

[liketofly1 11]

Hi Roland,

 

After using your nice little program for quite a while, all of a sudden I get following error:

 

Problemsignatur:

  Problemereignisname: APPCRASH

  Anwendungsname: aicontroller.exe

  Anwendungsversion: 1.4.1.2

  Anwendungszeitstempel: 5513a409

  Fehlermodulname: MSVCR120.dll

  Fehlermodulversion: 12.0.21005.1

  Fehlermodulzeitstempel: 524f7ce6

  Ausnahmecode: 40000015

  Ausnahmeoffset: 000a7676

  Betriebsystemversion: 6.1.7601.2.1.0.256.48

  Gebietsschema-ID: 1033

  Zusatzinformation 1: 1620

  Zusatzinformation 2: 1620dbaf8dc4c576293bbf0c81152d09

  Zusatzinformation 3: 4533

  Zusatzinformation 4: 45331b594f7b00a66a205e2139134b58

 

If already tried to repair the Microsoft Visual C++ 2013 librarys as well as a complete uninstall/reinstall of the librarys as well as your program, however nothing seems to help to get rid of this error...

 

any ideas what could cause that?

 

As I said - it was running nicely without problems and suddenly (inbetween two sim sessions) i get this error everytime AIController starts.....

 

kind regards

Richi

[FlyTweety 2]

Basically this Error was related to the setting in our Windows Language Setting.

 

We had to change the comma into a Period ( Systemsteuerung -> Region und Sprache -> Weitere Einstellungen -> Zahlen -> Dezimaltrennzeichen)

By default we use the Komma (,) but international it is common, to use the Period (.)
Though Rolands code should be able to use both, nevertheless he recommend in his readme.txt to change the setting.

Maybe, for some reason (windowsupdate, new programs) for you, your current setting is not working anymore.

[liketofly1 11]

Hi, FlyTweety,

 

thanks for replay, Windows language settings are set to period... and as I sayed -  between two flight sim sessions - maybe 30 min appart.... 

 

It worked like a treat - half an hour later - I want to start the program again - bumm I get this error - didn't change anything - no install - no update - nothing... thats what blew my mind... and since then, everytime I start the program I get this error, repairing Visual C++ 2013 librarys did not help - uninstallin/reinstalling of the Visual C++ 2013 with a reboot inbetween did not help and completely reinstalling AI Monitor there after did not help either... I'm at a loss at the moment...

 

I seems to me more like something got corrupted, I just dont know what.... since reinstallation of neither the C++ librarys nor the reinstallation of AiController solved the issue..

 

 

kind regards

Richi

[FlyTweety 2]

Sooooo, again me :smile:

 

One more weekend to check, a few new investigations:

 

The asignement of the Gates are still not working. AIController do not respect the Parking diameter, nor the Parking Code.

So i did a look in the AI_cfg_data.txt.

 

Unfortunatly it looked very messy, so i converted the file into a spreadsheed.

 

There it was more clear that for some reason the [AIRPLANE_GEOMETRY]  section is not readout correct. I tried to find out why but until yet i cannot find any difference between the sections

 

 

[General]
atc_type=AIRBUS
atc_model=A319
editable=1
performance=
Category=airplane

// FDE Template TwinEngineCommercialJet
// FDE Design   Jan Martin
// FDE Version  v6acof

[Contact_Points]
point.0=1,  32.50,   0.00, -12.65, 1181.1, 0, 1.442, 55.92, 1.0, 2.5, 0.9, 4.0, 4.0, 0, 0.0, 0.0
point.1=1,  -7.00, -15.00, -12.85, 1574.8, 1, 1.442,  0.00, 1.0, 1.7, 0.9, 7.0, 7.0, 2, 0.0, 0.0
point.2=1,  -7.00,  15.00, -12.85, 1574.8, 2, 1.442,  0.00, 1.0, 1.7, 0.9, 7.0, 7.0, 3, 0.0, 0.0
point.3=2, -14.17, -47.33,   0.00,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 5, 0.0, 0.0
point.4=2, -14.17,  47.33,   0.00,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 6, 0.0, 0.0
point.5=2, -54.00,   0.00,   2.83,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 9, 0.0, 0.0
point.6=2,  42.67,   0.00,  -3.75,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0
static_pitch     = -0.4026
static_cg_height = 11.8220
gear_system_type = 1

[Lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -13.50, -55.15,  2.85, fx_navredh ,
light.1=3, -13.50,  55.15,  2.85, fx_navgreh ,
light.2=2, -14.00, -55.50,  2.90, fx_strobeh ,
light.3=2, -14.00,  55.50,  2.90, fx_strobeh ,
light.4=2, -61.75,   0.00,  4.50, fx_strobeh ,
light.5=3, -61.75,   0.00,  4.50, fx_navwhih ,
light.6=1,   3.70,   0.00,  8.50, fx_beaconh ,
light.7=1,   6.00,   0.00, -6.00, fx_beaconb ,

[Reference Speeds]
flaps_up_stall_speed    = 95.0
full_flaps_stall_speed  = 113.0
cruise_speed            = 520.0
max_mach                = 0.92
max_indicated_speed     = 305.0

[Weight_And_Balance]
max_gross_weight = 166500
empty_weight     =  89000

reference_datum_position =  0.0, 0, 0
empty_weight_CG_position =  4.0, 0, 0

max_number_of_stations = 50

;Moments of Inertia
empty_weight_pitch_MOI   = 1750000
empty_weight_roll_MOI    = 2262183
empty_weight_yaw_MOI     = 3337024
empty_weight_coupled_MOI = 0

[Flight_Tuning]
cruise_lift_scalar          = 2.1
parasite_drag_scalar        = 1.8
induced_drag_scalar         = 0.1
elevator_effectiveness      = 1.0
aileron_effectiveness       = 1.0
rudder_effectiveness        = 1.0
pitch_stability             = 1.0
roll_stability              = 1.0
yaw_stability               = 1.0
elevator_trim_effectiveness = 1.0
aileron_trim_effectiveness  = 1.0
rudder_trim_effectiveness   = 1.0

[GeneralEngineData]
engine_type = 1
Engine.0 = 4.75, -18.0, -2.5
Engine.1 = 4.75,  18.0, -2.5
fuel_flow_scalar   =  1.00
min_throttle_limit = -0.01

[TurbineEngineData]
fuel_flow_gain          = 0.002
inlet_area              = 19.6
rated_N2_rpm            = 29920
static_thrust           = 27500
afterburner_available   = 0
reverser_available      = 1

[Jet_Engine]
thrust_scalar           = 0.5

[brakes]
parking_brake    = 1
toe_brakes_scale = 0.001
auto_brakes=4

[Flaps.0]
type             = 1
span-outboard    = 0.8
extending-time   = 8
lift_scalar      = 1.0
drag_scalar      = 1.0
pitch_scalar     = 1.0
flaps-position.0 = 0
flaps-position.1 = 8
flaps-position.2 = 8
flaps-position.3 = 11
flaps-position.4 = 14
flaps-position.5 = 14
damaging-speed   = 250
blowout-speed    = 300
system_type      = 1

[Flaps.1]
type             = 2
span-outboard    = 0.8
extending-time   = 2
lift_scalar      = 1.0
drag_scalar      = 1.0
pitch_scalar     = 1.0
flaps-position.0 = 0
flaps-position.1 = 3
flaps-position.2 = 3
flaps-position.3 = 23
flaps-position.4 = 23
flaps-position.5 = 23
damaging-speed   = 250
blowout-speed    = 300
system_type      = 1

[Airplane_Geometry]
wing_area               = 900.0
wing_span               = 111.83
wing_root_chord         = 18.0
wing_dihedral           = 6.2
wing_incidence          = 1.0
wing_twist              = -0.5
oswald_efficiency_factor= 0.75
wing_winglets_flag      = 0
wing_sweep              = 25.0
wing_pos_apex_lon       = 8.0
wing_pos_apex_vert      = 0.0
htail_area              = 338.0
htail_span              = 41.7
htail_pos_lon           = -35.0
htail_pos_vert          = 0.0
htail_incidence         = 0.0
htail_sweep             = 30.0
vtail_area              = 224.0
vtail_span              = 20.0
vtail_sweep             = 35.0
vtail_pos_lon           = -35.8
vtail_pos_vert          = 5.8
elevator_area           = 70.5
aileron_area            = 26.9
rudder_area             = 56.2
elevator_up_limit       = 30.0
elevator_down_limit     = 19.5
aileron_up_limit        = 20.0
aileron_down_limit      = 20.0
rudder_limit            = 26.0
elevator_trim_limit     = 20.0
spoiler_limit           = 207.5
spoilerons_available    = 1
aileron_to_spoileron_gain = 3
min_ailerons_for_spoilerons = 10
min_flaps_for_spoilerons = 0
auto_spoiler_available=1
spoiler_extension_time=2.000000
positive_g_limit_flaps_up=4.000000
positive_g_limit_flaps_down=3.000000
negative_g_limit_flaps_up=-3.000000
negative_g_limit_flaps_down=-2.000000
 

 

is fine, all settings set.

 

 

[General]
atc_type=BOEING
atc_model=B737
editable=1
performance=
Category=airplane

// FDE Template TwinEngineCommercialJet
// FDE Design   Jan Martin
// FDE Version  v6acof

[Contact_Points]
point.0=1,  30.00,   0.00, -8.00, 1181.1, 0, 1.442, 55.92, 1.0, 1.4, 0.9, 4.0, 4.0, 0, 0.0, 0.0
point.1=1,  -6.25, -15.00, -8.20, 1574.8, 1, 1.442,  0.00, 1.0, 1.4, 0.9, 7.0, 7.0, 2, 0.0, 0.0
point.2=1,  -6.25,  15.00, -8.20, 1574.8, 2, 1.442,  0.00, 1.0, 1.4, 0.9, 7.0, 7.0, 3, 0.0, 0.0
point.3=2, -14.17, -47.33,  0.00,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 5, 0.0, 0.0
point.4=2, -14.17,  47.33,  0.00,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 6, 0.0, 0.0
point.5=2, -54.00,   0.00,  2.83,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 9, 0.0, 0.0
point.6=2,  42.67,   0.00, -3.75,  787.4, 0, 0.000,  0.00, 0.0, 0.0, 0.0, 0.0, 0.0, 4, 0.0, 0.0
static_pitch     = -0.38901
static_cg_height =  7.17056
gear_system_type = 1

[Lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0=3, -18.30, -55.10,  5.20, fx_navredh ,
light.1=3, -18.30,  55.10,  5.20, fx_navgreh ,
light.2=2, -19.75, -55.75,  5.25, fx_strobeh ,
light.3=2, -19.75,  55.75,  5.25, fx_strobeh ,
light.4=3, -24.00, -56.35,  5.00, fx_navwhih ,
light.5=3, -24.00,  56.35,  5.00, fx_navwhih ,
light.6=2, -59.45,   0.00,  7.90, fx_strobeh ,
light.7=1,   4.75,   0.00, 10.30, fx_beaconh ,
light.8=1,  -2.75,   0.00, -3.70, fx_beaconb ,

[Reference Speeds]
flaps_up_stall_speed    = 112.5
full_flaps_stall_speed  = 113.0
cruise_speed            = 500.0
max_mach                = 0.875
max_indicated_speed     = 300.0

[Weight_And_Balance]
max_gross_weight = 154500
empty_weight     =  83000

reference_datum_position =  0.0, 0, 0
empty_weight_CG_position =  4.0, 0, 0

max_number_of_stations = 50

;Moments of Inertia
empty_weight_pitch_MOI   = 1750000
empty_weight_roll_MOI    = 2262183
empty_weight_yaw_MOI     = 3337024
empty_weight_coupled_MOI = 0

[Flight_Tuning]
cruise_lift_scalar          = 2.1
parasite_drag_scalar        = 1.8
induced_drag_scalar         = 0.1
elevator_effectiveness      = 1.0
aileron_effectiveness       = 1.0
rudder_effectiveness        = 1.0
pitch_stability             = 1.0
roll_stability              = 1.0
yaw_stability               = 1.0
elevator_trim_effectiveness = 1.0
aileron_trim_effectiveness  = 1.0
rudder_trim_effectiveness   = 1.0

[GeneralEngineData]
engine_type = 1
Engine.0 = 4.75, -16.1, -2.5
Engine.1 = 4.75,  16.1, -2.5
fuel_flow_scalar   =  1.00
min_throttle_limit = -0.01

[TurbineEngineData]
fuel_flow_gain          = 0.002
inlet_area              = 19.6
rated_N2_rpm            = 29920
static_thrust           = 27500
afterburner_available   = 0
reverser_available      = 1

[Jet_Engine]
thrust_scalar           = 0.5

[brakes]
parking_brake    = 1
toe_brakes_scale = 0.001
auto_brakes=4

[Flaps.0]
type             = 1
span-outboard    = 0.8
extending-time   = 8
lift_scalar      = 1.0
drag_scalar      = 1.0
pitch_scalar     = 1.0
flaps-position.0 = 0
flaps-position.1 = 5
flaps-position.2 = 5
flaps-position.3 = 6
flaps-position.4 = 8
flaps-position.5 = 8
damaging-speed   = 250
blowout-speed    = 300
system_type      = 1

[Flaps.1]
type             = 2
span-outboard    = 0.8
extending-time   = 2
lift_scalar      = 1.0
drag_scalar      = 1.0
pitch_scalar     = 1.0
flaps-position.0 = 0
flaps-position.1 = 3
flaps-position.2 = 3
flaps-position.3 = 26
flaps-position.4 = 26
flaps-position.5 = 26
damaging-speed   = 250
blowout-speed    = 300
system_type      = 1

[Airplane_Geometry]
wing_area               = 900.0
wing_span               = 112.58
wing_root_chord         = 18.0
wing_dihedral           = 6.2
wing_incidence          = 1.0
wing_twist              = -0.5
oswald_efficiency_factor= 0.75
wing_winglets_flag      = 0
wing_sweep              = 25.0
wing_pos_apex_lon       = 8.0
wing_pos_apex_vert      = 0.0
htail_area              = 338.0
htail_span              = 41.7
htail_pos_lon           = -35.0
htail_pos_vert          = 0.0
htail_incidence         = 0.0
htail_sweep             = 30.0
vtail_area              = 224.0
vtail_span              = 20.0
vtail_sweep             = 35.0
vtail_pos_lon           = -35.8
vtail_pos_vert          = 5.8
elevator_area           = 70.5
aileron_area            = 26.9
rudder_area             = 56.2
elevator_up_limit       = 27.0
elevator_down_limit     = 19.5
aileron_up_limit        = 20.0
aileron_down_limit      = 20.0
rudder_limit            = 26.0
elevator_trim_limit     = 20.0
spoiler_limit           = 120.0
spoilerons_available    = 1
aileron_to_spoileron_gain = 3
min_ailerons_for_spoilerons = 10
min_flaps_for_spoilerons = 0
auto_spoiler_available=1
spoiler_extension_time=2.000000
positive_g_limit_flaps_up=4.000000
positive_g_limit_flaps_down=3.000000
negative_g_limit_flaps_up=-3.000000
negative_g_limit_flaps_down=-2.000000
 

 

is collected without wingspan, empty whight and so on

 

Can you explain shortly which data you collect?

 

I recon: "title=" -> "atc_airline=" -> "atc_id=" -> "ui_type="  -> "atc_parking_types=" -> "wing_span" -> "empty_weight" -> "toe_brakes_scale" and "atc_parking_codes="

Is that right so far?

 

It is strange, i have no idea why the dataset is sometimes complete, sometimes not...

 

A small summary from my AI_cfg_data.txt

 

FAIB Airbus A319 Roll-Out Colors CFM|AIRBUS|F-WWAS|A319|GATE|111.83|89000|0.001|
FAIB_A319_CFM_Malta|AIR MALTA|9H-AEL|A319|GATE|111.83|89000|0.001|AMC
FAIB Airbus A319-100 Air Berlin OLT Hybrid|AIR BERLIN|D-ABGS|A319|GATE|111.83|89000|0.001|BER
FAIB Airbus A319-100 Germania|GERMANIA|D-ASTC|A319|GATE|111.83|89000|0.001|GMI
FAIB Airbus A319-100 Germania ex-Germania Express|GERMANIA|D-AHIM|A319|GATE|111.83|89000|0.001|GMI
FAIB Airbus A319-100 Germania AJW Aviaton|GERMANIA|D-ASTZ|A319|GATE|111.83|89000|0.001|GMI
FAIB Airbus A319-100 Germania WheelTug|GERMANIA|D-ASTY|A319|GATE|111.83|89000|0.001|GMI
|||||30|80000|1|
|||||30|80000|1|
|||||30|80000|1|
|||||30|80000|1|
WoA_FAIB_FSX_A319_IAE_TCW-Thomas Cook Airline|THOMAS COOK||A319|GATE|112.0|80000|0.6|TCW
|||||30|80000|1|
|||||30|80000|1|
|||||30|80000|1|
|||||112.0|80000|0.6|
|||||30|80000|1|
|||||30|80000|1|
|||||30|80000|1|
|||||112.0|80000|0.6|
|||||30|80000|1|
|||||30|80000|1|
FAIB Airbus A320 Roll-Out Colors CFM|AIRBUS|F-WWBA|A320|GATE|30|80000|1|
FAIB Airbus A320-200 Air Berlin|AIR BERLIN|D-ABDY|A320|GATE|30|80000|1|BER
FAIB Airbus A320-200 Air Berlin 2007 Belly|AIR BERLIN|D-ABDU|A320|GATE|30|80000|1|BER
FAIB Airbus A320-200 Air Berlin Etihad Hybrid|AIR BERLIN|D-ABDU|A320|GATE|30|80000|1|BER
FAIB_A320_CFM_Malta|AIR MALTA|9H-AEN|A320|GATE|30|80000|1|AMC
WoA_FAIB_FSX_A320_CFM_TCW-Thomas Cook Airline TCH|THOMAS COOK||A320|GATE|30|80000|1|TCW
WoA_FAIB_FSX_A320_CFM_TCW-Thomas Cook Airline TCI|THOMAS COOK||A320|GATE|30|80000|1|TCW
WoA_FAIB_FSX_A320_CFM_TCW-Thomas Cook Airline TCJ|THOMAS COOK||A320|GATE|30|80000|1|TCW
FAIB Airbus A320-200 CFM Iberia NC|IBERIA||A320|GATE|30|80000|1|IBE
|||||30|80000|1|
|||||30|80000|1|
|||||30|80000|1|
WoA_FAIB_FSX_A320_IAE_TCW-Thomas Cook Airline|THOMAS COOK||A320|GATE|112.0|80000|0.6|TCW

 

 

I hope you can fix it, editing the AI_cfg_data.txt by hand would be possible, but hard..

[liketofly1 11]

Hmm....

 

I also found something strange regarding my MSVCR120.dll crash... 

 

setting the Departure and Approach paths to Canada was causing the crash... tried with Austria and South Africa - no problem..... And I just have the program running monitoring all of the US, without that error, so there must be somethin wrong with my Canada SID/STAR's... thats causing that error...

 

will have to check again tomorro, maybe run the sidstar program again to reproduce canadas SidStar files...

 

kind regards

Richi

[Clipper Ocean Spray 189]

Do you know a workaround when the aircraft all stay too long to high and start the final approach too late so they land way too far at the middle of the runway. I tried it with custom Approaches (via the Converter) and the files you provide (My Problem is at SFO).

 

Do you happen to know what approach or final was selected in AIMonitor when you saw this behavior?  I haven't noticed this behavior myself, but I have received other reports similar to yours, so I'm sure there is an issue somewhere.  Looking into it.... 

 

 

My aircraft just begins to circle the area as if in a holding pattern...Always unable to assign the final approach.

 

Thing is i started ai controller well into my sim session.. Also I turned off Enhanced mode after seeing this issue and in final approach options set FSX to take over final approaches and its the same..it flies towards the airport waiting for fsx to give final approach vectors, and at a point it circles again.

 

In enhanced mode, if the program can't assign a final, it releases the AI back to FSX, so it makes sense you're seeing the same behavior with enhanced mode on and off.  Does the approach runway match the airport runway (sometimes the FSX data is out-of-date regarding runways).  What airport was this at?

 

 

It would appear AI Controller is relinquishing AI control to FSX after exiting the STAR, so I'm not getting any managed approaches. 

 

Rob, are you still having this issue?  Is AIController giving a reason (similar to Chris above), like "UNABLE to assign final approach (Enhanced Mode).

 This typically occurs when the sim session has just been started at the monitored airport...."?

 

 

It is strange, i have no idea why the dataset is sometimes complete, sometimes not...

 

Great data, much appreciated.  You're right...the snipped portions look the same.  The explanation probably has something to do with another part of the file(s)...could you send those two aircraft.cfg files to my support email address in the readme?  I'm sure I'll find the problem then.

 

The output data format is is:  title, atc_airline, atc_id, ui_type, atc_parking_type, wing_span, empty_weight, brake_scalar, and atc_parking_code list.

 

 

setting the Departure and Approach paths to Canada was causing the crash... tried with Austria and South Africa - no problem..... And I just have the program running monitoring all of the US, without that error, so there must be somethin wrong with my Canada SID/STAR's... thats causing that error...

 

Interesting, thanks for digging into the problem and finding this specific triggering event.  Are these the stock Canada samples provided with the program?  If stock, it could have something to do with a corrupted AIController.ini or AIControllerPath.txt file due to path selection/de-selection over time.   If that happens to be it, please email me the corrupted file(s).

 

BTW, do you (or anyone else) still need to set the Windows language settings to period to get the program to work?  I revised the code and tested it myself by setting the deliminator to comma and entering comma deliminated values.  However, I haven't heard from anyone in an affected locale confirming the fix worked.  Just curious.

[liketofly1 11]

Hi Roland,

 

Do you happen to know what approach or final was selected in AIMonitor when you saw this behavior?  I haven't noticed this behavior myself, but I have received other reports similar to yours, so I'm sure there is an issue somewhere.  Looking into it.... 

 

 

 

In enhanced mode, if the program can't assign a final, it releases the AI back to FSX, so it makes sense you're seeing the same behavior with enhanced mode on and off.  Does the approach runway match the airport runway (sometimes the FSX data is out-of-date regarding runways).  What airport was this at?

 

 

 

Rob, are you still having this issue?  Is AIController giving a reason (similar to Chris above), like "UNABLE to assign final approach (Enhanced Mode).

 This typically occurs when the sim session has just been started at the monitored airport...."?

 

 

 

Great data, much appreciated.  You're right...the snipped portions look the same.  The explanation probably has something to do with another part of the file(s)...could you send those two aircraft.cfg files to my support email address in the readme?  I'm sure I'll find the problem then.

 

The output data format is is:  title, atc_airline, atc_id, ui_type, atc_parking_type, wing_span, empty_weight, brake_scalar, and atc_parking_code list.

 

 

 

Interesting, thanks for digging into the problem and finding this specific triggering event.  Are these the stock Canada samples provided with the program?  If stock, it could have something to do with a corrupted AIController.ini or AIControllerPath.txt file due to path selection/de-selection over time.   If that happens to be it, please email me the corrupted file(s).

 

BTW, do you (or anyone else) still need to set the Windows language settings to period to get the program to work?  I revised the code and tested it myself by setting the deliminator to comma and entering comma deliminated values.  However, I haven't heard from anyone in an affected locale confirming the fix worked.  Just curious.

 

No, its not the stock you provided, Its the Navigraph data set 1503 converted with the SIDSTAR program - and I don't think its the locale settings although I have mine set to period - but I'll check on that in the evening.......

 

kind regards

Richi