Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LINDA not following Majestic Q400 SDK correctly

Featured Replies

After some additional analysis with the help of Bryan York at FS2Crew, it appears that LINDA is not correctly following the SDK for the Majestic Q400 when scanning for variables.

 

Two cases to consider:

 

1)  The L:RADIO1_SERV_INT_KNOB variable moves from 1 to 0 to 255 and cycles in this way all the time.  This is causing FS2Crew to cutout its voice sound while running.

 

2)  MJC_MDA & MJC MINIMUMS also toggles between the set number (1000 in my test) back to zero then 255.   This results in FS2Crew not getting the proper flows after takeoff and this may be the reason. 

 

 

In communication with Oleksiy he has pointed out that this is probably the reason for the issues with FS2Crew for those of us using LINDA and the MCPII Panel.   I am just wondering if it is possible to make some adjustments to LINDA so that these issues can be resolved?

 

 

thanks!

 

cleardot.gif

 

 

Mark   CYYZ      

 

Hi Mark, I am pleased the info I provided to Bryan was useful in identifying the possible cause. I don't have time to investigate myself but the problem lies not with LINDA itself but the Q400 LUA module you are using.  You will find this in the Q400 folder in /linda folder named actions.lua.  Search for the variables you list.  If you have a basic understanding of programming you should find LUA easy to master - there are plenty of examples.

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

  • Author

Thanks, good to know.  I looked at several files but did not see the actions.lua file so now I can investigate.  I know just enough programming to be dangerous but will take a look and see what I can figure out.

Mark   CYYZ      

 

Hi Mark

 

Your Q400 module will be located in your FSX root directory in /modules /linda /aircrafts /Majestic Dash 8 Q-400 /actions.lua.  Alternatively and easier, open LINDA, select your aircraft type, goto Joysticks and click on button entry, click on Majestic Dash 8 Q-400 (arrowed) and click on Edit Module at the top.

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

  • Author

Scott,

 

I had a quick look at it but could not find anything related to the volume control.  Perhaps it is part of the COM1/COM2 setup.  I need to look further and also see if I can find the Q400 SDK.

Mark   CYYZ      

 

  • 4 weeks later...
  • Author

Scott,

 

I did a lot of editing and deleting on the Q400.lua and removed all of the radio sections, comms etc. but it did not fix the problem and the debug gauge that Bryan from FS2Crew gave me still showed lots of changes to radio volume variables as well as other variables like the MDA while LINDA was running.  Is this something you can take a look at ?

Mark   CYYZ      

 

Hi Mark

 

I am not sure what I can advise you to try.  Basically, the radio panel on the Combo MCP panels is hard-coded. The Radios functions under MCP Combo Mode 1 should, by default, either be empty or default and have no impact on the operation of the Radio Panel and your Q400.  Neither LINDA itself or the VRInsight have any control over radio volume.

 

Andrew

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

  • Commercial Member

 

 


if I can find the Q400 SDK

 

There is no such thing.

 

Everyone who has interfaced the Q400 in some way, including ourselves, did it as "guess work".

 

Now, bear in mind LINDA has been around for a long time, and it appears it worked for you before.

 

If I was new to the game I don't understand completely (some have only heard about L:vars about 6 months ago), I would first look at what I may have done wrong, before blaming others for not "following" a "ghost" SDK correctly. Unless I decide, I am the correct SDK way...

  • Author

Andrew,

 

Thanks for the reply.  I guess the mystery will go unresolved.  Apparently the way LINDA reads the values or scans the system for values is the problem (according to Bryan).  I guess I will just have to fly this bird without the MCP when using FS2Crew.


Actually the SDK does exist.  I received a copy of it from the developers at Majestic.

Mark   CYYZ      

 

Hi Mark

 

Can you send me Bryan's information and analysis?  I will do some deeper analysis of how LINDA handles the Lvars.  I don't know if Atem (the original developer) has time to advise.  I would also me interested in the SDK if you can pm me?

 

Andrew

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

  • Author

Hi Mark

 

Can you send me Bryan's information and analysis?  I will do some deeper analysis of how LINDA handles the Lvars.  I don't know if Atem (the original developer) has time to advise.  I would also me interested in the SDK if you can pm me?

 

Andrew

 

I sent you a PM.

Mark   CYYZ      

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.