By Ross Carlson 887155
#499348 Note that you can disable the FIPS algorithm check by creating a file called vPilot.exe.config and placing it in the same folder as your vPilot.exe. The contents of the file should be as follows:

Code: Select all<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
   <enforceFIPSPolicy enabled="false"/>
  </runtime>
</configuration>


That should allow vPilot to read and decrypt the config file on systems that have the FIPS algorithm check enabled.

Out of curiosity, did you enable the FIPS check yourself, or was it enabled by some other system administrator, perhaps as part of a group security policy? I'm assuming it's not enabled by default on Windows 10 or I would have had many other users report this issue, and you're the first.
By Avalon Danvers 1355123
#499358
Ross Carlson 887155 wrote:Note that you can disable the FIPS algorithm check by creating a file called vPilot.exe.config and placing it in the same folder as your vPilot.exe. The contents of the file should be as follows:

Code: Select all<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
   <enforceFIPSPolicy enabled="false"/>
  </runtime>
</configuration>


That should allow vPilot to read and decrypt the config file on systems that have the FIPS algorithm check enabled.

Out of curiosity, did you enable the FIPS check yourself, or was it enabled by some other system administrator, perhaps as part of a group security policy? I'm assuming it's not enabled by default on Windows 10 or I would have had many other users report this issue, and you're the first.


I will make that configuration file. When I saw it first it read like it was required as part of the build process but that must have been an IIS Application.

On Windows 10, I believe FIPS is enabled by default for computer systems equipped with the Trusted Platform Module 1.2 (or later) enabled (i.e. fully authorized; etc.). Enforcing the FIPS cryptography group policy wasn't even configured on this system as it wasn't configured on the Azure AD Domain for which the system connects to (I own the network and while FIPS cryptography is forced enabled by the local domain controllers, systems such as personal systems connecting to the domain which are authorized are done so through Azure AD).

However, looking back at the logs, I see that Windows switched to FIPS enforced cryptographic validation on Windows 10 Pro (Insider Preview - Fast Ring) following the installation and initialization of the Infineon TPM module (before it was ever connected to an Azure AD) by myself so I am indeed leaning towards that Windows 10 defaults to enable it if a TPM is available and initialized.

Quick Edit - I forgot to mention from your earlier post: I tried vPilot 1 after vPilot 2 wouldn't launch.
By Ross Carlson 887155
#499361
Avalon Thorne 1355123 wrote:Quick Edit - I forgot to mention from your earlier post: I tried vPilot 1 after vPilot 2 wouldn't launch.


So the answer is no, you've never run vPilot 1.0 successfully in the past, on this machine, right? I assume that's correct, since the encryption methods used in vPilot didn't change at all from 1.0 to 2.0.
By Luka Stevens 1345102
#499394 hey I remember you saying that tower connect would be back in version 2.0, I sadly can't see the server in the server tab.
Is it me doing something wrong or is it not in this version?
By Ross Carlson 887155
#499395 It is now the .towerview command. It doesn't appear to be working with ES though, since in version 2.0 it connects in observer mode, not pilot mode. Evidently ES doesn't pass on aircraft type code information to observer connections. I will be contacting the ES devs about it.
By Niels Voogd 1331163
#499792
Ross Carlson 887155 wrote:It is now the .towerview command. It doesn't appear to be working with ES though, since in version 2.0 it connects in observer mode, not pilot mode. Evidently ES doesn't pass on aircraft type code information to observer connections. I will be contacting the ES devs about it.


would it be possible to return the localproxy option while we are waiting for the ES devs? (my experience is that they keep you waiting) + i've used towerview for quite a while at eham. never had problems with it, why did you remove this feature, without having a working replacement?

or maybe there is one and i didn't look well enough, correct me if i'm wrong.
By Ross Carlson 887155
#499798
Niels Voogd 1331163 wrote:would it be possible to return the localproxy option while we are waiting for the ES devs?


Possible, yes, but it's not going to happen. There were several reasons why I removed the local proxy server option:

1) It was an experimental, undocumented feature, intended to connect vPilot to a beta version of vSTARS which provided the appropriate information via a local proxy server.
2) It didn't work quite right with ES (because it was never intended for use with ES) because ES doesn't implement the ACCONFIG protocol, resulting in the lights/gear/engines not appearing correctly in many cases.
3) People were using it to connect vPilot to non-VATSIM networks.

I removed the feature because I hadn't yet found the time to update vSTARS so that tower controllers could use it with vPilot to get a tower view. I really shouldn't have ever added the local proxy server option until it was ready for actual usage with a supported ATC client. Only after I removed it did I really learn the extent to which people were using it in ways it was never intended, such as connecting to ES or connecting to non-VATSIM servers.

