AllanK

I was going through the Fault Diagnosis process and found the following when I got to the step "You may need to remove a block on logging in FSUIPCx.ini" There was an error message about LogOptionProtect - looking in the FSUIPC6.INI file the option was already set to "NO". At that stage I clicked on "SYNC TO SIM" and the green "Everything is OK" came up and the Joysticks panel started to respond to key presses on the Controllers. Should I do this whenever I have this issue? Allan

Some more information. When the error occurs, the Joysticks menu panel does not automatically jump to the associated joystick configuration screen. I have now tried the following: I moved the current FSUIPC folder and then reloaded a good backup copy into the Prepar3D v5 Add-ons folder. I copied all the files from the moved LINDA and LINDA-CFG folders except for the aircraft I was working on - Quality Wings 787. Now Linda no longer shows an error. As I mentioned above I think it happens if I manually shutdown Linda while P3D is running. Does this give any clue as to the problem or the resolution?

Yes - I see the error on the Summary page. The Setup VRA Panels have no ticks in MCP Enabled, CDU2 Enabled or an entry in CDU COM Port. Controllers I have are Honeycomb Alpha & Bravo; Thrustmaster engines 1&2, 3&4 as well as the left and right add-ons and 2 Thrustmaster Cougars. I think the issue comes up is I accidently shutdown Linda without letting P3D shut it down. Allan

I am a new user and I am frequently getting this message saying fsuipc6.ini is an issue. I don't use VRInsight, MCP or CDU. The fsuipc6.ini file has the following entry which was inserted by the installation very early on. [VRInsight] 1=com0 The only way I can recover is completely delete the folder FSUIPC6 and copy the folder from a backup. Any thoughts on what is happening?

Yes - I am aware of the difference between True and Magnetic. When I load the above flight plan into FS-FlightControl it displays both True and magnetic bearings for each section of the course. For a lot of the course the bearings are the same except, importantly, for the final FD26 to RW26. It shows True of 261 and Magnetic 260. Looking at the UNS-1 and comparing it to FS-FlightControl it always uses the Magnetic bearing. As a baseline. I set up the same flight plan, from scratch, from VEBN to VNNG on a FSLabs A320. The approach was the same - VOR26Z - to fly through FD26 to RW26. This set up a bearing of 261 to the runway as shown on the Navigraph chart. I am certainly no expert but it would appear it is using True north and not affected by the underlying database in P3D. So it seems to me that the odd-one out is the FMS. As I have not noticed this anomaly on any other flight plan I am reluctant to apply the update you suggest. Perhaps there could be a setting to get the FMS to use True or Magnetic North as required? Any thoughts? Allan

Navigraph charts show that RW26 is at 261 degrees. On approach via SIKTA, CD26 and FD26 the UNS-1 sets up a heading of 260 degrees. As a result the aircraft is not lined up with the runway and is to the left of the runway. Navigraph charts are at AIRAC 2108 and the update has been applied to <P35> Flysimware Navdata. P3D is V5.2 HF1. Any idea where the issue lies?

I am having fun playing with this! Is there any documentation on the CRS button? When I press on or try to rotate it I cannot see any change on any of the displays. Allan

Thanks for all the replies. I believe I have carried out these steps but still see "NAV DATABASE EXPIRED" "09-SEP-21" in yellow while my date is shown as 21-AUG-21. Allan

Thanks for the quick response. Q2 above: I have searched the manual and can find no reference to this. Can you please explain what info is to be added to the navdata folder. I find various references in this forum to FMS versions and updates. How do I find the version I have? Where do I find updates? Allan

I have worked out answers to my Q4. Also, I note in the Flysimware\Navdata the cycle_info.txt shows: AIRAC cycle : 2108 Version : 1 Valid (from/to): 12/AUG/2021 - 09/SEP/2021 So not sure why the expired message - any suggestions? Allan

I have just purchased and installed this FMS on P3Dv5.2 HF1. A couple of questions: Q1: The FMS startup screen shows FMC VER 001.P3. Is this the latest? - if not where can I get the latest version? Q2: The system also shows "NAV DATABASE EXPIRED" "09-SEP-21". I have a NAVIGRAPH subscription and have added "Flysimware Learjet 35A" to the update list and it is at "2108 rev 1". How do I update this AIRAC? Q3: The help file I have is V1.7 - is this the latest? Q4: Are there any instructions to load a Simbrief or other flight plan into the FMS? Q5: Is there a list of control codes or local variables that can be used to program Honeycomb Alpha and Bravo units? Thanks in advance for any help. Allan

I decided on FS-FlightControl - does what I want and more than I knew I wanted (but now I do).

Ahhhhh - excellent - thank you. Allan

Thanks for taking the time to reply. Yes - I have read that manual, however it does not specify where to put commands such as "G1000_MFD_SOFTKEY6". Searches I have done on the forum have not shown up any information. Can you please let me know where these settings are configured. Allan

Thanks for the tip - I have found the switch. This is the first plane I have used to have the switch there. Other planes i have used have both NAV1 and NAV2 together.