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

AIFP Error

J

jamesdude11

Messages
16
Country
unitedkingdom
I keep getting the attached screenshot error when I try to launch AIFP - I have tried uninstalling and re-installing AIFP and still the issue exists. I am using MSFS installed via Game Pass.
 

Attachments

  • image.png
    image.png
    361.9 KB · Views: 321
Make sure the path to your FS programs (including AIFP) do not contain any special characters or accents. Just English letters, numbers, and the underline.
 
It's not possible to give you a definitive answer from the information you have provided.

First of all, I'm not familiar with Game Pass - at least under that name. Also, I need the rest of the exception message to know where in AIFP the exception occurred.

What is probably happening is, as Tom suggests, the registry item checked by AIFP for MSFS contains a unexpected character. AIFP looks for the path to MSFS in registry item "AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt\InstalledPackagesPath".

Please post the value found in that registry item and the full exception message
 
Please see exception message:

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

************** Exception Text **************
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.NewNormalizePath(String path, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.GetFullPathInternal(String path)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards, Collection`1 Results)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards)
at AIFP3._4__Dev_.AircraftCfg.GetAllAircraftFolders(List`1& listFolders, Int32 fFSVer)
at AIFP3._4__Dev_.listAC.FindPathsToACs(List`1 listAC, Int32 fFSVer, List`1& listReport)
at AIFP3._4__Dev_.File_Handling.LoadFile(String sPath, List`1& listFP, List`1& listAC, List`1& listAP)
at AIFP3._4__Dev_.File_Handling.LoadMainFile(String sPath)
at AIFP3._4__Dev_.MainPanel.mnuFiles_Open_TextZip_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.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.Button.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.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
AIFP3
Assembly Version: 3.4.3.3
Win32 Version: 3.4.3.3
CodeBase: file:///C:/Users/USER%20PC/Desktop/AIFP1/AIFP3.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
ASToFra.Interfaces
Assembly Version: 1.0.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Users/USER%20PC/Desktop/AIFP1/ASToFra.Interfaces.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.
 
Click on the Windows icon in your task bar, enter "regedit.exe" into the search window, select it from the menu presented and then
find the item.
 
An easier way would be to open AIFP.ini and check the value of "Path to FS2020". If that's not the full path to your MSFS installation, then the registry is not set as usual. What you could try is changing the "Path to FS2020" value to the actual full path to MSFS.
 
gadgets said:
An easier way would be to open AIFP.ini and check the value of "Path to FS2020". If that's not the full path to your MSFS installation, then the registry is not set as usual. What you could try is changing the "Path to FS2020" value to the actual full path to MSFS.
Click to expand...
Still getting the error - tried doing what you suggested. Still no joy :(
 
Without knowing what you've found, (and where MSFS is actually installed) there's not much I can do to help you.
 
That's an unusual entry. Normally it reads "Path to FS2020="fully qualified path to MSFS2020

I suggest you replace the line starting "Path to FS2020.cfg=C:\Users\USER PC\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\FlightSimulator.cfg" with the above (including the path on your system, of course.
 
Apologies for butting here, Don.

The thing that caught my attention was that your path has your MS userid as 'USER PC'. Is this really correct? It should be the same as the abbreviation for your MS account. This would the folder in your C:\Users folder where all your system files and OneDrive files are kept.

I have checked my AIFP.ini file, I should clarify that I do not have 2020, and there are entries for 'Path to xxx' and 'Path to xxx.cfg' for both FS9 and FSX for me. It seems logical that you may need both for 2020 as well.
So it seems that you have the path for the cfg but need to add the path to 2020 as well, rather than replacing one with the other.
It goes without saying that Don knows far more about this point than me.
 
Unlike FS9 and FSX, "Path to FS2020.cfg" is not saved to AIFP.ini. It has no forward value. What is saved in AIFP.ini is the "Path to FS2020" and it should include the actual fully-qualified path to your MSFS2020 installation. That path is used as a backup in subsequent starts. If AIFP does not find the current version of MSFS2020, it will attempt to use the saved path,

AIFP has been successfully finding MSFS2020 on users computers for months - both Steam and MS versions. If there is a new installer now in use, I'll be pleased to add in that capability. But, someone will have to tell me the parameters.

In the meantime, no matter what version of MSFS2020 you are using, adding the line "Path to FS2020=fully qualified path" to AIFP.ini should allow use of MSFS with AIFP.
 
gadgets said:
Unlike FS9 and FSX, "Path to FS2020.cfg" is not saved to AIFP.ini. It has no forward value. What is saved in AIFP.ini is the "Path to FS2020" and it should include the actual fully-qualified path to your MSFS2020 installation. That path is used as a backup in subsequent starts. If AIFP does not find the current version of MSFS2020, it will attempt to use the saved path,

AIFP has been successfully finding MSFS2020 on users computers for months - both Steam and MS versions. If there is a new installer now in use, I'll be pleased to add in that capability. But, someone will have to tell me the parameters.

In the meantime, no matter what version of MSFS2020 you are using, adding the line "Path to FS2020=fully qualified path" to AIFP.ini should allow use of MSFS with AIFP.
Click to expand...
Hi,

Tried what you have suggested sadly, still no joy.

I installed FS2020 with XBOX GAME PASS from Microsoft and My Install Location is C:\Users\USER PC\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

Could my installation path - the fact there are complex characters, be causing this issue?

Thanks
 
The only odd character in there is the period, and I'm not sure if that is allowed or not...
 
No, that is not your install path. That's the first part of the path to the path UserOpt.cfg file - which you need to access in order to determine the install path.

Open that folder and you'll find it contains a series of sub-folders, one of which is named "LocalCache". In that folder you will find a text-based file UserOpt.cfg. Open it and the bottom item is labelled "InstalledPackagesPath" and that is where MSFS2020 is installed on your system - if the package has been installed properly.
 
gadgets said:
No, that is not your install path. That's the first part of the path to the path UserOpt.cfg file - which you need to access in order to determine the install path.

Open that folder and you'll find it contains a series of sub-folders, one of which is named "LocalCache". In that folder you will find a text-based file . Open it and the bottom item is labelled "h" and that is where MSFS2020 is installed on your system - if the package has been installed properly.
Click to expand...
This is what it says on UserOpt.cfg - InstalledPackagesPath

InstalledPackagesPath "C:\Users\USER PC\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"
 
gadgets said:
Then I'd uninstall and re-install.
Click to expand...
So will AIFP not work with FS2020 installed in this location?
Like I said, I installed using XBOX GAME PASS from Microsoft, I'm not sure if I can specify the installation location when installing through the Microsoft Store?
 
You must log in or register to reply here.
Back
Top