Hello,
I've been using LINDA 3.2.6 with the QW787 v1.1 module for the MCP Combo II for a month now. For the most part, it works very well. Thank you for the great job.
But there is a small problem with a key assignment in the EFIS sector. I have assigned weather, traffic and terrain to three buttons. These only work when I first activate the three buttons with the mouse in the virtual cockpit. Did any of you have the same or a similar event?
Is there a solution for this?

I am using P3D V5 / V5.1.

With regards from Austria

Thomas

Hi Thomas

I have not heard of this issue before. I have had to download and install the latest QW1.3.1 to P3Dv5.0 as I don't normal use it.

I looked at various EFIS functions from LINDA module 1.1 and all responded correctly without the need to use the mouse in the VC. Can you let me know which functions you were trying to assign? A copy of your config-mcp2.lua would be useful (email to linda @ awginfosys DOT net).

 

Edited November 11, 20205 yr by ScotFlieger

Hi Thomas

Thank you for the config file. I have used the functions for QW_MCP_L_WXR_press, QW_MCP_L_TFC_press and QW_MCP_L_TERR_press and assigned them to buttons on my MCP. All functioned correctly first and all subsequent times I pressed the button. None of the QW787 buttons are animated so I can't see their direct effect.

EDIT There is a delay when pressing subsequent buttons. If WXR is selected and TERR is pressed it cancels WXR. A second press is required to display the TERR map. 

Edited November 11, 20205 yr by ScotFlieger

As mentioned I found a slight anomaly that required some of these 3 buttons to be pressed for the function to change. You say the test version I sent you (v1.2) did not work.

I need more of a explanation as to what is not working. In my testing today the buttons with WXR/TFC/TERR had a visible affect on the PFD. I did not need to use the mouse at any time.

Hi Andrew, 

I tested your new file. But it didn't work. I tried to test this three button with new key assignment. F. e. Instead weather I tested starter one. It worked perfect. Then I changed back to QW_MCP_L_WXR_press. It didn't work again. Only when I activated the Wxr-button in VC cockpit with the mouseclick, then it worked the rest of my flight. Also happened with tfc and terrain. 

Thomas

Why would you need to change the button assignment so often? One saved the configuration will reload (reported in the console). That should be it. I can’t find any problems as you report. 

Hi Andrew,

Yesterday I changed this button assignment for test purposes for the first time.
Maybe this video will help you. Please excuse my English.

Thomas

Thank you for the clear explanation and video. What are your start conditions before the video starts?

I start every flight with coldanddark.pnl.

This video I recorded after the preflight checklist. Flight was programmed. 

What order do you start your system? LINDA first or automatically with P3Dv5 and FSUIPC6.

LINDA starts automatically with P3Dv5.1 - Setting in LINDA Menu

Thomas

Hi Thomas

I have tried to use the same starting position as you describe but I am unable to reproduce the problem. I do not have to use the mouse in the VC to 'activate' the WXR/TFC/TERR buttons. They work directly from my MCP. I would ask you to try some more logging for me.

Please activate the Fault Diagnosis Mode (from Maintenance page) and then open the Console and tick the Log VRI events checkbox. Also on Setup LINDA page ensure that Display VAS in unchecked. Then close everything.

Start P3D (with FSUIPC6 and LINDA) with QW787. After LINDA reports ready, press the MCP WXR/TFC/TERR assigned buttons several times each and then one after the other. Do not operate the VC buttons for this test. Close everything down. Email me the fsuipc6.log and linda2.log files.

Then repeat same test. Operate the MCP buttons again and, if they don't work, operate the VC VXR button. Repeat the MCP button presses. Operate the VC TFC button and then the MCP buttons. Finally, operate the VC TERR button and then the MCP buttons. Close everything and email me the new logs.

Hi Thomas

Thank you for the latest logs. Can you confirm that the Log VRi Events was ticked on the LINDA Console? I am not see any events or button presses in either logs.

I can see that the MCP2 if correctly identified by FSUIPC6 and the configuration loaded by LINDA. The correct QW787 files are also loaded  

The first linda2.log does not show that the GUI is detecting the FSUIPC connection or version or the Flt Sim version. The second one does. The second time LINDA was not in Fault Diagnosis Mode and the fsuipc6.log ends before it is properly closed down.

Can you again look at your setup and run the tests again please?

Hi,

i can confirm, that the Log VRi Event was tickted. For the next test I will tick on all events, because it was only the Log VRi event ticked before.

Hi Thomas

Can you check/add these lines to your fsuipc6.ini file [general] section:

• Debug=please
• LogOptionProtect=No
• VRIDisableCMDRST=Yes

EDIT: I have just found that you have to untick and tick the Log VRI events checkbox for it to start logging. In the LINDA Console, with the Display VAS option selected (in Setup LINDA) you should see the FPS displayed every second as:

VRI com3 <--- dsp3 43/ [from LUA Plug-in]

Also change LINDA logging level to DEBUG.

Edited November 16, 20205 yr by ScotFlieger
Updated information