By Ross Carlson 887155
#501425 Yeah, that's the only add-on I know of that has had some sort of conflict with vPilot. I'm not sure what the actual problem was, but it was fixed by the FS2Crew developers.
By Rodrigo Abulafia 874508
#501428 Hello and thanks for the help, but I insist: it only happens the freezing with vPilot, nor any of the others add-ons make FSX SE to freeze. I guess all of them are "informally" certified to work with FSX SE while vPilot or any other Vatsim Software isn´t. The thing is that FSX SE has been out for some years from now and none of the software has been update. Curious.

Anyway,
Thanks to all for the support.

cheers
By Ross Carlson 887155
#501429 Yeah, definitely strange ... I wish I had more information about what's happening. I do know that plenty of people use vPilot with FSX SE without a problem.
By Kyle Ramsey 810181
#501430
Rodrigo Abulafia 874508 wrote:
As I mentioned before, it only happens with vPilot, that´s why a really don´t see the sense to disable the add-on scenery & others.


Because then you'd know the source of the error and can correct it. Sometimes just reloading that scenery will fix it and everything is good to go. It also adds to the body of knowledge about this error type as it seems to have mysterious elements to it so any new knowledge gets us closer to nailing it shut forever.
By Bradley Grafelman 1242018
#501432
Rodrigo Abulafia 874508 wrote:The thing is that FSX SE has been out for some years from now and none of the software has been update. Curious.

Eh.. not too curious, given that the most significant changes that FSX:SE seems to have brought are where FSX gets installed on your hard drive, a new splash screen, new defaults for .cfg file values, and a new multiplayer network. I'd be shocked to learn they really changed the SDK that addon developers use in any meaningful way.

Rodrigo Abulafia 874508 wrote:it only happens the freezing with vPilot

The one thing off the top of my head that vPilot could do differently than, for example, IvAP, would be the choices for models it tells FSX to use when displaying other aircraft from VATSIM.

@Ross: Before v2.0, you had the "Run Model Matching Test" functionality. Did this iterate through all model rules force FSX to create and render an aircraft (even if momentarily) with each model? For some reason I thought it did, because I remember some models causing FSX to crash when used and the model matching test helped identify such models. All that to say... could it not be a specific aircraft model (e.g. one that IvAP wouldn't be using) that is causing Rodrigo's crashes?
By Rodrigo Abulafia 874508
#501436 Hi @Ross and thanks for the support.

I have checked base on your question and I am only using the matching models of IA of FSX SE. Make Sense? Do you suggest to make any change about that?

Reinforcing my comparison with IVAO -> Why they do have a Software that works absolutely perfectly really without any complaint at all, even thought inside FS with Full Screen, why Vatsim is not at the same stage?

We are -indeed- lot of Vatsim lovers for so many years with the aim of helping and make things done.

Greeting to all and sorry for the passion beyond my words.

RA
By David Zhong 1027224
#501442 It's a matter of perspective. I have had issues with Squawkbox and FSInn in the past, but no problems with vPilot! So no complaints from me.

Of course, you'll see things a bit differently given your current situation.
By Rodrigo Abulafia 874508
#501518 Hello David & Vatsim Staff:

I have been trying different stuff these past days, and I have overcome the situation and would like to share with the community something that -most of the time- didin´t crash at all. First let me figure out the configuration I am using:

-FSX SE (updated via steam)
- Activeweather 5
- FSPS
- PDMG Products (737, 777 and 747)
- FSPS xtreme FSX Booster v2
- REX4 (Plus+Overdrive)
- Windows 10 Home, updated
- Core i7+32GB RAM+nVidia GTX 760 FTW+

Usually, I used to load first REX, define the route, load the textures and run FSX from REX. I shift the loading process and FIRST load FSX SE as ADMINISTRATOR and all of the following software to run in the SAME MODE.

SO basically the loading process follows like this:

- xtreme FSX Booster (should be loaded before FSX)
- FSX SE
- REX
- Active Weather
- FSPS

and of course, happy to be online again! :D

Hope it helps

cheers
By Rodrigo Abulafia 874508
#501887 Hi Kyle & Vatsim & vPilot Team,

Have I had recently experienced quitely often the following errors while trying (once more) to connect to vPilot while exiting Full-Screen mode from FSX SE:

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

************** Exception Text **************
System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type)
at bo.v()
at bz.g(Object A_0, EventArgs A_1)
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.8689 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
vPilot
Assembly Version: 1.1.5901.24775
Win32 Version: 1.1.5901.24775
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/vPilot.exe
----------------------------------------
Ninject
Assembly Version: 3.2.0.0
Win32 Version: 3.2.2.0
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/Ninject.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
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.8690 (QFE.050727-8600)
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.8681 (QFE.050727-8600)
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.8693 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8689 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/mscorlib/2.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8679 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
protobuf-net
Assembly Version: 2.0.0.640
Win32 Version: 2.0.0.640
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/protobuf-net.DLL
----------------------------------------
w1_kxwai
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
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.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
hiy9thg2
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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
----------------------------------------
SharpDX.DirectInput
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/SharpDX.DirectInput.DLL
----------------------------------------
SharpDX
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3
CodeBase: file:///C:/Users/rabulafia/AppData/Local/vPilot/SharpDX.DLL
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
bmeljsgb
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.9193
Win32 Version: 8.00.50727.9193
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd/msvcm80.dll
----------------------------------------
hkb_njzl
Assembly Version: 1.1.5901.24775
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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.


Thanks for the help
cheers
By Walter Anderson 1344316
#502090 I had the same issue and did this - reinstall sim connect going to the steam/steamapps/common/fsx/sdk/core utilities kit/simconnect sdk/legacyinterfaces/ and then click on each folder and run the msi setup to each folder fsx-rtm, fsx-sp1, fsx-xpack

it works solid now. Also use ccleaner from piriform.com , and malwarebyte.org to check your system