Running FDR on a Remote Computer (WideFS Users)

(a) The reasons why FDR could not read some functions of aircraft due to the use of LVAR instead of standard OFFSET have been mentioned at length above. Thanks to the LvarFix.dll file brought to FDR, many of these problems have been eliminated. As new aircraft software is released and new LVAR problems occur, these problems will be eliminated with the LvarFix.dll file updates.

(b) However, when this small file, which produces great solutions in FSX, p3d and MSFS (not applicable in FS2004) simulations, is unfortunately used on a remote computer due to the restrictions imposed by the FSUIPC software, that is, when the aircraft is used on a separate computer and FDR on a separate computer with the help of the wideFS program, the LvarFix.dll file does not work. It is not possible to find a solution to this problem due to the technical inadequacies of FSUIPC.

(c) For this reason, because LvarFix.dll file will not work when FDR is used on a separate computer, LUA files should be used to translate the LVar variables used on the aircraft into a form that FDR can understand.

(d) How to install the LUA solution files provided with the FDR installation package by Turkish Virtual is explained in the files in the folder where the relevant LUA file is located.

(e) The installation process should be done by carefully reading these files.

(f) Turkish Virtual will provide LUA files voluntarily written by our members in the past for remote computer users, as well as new LUA files if written in the future, to pilots, but will not strive for a LUA software as administration (except Xplane LUA files). Instead, it will provide LvarFix.dll support for users using FDR on the same computer.

(g) In short, those who use FDR with wideFS on a remote computer will have to install the LUA files that we have provided to you in order to troubleshoot their various problems.

(h) Turkish Virtual recommends virtual pilots to use FDR on the same computer instead of another.

(i) Two problem areas can be encountered when using FDR on a Remote Computer:

(I) Resetting the modem (breaking the connection between the modem and the computer): When such a situation is encountered, the simulator should be put into "pause" immediately; the flight should be stopped! Although the flight is normally disqualified within 60 seconds when the simulator is paused, this rule will not be applied since the connection between the aircraft and the FDR will be wholly disconnected if the modem connection is lost while the FDR is being used on the remote computer. If the simulation is not stopped immediately, the aircraft will continue to fly. When the modem connection is re-established, FDR will disqualify the flight due to "slew" (large displacement) if it is more than a certain distance from the last coordinates FDR received. To avoid this situation, if the modem connection is completely broken and determined that the flight's data on the FDR is not continuing, the aircraft should be stopped immediately (The flight should be put in a pause state). As soon as the modem connection is established, this time the aircraft should be removed from the "pause" state and continue the flight; otherwise, the FDR will start counting for 60 seconds, and if the aircraft is not removed from the "pause" state, this time the flight will be disqualified for 60 seconds of "pause" reason.

(II) Loss of Internet connection: If there is a connection between the modem and the computer, but the Internet connection is lost, the flight should be continued. FDR will start the ''Vatsim flight plan not found'' warning once every 5 minutes, and if, after the fifth warning, an internet connection still cannot be established and a valid flight plan did not send to VATSIM, the flight will be disqualified. Therefore, when the internet connection is lost, it must be re-established within 25 minutes.

(j) If the FDR is to be used on a remote computer, connecting the modem with an ethernet cable is recommended!

(2) Attention for those who TESTED FDR v5.16 during beta tests: Some of our pilots have been sent a beta version of FDR v5.16 during the coding. If you have ever used any beta version of FDR v5.16, which was named as _RC (Release Candidate), please check the folders of your aircraft in your simulator and see if there is any file which has an extension of .nvx that sits next to an .air file or .acf file (for Xplane). If there is an .nvx sitting next to your .air file or .acf file (for Xplane), delete the .nvx file. *This .nvx file has been created by FDR and it contains a specific identification code for aircraft which are difficult to recognize by FDR due to its’ contents of the .air or .acf file. Don’t hesitate to delete this .nvx file and let FDR create it again next time since the coding logic of that .nvx file has been changed for this final stable version. If you do not delete it, your aircraft may not be recognized correctly and you may have some problems in terms of aircraft lights, door and park brake actions.*


Since FSUIPC’S LVAR reading is not supported on FS2004 (FS9) our LVarFix.dll solutions cannot be used by FS2004 users!