Test version 1.4.35 error

[edakridge]

I received the following error when scanning MSFS for models today.


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

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\WpSystem\S-1-5-21-936619755-2409447364-1802826837-1000\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments-navsystems\html_ui\Pages\VCockpit\Instruments\NavSystems\Shared'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
at JoinFS.ááààûðãîôç.þàöé()
at JoinFS.ááààûðãîôç.þþûôþù()
at JoinFS.ëèæññüíè.ùûìèíéüàñøéîèõøéçîöèõêûäâì(Object èäçåùù, EventArgs e)
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.MenuItem.MenuItemData.Execute()
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.Command.DispatchID(Int32 id)
at System.Windows.Forms.Control.WmCommand(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.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.9151 (WinRelRS6.050727-9100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
JoinFS
Assembly Version: 1.0.0.0
Win32 Version: 1.4.35.0
CodeBase: file:///C:/Program%20Files%20(x86)/JoinFS%20(TEST)/JoinFS.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100)
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.9147 (WinRelRS6.050727-9100)
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.9136 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9153 (WinRelRS6.050727-9100)
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.9136 (WinRelRS6.050727-9100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.FlightSimulator.SimConnect
Assembly Version: 10.0.61259.0
Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.9659
Win32 Version: 8.00.50727.9659
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9659_none_d08cfd96442b25cc/msvcm80.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.

[Peter]

That path name looks a bit complex. Does it look correct to you, and does it start with the path that you entered for the simulator path?

Peter

[edakridge]

Copied straight from windows:

E:\WpSystem\S-1-5-21-936619755-2409447364-1802826837-1000\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments-navsystems

I know that it's convoluted and I have no idea why they made it so difficult, but this is where it installed to when I moved it to my E:\ drive.

[Peter]

That's a bit odd. When I installed it I just entered my own path, "E:\Flight Simulator Packages" and it put everything in there.

Anyway, does this happen each time you do a scan or was it a one off?

I'm just wondering if Windows did some file management in the background while you were doing the scan. That might cause it. If so, I could get it to ignore that error.

[picnic]

I installed both the launcher and FS2020 to my H: drive and didn't see any asserts during the model matching although I did see my own funnies.

It maybe you just ignore this Peter as I had previously played with getting the previous version of joinFS to work. I therefore had a few extra folders entered in to joinFS. However I deleted these and the main path. When I ran the scan I ended up with nearly all, if not all, my P3D aircraft and only a couple of FS2020 aircraft in the substitution list. After messing around and running the old version again eventually the list of models resolved itself to just the FS2020 models. Sorry I didn't do this in a scientific way so can't really help. Is it worth adding a clear out everything and start model matching again or is this how it's meant to work now?

Thanks for you efforts Peter, really appreciated

[Peter]

Every time it does a scan, either manually, or automatically when you connect, it should completely update the model list with the discovered aircraft. The substitutions are in a separate list and it should only remove substitutions if the model is no longer present.

You shouldn't see any P3D models in there, unless one of the paths in the scan window was pointing to the P3D folders? JoinFS keeps separate lists for each simulator.

Peter

[edakridge]

Just tried it again and got the same error.

[Peter]

I'll get it to skip that error, it shouldn't affect the discovery of the aircraft.

Peter

[stevieb]

I, too, am getting the same message as the OP, and the scan has found just 5 items, which are:

• Cessna 152 Asobo|All|Cessna 152 Asobo|Cessna 152 Asobo|SingleProp|0|
  DA62 Asobo|All|DA62 Asobo|DA62 Asobo|SingleProp|0|
  DV20 Asobo|All|DV20 Asobo|DV20 Asobo|SingleProp|0|
  Mudry Cap 10 C|All|Mudry Cap 10 C|Mudry Cap 10 C|SingleProp|0|
  VL3 Asobo|All|VL3 Asobo|VL3 Asobo|SingleProp|0|

I'm unclear what to enter for the root folder path, and I've chosen:
K:\WpSystem\S-1-5-21-1768737758-1701256610-2061698579-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

However, it seems that I have to clear the root folder path completely otherwise the simulator and network connections are not made (i.e. the boxes are clear, not red, amber or green). I've yet to do any actual network testing, given that I'm currently unable to understand this problem.

[picnic]

I pointed mine at h:\fs2020 the folder the game is installed to, i.e. the one the Community folder sits in. Does your complex path point to the same folder via a different route?

[edakridge]

Mine isn't picking up any.

[stevieb]

I pointed mine at h:\fs2020 the folder the game is installed to, i.e. the one the Community folder sits in. Does your complex path point to the same folder via a different route?

No - I'll need to go deeper - ...\LocalCache\Packages - to target that folder. I'll give it a try.

Edit: Pointed scan to the above folder. Practically the same result, i.e. error reported, except only 1 model found?
Installed and ran version 1.4.36. No error message this time but reported no models found (and Kittyhawk.txt still contains the original five entries as I showed in my earlier post). One significant difference, the simulator connects without having to clear the path.

I reverted to the original path (2 folders up) - no difference.

Then I noticed something else. I stopped and restarted JoinFS. On stopping, I looked at the model list and found it contained the five entries referred to above, but on restart, JoinFS reported that the model list was empty with an invitation to scan, and, at this point, Kittyhawk.txt was definitely empty. Then, regardless of whether I said Yes or No to the scan, Kittyhawk.txt contained the aforesaid five lines. (Peter, I hope this makes some sense to you - I'm completely perplexed)

PS I'm hoping to run a test later with an FSX user. (edit: No joy)

Further edit: I've just noticed that the five entries in the model list coincide with five AI aircraft in my current flight. They are listed in the aircraft view when I connect a network. As the session progressed, more AI aircraft types appeared and they were added progressively to the model list.

[Peter]

Further edit: I've just noticed that the five entries in the model list coincide with five AI aircraft in my current flight. They are listed in the aircraft view when I connect a network. As the session progressed, more AI aircraft types appeared and they were added progressively to the model list.

Ah, yes, that bit makes sense. What's happening is that whenever an aircraft gets listed in the Aircraft view, JoinFS will add it to the model list if not already listed. This is to get around the problem of DRM locked aircraft which can't be scanned. So the model list should self populate over time in order to catch all the DRM aircraft. So that explains that, which just leaves us questioning why the scan itself isn't picking up any aircraft. I'm sure it's something to do with that long path name. Mine works but I have my packages under my custom 'E:\Flight Simulator Packages' folder. Can you remember what you specified during the installation of MSFS2020 when it asked where you would like to install packages?

Peter

[stevieb]

I'm fairly sure you're right about the problem being something to do with the long pathname, Peter.
I'm sorry that I can't be 100% certain about what I specified during installation, but I think I simply directed it to the root of K: which is a new SSD that I had installed. In the root of K: the installer has placed three folders "Program Files", "WindowsApps", "WpSystem". "Program Files" has a sub-folder "ModifiableWindowsApps" which is empty. "WindowsApps" tells me I don't have permission to access this folder. "WpSystem" is the start of that long path.

Edit: It IS the pathname.
You'll understand this better than I do. There's some sort of logical redirection involved; I found a file called UserCfg.opt within which there's a definition of something it calls "InstalledPackagesPath". It's defined as follows:
C:\Users\[username]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages.
When I set that as my pathname the result was that 63 models were found.
6 of those models are from the additional folder defined in my version 1.4.34 and belong to P3D.

[Peter]

I'm fairly sure you're right about the problem being something to do with the long pathname, Peter.
I'm sorry that I can't be 100% certain about what I specified during installation, but I think I simply directed it to the root of K: which is a new SSD that I had installed. In the root of K: the installer has placed three folders "Program Files", "WindowsApps", "WpSystem". "Program Files" has a sub-folder "ModifiableWindowsApps" which is empty. "WindowsApps" tells me I don't have permission to access this folder. "WpSystem" is the start of that long path.

Are you using the Steam version of MSFS2020 or the stand-alone? I wonder if the installation for Steam is slightly different.

Peter

[stevieb]

@Peter. See above (edited) post which now has more information.
It's the stand-alone version.

[edakridge]

I am using the "Microsoft Store" version. I believe that the three different versions (Store, XBox Live, and Steam) all have different install parameters/locations. Jon Murchison is running into that problem trying to get an ADE up and running.

[Peter]

I am using the "Microsoft Store" version. I believe that the three different versions (Store, XBox Live, and Steam) all have different install parameters/locations. Jon Murchison is running into that problem trying to get an ADE up and running.

Ah, I see, it's all starting to make sense now. I wonder if some of those folders are not accessible or something like that. Given the unusual numbers in the path name it may be that Windows manages those app files in very specific ways.

For now I would suggest opening the JoinFS settings and unticking 'Model scan on connection' and then don't bother using the scan at all. Just rely on the auto populate instead.

Could you try using Windows Explorer and searching for 'aircraft.cfg' in that folder. That should effectively do what JoinFS does when it looks for those files. Does Explorer successfully return you a list of files?

Peter

[stevieb]

For me, Windows Explorer returned a list of 29 files when searching K:\WpSystem\S-1-5-21-1768737758-1701256610-2061698579-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
and the same when searching C:\Users\[username]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

[Peter]

For me, Windows Explorer returned a list of 29 files when searching K:\WpSystem\S-1-5-21-1768737758-1701256610-2061698579-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
and the same when searching C:\Users\[username]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

Ok, and have you tried using 'C:\Users\[username]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe' as your scan folder in JoinFS?

Peter