OpusFSI Flight Simulator Interface for and

OpusFSI_v5_Overview OpusFSI_v5_User_Guide OpusFSI_v5_Getting_Started_Single_PC OpusFSI_v5_Getting_Started_Networked_PCs OpusFSI_v5_Live_Weather OpusFSI_v5_Live_Camera OpusFSI_v5_ButtKicker

OpusFSI Flight Simulator Interface for FSX & Prepar3D

Getting Started - Single PC

11 Jan 2022

Opus Software Limited

Email: opusfsi@opussoftware.co.uk Website: www.opussoftware.co.uk/opusfsi.htm

Contents

System Requirements. 2

Software Installation. 2

Create Desktop Shortcuts. 3

Sharing and Permissions. 4

Installation Log File.

Error Messages. 4

Initial Set Up and Configuration. 5

Starting the OpusFSI Software Automatically with FSX and P3D.. 9

Operating System Recommendations

Simulator Recommendations

FSX Steam Edition Recommendations

Prepar3D Recommendations

FSX Computer System Settings. 10

SimObject Path Additions

Ensuring AI Traffic use the Correct Runway

FSUIPC Settings. 11

TrackIR Settings. 11

Using FS2Crew with OpusFSI. 13

Using ActiveSky with OpusFSI. 13

Uninstalling OpusFSI

FAQ and Troubleshooting. 13

System Requirements

·         Microsoft Simulator X (with SP2 or Acceleration Pack), or FSX Steam Edition, or Lockheed Martin Prepar3D simulator.

·         Windows 11/10/8/7/XP/Vista (32 or 64-bit version) operating systems.

·         Microsoft .NET Framework v2 (for FSX/Steam and P3D up to and including v3.3) or .NET Framework v4 for P3Dv3.4 onwards.

·         FSUIPC (see note below).

·         90 MB hard disk space.

You need FSX/P3D, Microsoft .NET v2 (v4 for P3Dv3.4 onwards) and SimConnect to be installed on your server (and optional client) systems for OpusFSI to work.

Microsoft.NET

You can check what versions of .NET you have installed in Control Panel by selecting Settings, System, Apps and features, then search for .NET and a list of installed versions will be displayed. For older operating systems check your c:\Windows\Microsoft.NET\Framework or Framework64 folders. You should see a v2.0.xxxxx folder in addition to the v4.0.xxxxx folder etc..

FSUIPC

FSUIPC is required on the FSI SERVER system. FSUIPC is required on Live View clients that are used to display camera views.

You can download a free copy from http://www.fsuipc.com

SimConnect

In the case of SimConnect, first make sure you have installed FSX or P3D along with its SP2, or installed the FSX Acceleration version, SimConnect is installed automatically with it.

If you have mislaid or corrupted your SimConnect then you can try re-installing it.

For FSX/Steam and P3D up to P3Dv3.3 inclusive

Run the Microsoft.FlightSimulator.SimConnect.msi file within your OpusFSI_v5 folder. This msi is the former standard dotNet 2 variety which can be used with all dotNet2 sim types and versions. This is used in our v5 software whenever you run the software selecting the dotNet 2 SlimDX and SimConnect mode ...

FSISERVER.EXE FSX
FSISERVER.EXE STEAM
FSISERVER.EXE P3D2

FSISERVER.EXE P3D30

FSISERVER.EXE P3D31

FSISERVER.EXE P3D32

FSISERVER.EXE P3D33

For P3Dv3.4 onwards

The FSISERVER and FSICLIENT startup programs will copy and rename the supplied LockheedMartin.Prepar3D.SimConnect_v3.4.dll into the required LockheedMartin.Prepar3D.SimConnect.dll (in OpusFSI_v5) whenever appropriate and the LM SimConnect dll does not exist.

The following will select the dotNet 4 SlimDX and SimConnect modes ...

FSISERVER.EXE P3D
FSISERVER.EXE P3D3

FSISERVER.EXE P3D34

FSISERVER.EXE P3D4

FSISERVER.EXE P3D45

There is a distinction between the latest Prepar3D v4.5 mode and earlier Prepar3D v4.x modes (refer to OpusFSI_Release_Notes.txt) so you should specify P3D41 through to P3D44 explicitly when using these versions. Note, specifying any combination of P3D, P3D4 or P3D45 and above will select the latest Prepar3D v4.5 mode of operation.

If for any reason Opus is blocked from automatically copying these dlls then you can do it manually. We supply SimConnect_v3.4 dll variants. You should copy (to OpusFSI_v5) and rename (to LockheedMartin.Prepar3D.SimConnect.dll) to the v3.4 variant.

