1.3.8 issues

[JarangMandi]

Peter,

Trying TEST version 1.3.8 on a machine that's also running 1.3.6

Firstly, 1.3.8 reports the following in the log window on startup (whether 1.3.6 is running or not). The middle line is unusual...

Code: Select all

29/11/2017 18:42:48 Started
29/11/2017 18:42:48 Node failed to read message: 3 Unable to read beyond the end of the stream.
29/11/2017 18:42:50 Looking for simulator...

Also, getting an error that suggests that JoinFS is trying to open the same port in both instances when the second of the two are started - whichever is started first. Exception details from starting 1.3.8 with 1.3.6 running pasted below - clearly obfuscated, but I hope you can make sense of it!

Code: Select all

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

************** Exception Text **************
System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family)
   at JoinFS.äâäââúððÿ.Open(Int32 óúíâ)
   at JoinFS.îñãéøé.Open()
   at JoinFS.êâî.òãðøëùüûãåóíàìø()
   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.8762 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
JoinFS
    Assembly Version: 1.0.0.0
    Win32 Version: 1.3.8.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.5491 (Win7SP1GDR.050727-5400)
    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.8770 (QFE.050727-8700)
    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.5495 (Win7SP1GDR.050727-5400)
    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.5483 (Win7SP1GDR.050727-5400)
    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.5494 (Win7SP1GDR.050727-5400)
    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.4940
    Win32 Version: 8.00.50727.4940
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc/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.

Ignoring the exception allows the program to continue to run insofar as it's possible to see the settings and the fact that it is configured to run on port 6113 instead of the default 6112.

Anything you want me to try?

[JarangMandi]

Actually, it doesn't look like 1.3.8 that's caused the networking problem... I've been trying to roll back and have tried 1.3.6 with 1.3.6 TEST and also 1.3.3 with 1.3.6 TEST and am seeing the same thing - which is weird because I had that last combination running OK before I tried the upgrade.

I've even scoured the registry and application data folders and erased all trace!

[JarangMandi]

Sorry for the ongoing narrative...!

The problem seems to be related to use of UDP port 7471 which both "production" and TEST versions/instances of JoinFS listen on in addition to the defined port.

It doesn't seem to be being used to pass traffic at the moment though as I've been running Wireshark on it for a while and there's been nothing coming or going on that port. Is this related to the chat function you're building? In any event, whatever its for, it would be good to be able to define a separate port...

Thanks.

Andy

[Peter]

Ah, I'm glad that you narrowed it down to that port. That is the port it uses to communicate with the X-Plane plugin.

Are you using X-Plane? Even if you aren't I think it will still attempt to find X-Plane and open the port.

Shouldn't be a problem, I'll just change the port for the TEST build.

Thanks,
Peter

[JarangMandi]

I am using X-Plane, yes... but as you say, in respect of opening a listening port that's probably irrelevant. The server machine where I first saw the issue has no simulator installed on it and never has had.

Reading between the lines, I'm assuming that your X-Plane plugin tries to establish a UDP connection to a JoinFS instance listening on that port. I suppose I could check the traffic, to be sure. Does that mean post fix there's going to need to be two different X-Plane plugins (and if so will they be able to co-exist) in the scenario where I have both JoinFS versions installed on my flying machine?

[Peter]

No, it's the other way round JoinFS establishes a connection to the plugin. I'll use a separate TEST setting for the X-Plane address in File|Settings. Then you should be able to change the one that you don't want to connect to something like 127.0.0.2 or 0.0.0.0. I'll have a play around and see what works.

Peter

[FireRx]

FYI Peter, also for Perpar3D folks flying with XP'rs in session the XP planes are flying sideways again. right wing down

[Peter]

FYI Peter, also for Perpar3D folks flying with XP'rs in session the XP planes are flying sideways again. right wing down

Check your ATC setting in File|Settings. It should be disabled otherwise it activates the AI on the aircraft. That could be the cause.

Was it a particular aircraft doing it?

Peter

[FireRx]

We'll try that Peter,
All this time we had it on. Thanks sir. Is it a way to make it where we can use ATC and omit the AI aircraft? or will that defeat the purpose?

[Peter]

We'll try that Peter,
All this time we had it on. Thanks sir. Is it a way to make it where we can use ATC and omit the AI aircraft? or will that defeat the purpose?

In ATC Mode, it configures the aircraft so that they show on the FSX radar screen and other add-ons. However, the simulator forces the AI control back on for those aircraft, so you get the strange banking effect and also the lights can switch on and off as the AI competes with JoinFS to control the aircraft. But getting JoinFS to switch the AI off again then removes it from the radar. Catch-22 I'm afraid. There's possibly another solution which I'll look into at some point.

Peter

[FireRx]

YAY.. So far so good in 1.4.0, Did a test flight with 2 P3D, 1 XP11, and 1 FSX in session. Everyone aircraft looks right in aspect, and no one cut off each others engines. Were do a bigger flight test tomorrow. Also your hunch on the ATC was correct. ATC on, planes in XP were leaned over. ATC off. aircraft flew flat and level.

[Peter]

YAY.. So far so good in 1.4.0, Did a test flight with 2 P3D, 1 XP11, and 1 FSX in session. Everyone aircraft looks right in aspect, and no one cut off each others engines. Were do a bigger flight test tomorrow. Also your hunch on the ATC was correct. ATC on, planes in XP were leaned over. ATC off. aircraft flew flat and level.

Needs to come with a bigger warning.

Sounds like a good test. We're getting there!

Peter