October 31, 201411 yr Have Simconnect installed and have also installed the SP1 version as mentioned earlier in the thread I've been getting this message after installing the latest version: See the end of this message for details on invokingjust-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.OverflowException: Arithmetic operation resulted in an overflow. at AirTrafficManager.Main.p3d_simconnect_OnRecvSimobjectDataBytype(SimConnect sender, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE data) at Microsoft.FlightSimulator.SimConnect.SimConnect.raise_OnRecvSimobjectDataBytype(SimConnect value0, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE value1) at Microsoft.FlightSimulator.SimConnect.SimConnect.OnReceiveMessage(SIMCONNECT_RECV pData, UInt32 cbData) at Microsoft.FlightSimulator.SimConnect.CSignalProcDelegateMarshaler.CallSignalProc(SIMCONNECT_RECV* pData, UInt32 cbData, Void* pContext) at SimConnect_CallDispatch(Void* , IntPtr , Void* ) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() at AirTrafficManager.Main.DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) 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: 4.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR----------------------------------------AirTrafficManager Assembly Version: 1.8.0.1 Win32 Version: 1.8.0.1----------------------------------------Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL----------------------------------------System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR----------------------------------------System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL----------------------------------------System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL----------------------------------------System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL----------------------------------------System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34108 built by: FX45W81RTMGDR----------------------------------------System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL----------------------------------------System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR----------------------------------------Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61242.0 Win32 Version: 10.0.61355.0 (fsx-sp1.20070510-2038)----------------------------------------msvcm80 Assembly Version: 8.0.50727.6195 Win32 Version: 8.00.50727.6195----------------------------------------Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL----------------------------------------FSUIPCClient Assembly Version: 2.4.4910.2 Win32 Version: 2.4.4910.2----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration> <system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box. Chillblast Core i5 14600KF Liquid Cooled RTX 4070 SUPER 32GB RAM. Internet: 1 Gig Fibre. HoneyComb Throttle & Flight System. UK PPL since 2006 current on PA-28, C-152, C172, Decathlon, C-42 based at EGHP.
October 31, 201411 yr Author Have Simconnect installed and have also installed the SP1 version as mentioned earlier in the thread I've been getting this message after installing the latest version: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.OverflowException: Arithmetic operation resulted in an overflow. at AirTrafficManager.Main.p3d_simconnect_OnRecvSimobjectDataBytype(SimConnect sender, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE data) at Microsoft.FlightSimulator.SimConnect.SimConnect.raise_OnRecvSimobjectDataBytype(SimConnect value0, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE value1) at Microsoft.FlightSimulator.SimConnect.SimConnect.OnReceiveMessage(SIMCONNECT_RECV pData, UInt32 cbData) at Microsoft.FlightSimulator.SimConnect.CSignalProcDelegateMarshaler.CallSignalProc(SIMCONNECT_RECV* pData, UInt32 cbData, Void* pContext) at SimConnect_CallDispatch(Void* , IntPtr , Void* ) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() at AirTrafficManager.Main.DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) 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: 4.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR ---------------------------------------- AirTrafficManager Assembly Version: 1.8.0.1 Win32 Version: 1.8.0.1 ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34108 built by: FX45W81RTMGDR ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR ---------------------------------------- Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61242.0 Win32 Version: 10.0.61355.0 (fsx-sp1.20070510-2038) ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.6195 Win32 Version: 8.00.50727.6195 ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL ---------------------------------------- FSUIPCClient Assembly Version: 2.4.4910.2 Win32 Version: 2.4.4910.2 ---------------------------------------- ************** 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. Do you have verbose log on? If yes can you turn it off to see if this message goes away?
October 31, 201411 yr Do you have verbose log on? If yes can you turn it off to see if this message goes away? No it's unticked. The program still appears to run OK if I just click "continue" and the error window goes away. It happened the first time I clicked "refresh" in the GUI, then again when the radar window was open. Regards Adam Chillblast Core i5 14600KF Liquid Cooled RTX 4070 SUPER 32GB RAM. Internet: 1 Gig Fibre. HoneyComb Throttle & Flight System. UK PPL since 2006 current on PA-28, C-152, C172, Decathlon, C-42 based at EGHP.
October 31, 201411 yr Author New version: http://www.mediafire.com/download/zmdftsy127jgux2/AirTrafficManagerFSX-P3D_Radar.zip Features: 1. Runway clear option. The runway combo will be filled with Runways currently assigned to AI Aircraft. Select a runway in this combo to clear those AI aircraft. In the next optimize cycle they be deleted. In case you don't see your runway listed in the combo (which mean no AI is currently assigned to that runway), but you want keep it clear in future, then just type in that runway number (case sensitive). Runway clear, as of now, clears aircraft landing, taking off and on taxi to that runway. So it can be used both in Departure and Approach scenarios. No it's unticked. The program still appears to run OK if I just click "continue" and the error window goes away. It happened the first time I clicked "refresh" in the GUI, then again when the radar window was open. Regards Adam I have removed some extra data in this version, just try it. Maybe this error goes away.
October 31, 201411 yr 1. Runway clear option. The runway combo will be filled with Runways currently assigned to AI Aircraft. Select a runway in this combo to clear those AI aircraft. In the next optimize cycle they be deleted.In case you don't see your runway listed in the combo (which mean no AI is currently assigned to that runway), but you want keep it clear in future, then just type in that runway number (case sensitive). Does this mean I can use it to remove traffic to opposite direction runway? When traffic gets heavy FSX ATC goes a little nutso. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
October 31, 201411 yr Author Does this mean I can use it to remove traffic to opposite direction runway? When traffic gets heavy FSX ATC goes a little nutso. Ah, I knew something was missing. Next time, till then you can optimise once with your selected runway end and then select the opposite end and optimize again.
October 31, 201411 yr Ah, I knew something was missing. Next time, till then you can optimise once with your selected runway end and then select the opposite end and optimize again. Oh, I don't mind sharing the runway I'm using...just as long as we're all using it in the same direction. :rolleyes: I've had several situations where AI was using both ends...I actually landed right over the top of an airplane that landed opposite direction. I went straight over him and set down...I had reversers. They actually swerved...well...I think they swerved. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
October 31, 201411 yr Author Oh, I don't mind sharing the runway I'm using...just as long as we're all using it in the same direction. :rolleyes: I've had several situations where AI was using both ends...I actually landed right over the top of an airplane that landed opposite direction. I went straight over him and set down...I had reversers. They actually swerved...well...I think they swerved. They must have been running out of fuel with all the go-arounds I had once three in front of me getting go arounds from the ATC. BTW, is fuel even simulated for AI?
November 2, 201411 yr Author New version, 1.9.0.1: http://www.mediafire.com/download/zmdftsy127jgux2/AirTrafficManagerFSX-P3D_Radar.zip Changes: 1. Radar label now shows ATC Airline + ATC Flight Number, as that's what ATC prompts you when sighting 2. Heading arrow is now correctly shown for aircraft
November 2, 201411 yr Thank You DukeSan27, you da man!!! How I Evaluate Third Party Sim Addon Developers Refined P3Dv5.0 HF2 Settings Part1 (has MaddogX) and older thread Part 2 (has PMDG 747)
November 2, 201411 yr Great support thanks! New error with the latest build? I get exactly the same error message when I try to open the newest ATM (of today v 1.901). Same was with a version some days ago. Running P3Dv24 with win81. Harry - Harry 9800x3D (Strix x870e-E) - 64GB RAM (DDR5 6000, CL 30) - RTX 5090, 34'' 1440p OLED HDR - Windows 11 Pro (1TB M.2) - MSFS 2024 (MS Store, 4TB M.2).
November 2, 201411 yr Author I get exactly the same error message when I try to open the newest ATM (of today v 1.901). Same was with a version some days ago. Running P3Dv24 with win81. Harry Harry, the solution was in the next post: Ok, so now it's the sim connect problem. Please install SP1 "SimConnect.msi" from the P3D folder, e.g.: ...\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP1\retail\lib or from the FSX SDK folder: ...\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1 That should get it going.
November 2, 201411 yr I just got this exception mid-flight. This is all the info it gave me. System.AccessViolationException was unhandled Message: An unhandled exception of type 'System.AccessViolationException' occurred in mscorlib.dll Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
November 2, 201411 yr Moderator Removed as posted in wrong forum. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 2, 201411 yr Harry, the solution was in the next post: Ok, so now it's the sim connect problem. Please install SP1 "SimConnect.msi" from the P3D folder, e.g.: ...\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP1\retail\lib or from the FSX SDK folder: ...\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1 That should get it going. That was it. Everything seems to work now. Maybe you could add a small readme/installation instruction to the download. Thank you for this great product and your excellent support. Cheers, Harry - Harry 9800x3D (Strix x870e-E) - 64GB RAM (DDR5 6000, CL 30) - RTX 5090, 34'' 1440p OLED HDR - Windows 11 Pro (1TB M.2) - MSFS 2024 (MS Store, 4TB M.2).
Archived
This topic is now archived and is closed to further replies.