• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

AI Flight Planner Crashes

R

Rce21

Messages
8
Country
australia
AI Flight Planner Crashes as soon as I check the "FSX" bubble. Anybody know how to fix this? ._.
It says


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 AIFP2.AircraftCfg.GetCruiseSpeed(List`1& listAircraftCfg)
at AIFP2.CollectAircraft.MakeAircraftList(List`1& listACFolders_, Int32 fFSVer, List`1& listAC)
at AIFP2.listAC.FindPathsToACs(List`1 listAC, Int32 fFSVer)
at AIFP2.Common.SelectFSVersion(Boolean bChecked_FS9, Boolean bChecked_FSX)
at AIFP2.Main_Panel.chkFS_CheckedChanged(Object sender, EventArgs e)
at System.Windows.Forms.RadioButton.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.RadioButton.set_Checked(Boolean value)
at System.Windows.Forms.RadioButton.OnClick(EventArgs e)
at System.Windows.Forms.RadioButton.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.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: 2.0.0.0
Win32 Version: 2.0.50727.4214 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
AIFP2
Assembly Version: 2.1.11.0
Win32 Version: 2.1.11.0
CodeBase: file:///C:/Users/daddy/Documents/AIFP/AIFP2.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4214 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4212 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.1 built by: SP
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Deployment
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------

************** 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.
 
What were you doing, or what was the state of the system, when you checked FSX, please.

I suspect it is being triggeed by a particular aircraft since it is checking cruise speeds when it crashes.

I'll investigate tomorrow.

DOn
 
I've now looked at the code. The problem is invalid aircraft data.

If you check the "cruise_speed" item in the "[reference speeds]" block of the aircraft.cfg files for the aircraft used in the flight plan/traffic file that was loaded (with any changes you may have made) when the exception occurs, I expect you'll find one containing a grossly excessive or improperly-formatted cruise speed value.

AIFP should handle such situations (and future versions will). In the meantine, if you fix the invalid cruise speed, the problem should go away.

Please confirm this was the problem.

Don
 
When I developed AIFP, I neglected to make provision to protect it from data corruption or invalid data in external files that might cause processing problems for AIFP itself. AIFP does check for values in range but the nature of the problem at hand is that AIFP never gets that far if a numeric value is invalid for the data type AIFP expects.

So, I have now added an additional check on all imported data to ensure basic-processing integrity. While the change is minor, it had to be applied in almost one hundred places. So, just in case my typing wasn't perfect, I'd like to have some of you use the changed version for a few days before I release it generally.

The interim release is available at stuff4fs.com/AIFP/Downloads/AIFP2119d.zip.

rcs21, if you haven't already corrected the problem aircraft.cfg file, please first test with this release to confirm it addresses your situation.

Don
 
Yeah Don, it works now. I figured that because of how much information the error supplied that it was a MAJOR error. I tried it with the error, and everything worked fine. Turns out it is a error with an aircraft.cfg. Its all good now, thanks a lot (: However, I have one final question, how do you figure out all the times and stuff for UTC -5?
 
I figured that because of how much information the error supplied that it was a MAJOR error
Click to expand...
Any time AIFP throws and exception, I consider it a major error. Actually, the amount of information displayed about the error is a function of some Windows setting on your system.

However, I have one final question, how do you figure out all the times and stuff for UTC -5?
Click to expand...
Not sure what you are after. All calculations are done in UTC, with the proper (hopefully) UTC offsets of applied to the displayed values. There are a couple of sections in Chapter 9 of the user manual that address timezone management.

Since I now know I fixed the right problem, I would encourage all experienced users to download and use the interim version (link earlier in this thread) so as to highlight any errors I might have introduced this morning.

Don
 
Thanks so much Don. What I was trying to get across was If the airport is at UTC -5 and I want several airplanes to take off at 12 Noon, what would the UTC time be for "Depart" time?
 
If the airport is at UTC -5 and I want several airplanes to take off at 12 Noon, what would the UTC time be for "Depart" time?
Click to expand...
17:00.

But why do you care with AIFP? You can select Local Time and specify noon or select the -5 time zone and, again, set departure at noon.

Don
 
Well, I wanted to know, because its in UTC, and I do not know ANYTHING about UTC time. I keep setting 12:00, but it appears a whole different time. So what do you do? 17:00-5:00 = 12:00. Do you set a time and then -5? What if you want a plane to takeoff at 10:00PM?
 
Last edited:
Select local time in AIFP and you won't have to worry about UTC offsets.

But, if you really want to work in UTC, add offset to UTC to get local time and subtract offset from local time to get UTC.


Don
 
By the way, you may know UTC by its old name: Greenwich Mean Time (GMT)...

Note though:

Historically the term GMT has been used with two different conventions, sometimes numbering hours starting at midnight and sometimes starting at noon. The more specific terms UT and UTC do not share this ambiguity, always referring to midnight as zero hours.
Click to expand...
 
You must log in or register to reply here.
Back
Top