I have a few questions about how to write code for LINDA, so thought I woudl start a new thread for that. I am sure more will pop up later :)- I want to place spoilers off and spoilers arm on my joystick, but cannot find functions in the default fsx library for that. Currently I have placed them in lib-user.lua, is that the right place for them? They look like this:function Spoilers_Off() _SPOILERS_OFF() DspShow("Splr", "Off")end-Currently the display contains "-ap-" most of the time, I was wondering if I could put the state of the MCP there instead:Something like: V if Vnav is active, L if LNav is Active, N if N1 is active, S if Spd is active etc."Or maybe even better: Use the radio panel display 5 secs after last use for radio settings or when a mode button is pressed.Is that possible?

Hi,I have add a function for the PMDG MD11 (DIAL_a_FLAP_set) directlty in actions.lua of the MD11 directory.Two questions : - is it the good place ?- how to share all our new function with other ?Michel

Hi Helge and Michael,

Currently I have placed them in lib-user.lua, is that the right place for them?

YesBut general for your "problem": have you seen the "Set FSX control" in the pop-up when assigning a button???If you click on it, there will open a little window where you have ALL fsx controls, also your Spoilers_off.You can search for the function, either by name or by number ... a very cool feature waht Artem implemented, isn't it? :biggrin:Despite this, your functions looks right for me except a space before the ()Try and look if it works...For the question about the displays:I have an idea why it is not working, but Artem will give you a proper answer ...@ Michaelif you have selected the MD11 you can click in the Pop-up assigning menu at PMDG MD11 --> edit module and the right script will open.actions.lua is correct, but this way is much easier ...But beside this, theres already a dial a flap implemented: PMDG MD11 --> Pedestal --> Dial a flap inc/dec

- how to share all our new function with other ?

I will talk to Artem what the best way will be, but I think you could send him a mail and he will open then a thread here.Hopefully we get some subforums to have a better structure for this here, soon.

lol I missed the "Set FSX Control" thing. Linda's UI is so deceptively simple but can do a LOT of things. I am really impressed that you guys have been able to create such a great utility!Awaiting Artem on the display thing...Helge

Günter,I have seen the 2 functions for DIAL_a_FLAP_inc & dec to select the Flap position.What i have added is assigning a button to extend the Flap at the selected position.It is just used before Take-Off but it is a simple exemple i want to try/test.MichelHi Helge,First i missed also the "Set FSX Control" :( What i learn now is that a lot of basic functions are not repeated in the specific aircraft like the MD11 when they already exists in FSX Control.Michel

Guys, We are going to create some additional subforums for LINDA next days. There will be a separate forum for discussing the development process and share the ideas and user-created modules too. And the separate Download forum for collecting all work done in one place. I'm not sure if could provide access for my server to everyone, but when user created module is ready and tested, I will place it there as a separate zip.

MCP there instead:Something like: V if Vnav is active, L if LNav is Active, N if N1 is active, S if Spd is active etc."Or maybe even better: Use the radio panel display 5 secs after last use for radio settings or when a mode button is pressed.Is that possible?

Some time ago (before Beta) we discussed that question with Guenter. The problem is that i.e. Boeing AP system has 12 (or more) different modes, each other complex aircraft has many other modes... and have no idea how to put them on a two-lines display with 4 char in each line only. I can allow the particular module to change the "[AP]" string which is appeared when AP is on, and that's all... Have no better ideas for that.As for RADIOS display - it is unaccessible for scripting, Shame.

What i have added is assigning a button to extend the Flap at the selected position.It is just used before Take-Off but it is a simple exemple i want to try/test.Michel

Dial a flap is programmed by PMDG with controls (RotorBrake; which is their control for everything)They use several parameters to make all functions.Di al a flap looks in LUA so:

function DIALaFlap_inc ()	   	ipc.control(66587,80082)	endfunction DIALaFlap_dec ()	   	ipc.control(66587,80081)	end

As you can see there are only two parameters for it: increase and decrease - nothing to select it directly.So, from my side theres no idea to select a specific value for it, sorry.If you have an idea its welcome ...

What i learn now is that a lot of basic functions are not repeated in the specific aircraft like the MD11 when they already exists in FSX Control.

Jep, why doing things twice :Whistle:We can go a bit back in history:LINDA is based on my LUA scripts which I have made in the last years for several addons.And I shared this scripts (mostly to find in the FSUIPC forums), but the intention was just to make them work with my hardware and my needs.So, LINDA is just a platform and a kind of standard for the community now to gather and create LUA scripts and can easily assign them.But the content of each script does not mean that every possible function of the addon is implemented.Its just a start and everyone can add and modify these scripts and share them ...

If I remember correctly you can assign a keypress in the key assigning application that comes with the PMDG MD 11 to move the flap handle to the Dial-a-flap position, I may have dreamt it though :) I think there is even an assignment to move it to dial-a-flap 15 as well.

As you can see there are only two parameters for it: increase and decrease - nothing to select it directly.So, from my side theres no idea to select a specific value for it, sorry.If you have an idea its welcome ...

There is the way.. not the pretty solution, but may work in some cases.Let's say there are 4 flaps positions - 0, 1, 2, 3To jump directly to the 0 position we need to send 3 DEC commands:

ipc.control(66587,80081)ipc.control(66587,80081)ipc.control(66587,80081)

No matter where were flaps after these 3 call they will go to the 0 pos.Next. To jump to the position 1 we can send this sequence:

ipc.control(66587,80081)ipc.control(66587,80081)ipc.control(66587,80081) -- dec to zeroipc.control(66587,80082) -- and now inc to the pos 1

For position 2:

ipc.control(66587,80081)  ipc.control(66587,80081)  ipc.control(66587,80081) -- dec to zeroipc.control(66587,80082) ipc.control(66587,80082) -- and now inc to the pos 2

You got the idea...The success depends on how fast addon internals will react on these commands.. need to be tested.

No I wasn't dreaming lol.No keys are assigned by default, they are the keys I have assigned a long time ago. It's probably more efficient in this case to use keys rather than Artems suggestion above, although I cannot see it being a problem unless you struggle with low frame rates.

I thinck the functionfunction DIALaFlap_set () ipc.control(66587,73083)enddo the same as "Dial-A-Flap to take-off flaps"It is ok like that. Thanks for the idea to set flaps to incremental positions.Michel