FAQ

---

We have listed some frequently asked questions and replies about your experience with OpusFSX.

If you have any queries then we will be very pleased to hear from you. Please email us at opusfsi@opussoftware.co.uk including details of your operating system.

Can I use other software packages with OpusFSX?

We strongly recommend the use of 3rd party packages such as REX, ASE, or FEX for their high-definition sky and cloud textures. You will really see the benefit of using the OpusFSX Live Weather Engine with these high-def textures loaded. In our opinion, the OpusFSX weather engine is far superior to any other weather engine on the market for all the same reasons we have pointed out on our web site and in the manual. But we do not include or load any sky and cloud textures at all, we just create and load the most detailed and realistic weather. However, if you rely on the default sky and cloud textures within FSX/P3D then no matter how detailed the weather is it will not look very impressive. Disable the weather update in these 3rd party packages and use the OpusFSX weather engine.
We would also recommend the use of Accu-Feel for sounds but with the Accu-Feel aircraft movement options disabled, use OpusFSX Dynamic Head Movement instead.
TrackIR interfaces with OpusFSX but you must follow the set up instructions in the Getting Started guide.

Installation

System.TypeInitialisationException error

You need Microsoft.NET version 2 and SimConnect to be installed for OpusFSX and its SimConnect links to work.

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 usually installed automatically with it. If you have mislaid or corrupted your SimConnect then you can try re-installing it using the SimConnect.msi file within your c:\OpusFSX folder.

Spy error messages

FSX Failed to establish link 1 with FSX
Error HRESULT E_FAIL has been returned from a call to a COM component.

This usually does not indicate a serious error, it usually means FSX is not running and hence, the software cannot connect to SimConnect. If you are running FSX it could mean you do not have SimConnect installed, or SimConnect is not functioning correctly.

You must have FSX installed on the main 'flying' server and each client computer system. You should also install the same scenery and aircraft addon packages. The aircraft addon packages need only be installed however if you want to use external 'aircraft' views on the client system. If this happens to be one particular client PC or laptop then install the aircraft addon just on that machine.

Note, you do not need to run FSX if you just wish to test the network connections or set up the FSXSERVER and FSXCLIENT programs.

Failed to establish link with FSUIPC
Error code 8

Error code 8 means you have the wrong Flight Simulator system for FSUIPC4. Have you selected the correct simulator (FSX or P3D) in the OpusFSX configuration dialog and located its installation folder. If you have not then OpusFSX will be trying to connect to the wrong sim type!

Unable to load fsgencom.dll

System.DllNotFoundException: Unable to load DLL 'fsgencom.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at FSSYSTEM.FSGencom.fsgencom_init()
at FSSYSTEM.FSGencom.Gencom_Init(UInt16 taskID) ...

This error implies a Windows DLL is missing. The most common cause is a missing or corrupt msvcr100.dll (Microsoft Visual C Runtime import library). First check using Windows Explorer if the following library file is present,

c:\Windows\System32\msvcr100.dll on 32-bit operating systems
c:\Windows\SysWOW64\msvcr100.dll on 64-bit operating systems

If it is missing (or corrupt) you will find a copy in the c:\OpusFSX installation folder labelled MSVCR100_x32.DLL. You should copy and rename this file to one of the above folders, rename by removing the '_x32' suffix. Alternatively, you can simply rename the file in the c:\OpusFSX folder and leave it there since this will be the first place Windows will look for it unless you have not started the program in its installation folder.

If this does not rectify the problem download the x86 Dependency Walker program from the Dependency Walker website http://www.dependencywalker.com. Unzip the file into any directory and run the depends.exe program. Open the c:\OpusFSX\FSGENCOM.DLL library file, all missing library files will be highlighted with a yellow question mark in the bottom files window. You can ignore the reference to the IESHIMS.DLL file, this is an Internet Explorer library that is delay loaded and in fact not needed.

The master battery and parking brake indications aren't correct

You need to install FSUIPC4 on the OpusFSX server and client PCs. You can download a free copy from http://www.schiratti.com/dowson.html. FSUIPC4 is used for the following functions;
reading the sim clock, master battery and parking brake, and pausing the sim.

Weather

I see horizontal 'bands' of haze with clear areas between

This is a known issue with 3rd party weather engines, just use 3rd party weather engines for the textures and use OpusFSX for the weather updates. Make sure you have disabled your 3rd party weather engines and in addition disabled/removed all their visibility, haze and fog effects.