Similarly for SlimDX we supply SlimDX2.dll and SlimDX4.dll which may be copied manually to OpusFSI_v5\SlimDX.dll if Opus is blocked from doing so.

Any other argument will assume the last saved operating mode for the FSISERVER and FSICLIENT programs.

Windows problem running msi files fix ...

To run a msi that doesn’t have a valid Digital signature follow one of the methods mentioned below.

Method 1:
1. Right click on the file or program that you are not able to access.
2. Go to properties and click “Unblock”.
3. Try to run the application again.

Method 2:
1. Click on start button.
2. Type “Internet Explorer” in the “Start Search Box” and select it from the menu.
3. Click on “Tools” in the menu bar and select “Internet Options”.
4. Click on “Advanced tab” and locate “Allow software to run or install even if the signature is invalid” under the “Security” category and check the box.
5. Click Apply and then Ok.
6. Close the Internet Explorer and restart Internet Explorer.

Method 3:
1. Turn UAC OFF. Just type UAC into the start menu or Control Panel search box. Drag the slider to the bottom, never notify.
2. Run the Command Prompt in Admin Mode (not the same as you being an Admin user).
3. Type: bcdedit /set testsigning off
4. Reboot. Windows will power up in a test mode and will allow you to run any msi file.
5. Install the msi file. After installing the software ...
6. Run the Command Prompt in Admin Mode (not the same as you being an Admin user).
7. Type: bcdedit /set testsigning on
8. Reboot
After rebooting you should still be able to run msi files but may need to answer 'More Info' and 'Yes' to a Windows user query.

Software Installation

Ensure Microsoft .NET v2 (if using FSX/Steam or up to P3Dv3.3), Microsoft .NET v4 (if using P3Dv3.4 onwards), SimConnect and FSUIPC are installed on your PC.

Installing the Demo version of OpusFSI

1. Click on the OpusFSI_v5 Demo or Upgrade button on our downloads webpage and download (save) the OpusFSI_v5.msi file.

2. Double click on the downloaded OpusFSI_v5.msi file and follow the instructions to install the software into the standard OpusFSI_v5 directory. You may install the software onto any drive provided its folder name is OpusFSI_v5 with the exception that you must not install OpusFSI_v5 in the Opus Software, FSX, Prepar3D or Program Files folders, and don't install in more than one folder on your PC.

Note that in Demo mode the Live Weather Engine is restricted to 160km (100 miles) in all directions and weather updating only whilst your aircraft is on the ground. Also World Weather Themes are not accessible in demo mode. Demonstration mode will run for 15 minutes with a minimum 2 minute interval required between runs.

Purchasing OpusFSI

1. Click on the Purchase OpusFSI_v5 button on our downloads webpage and download (save) the OpusFSI_v5_Flight1_Purchase.exe file.

If you get a warning the signature is invalid then right click on the msi and select Run Anyway.

You may get some warning messages from your virus checker at this point which is quite normal for this file type and as a result the installation window may be hidden behind your browser window. You may need to stop your virus checker if it automatically deletes the msi or the exe files.

If you see the following screen then click on the More info button to run the software. Next select Run Anyway.

Using Windows Explorer navigate to the location of the downloaded file and run the software. If you have a problem running the software then right click on the file and click “Unblock".

2. If you have previously installed the Demo then uninstall it via Control Panel, Uninstall a program. Do not delete your OpusFSI_v5 folder containing your camera and system configuration files.

