• 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.

2.1.25(o) - Repaint Intsall (model select) / crash

jordanal

jordanal

Messages
78
Country
us-florida
Although I had installed other repaints today using the 2.1.25(o) release, for some reason the AIG Thomas Cook Scandanavia repaint for the AIG 757-200 (RR) caused a crash. It was one of the first, if not the first paint installed today whereby AIFP couldn't identify the model and I had just designated my AIG 752 model from the AIFP pick list when the below JIT occured. The repaint being installed at the time was from the AVSIM library "aig_752_thomas_cook.zip"


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

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at AIFP2.Common.ScanRepaints(Boolean bUnpack)
at AIFP2.MissingACs.Form_Activated(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnActivated(EventArgs e)
at System.Windows.Forms.Form.WmActivate(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.5448 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
AIFP2
Assembly Version: 2.1.11.0
Win32 Version: 2.1.11.0
CodeBase: file:///C:/FSApps/AI%20Flight%20Planner/AIFP2.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Ionic.Zip.Reduced
Assembly Version: 1.9.1.5
Win32 Version: 1.9.1.5
CodeBase: file:///C:/FSApps/AI%20Flight%20Planner/Ionic.Zip.Reduced.DLL
----------------------------------------
System.Deployment
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.
 
AL, I've downloaded the repaint archive and installed it stand-alone. No problem, so I suspect the problem lies with the flight plan archive you were working on at the time.

Please send me the flight plan archive/traffic file (or a link to it) and a copy of the aircraft folder into which you were attempting to install it.

Don
 
Al, I haven't been able to make it crash - even with the stuff you sent me. Can you give me a set of steps that cause the problem?

One thing I did notice is that in the aifp.cfg file, an existing model name is specified for that aircraft, but the (optional) file name is invalid. Perhaps AIFP is "tripping over" that. It's rather complex code in that area, so I need to investigate further. But, if I had a repeatable problem, it would be a lot easier.

Don
 
Well, I removed the existing livery, loaded up the FP and installed the livery again. The first (only) time it crashed, was when I hit the 'Continue' button on the select target window, after putting a check in the AIG-752 folder box. Of course, this time, the livery was installed without issue or any JIT window being produced. Spurious electrons? My other (better) guess is maybe some sequence of continually installing paints and FP's for a few hours this morning and some peculular sequence lead to the JIT. I wouldn't be able to reproduce any of that lenthy (install) sequence I did this morning as it was about 16 FP's in all...
 
I think I know what's happening and, if I'm correct, you won't be able to repeat the problem, at least not consistently. It's an internal timing issue. (I'm not going to even attempt to explain.)

I'll make a few changes that should avoid recurrence.

Don

PS, the error in the aifp.cfg file explains why you had to tell AIFP where to save the aircraft.

Don
 
Roger that, and no hurry, I'm just trying to help where I can. Let me know if these reports become tiresome in any way. :)
 
Let me know if these reports become tiresome in any way.
Click to expand...
As you know, it's my philosophy that a program should never crash. Garbage-in, garbage-out. Not much the programmer can do about that other than, perhaps issue an error message. But, the program should NEVER crash.

So, please, continue to report any such issues.

Don
 
AIFP Version 2.1.25(p), available as the AIFP Development Release from http://stuff4fs.com, contains a couple of revisions that, hopefully, will elimiante thse occasional exceptions.

Don
 
You must log in or register to reply here.
Back
Top