I get a consistent static cloud layer that forms above the aircraft

This is not an OpusFSX problem, we have just provided a solution to a problem that occasionally occurs on some systems due to a corrupt or faulty cirrus overcast bitmap mask file in the FSX/P3D Texture folder. If your system has a faulty bitmap file it will be quite obvious, there will be a thick cloud hovering above you wherever you fly. If your system suffers from this problem then please follow the instructions below for the cure.

Make sure you have disabled your 3rd party weather engines and in addition disabled/removed all their visibility, haze and fog effects. You must replace the cirrus_overcast03.bmp file within your flight simulator's Texture folder as follows,
1. Navigate to your simulator's texture folder, either <FSX>\Texture or <Prepar3D>\Texture
2. Rename your cirrus_overcast03.bmp file to cirrus_overcast03_foggy.bmp.
3. Truncate our cirrus_overcast03_Opus_1024.bmp filename to cirrus_overcast03.bmp.
4. Restart your FSX or P3D simulator.
If you still have problems then repeat the above exercise using our 512 bitmap.

I tried importing METAR data from a user specified import file but it didn't work.

METARs are specific to a location unless you use the GLOB ICAO code which is global. If you use a METAR for a specific station and try to import it when you are outside the 480km x480km area of the weather region then the Live Weather Engine will not accept the report since the met station is not within your area. Best change the ICAO code to GLOB and import that. The met station must also coincide with one used within FSX so that OpusFSX, which has a list of all valid FSX met stations, can identify its lat/long coordinates, and hence its location relative to your aircraft's current location.

Unable to view Live Weather or "Unable To Update Dynamic Weather " spy message

This error most likely results from a failure to copy the generated weather OpusWeather.WTB file. The software needs to copy this from ... c:\OpusFSX\Themes\OpusWeather.WTB to ... <fsx_install_folder>\Weather\Themes\OpusWeather.WTB

So, you have either,
not specified the FSX option and identified your FSX installation folder correctly within the OpusFSX Configuration dialog,
or,
your system does not have sharing enabled, or security and permissions set to allow OpusFSX to write to the FSX installation folder.

You can check the first by confirming there is a Weather\themes sub-folder.

You can check the second using the Command Prompt, navigating to c:\OpusFSX\Themes and trying to manually copy the file. Perhaps you have installed FSX in the Program Files folder and there is no sharing or access rights to this folder. Refer to our OpusFSX_Getting_Started guide for details on how to set up sharing and security permissions.

Live Camera

The camera dialog only lists "All aircraft types" or DHM doesn't work

Right click on the your OpusFSX SERVER desktop shortcut icon (C:\OpusFSX\FSXSERVER.EXE) and select Properties, select the Compatibility tab, tick the checkbox to "Run as Administrator". Also set this option for FSXCLIENT.EXE on your optional client PCs.

TrackIR doesn't work or DHM is jerky

You must follow the setup instructions in the Getting Started guide.

What views can I see on the server and client computers ?

You can display any interior (cockpit), exterior (scenic), or external (aircraft) views on the
main 'flying' server system. You can only display exterior (scenic), or external (aircraft) views on the secondary client systems. You cannot control the aircraft by displaying panels such as CDUs or GPS on the client systems - these are non flying slaves.

On networked systems, the main 'flying' server PC operates the same as it would on a standalone, single PC, system, providing the same assortment of interior (cockpit), exterior (scenic), and external (aircraft) views; and hence, provides the means to monitor and control the aircraft and its systems. In addition, the Live View and Live Camera networked links with the secondary client systems (PCs or Laptops) allows a variety of exterior (scenic) and external (aircraft) client system views to be created and controlled. If desired, a number of exterior views can be used on a networked multi-screened system to create a panoramic vista. All views are created and controlled centrally from the server system.

On networked systems, the Live View connections automatically synchronize the aircraft's current position, attitude, flaps, gear and lighting configuration, and simulator's date/time, along with either your chosen weather theme or the full METAR weather for the surrounding area.

OpusFSX version 1.40 supports Windowed Views on the server and all client systems. These additional views are ideal for multi-screened PCs as well as single large screen displays. All windowed views can be positioned and sized according to your needs. Version 1.41 allows you to position and size the windowed views automatically.

Can I create an Instrument Panel view ?

Yes, but only on the main 'flying' server machine, and you will need OpusFSX version 1.40 onwards.

