NatK50,

 

The Target Count is not a factor when it comes to Ai taxiing onto the active runway when you're on approach. That's an inherent weakness in FSX.

 

I use Radar Contact which freezes Ai (also ensuring they're not stopped on a runway) when your aircraft is on approach. Other similar programs may do the same.

 

For the record my Target Count was over 150 when I was approaching EDDM. I landed without needing a go-around and Ai were waiting at the holding point.

Hi,

 

I'm FSX Acc on Win7

 

Your latest link posted above doesnt want to work on my system. After the download, I extract the AirTraffic Manager.exe, plus four other files inc two FSUIPC Client. I try to run the AirTrafficManager.exebut this fails when I try to open it it? I get an error dialogue box saying that "A problem caused the program to stop working correctly. Please close the program".I have ended up with an AirTrafficManager Application located in the Documents Library, but if I try to run it from there, nothing happens. looks like I'm in a muddle somewhere....

 

Could you please advise and let me know what you think the problem is at my end?

 

Many thanks in anticipation.

 

Best wishes

 

Andrew

Supplementary to the above,

 

I went into my task manager this evening and discovered by chance that un be known to me, multiple instances of Traffic Optimizer were running in the background somewhere?

 

What's happening!

 

Andrew

Supplementary to the above,

 

I went into my task manager this evening and discovered by chance that un be known to me, multiple instances of Traffic Optimizer were running in the background somewhere?

 

What's happening!

 

Andrew

Andrew, you should run only once. When the program starts, it will minimize itself. Do you not see it in the task bar? What version of FSX do you have?

duke,

 

I'm experiencing a problem with your program and its unintended interaction with a program called Electronic Flight Bag.

 

The data provider of EFB is crashing because of a .NET error and it looks like TO might be the problem because the two programs share the same flight plan.

 

Here's the error. I wonder if the simplest resolution might be for TO to read the plan once and then discard it leaving EFB free to access it.

 

duke,

 

I'm experiencing a problem with your program and its unintended interaction with a program called Electronic Flight Bag.

 

The data provider of EFB is crashing because of a .NET error and it looks like TO might be the problem because the two programs share the same flight plan.

 

Here's the error. I wonder if the simplest resolution might be for TO to read the plan once and then discard it leaving EFB free to access it.

 

 

The crash box is from EFB and not TO, right? Can you click on details button and see what it shows?

 

Its strange because I read the plan only once and that too in read only mode. After that the flight plan is not touched unless it changes.

 

To be exact, I read the flight plan path/name from FSUIPC, if that path is different from the last time I read it, only then do I actually read the flight plan file. So most of the time I am just comparing paths without actually doing anything with the actual file.

 

 

The crash box is from EFB and not TO, right? Can you click on details button and see what it shows?

Yes. It causes EFB's Data Provider to fail. I'll post the full info after my next flight - probably tomorrow.

 

Its strange because I read the plan only once and that too in read only mode. After that the flight plan is not touched unless it changes.

To be exact, I read the flight plan path/name from FSUIPC, if that path is different from the last time I read it, only then do I actually read the flight plan file. So most of the time I am just comparing paths without actually doing anything with the actual file.

 

Yes, I can see the read only occurs once but the message is saying it cannot access the plan. Actually I'm wondering why it has that name rather than the name of the FSX plan - LEMHEGCCX.PLN. I'll ask on the EFB forum about that.

I use both EFB and TO in FSX and P3D and have not experienced a crash. My last flight from EGKK to EGPF in P3D was a complete success. I should also add that I also use ProATC and Opus, which also reads the flight plan from EFB. I have no problems at all.

dukeav,

 

Had a different error this morning. I'm loading TO from FSUIPC.INI using the READY parameter so it doesn't load until FSX is fully loaded. Here is the error and details...

 

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
   at System.Windows.Forms.Control.WaitForWaitHandle(WaitHandle waitHandle)
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at System.Windows.Forms.Control.Invoke(Delegate method)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.HideSplashScreen()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.MainFormLoadingDone(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at DevExpress.XtraEditors.XtraForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at DevExpress.XtraEditors.XtraForm.WndProc(Message& msg)
   at DevExpress.XtraBars.Ribbon.RibbonForm.WndProc(Message& msg)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
FSX Fiber Accelerator
    Assembly Version: 1.3.1.0
    Win32 Version: 1.3.1.0

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
FSX Fiber Accelerator7284614
    Assembly Version: 0.0.0.0
    Win32 Version: 1.3.1.0

----------------------------------------
FSUIPCClient
    Assembly Version: 2.3.4653.1
    Win32 Version: 2.3.4653.1

----------------------------------------
DevExpress.XtraBars.v12.2
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
DevExpress.XtraEditors.v12.2
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

----------------------------------------
DevExpress.Utils.v12.2
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
DevExpress.Data.v12.2
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 10.0.61259.0
    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

----------------------------------------
DevExpress.XtraGauges.v12.2.Core
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
DevExpress.XtraGauges.v12.2.Win
    Assembly Version: 12.2.13.0
    Win32 Version: 12.2.13.0

----------------------------------------
FSX Fiber Accelerator7284614
    Assembly Version: 0.0.0.0
    Win32 Version: 1.3.1.0

----------------------------------------
FSX Fiber Accelerator7284614
    Assembly Version: 0.0.0.0
    Win32 Version: 1.3.1.0

----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.6195
    Win32 Version: 8.00.50727.6195

----------------------------------------
ChilkatDotNet2
    Assembly Version: 9.4.0.0
    Win32 Version: 9, 4, 0, 0

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

---------------------------------------------------------------------------------------------------------------

 

I also load Fiber Accelerator - another program dependent on .NET4. That is fine.

 

I exited FSX and amended fsuipc4.ini so it didn't load Traffic Manager. No error.

 

Then I launched Traffic Manager manually. After 3 minutes it still was okay.

 

I then launched EFB Display on a WideFS computer. Only the EFB Data Provider runs on the FSX PC. It loaded EFB_current_garmin.PLN and continued to monitor and delete Ai.

 

So it's beginning to look like it might be a timing issue. Loading Traffic Manager well after FSX has started and EFB's Data Provider seem to bring stability. Only time will tell but for now I'll manually load it and keep my fingers crossed.

dukeav,

 

Had a different error this morning. I'm loading TO from FSUIPC.INI using the READY parameter so it doesn't load until FSX is fully loaded. Here is the error and details...

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

   at System.Windows.Forms.Control.WaitForWaitHandle(WaitHandle waitHandle)

   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)

   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)

   at System.Windows.Forms.Control.Invoke(Delegate method)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.HideSplashScreen()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.MainFormLoadingDone(Object sender, EventArgs e)

   at System.EventHandler.Invoke(Object sender, EventArgs e)

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at DevExpress.XtraEditors.XtraForm.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.OnCreateControl()

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ContainerControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WmShowWindow(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at DevExpress.XtraEditors.XtraForm.WndProc(Message& msg)

   at DevExpress.XtraBars.Ribbon.RibbonForm.WndProc(Message& msg)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)

 

----------------------------------------

FSX Fiber Accelerator

    Assembly Version: 1.3.1.0

    Win32 Version: 1.3.1.0

 

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)

 

 

So it's beginning to look like it might be a timing issue. Loading Traffic Manager well after FSX has started and EFB's Data Provider seem to bring stability. Only time will tell but for now I'll manually load it and keep my fingers crossed.

 

 Ray, that's a crash box from FSX Fiber Accelerator.

 

 

Ray, that's a crash box from FSX Fiber Accelerator.

 

But FA didn't crash. :unsure: I'll carry on monitoring. Just completed LSZH-EDDF without any problems.

 

Can I just remind you about the FS9 plan fix please.

New version:

 

http://www.mediafire...agerFSX-SP2.zip

 

Changes

 

1. Reads FS9 style plans

2. Optional Minimize on start up

Duke,

 

I really appreciate your work creating this very handy utility.  I've bumped up my AI levels to 50% and it's great having all the extra eye candy while still maintaining solid FPS and smoothness in the sim.

 

Thanks a bunch!

Thanks duke. A couple more flights yesterday were fine. It seems to be down to timing. If I load TO after everything else then it's okay.

@dukeav:
Do you think, in the near future we can open your tool via exe.xml?