This forum is no longer active. Reference only.

Our group using v3.0.7 today had 3 Unhandled Exception Errors and JoinFS failure with P3D & 2020. Evidently the problem is still there.

Do you have any more information, such as crash output?

Peter

sorry, I don't have that. I installed the new version over the old one thinking it was going to delete the old one first.
After all the problems, I removed the JFS using Win10 programs and features and then installed the new version.
I will test it again with our next group flight and see how it does.
Jerry

We had our group flight this morning and during that 1.5 hour flight I had two more errors. This is the detail from the second one. Any idea how to solve this? Thanks,

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

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Generic.List`1.ToArray()
at JoinFS.ïâþòèèüùâãä.ÿðõøôãïêûöìãë()
at JoinFS.ïâþòèèüùâãä.êüüïæéæóõâåãöçü(Boolean ÿäêûû)
at JoinFS.ïøäúëéïó.ûùúäêâÿîçàüõöê(Object ìàáïùâ, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.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: 3.0.7.0
CodeBase: file:///C:/Program%20Files%20(x86)/JoinFS/JoinFS.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.9149 (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.9149 (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.9149 (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.9149 (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.9672
Win32 Version: 8.00.50727.9672
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9672_none_d08f9da24428a513/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.

Hi Peter

Just to add several members of the the A2A Misfit Squadron, including myself have suffered the unhandled Exception Error. Sometimes we get a Net Frame error and other times joinfs just shuts down with no warning. We are all on v3.0.7.

ianfisher wrote: ↑Sun Aug 08, 2021 8:18 pm Hi Peter

Just to add several members of the the A2A Misfit Squadron, including myself have suffered the unhandled Exception Error. Sometimes we get a Net Frame error and other times joinfs just shuts down with no warning. We are all on v3.0.7.

Thanks. Hopefully it's the same issue. Try 3.0.8 when it comes out and let me know if you still get the problem.

Peter

Also, we of the A2A Misfit Squadron have the problem where everybody's engines are running except for MINE. We ask each other what is going on on our Discord channel, and everybody says, "MY engines are off, but all of you guys, your engines are running." Guys who haven't updated yet, their airplanes are visible, but it looks like their gear is retracted - their just hanging there like some kind of antigrav. With their engines running.

Please help. Get this squared away and I'll contribute. Honest.

Paughco wrote: ↑Tue Aug 10, 2021 2:32 am Also, we of the A2A Misfit Squadron have the problem where everybody's engines are running except for MINE. We ask each other what is going on on our Discord channel, and everybody says, "MY engines are off, but all of you guys, your engines are running." Guys who haven't updated yet, their airplanes are visible, but it looks like their gear is retracted - their just hanging there like some kind of antigrav. With their engines running.

Please help. Get this squared away and I'll contribute. Honest.

Could you post this on the correct thread, please. Also, thanks for the "promise" of a contribution. If I had a dollar for everyone who said that...

Peter

In my case, the errors started to appear after upgrading to 3.0.0. As far as I can tell, it only manifests itself with P3D4.5, and on MSFS hasn't occurred. It crops up about 40-50 minutes into the flight.
Error log attached.

Could you let me know if you see this with 3.0.8, please. And if it appears fixed, could you just check the monitor output during a flight to see if there are any error message being shown. It seems that this error was due to the monitor getting flooded for some reason.

Peter

Peter wrote: ↑Tue Aug 10, 2021 7:30 am

Paughco wrote: ↑Tue Aug 10, 2021 2:32 am Also, we of the A2A Misfit Squadron have the problem where everybody's engines are running except for MINE. We ask each other what is going on on our Discord channel, and everybody says, "MY engines are off, but all of you guys, your engines are running." Guys who haven't updated yet, their airplanes are visible, but it looks like their gear is retracted - their just hanging there like some kind of antigrav. With their engines running.

Please help. Get this squared away and I'll contribute. Honest.

Could you post this on the correct thread, please. Also, thanks for the "promise" of a contribution. If I had a dollar for everyone who said that...

Peter

Peter: You are right. I can see that you have put a lot of time and effort into JoinFS. It's a great resource. I donated $21 bux to the cause. Looking forward to v3.0.8

Seeya
ATB

V3.0.8 appears to have fixed it. Many thanks, Peter.

stevieb wrote: ↑Tue Aug 17, 2021 8:31 pm V3.0.8 appears to have fixed it. Many thanks, Peter.

Great. Do check the JoinFS monitor window a couple of times just to see if you are seeing excessive messages displayed. If so, it may be affecting performance.

Thanks,
Peter