Hi,

what is the difference of the 2 new Linda-versions v 4.1.4 from 1 Mar and the FWB-package v 1.0.2.a?

is using the FBW- version necessay or does Linda 4.1.4. gives me the full functionallity.

A littlebit confusing forme.

Please  help.

 

Theo

Edited March 13, 20224 yr by ScotFlieger

Hi Theo

LINDA 4.1.4 is a normal update with the changes as listed. I found an issue with the FBW 1.0.2 release involving the use of the event files that could cause a crash on initial startup. The interim 1.0.2a includes a single code line move to address the problem. It needs LINDA 4.1.4 as well to fully fix the error. As we are using GitHub for the FBW A32NX development a formal update will follow in due cause. 

I believe I have done the proper installations as most of the vrinsight functions seem to work well. However the only functions of the EFIS panel that seems to work is the BARO.  The Autopilot display mode does not turn or change, nor does the display distance change, etc. I noticed in your setup description the following;  "You need to assign one of the VRInsight library DSPmode functions to switch between INFO and AP (autopilot) modes".  I have searched and searched some more to try to understand how to do this.  I am assuming this is why the Boeing MCP2 is not working properly.  I would be very grateful if you could shed some light on the process to enter the above setup.   Thank you in advance R. Williams.   [[email protected]]

@randy49 the INFO mode has not been implemented for the FBW A32NX module v1.0.2a. The DSPMode defaults to the AP display mode.

If you are using other aircraft modules the DSPMode functions can be found in the VRInsight library via the pop up menu assignment.

There are delays with the start up process with MSFS. FSUIPC7 7.3.0 adds some delays on startup but it is still recommended that users click Restart LUA Engine after MSFS and aircraft are running to ensure things are working correctly.

 

Hi, I'm having trouble starting the a32fbw version 1.0.2 module with the latest update of the actions.lua file from 2 days ago.

I have the version of fsuipc 7.3.2 registered and with the wasm module installed and activated

I have the version of linda 4.1.4a

I start everything as usual but after synchronizing and leaving the yellow box I wait more than 5 minutes and wait continues to appear and mcp2 does not start testing with a cessna 172 by default I do the same procedure and in 30 seconds ready appears on the panel Regards, and thank you very much

Edited March 29, 20224 yr by bevik66669

@bevik66669 which 2-day old actions.lua file are you referring to? If it is from GitHub then this has not been released yet. Please stick to v1.0.2a available under LINDA Download.

Before I can say what is going wrong with your set up I need to ask you to read and follow the Fault Diagnosis Procedure (under LINDA Support) and email me the logs. 

Good evening Scott here I send you the photo so you can see the file of the module to which I refer.

In any case, tomorrow I will process to send you the fault diagnosis procedure.

 

https://ibb.co/Csv6dm4

That file on GitHub is still undergoing final testing and is used at your risk. I will await sight of your logs to see what may be going wrong.

Hi scott 

I have proceeded to send you the requested documentation a greeting

Finally I think I have found the problem, it was because of the MobiFlight application that has opened the same mcp2 com port and created a conflict when connecting fsuipc. I've done a clean install of Linda fsuipc and the module without the .macro files and connected to the first one.

I saw the GitHub of the author of the module that the MobiFlight program was necessary to make it work, it seems that it was for old versions and not for the current version

 

In my case I only needed fsuipc with active wasm module linda 4.1.4a and a320nx module 1.0.1a; start msfs2020 and in the cabin image wait a bit then start linda and fsuipc and the magic is done