Edited by guenseli, 20 February 2012 - 08:49 AM.
FS9. FSX & P3D CTD Guide - NEW!
FSX / P3D Configuration Guide - UPDATED!
Simulation's Premier Resource!
AVSIM is a free service to the flight and simulation communities. Please help us keep it that way. Donate what you can today! Thank you for your support!
PMDG MD11 (module version 1.2)
24 replies to this topic
Posted 03 August 2011 - 11:05 AM
Here you can download the LINDA aircraft module for thePMDG MD11 (module version 1.2).Download and unzip it and place the complete folder into:Microsoft GamesMicrosoft Flight Simulator XModulesOverwrite existing files (maybe backup them if you like)MCP default assignemnt is included: rename your present one from config-mcp.default to config-mcp.lua if you want to use it.We will update this files from time to time and will make a little note in this thread about the changes.Users, who also made changes to this codes could post it in this thread or drop me a PM and we will update the module.If you have created a complete new module (also for other addons) please PM us.Download link:www.fs-linda.com/downloads/modules/PMDG_MD11_v1_2.zipEdit:updated on Jan 2012Complete overhaul of the module with many new features.After a long while flying just the NGX, I installed the MD11 again. Also a nice addon...but the NGX is another generation ^_^Unfortunately it is still not possible to sync the AP-displays with MCP Combo, sorrythanks to Navajo!UPD Feb 2012: added reverser section
Please donate today!
Posted 19 September 2011 - 09:46 AM
Thanks for the profile :) I think I found some bugs on the EFIS_Mode_inc and EFIS_Mode_dec functions. After loading the profile, I noticed that those functions cycle partially thru wrong buttons. The functions gave wrong values on NDvar, being one off. The range for the EFIS mode buttons is 71132-71136 but EFIS_Mode_inc produced values 71133-71137 and EFIS_Mode_dec 71131-71135. I edited the values on the function a bit and made it work. Here's the edited part.
function EFIS_Mode_inc () NDcount = ipc.get("NDvar") if NDcount == nil then NDcount = 71131 elseif NDcount == 71136 then NDcount = 71131 end if NDcount <= 71135 then NDcount = NDcount + 1 end ipc.set("NDvar", NDcount) ipc.control(66587, NDcount)endfunction EFIS_Mode_dec () NDcount = ipc.get("NDvar") if NDcount == nil then NDcount = 71132 elseif NDcount == 71132 then NDcount = 71137 end if NDcount >= 71133 then NDcount = NDcount - 1 end ipc.set("NDvar", NDcount) ipc.control(66587, NDcount)endHope it makes some sense, I'm not a coder or anything
Posted 21 November 2011 - 05:36 AM
First a big thank you to everyone involved with L.I.N.D.A.!!!!!!!!!!!!!!!!!!You totally saved my PMDG MD-11 experience!!!!!Just wish i had found it before starting my real flight training on the MD11.I was also very happy that the MD-11 was also included.One question; Is there a way to speed inputs up? e.g. the minimums take forever to set from 200 to 1500.I did try the "on repeat" option and entered the same command there as i did "on press"There were a few important MD-11 functions missing, but i was able to get them working and wanted to share what i've found.The SD Cue switches (on the SDCP) to view the different systems:-- ## SD-CUE ###############function SD_CUE_ENG () ipc.control(66587,73390)endfunction SD_CUE_HYD ()ipc.control(66587,73391)endfunction SD_CUE_ELEC ()ipc.control(66587,73392)endfunction SD_CUE_AIR ()ipc.control(66587,73393)endfunction SD_CUE_FUEL ()ipc.control(66587,73394)endfunction SD_CUE_CONFIG ()ipc.control(66587,73395)endfunction SD_CUE_MISC ()ipc.control(66587,73396)endfunction SD_CUE_STATUS ()ipc.control(66587,73397)endfunction SD_CUE_CONSEQ ()ipc.control(66587,73398)endfunction SD_CUE_ND ()ipc.control(66587,73399)endAlso i found some functions on the ECP (Electronics Control Panel) or EFIS as it called in the linda module.I made an extra section, and found out later that the minimums were already in the module.The names are self explanatory, I think.-- ## ECP ###############function BARO_QFE ()ipc.control(66587,71143)endfunction BARO_QNH ()ipc.control(66587,71144)endfunction MINIMUMS_RA ()ipc.control(66587,71121)endfunction MINIMUMS_BARO ()ipc.control(66587,71122)endfunction MINIMUMS_INC ()ipc.control(66587,80023)endfunction MINIMUMS_DEC ()ipc.control(66587,80024)endfunction BARO_INC ()ipc.control(66587,71107)endfunction BARO_DEC ()ipc.control(66587,71106)endfunction PULL_STD ()ipc.control(66587,71102)endBest RegardsP.S. Don't hesitate to ask any MD-11 related questions, I'm a second officer on the real thing.P.S.2 made donation as well. Well deserved!!
Posted 22 November 2011 - 02:11 AM
Hello,many, many thanks for this!I haven't installed the MD11 since NGX was released But you brought this great addon now back to my mind. Will install and update this module as soon as possible!Though, without doubt, the rela thing must be much more fun :)thank you!
Posted 17 January 2012 - 09:21 AM
HiExcellent product, love the way I can combine FSUIPC for axis control with the "simplicity" of use of Linda.I have the MCP Combo 1 with flight sim yoke and pedals.Although I do use the term "simplicity" from the point of view of installation and use rather than because I have any idea how to master LUA programming.Anyway.Now that the PMDG NGX module has been issued with "full display sinc" can this be leveraged from to help produce a module with "full display sync" for the PMDG MD11?Whilst I gather that PMDG have no intention of releasing the SDK for the MD11, did they completely re-write the programming between the MD11 and NGX?Or can an "imaginative" leap be made by one of you very clever "Linda" guys to solve the issue once and for all the MCP Combo 1 display and the PMDG MD11?Kind RegardsStuartPS made a donation, well worth the effort I think
Posted 17 January 2012 - 03:12 PM
thanks for your kind words...unfortunately I see no possibility to make the displays sync for the MD11!I have tried a real lot, but as long as we can't read the values out of the addon, there's no chance!And: looking at the MD11 support or JS41 support: as good as development and initial supporting from PMDG is, I wouldn't wait for an SDK or SP for the MD11
Posted 17 January 2012 - 07:24 PM
What a shame but many thanks for taking the time to respond to my post. For now I will continue to enjoy LINDA. By the way, my wife came home from work today and wanted to know why I was making a donation to a female called "LINDA" LOLApparently my wife saw the e-mail on her phone from Paypal about the donation. LOLBeen laughing all evening LOLAnother positive thing about your software...........
Edited by eeyore, 17 January 2012 - 07:33 PM.
Posted 18 January 2012 - 04:21 AM
:LMAO:cool, we already have a marriage, now we have also a divorce ...Come on guys, there's a father-to-be whos considering LINDA as name for his baby ...
By the way, my wife came home from work today and wanted to know why I was making a donation to a female called "LINDA" LOL
Posted 20 January 2012 - 10:00 AM
module 1.1updated on Jan 2012Complete overhaul of the module with many new features.After a long while flying just the NGX, I installed the MD11 again. Also a nice addon...but the NGX is another generation ^_^Unfortunately it is still not possible to sync the AP-displays with MCP Combo, sorrythanks to Navajo!
Posted 22 January 2012 - 10:00 AM
That is a most helpful update — thank you, Günter! I very much look forward to trying it.For some years now I have flown only the PMDG 744, MD-11, and now the NGX, but once I have become completely comfortable with the NGX (gotta love the -600 version, especially!) I will be happily returning to the MD-11 (and the 744) also, so my most sincere thanks in anticipation of that event. :drinks:As has been said before, the simming community owes a huge vote of thanks to yourself and Artem — and a few others who have made modules for us! Hopefully, more of us will now begin to develop and contribute additional modules, too.Best wishes,Brian
Edited by brian747, 22 January 2012 - 10:01 AM.
Posted 10 February 2012 - 11:19 AM
Yeah sure no problem to share.As long as people understand that not having worked with LUA before my function writing skills may appear a little "clunky" to those more adept at the language.Where do I send the file(s) or do you want me to attach them to a post on here?RegardsStuart
Posted 12 February 2012 - 04:45 AM
You can rename you actions.lua to actions.txt and attach it here. Or you make a ZIP folder out of it.If this does not work, simply put it into your thread in the
Where do I send the file(s) or do you want me to attach them to a post on here?
codefield.Then I will copy it and update the MD11 module.Thanks!
Posted 14 February 2012 - 09:51 AM
Hi,So please find attached the txt “actions” file as requested.Basically, I managed to locate/identify/functionalise many of the PMDG MD11 implemented controls not already identified in previous versions of this file posted on this site for download.Why (I here you say) did I bother try to find them when many will never be allocated to a button on my MCP?Well, there were two reasons for this.Firstly, I have never, ever done anything in LUA before and so was eager to learn as much as I could and the more I worked with it the more I learned. Writing a LUA function that helped me to identify controls was definitely a way to learn more about syntax, structure, nesting, blah, blah, blah. All of which I am sure many will be familiar to others but for me was a complete mystery until recently. I hate syntax errors by the way, with a passion.Secondly, there was some functionality that I wanted to implement that was not available from previous posted versions of this file. So if I needed to find what control initiated that particular button push, switch or knob turn then I had to go through a process that inevitably discovered something else. Why not at least note it down and make it available should I ever have cause to want to use it at some point in the future?There are still a few controls I have not identified. These basically boil down to the fact that (i) I “ran out of steam” (ii) there was no way (that I could figure out) to easily monitor a switch’s or button’s change of state (like the GEAR horn inhibit, EVAC horn inhibit or the entire SISP functionality) without simply and laboriously “watching the screen” for hours or (iii) I have no need for them at present, like for example “PAX load numbers” because I tend towards use of the FEDEX freighter variant rather than anything else. For my own use I have re-organised the file and also made some changes so that functionality, information display and use is handled in a way that I liked and found easy to use. This does mean that someone may not simply be able to copy this file for their own use but it does mean that anyone can copy and paste want they want to add functionality to their own MD11 actions file if they want. In general, the file is split (with a few exceptions) into various sections that are aligned to the way that PMDG constructed their panels on the MD11.Each main section is also subdivided into various subsections within which are located the various buttons, switched, knobs, etc.Main sections are denoted by a string of “########” marks surrounding capitalised text. Subsections are denoted by two “##” marks followed by lowercase text.So for example, I have called a main section in the file “OVERHEAD PANEL (OP)” and there is a subsection called “OP – Electrical” and another called “OP – Hydraulics” and another called “OP – FADEC Mode & E/Start Select” and so on and so forth.I make no apologies for the fact that:-1. I have written my additional functionality around the original MCP only. This is the only one I have and the only one I am likely to own so did not concern myself with anything else. This does mean that text used for display purposes is very limited and so will inevitably be “cryptic”. For example, the on/off and brightness button on the system display panel for the primary flight display can be repeated on my MCP as top line “PFD” and bottom line “BRON”. To me this means primary flight display captains side, brightness button turned on. In addition, a common theme on all such text is that if I try and switch on something that is already on (according to the switch/button/knob/etc position) then the repeat on my MCP will show top line “PFD” and bottom line “ASET” meaning primary flight display captains side already set i.e. turned on. Of course this also applies to the off state, flaps 35 state, HI state, etc, etc.2. The wording I have used to describe things or define things is my wording, so it may not be right but it is how I did it for my purposes.3. Some of the functionality I have chosen to implement for myself may not make sense or be “prototypical” but with a limited number of MCP buttons available and yet much that I wanted to implement, it was inevitable that sometimes I wanted a single button push to achieve a number of different results. Conversely, there may be functionality that others believe to be superfluous. That’s fine just don’t implement it, just as I have also not implemented in many cases.4. I have not spent hours “testing”. What I have done seems to work so I have left it at that. This file is only an adaptation of work originally done by others with their permission. I make no claim to the file and any additional functionality I have provided is offered freely for anyone who wants to make use of it (in whole or in part) but at their own risk and without a guarantee or support. I will try and help if anyone posts a question and if anyone comes across or spots an error in my work feel free to let me know, it will save me coming across it myself at some later date.Lastly for now, once I wrote something and it worked I left it alone. As I have already mentioned above.I did not go over old ground or re-write something when I found a better way of doing things in LUA.This means that if you look closely, you can see how my learning curve improved a little as time progressed and I taught myself how to do things better.For example, one of the first sections I looked at was the system display panel, how to simply switch on, dim and brighten the various displays. I did not want to have to press a button to increase brightness slowly, I just wanted to be able to press a button so it snapped to bright, snapped to dim or snapped off.Latterly, I concluded I wanted to use just one button on my MCP to simply toggle between a day and night settings when the lights were switched on or off. Now all the functionality in this section works, it is just that the solution implemented for the day and night toggling is far more elegant than the solution I first implemented for switching a display on/off or making it bright or dim.Hope this file proves useful.RegardsStuart
Posted 14 February 2012 - 04:35 PM
Hi Stuart!...and Wow! Tonight I have only had time to superficially scan through your work, but I am extremely grateful — thank you.I have to confess that my MD-11s at present are being shamefully neglected whilst I explore in depth the various aspects of the NGX 9/8/7/600 series, but once that familiarisation process is is complete I look forward to looking through and deploying the fruits of your MD11 labours. Most sincere thanks, Brian
Posted 14 February 2012 - 05:20 PM
Hi Stuart!This is really great work!!! Many thanks!I haven't had look closely into the script (way toooo huge ), so just one question:have you kept the old function names from the initial 1.1 version?Or have you changed this all completely?I ask, because users of current 1.1 have to change their assignments if YOU have changed the function already existing function names....And I have to point that out when I upload your work here as version 1.2
Posted 14 February 2012 - 08:11 PM
HiI am sorry but I did not keep the original function names, no.When I re-organised the file structure to reflect panels on the PMDG MD11, I changed function names so that (i) I could easily trace them back to the panel within which they are located on the sim (ii) they meant something (to me) and (iii) mostly "fitted" the drop down menu when looking to assign a function to a button, switch or knob on the MCP or yoke.I must admit I was not originally thinking that anyone else would be interested in what I have done so did not think this particular aspect through.However, when I posted the file earlier today this was why I made the comment "..... and also made some changes so that functionality, information display and use is handled in a way that I liked and found easy to use." For example, my MCP does not continuously display current flap positions but rather defaults to current VVS and only shows flap or DAF when the function is called.This does mean that someone may not be able to simply copy this file for their own use and I do imagine that this will mean some additional work from your perspective for which I am sorry.However and as I also said earlier, it does not prevent anyone from copying and pasting what they may need in order to add specific functionality to their own MD11 actions file.RegardsStuart
Posted 21 February 2012 - 09:24 AM
HiFound some additional functionality whilst looking for the ADG "controls".Mainly in the area of Capt. side SISP, FO side Oxygen panel, Capt. side Coms Radio, the alternative Centre/Main Gear controls and the aforementioned controls to deploy the ADG.Txt file attached.Same comments as previous apply.RegardsStuartThis time the file...........
Posted 21 February 2012 - 10:39 AM
The new section works great, many thanks for this as always.I was trying to work out the other day how to gain a little more functionality from my yoke and you have provided me with the answer. :Peace:I am however a little confused by the reference to a TH4 in the final function of this new section?RegardsStuart
Updated to v1.2added reverser section
Edited by eeyore, 21 February 2012 - 10:44 AM.