I don't have a problem with the software being used in ways I didn't envision, but I do have a problem with it being used in ways that are "broken" in some fashion, such as was the case with ES not supporting the ACCONFIG protocol. Same with connecting it to non-VATSIM servers, since that was a very hackish process involving a "fake" proxy server, sort of like the old SB2 days.

So I removed the local proxy option from the server dropdown, and replaced it with the .towerview command so that users could still connect it to ES, using an observer connection instead of a pilot connection. Unfortunately that broke it even more with ES, because now not only does the ES connection lack ACCONFIG protocol support, it also doesn't pass any aircraft data at all to vPilot. The upside is that I have opened an email conversation with the ES devs to get full support built into ES, in which case it will work just as well as the upcoming vSTARS for providing a server connection for vPilot for the purpose of creating tower displays.

I'm also planning to release a version of vPilot that works properly with non-VATSIM servers. That version will have all the VATSIM-proprietary stuff removed from it, such as the voice server connection capability.

Niels Voogd 1331163 wrote:why did you remove this feature, without having a working replacement?


I trust the above answers this question as well.
By Niels Voogd 1331163
#499809 Hey Ross,

thanks for the information, anxiously waiting until the feature is re-implemented.
If you come to a solution with the ES devs, would this then become a documented feature?

would be great if you could keep us up to date on the progress, if there is any.

Cheers!
and keep up the great work so far!
By Ross Carlson 887155
#499813
Niels Voogd 1331163 wrote:If you come to a solution with the ES devs, would this then become a documented feature?


Yes, it's already documented in the 2.0 docs:

http://vpilot.metacraft.com/Documentation2.aspx
By josh king 1341657
#500133 hey guys, i have had a massive problem with my model matching in the past then i heard Vpilot 2.0 does it for you so i downloaded it and i get this error

************** Exception Text **************
System.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Max(IEnumerable`1 source)
at System.Linq.Enumerable.Max[TSource](IEnumerable`1 source, Func`2 selector)
at dt.c()
at dt.a(Object A_0, RunWorkerCompletedEventArgs A_1)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
vPilot
Assembly Version: 2.0.3.0
Win32 Version: 2.0.3.0
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/vPilot.exe
----------------------------------------
Ninject
Assembly Version: 3.2.0.0
Win32 Version: 3.2.2.0
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Ninject.DLL
----------------------------------------
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.5485 (Win7SP1GDR.050727-5400)
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.5492 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.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
----------------------------------------
Ninject.Extensions.Factory
Assembly Version: 3.2.0.0
Win32 Version: 3.2.1.0
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Ninject.Extensions.Factory.DLL
----------------------------------------
Castle.Core
Assembly Version: 3.2.0.0
Win32 Version: 3.2.0.2259
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Castle.Core.DLL
----------------------------------------
bbv.Common.EventBroker
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/bbv.Common.EventBroker.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.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
DynamicProxyGenAssembly2
Assembly Version: 0.0.0.0
Win32 Version: 3.2.0.2259
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Castle.Core.dll
----------------------------------------
DynamicProxyGenAssembly2
Assembly Version: 0.0.0.0
Win32 Version: 3.2.0.2259
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Castle.Core.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
protobuf-net
Assembly Version: 2.0.0.668
Win32 Version: 2.0.0.668
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/protobuf-net.DLL
----------------------------------------
78nlvswh
Assembly Version: 2.0.3.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
log4net
Assembly Version: 1.2.10.0
Win32 Version: 1.2.10.0
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/log4net.DLL
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
SharpDX.DirectInput
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/SharpDX.DirectInput.DLL
----------------------------------------
SharpDX
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/SharpDX.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
----------------------------------------
Metacraft.Vatsim.Vpilot.Plugins
Assembly Version: 1.1.0.9
Win32 Version: 1.1.0.9
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/Metacraft.Vatsim.Vpilot.Plugins.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
f2m8puek
Assembly Version: 2.0.3.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
-89xhx2r
Assembly Version: 2.0.3.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
INIFileParser
Assembly Version: 2.2.2.0
Win32 Version: 2.2.2
CodeBase: file:///C:/Users/Josh/AppData/Local/vPilot/INIFileParser.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>




Could you please help me, thanks
By Andrew Ogden 1336925
#500147
josh king 1341657 wrote:hey guys, i have had a massive problem with my model matching in the past

Have you got the actual models downloaded. Just adding the model matching rules doesnt make aircraft their correct type.