Dear hunting friends,

 

As Gunther recenlty released a profile for the Maddog (version 0.9) I decided to start working on this profile.

Some things are clear to me and some are absolutely not...I was able to add a function for the TOGA buttons :lol: , but I'm

stuck now with some basic issues :huh: .....the main issue for the moment is that I do not understand the XXXX and YYYY codes

in the command icp.control (XXXXX, YYYYY). The XXXX is a FSX control and YYYY is an argument to set the control to.

In most cases however I see XXXX values which are higher than the well known standard FSX controls numbers from Pete Dowson.

The YYYY can be simple 10, 0 or 50 but also can show hughe row of numbers....Where can I find these XXXX controle numbers?

In the Linda tracer you can play around and hunt for actions...but uptill now I never have been able to find these XXXX and YYYY values.

Can you please be so kind to clarify this to me?

 

Kind regards,

Frans

Hello Frans,

 

this is the art of LUA hunting :lol:

 

Where can I find these XXXX controle numbers?

 

Just in the LINDA console.

Enable the developer mode for LINDA and open the console. In the lower right you'll find three little arrows. Click on them to expand an additional menu to enalbe or disable LUA logging or FSX controls logging.

 

Then you have to click a button in the VC and see what happens.

 

That's all ^_^

 

 

 

You can't say what to do exactly, because every addon is completely different. Each developer uses different methods, even from one addon to another it could change. Example:

PMDG has used the ROTOR_BRAKE (66587) control with several parameters for all functions.

Now, since the NGX, they use (like the Maddog I think) special control numbers, with several parameters.

 

This is what you see in the Maddog: special control parameters, and you just can hunt them with controls logging.

 

 

The Maddog uses a set of Parameters e.g. 16777216, 16777217 and 16777218

If you have a switch with three positions, you'll see (and have to use) this three parameters.

 

 

A general tip (not valid for the Maddog):

Nobody could say how things work, as I said.

It could be, that you'll find a control number for a certain function. But the sound of the switch is definded with a LUA variable.

Or you find a parameter number, but this does only toggle the switch (not on off). Then you have to search about LUA variables where you can see the swicth state. Example here is the NGX:

function NGX_W_HEAT_L_SIDE_on ()
   if ipc.readLvar('ngx_switch_135_a') == 0 then
    ipc.control(69767, 536870912)
    DspShow ("Heat", " on ")
   end
end

 

 

(69767, 536870912) just toggles the function itself.

So, you have to look for the switches LUA variable ("ngx_switch_135_a") and say, "just move the switch to on, when it's off"

 

 

 

Hope this helps a bit,

Günter

Hi Gunther,

 

Thanks for that detailed answer! Indeed that was the missing link to serious hunting!

I have attached a list of the Maddog Lvar's (Thanks to the guys from md80project.dk!!!!!!!!!).

I'm not sure if it is the complete list but I think it wll be helpfull to your own hunting as well...since version 0.9 needs an update to version 1.0 !

My goal now is to the find some functions for the Autobrake system, Vertical Speed knob and the barosettings.

Also I will be flying this beast as PF & PNF so I will try to add add some functions to control the knobs on the FO's side.

Propably I'll need a guide/sparring partner to get these functions tested and working! So I'll be knocking at your door Sir!

 

Kind regards,

Frans

Hello to all,

what can I do if I do not see the "ipc.control" numbers in the console when traving them. I speak about the FSL Concorde. Example if I hit the Chrono Button for countdown I see the following enries in the console:

LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 10
LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 0

but now ipc.control!

But I need the ipc.control to add functions as far as I understand the subject.

Can somebody help me?

Regards Tom

Ok I was wrong - in this case there is no ipc.control! But how can I write the script for pushing the Chrono Button with:

LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 10
LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 0

Kind Regards Tom

The Concorde is _ LUA wise _ the most ugly aircraft

 

believe me, I have "wasted" countless hours with the Concorde to get any functions out.

Most parts do work with IPC controls. But not all.

It is very tricky and in most cases impossible.

 

I asked the devs for LUA variables, but without success.

 

 

I wanted to start another approach 2 days ago with mouase macros and installed the Concorde again.

But now, the Concorde is crashing FSX every time.

I had a long conversation with (the very good) FSL support, but no success - I should reinstall FSX.

 

I have planned this already, but will do that after FTX Global Vector is released.

Hi Guenseli,

Thnx for answer. Mouse Macros are fine for older planes when no SP are arriving. The Problem is that the macros are Not working. Was tom make, but not working. Caused by this issue I tried the other approach.

About FSX and reinstallation I am using ACRONIS a very good BU programm. So I can try everything withour ruin FSX. This helps a lot.

Regards Tom

Hi Guenseli,

Thnx for answer. Mouse Macros are fine for older planes when no SP are arriving. The Problem is that the macros are Not working. Was tom make, but not working. Caused by this issue I tried the other approach.

About FSX and reinstallation I am using ACRONIS a very good BU programm. So I can try everything withour ruin FSX. This helps a lot.

Regards Tom

...I have no idea why the text above came twice - maybe a second touch on my mobile whle sending?...

 

Guenseli, does your answer mean that there is no way to get those commands to work?

LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 10
LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 0

As I said, Mouse Macros are not working at all for this plane.

 

Regards Tom

Simple answer: try it with LINDAs "set value"

open LINDA, press Shift+1. On the left side are the LUA variables listed the concorde uses.

Click at that one you want to test.

 

Insert a value below (zero or 1 or whatever) and press "toggle"

The Lvar is now sent to the addon

Yes I see the values - but if I click in the Tracer and toggle the value 10 and 0 - I see the variable in the in the console but in the plane nothing happens.

 

on mouse click

LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 10

on release mouse click
LUA.0:  [L] LVar: vc_Chrono_CP_Chrono_Btn = 0

 

no ipc.control

 

Regards Tom

Then it does not work, sorry.

As I said, the Concorde is a beast.

 

And welcome to the world of LUA variables hunting

 

 

No addon behaves as another

Search and try!