First create a windowed view associated with the aircraft type on your main 'flying' server. 
Select virtual or 2d cockpit view.
Tick the Windowed View checkbox.
Adjust the viewpoint (x,y,z,pitch and yaw) to centre the view on the required instrument panel. You can adjust the z axis to move the eyepoint in as close as you want. 
Save the camera views and reload the aircraft type to force FSX to reload the aircraft.cfg file.

Your new windowed view should be on display, you can now position your window. From version 1.41 you will be able to click on the Save Views button to save the position and size of your window.

Networked Systems

Can I use a Wifi network ?

Yes you can, however you should note that a direct WiFi link is only going to give you 54Mbps and a redirected link will operate at about 16 to 24Mbps. This may be faster than an ancient 1990s 10base-T network running at 10Mbps but nowadays everyone uses either 100Base-TX (100 Mbps) or a 1000Base-T gigabit LAN running at 1000Mbps (1Gbps). The modern cabled LANs are going to operate up to 64 times faster than the WiFi link!

However, if you must use a WiFi link (no LAN ports or Cat5 cable) then just make sure all the computer systems have the same workgroup set (Control Panel - System and Security - System - Change Settings - Change...) and configure the main server's computer name into the FSXCLIENT programs. You will find the link works perfectly well with perhaps a few tiny jitters when taking off or flying fast and low (depends how good or busy your WiFi link is).

How do I set up the network ?

Please refer to the latest OpusFSX Getting Started guide, the pdf is available from our Home and Downloads pages. This guide provides detailed instructions and guidelines to assist you in setting up your network for the default IPC (Inter Process Communication) links.

If you have problems on the network and are using Computer Names in the configuration then try using IP addresses and vice versa.

"Unable to transfer camera configuration data across to system <client_name>" message

You must set up your drive sharing, security, permissions etc. as described in the Getting Started guide so that the server and client systems can access each other BOTH ways. You will find your configured camera definition files for your client systems stored in the c:\OpusFSX installation folder on your server system, they are named < CLIENTNAME>.CAM

My client system lags behind the server

The lag indicates the clients cannot keep up with the updates. The programs have 32K buffers for both receive and transmit over each IPC link, hence the possible back log. If this does happen, simply pause the main system using the 'P' key, let everything catch up and then unpause. But if your system is set up correctly it should be able to cope with the throughput. 

Start up all the client FSX systems and the server FSX so that they are all up and running. Then start the FSXSERVER program, let it settle, then each of the FSXCLIENT programs. Once they connect their FSXs will normally reload to the new location, they will also resync after receiving their first weather update (necessary to ensure correct cloud sync). Once all the client systems are settled then you can force another weather update just before takeoff to make sure all is well and then you are ready to go. Please refer to the recommended start up procedures in the Getting Started guides.

It is very important to set up your client systems as per the Getting Started guides to optimise your client systems, this can have a dramatic impact on the performance. It also helps if you are displaying scenic views to select one of the simple FSX stock aircraft ( e.g. the C172 or B737), some people even use a dummy aircraft that has zero overheads. You may also try adjusting the target frames rates, either Unlimited or on slower systems you could even set 20 to 30. It's all about giving FSX more time to process the stream of position updates.

Also, if you are using Static Weather Themes and have paused the system for any length of time (>1min), then it would be best to select Weather on the FSXSERVER and click OK, this re-synchs everything including the cloud formations. The tell tale sign that one system has been paused too long is that you will get different cloud formations on the server and client system. Anytime this happens just re-sync via the Weather option in the FSXSERVER program. If you don't pause this should never happen.

CPFlight MCP737/EFIS737 PRO/EL (Device Driver No.1)

TOGA button

The TOGA button has been added to the CPFlight MCP737/EFIS PRO/EL panel driver on auxiliary input K121.

A/T Arm switch

The A/T Arm switch on the CPFlight MCP737 is automatically disengaged 2 to 3 seconds after landing.

Unable to Open COMn serial port !

Have you configured the wrong serial port number or forgot to connect power to the panel?

CPFlight MCP controls have stopped working with PMDG 737 NGX

There is a problem with PMDG's FSXPMDG.EXE software when you open an FSX dialog. If you have paused the sim then you must unpause it before any MCP changes will be effective.

Also if you stop OpusFSX and restart it, then after the panel is initialised you must make a change on the sim's MCP to kick the PMDG connection back into life.

---

Home  About Us  Products  Downloads  FAQ  Gallery  Contact  Links