OpusMSFS Flight Simulator Interface for
Started - Networked PCs
We recommend turning off all
virus checkers whilst running the sim since they can have a serious effect
on performance and even stop or delete our software.
using Live View
remember you cannot just rely on the frame rate measurements because the sim
will always give a fairly high priority to updating the screen. On
networked systems you must always give your server's sim adequate
CPU capacity to perform other essential tasks, such as issuing the very
important postion updates. If your system has the stutters, then
it is these infrequent position updates from the server's sim that
is producing them!
has very little impact on the MSFS performance and can generally
communicate the position updates as fast as MSFS can issue them. So
if you are having stutter problems then you should investigate other
possible causes. For instance, make sure you are not running any software (AV or Firewall) that could be interfering with the SERVER program's piped
IPC link communications. Are you draining the MSFS performance by
displaying too many views on the server, in-house we never drive more
than the single view on the server. Remember if you must have a wide
panoramic view then you can always install a wide view screen or use
three identical display screens with a TrippleHead2Go type product, in
which case, as far as the sim is concerned, you are still driving a
single main view, just one with a large pixel width. Other possible
causes could be your server's PC spec (is it up to the job),
insufficient memory (Windows 10 64-bit + loads of memory is highly
recommended), do you have a poor or slow network connection (this is the
age of Gigabit LANs - there's no excuse), is your actual aircraft sim
well behaved (or does it hog the processor?), is your scenery too
complex for your system, or have you been over enthusiastic with the MSFS
The client position update rates (most important) are
displayed in the client's Spy window for the 'Networked Live View
- Position and Attitude' application link when the aircraft is in motion.
Remember OpusMSFS generally updates the client systems as fast as the
server MSFS program can issue position updates.
client systems are set up in accordance with our Getting Started guide.
Note also, I use Kingston Solid State Drives (SSDs) to give the fastest
possible read performance for MSFS. Do not load the operating
system on these drives though since the write performance is quite poor.
These tests are designed to
help you set up your Live View system and isolate problems within your
server, network, or client systems. Make sure you have set up all
systems in accordance with the Getting Started Guide for Networked
Pay careful attention to all
the recommended sharing, permissions and security settings, remembering
the share both the install drive and folders of Opusmsfs and your
simulator. Also pay attention to the recommended settings and
optimisation of your client systems.
Run the simulator and load the
flights on the server and all client systems (or just the client system you wish to test and set up). Your aircraft can be sat at an airport
before starting the test, alternatively you may conduct the test with
the aircraft positioned anywhere you want.
Your simulator should be run in
Windowed Mode on all systems.
Run the SERVER program on
your server and let it initialise, then run the CLIENT program on
each client system you are going to test.
Allow all the systems to settle down with all client system simulators fully initialised and positioned. You are now ready to conduct the Live View link tests.
Testing Your System
Testing Your Client System ...
Run the client side Live View Test first to make sure your client system can cope with the changing position and attitude updates reported via its SimConnect interface.
1. Close all Spy windows.
2. Pause your server system's simulator.
3. Open the Configure dialog on your client system.
4. Click on the Live View Test button.
5. Your aircraft should jump to 2000 feet above the runway.
6. With all Test tick boxes ticked, click the Start button.
7. Your client display should now show relatively smooth changes in attitude without any major stutters.
8. You should be able to alter the Update Rate slider and see a fairly smooth motion for all rates.
Testing Your Server Link ...
Determine Your Optimum Update Rate ...
Close any Spy windows you have opened and ensure you have minimised your server's simulator to the taskbar.
To start the test, open the server Configure dialog and click on the Live View Test button. The Live View Test dialog will be displayed and your simulator will be un-paused.
Start off with the Update Rate slider in the centre position and tick each of the Pitch, Bank, and Yaw test options, then click the Start button. You should now see your client display jump to 3000 feet above the surface and start moving in all three attitude axis. Let it run for a few seconds then click the Stop button. The client display should stop and reset straight and level without any significant delay. Adjust the Update Rate until you can run this test and Stop without any appreciable lag in the client response.
Once you have determined your optimum Update Rate open the Position & Attitude Spy window on your client system, start the test and make a note of the rough average number of Position Updates per second. Divide 1000 by this figure and set the ms rate in the Live View Scan Rate box provided in the Configure dialog e.g. 100 updates per second is 10 ms. For MSFS you may need to set the server Live View Scan Rate to zero.
Both server and client systems display the following reports,
APP Position Updates: SIM xxx LAN xxx /sec
APP Position Updates: LAN xxx SIM xxx /sec
On the server, the SIM and LAN counts indicate the approximate rate at which SimConnect updates are received and IPC updates are transmitted. On the client, the LAN and SIM counts indicate the approximate rate at which IPC updates are received and SimConnect updates are sent to the MSFS sim.
N.B. These rates are not synchronised so will not be identical.
Your client display should move fairly smoothly with no major stutters or abrupt changes in attitude.
If your client display stutters badly running the Live View Test on your Server then you most likely have a problem with either your network connection or your actual client simulator system, try conducting the Live View Test on your client system.
If your client display stutters badly whilst running the Live View Test on your Client then this will indicate your client simulator system cannot cope with the position and attitude updates. Please make sure you have optimised your client simulator system and stopped all unnecessary software including any virus scanners. You could also try adjusting the simulator settings. For MSFS you may need to set the server Live View Scan Rate to zero.
This slider will typically alter the update rate from between 50 updates per second (Slow) up to about 120+ updates per second. This slider should be adjusted so that there is no appreciable lag when Stopping the test.
If there is a lag then reduce the rate of updates sent from the server by adjusting the configurable scan rate (i.e. increase the value) in the server Configure dialog's Live View Scan Rate (ms).
The Test Speed, Pitch, Bank and Yaw tick boxes allow you to select speed and each of the attitude modes individually.
Click the Start button to start the test and vary the selected pitch, bank and yaw attitudes for the aircraft. At the start of a test the aircraft is automatically positioned 2000 feet AGL.
Click the Stop button to terminate the test and recentre the aircraft.
Either click on the Quit button or the dialog's X to abort the test and close the Live View Test dialog.
when running the
Select the .NETv4 variant of
SimConnect and SlimDX.
Run the SlimDX dotNet 4
runtime using our supplied msi file in the OpusMSFS folder.
Run the SlimDX dotNet 4
runtime using our supplied msi file in the OpusMSFS folder.
You must ensure the FSICLIENT program ...
Is starting in the correct c:\OpusMSFS 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 4 runtime using our supplied msi file in the OpusMSFS folder.
Can't connect to client
Have you configured the correct number of clients in the server?
Can you still see the server's OpusFSI drive and folder in Windows Explorer on your client? Check a windows update hasn't re-enabled 'password protected sharing' on the PCs.
Is an Anti Virus program active or Win Defender active on the client? Stop Anti Virus software and disable Win Defender since these will cause problems and even possibly stop or delete the software.
Are you identifying the server using its IP Address or Computer Name? Try both methods.
Does the client IP Address have the same group numbers as the server, as per the GettingStarted Guide?
Can I use a Wi-Fi network ?
Yes you can, however you should note that a direct Wi-Fi 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 Wi-Fi link!
However, if you must use a Wi-Fi 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 CLIENT programs. You will find the link works perfectly well with perhaps a few tiny jitters when taking off of flying fast and low (depends how good or busy your Wi-Fi link is).
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.
are two solutions. The best is to reduce the rate of updates sent from
the server by adjusting the configurable scan rate (i.e. increase the
value) in the server Configure dialog's
Live View Scan Rate (ms). The second solution is to occasionally
pause using the 'P' key on the server, let everything catch up and then
unpause, let things settle and the lag will then be gone. You can also
use the pause key to measure the lag or amount of buffering at the
client end. If the system is configured and tuned correctly there should
never be any lag and both server and client should pause together almost
instantly. If your system is set up correctly it should be able to cope
with the throughput.
We have a Live View test facility to help you tune your system.
Start up all the client MSFS systems and the server MSFS so that they are all up and running. Then start the SERVER program, let it settle, then each of the CLIENT programs. Once they connect their sims will normally reload to the new location.
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's all about giving MSFS more time to process the stream of position updates.
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. If you don't pause this should
also recommend not running anti-virus software since this can have a
serious performance effect on the clients and
can even stop or delete our software.
and XP networked systems
may (or may not) experience problems if you have both Win7 and XP systems on your
network. Removing the homegroup and reverting
to standard networking may help.
also refer to the FAQ in the OpusMSFS_Getting_Started_Single_PC guide
which can be found in the OpusMSFS installation