3. Run the OpusFSI_v5_Flight1_Purchase.exe file. A Flight1 form with 3 buttons will be displayed. If you already have a Flight1 account click button 1 to log in (this is optional and if you get any Flight1 login error messages don't use it). Click on buttons 2 and 3 to fill in your purchase details and then the Purchase button will appear, click on this button to complete purchase.

4. You will now find the OpusFSI_v5.msi installation file in your 'unwrapped' C:\Opus Software folder. N.B. You need to keep your Flight1 key and licence files on drive C in the C:\Opus Software folder but can move the msi file to another drive.

Double click on the OpusFSI_v5.msi file and follow the instructions to install the software into the OpusFSI_v5 directory. You may install the software onto any drive provided its folder name is OpusFSI_v5 with the exception that you must not install OpusFSI in the Opus Software, FSX or Program Files folders, and don't install in more than one folder on your PC.

Upgrading OpusFSI

1. Click on the OpusFSI_v5 Demo or Upgrade link on our downloads webpage and download (save) the OpusFSI_v5.msi file.

2. Do not delete your OpusFSI_v5 folder. Double click on the OpusFSI_v5.msi file and follow the instructions to install the software. All your original configuration (DAT and CMD) and camera definition (CAM, LIM and CDF) files will remain intact (in the OpusFSI_v5 folder) but it is a good idea to take a backup of your camera files anyway in case they get corrupted (this may happen when you revert to a previous version with a different CAM format).

Installing the Beta version of OpusFSI

1. Click on the OpusFSI_v5 Beta link on our downloads webpage and download (save) the OpusFSI_v5.msi file.

2. Double click on the downloaded OpusFSI_v5.msi file and follow the instructions to install the software into the standard OpusFSI_v5 directory. You may install the software onto any drive provided its folder name is OpusFSI_v5 with the exception that you must not install OpusFSI in the Opus Software, FSX, Prepar3D or Program Files folders, and don't install in more than one folder on your PC.

Create Desktop Shortcuts

After installing the software we recommend you create a shortcut on your desktop for the server program. This shortcut will allow you to manually start your sim system without too much fuss.

1. In Windows Explorer, navigate to your installation folder (OpusFSI_v5) and right-click on the FSISERVER.EXE program.

2. Select the Send to - Desktop (create shortcut) option.

3. Right-click on the new desktop icon, select Properties, in the Shortcut tab check the program is configured to Start In: your installation folder (c:\OpusFSI_v5). Select the Compatibility tab (if available) and tick the checkbox to Run this program as an Administrator.

4. Left click on the icon once to select it and then left click again to select the icon name, type in OpusFSI_v5 SERVER to rename the icon.

You will find alternative program icons in the OpusFSI_v5 installation folder should you wish to change the existing icon.

Automatically Selecting the Simulator Type

The FSISERVER program will accept an optional argument to automatically select the simulator type when it runs.

FSISERVER.EXE FSX

FSISERVER.EXE STEAM

FSISERVER.EXE P3D

FSISERVER.EXE P3D2

FSISERVER.EXE P3D3 (or P3D30, P3D31, P3D32, P3D33, P3D3, P3D34)

FSISERVER.EXE P3D4 (or P3D40, P3D41, P3D42, P3D43, P3D44, P3D45)

So if you have FSX, FSX Steam Edition and/or P3D you can create desktop shortcuts, one running 'c:\OpusFSI_v5\FSISERVER.EXE FSX' for Microsoft FSX, one running 'c:\OpusFSI_v5\FSISERVER.EXE STEAM' for FSX Steam Edition, and the other running 'c:\OpusFSI_v5\FSISERVER.EXE P3D' for the latest version of Lockheed Martin Prepar3D (use the other arguments listed above for specific versions of P3D).

Note, specifying any combination of P3D, P3D4 or P3D45 and above will select the latest Prepar3D v4.5 mode of operation.

The FSICLIENT program will accept an optional argument NONE to select a No Connection To Simulator type for the FSICLIENT and activate the dotNet 4 client program.

Automatically Selecting an Optional User Configuration File

The FSISERVER.EXE and FSICLIENT.EXE start up programs accept an optional User CFG Filename as a program argument. This argument can be specified before or after the sim type argument. When specified the User CFG File will replace the current FSISERVER.CFG or FSICLIENT.CFG file. This option allows you to create various OpusFSI server and client configurations. The configurations can be specific to different sim versions for example, or different flight modes (e.g. the preferred weather options for VFR flying etc.).

To create a new configuration simply edit the options in OpusFSI, quit OpusFSI, then copy/rename the current CFG file as appropriate, finally append the name of your CFG file to the start up program. You can create various Desktop Shortcuts which utilise your various User CFG Filenames.

Sharing and Security Permissions

Firewall

You may need to allow OpusFSI through your firewall. In Control Panel select System and Security, Windows Firewall, Allow a Program or feature through Windows Firewall. Click on Allow another program and browse to FSXSERVER/P3DSERVER (or FSXCLIENT/P3DCLIENT on a client PC) in the OpusFSI_v5 installation folder.

Sharing

You may need to set sharing and security permissions on both your OpusFSI_v5 and on your FSX (or Prepar3D) folder in order for OpusFSI to write the necessary weather files into the FSX\Weather\themes (or Prepar3D\Weather\themes) folder. This is usually necessary if you have installed the simulator in the Program Files folder, for this reason it is advisable to install FSX in a folder outside Program Files. If this does not work then set sharing and security permissions on your whole drive. Be aware that if you set permissions and sharing on the whole drive then you may have different permissions and sharing on subfolders so make sure you check the OpusFSI_v5 and FSX\Weather\themes (or Prepar3D\Weather\themes) folders. Also ensure the folders are not set to 'read only'.

Absolute worst case, just install FSX or Prepar3D in its own folder (e.g. d:\Prepar3D), moving outside the secured Program Files folder. If OpusFSI still doesn't work correctly after setting sharing and permissions a re-install may be necessary.

To set up Sharing on a folder/drive run Windows Explorer, right click on the folder/drive you wish to share, select Properties, select the Sharing tab, select Advanced Sharing, tick the checkbox to share the drive and enter a share name, make sure you use the single letter code, e.g. C, not 'Drive C' for instance. Click on Permissions, enter Everyone in the Group or user names box and tick the checkboxes to allow Full Control for Everyone.

Security

To set up Security Permissions run Windows Explorer, right click on the folder/drive you wish to set Security settings for, select Properties, select the Security tab, select Everyone in the Group or user names box and ensure the Permissions are Full Control, if not click on the Edit button and tick the Permissions checkboxes to allow Full Control for Everyone. If Everyone does not exist click Advanced, click Change Permissions, click Add, type in the name Everyone and click OK. Then specify Full Control for your newly created Everyone group. Click OK.

Also select Authenticated Users in the Group or user names box and tick the checkboxes to allow Full Control.

Installation Log File

The SERVER program will create a FSISERVER.log file in the OpusFSI_v5 installation folder which will be automatically displayed if any installation errors are detected.

The log file includes installation details along with any installation errors that are detected when the program is activated. Refer to this file and send it to Opus Software if there are any problems encountered when running the software.

Example content of the \OpusFSI_v5\FSISERVER.log file ...

OpusFSI Flight Simulator Interface

Log Generated 09 May 2019, 09:39 Hrs

Installed Folder: C:\OPUSFSI_V5

FSICONFIG Sim Folder: E:\Prepar3D v4
FSICONFIG Sim Folder: OK
FSITHEMES Initialise: C:\OPUSFSI_V5\Weather\OpusWeather.WTB
FSIGENCOM Initialise: OK
FSIGENCOM Validation: OK

Data Download ...
Data Download Initiated
Data Download Completed
Data Download Checked
Data Download Validated

Invoking DLL Checks ...

No DLL Errors Detected.

Licence Files:

OpusFSI v5 : 28 April 2019

Installed Files:

FSISERVER.EXE Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
P3DSERVER.EXE Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
FSXSERVER.EXE Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
FSDECODER.EXE Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
FSISYSTEM.DLL Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
OPUSFSI.DLL Version: 5.2.6.0 , 09 May 2019, 08:53 Hrs
OPUS.DLL Version: Correct , 29 October 2012, 18:24 Hrs
OPUS.DLL Version: Correct , 29 October 2012, 18:24 Hrs

Error Messages

OpusFSI tries to copy the OpusWeather.WT weather file into the FSX\Weather\themes (or Prepar3D\Weather\themes) folder and will display this error message if it cannot do this.

If you see the above error message then it is essential that you check your installation folder is specified correctly in the Configuration dialog. Try reconfiguring the sim location again. If the dialog to enter the sim location does not appear then check it is not hidden behind another window and also ensure OpusFSI is set to Run as Administrator.

Also check your sharing and permissions, it is important to set permissions as well as sharing as described in the section above.

System.TypeInitialisationException error

You need .NET version 4 for P3Dv3.4 onwards (or .NET version 2 for FSX, P3D before P3Dv3.4) and SimConnect to be installed for OpusFSI and its SimConnect links to work.

You can check what versions of .NET you have installed in Control Panel by selecting Settings, System, Apps and features, then search for .NET and a list of installed versions will be displayed. For older operating systems you can check what versions of .NET you have installed by checking your c:\Windows\Microsoft.NET\Framework or Framework64 folders. You should see a v2.0.xxxxx folder in addition to the v4.0.xxxxx folder.

In the case of SimConnect, first make sure you have installed FSX or P3D along with its SP2 or installed the FSX Acceleration version, SimConnect is installed automatically with it. If you have mislaid or corrupted your SimConnect then you can try re-installing it for FSX or P3D (prior to P3Dv3.4) using the Microsoft.FlightSimulator.SimConnect.msi file within your OpusFSI_v5 folder. For P3Dv3.4 onwards we supply SimConnect_v3.4 dll. Copy and rename (to OpusFSI_v5 folder) if that is needed, otherwise the FSI startup program will copy and rename the v3.4 dll automatically when no LM dll exists. Alternatively use the FSISERVER.EXE program argument P3D33, P3D32, P3D31, P3D30, or P3D2. The FSISERVER program arguments P3D (or P3D4, P3D3, P3D34) select the .NETv4 variant of SimConnect and SlimDX .

SlimDX error

Do not run P3DSERVER.EXE or FSXSERVER.EXE directly, instead run the FSISERVER.EXE program with the correct argument for your sim type.

If you still have problems you must ensure the FSISERVER program ...

Is starting in the correct c:\OpusFSI_v5 folder.

Has permissions to copy and rename the relevant SlimDX DLL file.

Is able to copy the current SlimDX DLL, it's not locked or write protected.

Is not blocked by AV or Win Defender software.

Otherwise its attempt to copy and rename the SlimDX file will fail. You may also need to install the SlimDX dotNet 2 or 4 runtime using our supplied msi file in the OpusFSI_v5 folder.

OpusFSI won't run in Windows 10

If you have set up the security and sharing permissions as described in the above section, have run as Administrator, and the software still won't run on Windows10 then run the Microsoft vcredist_x86.exe VC redistribution package located in the OpusFSI_v5 folder.

Initial Set Up and Configuration

Run the SERVER program on your FSX/Prepar3D system.

The SERVER program MUST be started in its local installation folder, in other words it MUST be started in OpusFSI_v5.

N.B. Do not run the CLIENT program on your server PC since it will cause the sim to freeze, it is only used on networked client PCs.

You do not need to run the flight simulator at this time since we are just going to configure the system.

Click on the Configure button to display the 'OpusFSI Server - Configuration' dialog.

OpusFSI Server Form

Figure 1 - FSI Server's Main Form

OpusFSI Server Configure dialog

Figure 2 - FSI P3D and FSX/Steam Server Configuration Dialogs

The number of (Live View) client computers should be configured to zero.

Live Traffic displays local traffic on the LWA Map and may be configured within 32km (20 miles) to 192km (120 miles) of your aircraft.

Enable Live Weather Engine if required.

Enable Live Camera unless you want to control the views manually manually using Live Camera Control and use General DHM Options.

Enable the CPFlight driver if you have a CPFlight MCP737/EFIS panel and specify a COM port.

If you enable TrackIR please refer to the TrackIR section of this document for important initial set up and configuration details.

The Live View Scan Rate (0 to 60ms) adjustment is for networked systems and controls the position update rate communicated to the server enabling you to match the preferred rate found using the Live View Test.

Click on the Browse button and locate your simulator installation folder. N.B. Any time you change this folder location you must restart the SERVER program. If you fail to do this correctly you will be unable to select and activate any dynamic weather or weather themes.

If you are using Prepar3D then select the P3D Version from the dropdown box and enable the Prepar3D PDK Interface to provide a more efficient Live Camera, Live Camera Control, and DHM eye point control. Refer to the OpusFSI_v5/OpusPDK_Setup text file to set up the Prepar3D OpusPDK interface. If you encounter problems (errors in the Spy window) then you can disable the PDK. The PDK is not applicable and automatically disabled for P3Dv4.

Close OpusFSI.

Run FSX/P3D.

Run OpusFSI.

Weather

Click the Weather button on the server's form and set your Destination and Max Cruise Altitude if known, no need to set anything else unless you wish to tweak the settings.

OpusFSI Server Weather dialog

Figure 3 - FSI Server's Weather Options Dialog

Click OK, and you are ready to fly.

For further details please refer to the OpusFSI_v5_Live_Weather pdf guide which can be found in the OpusFSI_v5 installation folder, also available from our download page.

Cameras

Please refer to the OpusFSI_v5_Live_Camera pdf guide which can be found in the OpusFSI_v5 installation folder, also available from our download page.

Spy

If you run the simulator in windowed mode you can click on the OpusFSI server program's Spy button and monitor its progress. If you have enabled Dynamic Weather then you should witness the server programming initiating the live weather METAR download culminating in creating and updating the Dynamic Weather.

The Options button provides the means to specify the form's topmost, opacity, and font settings. The window can be resized.The Spy window is automatically cleared after ten minutes.

Spy indicates what joystick numbers have been mapped to each controller device. The button events within the Spy window will also indicate what physical device is currently mapped to the simulator's joystick number. The joystick order should match the controller order within the simulator's Controls Settings. If they don't then you can change the order via the Remap Joystick Numbers button in the Config dialog.