Hello @ll,

the DC-6 uses two methods with the buttons, knobs and levers in the VC:

1. LVars: when you collect the LVars from the sim, there will be a lot of this: (L:dc6_398_obj,·Number). The number 398 corresponds to a control in the VC, in this case it is the gust locks (people who are new to the plane will know why I bring this up…)
   So operating the gust locks is as easy as
   0·(>L:dc6_398_obj,·bool)
   1·(>L:dc6_398_obj,·bool)
    
2. The good old (>K:ROTOR_BRAKE) method. They use the same number, in this case 398, multiply it by 100 and then add a number from 1 to n for the mouse action. (left down = 1, right down = 2, move = 3 etc.).
   As a result, sending
   39801 (>K:ROTOR_BRAKE)
   does the same as a left click on the lever.

To find out what the numbers mean, you will either have to use developer mode or look inside the animation definiton XML file for the VC. The latter is very clear and easy to read.

Hope this helps.

Edited June 18, 20214 yr by Lorby_SI

In the days that I was using the PMDG DC-6 for FSX, I made these panel screenshots. I gathered that the LVAR's could be the same in MSFS. So far they are: It took me a while and it's not complete, but for those who want to use their VRinsight or Saitek panels in combination with Spad.next, I've created screenshots of the different DC6 panels on which all useable buttons, switches etc have there variable (LVar) in yellow numbers. The syntax is "DC6_###_OBJ(LVAR) for almost all the assignments you want to make.

www.dropbox.com/s/5i78wzgl6e0oyc7/LVAR_DC-6.rar?dl=0

I'm busy today and tomorrow to implement them. Hopefully it will work as smooth as in FSX.

Peter

4 hours ago, bleekemolen said:

The syntax in SPADNext is "DC6_###_OBJ(LVAR) for almost all the assignments you want to make.

In AxisAndOhs you have the following options:

1. Execute "Scripting -> Read LVars from sim". Then all LVars are available in the event lists on the Add/Change Button dialogs, in the event group "Local Simulator Variables". This is only usable for switches with two values

2. In RPN scripts, like 1·(>L:dc6_398_obj,·Number) or by using the script variables (that way you can also assign an axis to the LVars - check the example in the AAO support thread in the official MSFS forum)

3. By sending the appropriate value to K:ROTOR_BRAKE if applicable. This must currently be done via RPN script, in version 2.08 it will be possible directly on Add/Change Button.

Edited June 20, 20214 yr by Lorby_SI

I must be doing something wrong.  I collect the LVARS and it says completed, but I don't see anything with dc6 in it in a search.

16 minutes ago, Crabby said:

I must be doing something wrong.  I collect the LVARS and it says completed, but I don't see anything with dc6 in it in a search.

Sitting in the cockpit of the DC-6?

Scripting -> Read LVars from sim?

Where are you conducting the "search"? Try the RPN Script editor first, "Insert Variable".

Edited June 20, 20214 yr by Lorby_SI

sitting in DC6, ready for take off

Scripting----Read LVars from Sim

LVARS Successful

Then went to set a button or axis either one. Searched from there.  Didn't try the RPN, will in a bit. 

10 minutes ago, Crabby said:

Then went to set a button or axis either one. Searched from there.  Didn't try the RPN, will in a bit. 

An LVar can only be assigned directly to a button, not an axis. Should be in the "Local simulator variables" group when you open the Key Down Event box. I know that they are there for me, but I'm already on beta version 2.08.

If they don't show up in the button event list, please let me know. Work around is using them in an RPN script as shown above and assigning that to a button. Or sending an email with your proof of purchase to the address on the last page of the manual, then you can have an advance copy of the 2.08.

Edited June 20, 20214 yr by Lorby_SI

3 hours ago, Lorby_SI said:

An LVar can only be assigned directly to a button, not an axis. Should be in the "Local simulator variables" group when you open the Key Down Event box. I know that they are there for me, but I'm already on beta version 2.08.

If they don't show up in the button event list, please let me know. Work around is using them in an RPN script as shown above and assigning that to a button. Or sending an email with your proof of purchase to the address on the last page of the manual, then you can have an advance copy of the 2.08.

email sent.  You have sent me the betas in the past.  Thanks!