SimForums.com Homepage
Forum Home Forum Home > Flight One Partner Forums > Opus Software
  New Posts New Posts RSS Feed - Issue starting Opus FSX
  FAQ FAQ  Forum Search   Register Register  Login Login

Issue starting Opus FSX

 Post Reply Post Reply
Author
Message
scottharmes6 View Drop Down
New Member
New Member


Joined: November-24-2012
Location: Melbourne
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote scottharmes6 Quote  Post ReplyReply Direct Link To This Post Topic: Issue starting Opus FSX
    Posted: October-05-2017 at 4:17am
Hi.  I have been having issues with Opus FSX, and am at a loss about what is happening in the background.

I am seeing the following when trying to start the Opus FSX Server:



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

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'bd' threw an exception. ---> System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at bd..cctor()
   --- End of inner exception stack trace ---
   at bd.f()
   at bn.v(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(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.WmShowWindow(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.8762 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FSXSERVER
    Assembly Version: 3.5.5.2
    Win32 Version: 3.5.5.2
    CodeBase: file:///C:/OpusFSX/FSXSERVER.EXE
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (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.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
FSXSYSTEM
    Assembly Version: 3.5.5.2
    Win32 Version: 3.5.5.2
    CodeBase: file:///C:/OpusFSX/FSXSYSTEM.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.6195
    Win32 Version: 8.00.50727.6195
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/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.


If I continue I get the following:





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

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at am.b()
   at y.q()
   at bn.t(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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.8762 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FSXSERVER
    Assembly Version: 3.5.5.2
    Win32 Version: 3.5.5.2
    CodeBase: file:///C:/OpusFSX/FSXSERVER.EXE
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (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.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
FSXSYSTEM
    Assembly Version: 3.5.5.2
    Win32 Version: 3.5.5.2
    CodeBase: file:///C:/OpusFSX/FSXSYSTEM.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.6195
    Win32 Version: 8.00.50727.6195
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.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
----------------------------------------

************** 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 any information.

 

Cheers,

 

Scott




Scott
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13053
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 4:25am
The type initialisation error indicates no SimConnect libraries installed (see our FAQs). Use our SimConnect msi file to install SimConnect on your system and all should be ok.

Stephen
Back to Top
scottharmes6 View Drop Down
New Member
New Member


Joined: November-24-2012
Location: Melbourne
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote scottharmes6 Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 7:14am
Thanks for the quick reply.  Unfortunately it's not that simple.  There seems to be a conflict with something related to runtime C++ libraries.  I have discovered I get the above errors if I disable the MSVCR90.dll which is located in:

 "C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57"

I did so because P3D V3 started crashing with that faulting module while using another addon (TFDi 717).

Is there some reason that Opus FSX is dependant on this module in particular?  Uninstalling and reinstalling required C++ runtimes hasn't helped so far and in fact I can't even find a package which installs this particular module mentioned above.

If I turn this dll on Opus FSX is fine, but the 717 causes a CTD.  If I turn this dll off the 717 is fine but Opus FSX (and Intel Rapid Storage) fail to start.

Cheers,

Scott
Scott
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13053
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 7:58am
OpusFSX is not intended for P3Dv4 as it was developed years ago for dotnet2 FSX and P3Dv1.
It was also developed on the former VS and so may not compatible with the latest VS runtime.

OpusFSI v5 is the product intended for later versions of P3D including the latest v4 sim.

Stephen
Back to Top
scottharmes6 View Drop Down
New Member
New Member


Joined: November-24-2012
Location: Melbourne
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote scottharmes6 Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 8:37am
 I have only been using Opus FSX with FSX and P3D V3, and it has always worked well in the past.  In fact the issue I am having wasn't directly related to Opus FSX initially, I was more just looking for some clue on why disabling the mentioned C++ library dll causes this issue with Opus FSX.  As I said above I disabled that dll and basically caused the issue with Opus FSX, but I'm just trying to troubleshoot and understand why that particular dll is causing so many issues.

I definitely will be getting the latest Opus FSI for use with P3D V4.

Cheers,

Scott
Scott
Back to Top
Opus Software View Drop Down
Senior Member
Senior Member


Joined: April-12-2012
Location: Grantham, UK
Points: 13053
Post Options Post Options   Thanks (0) Thanks(0)   Quote Opus Software Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 8:51am
Hi Scott, as you’ve discovered the DLL in question is needed as it contains all the windows runtime goodies. I believe there may also be a copy supplied in the OpusFSX folder unless it wasn’t included until OpusFSI. OpusFSI v5 is much better with all later versions of P3D. The OpusFSX has probably worked (not as well) due to opus only using standard SimConnect and FSUIPC external program interfaces.

Regards
Stephen
Back to Top
scottharmes6 View Drop Down
New Member
New Member


Joined: November-24-2012
Location: Melbourne
Points: 15
Post Options Post Options   Thanks (0) Thanks(0)   Quote scottharmes6 Quote  Post ReplyReply Direct Link To This Post Posted: October-05-2017 at 8:54am
OK.  Sounds good.  Thanks for the quick replies and all the info Stephen.

Cheers,

Scott
Scott
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.10
Copyright ©2001-2017 Web Wiz Ltd.

This page was generated in 0.188 seconds.