Search the Community

Showing results for tags 'LUA'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • New Member Forums
    • Welcome New Members!
    • Help Using the AVSIM Forums
    • Help Creating an AVSIM Account and Logging on to AVSIM
  • AVSIM Fixed Based Operations (FBO)!
    • Hangar Chat
    • Virtual Reality (VR) Hardware and Games
    • Letters to the Editorial Staff of AVSIM
    • In Memoriam of Tom Allensworth
    • All About Us
    • Crash To Desktop (CTD) Forum
    • The Bargain Hunter's Shack
    • Classified Ads | Want Ads | Swap Meet
    • AVSIM's Round the World Race Forum
    • AVSIM User Surveys and Opinion Polls Forum
    • Review Feedback
    • The File Library General Forum
    • The Focus on Freeware Forum
    • Flight Sim & Aviation User Stories
    • In Memoriam
  • FlightSimExpo 2018
    • FlightSimExpo 2018 Discussions
  • FlightSimCon 2018
    • FlightSimCon 2018 Discussions
  • Microsoft Flight Simulator Forums
    • MS FSX | FSX-SE Forum
    • The Microsoft Flight Forum
    • The FS2004 (FS9) Forum
    • Flight Simulator Tips and Tricks
    • Shared Cockpits | Multi-Player Forum for FSX | FSX-SE | P3D
    • MS FSX | FSX=SE | P3D Simconnect Forum
    • MS FSX Missions Forum
    • MSFS Aircraft and Panel Design Forum
    • MSFS Scenery Design Forum
    • The Paint Shop - The Aircraft Painter's Forum
    • Mesh Scenery Design
    • The TerraBuilder Forum
    • TTools for MSFS Forum
    • Add On Developer's Forum
    • DX-10 Discussions, Hints and Help
  • The Prepar3D Forums
    • The Prepar3d Forum
    • Prepar3D Tips, Tricks and How To's
  • The X-Plane Forums
    • X-Plane Tips and Tricks
    • The X-Plane General Discussions Forum
    • The X-Plane Scenery Forum
    • The X-Plane Aircraft & Panel Design Forum
    • X-Plane Addons
    • X-Plane Add-On Developer's Forum
  • The Dovetail Games (DTG) Flight Simulator Forums
    • The Dovetail Flight Sim World
    • The DTG Flight School Forum
  • Screen Shots, Videos & The Gallery
    • The AVSIM Screen Shots Forum
    • Real Aviation Photos
    • Aviation and Flight Sim Video Forum
  • Hardware & Operating Systems Discussions
    • WIN10 OS Forum
    • WIN8 OS Forum
    • The Win7 OS Forum
    • MOBO | RAM | CPU | HDD | SSD | Desktops | Laptops
    • Monitors | Multi-Monitors | Video Cards | Drivers
    • Hardware Controllers | Joysticks | Drivers
    • Networks | WIFI | Routers | Ethernet | DSL | Cable Modems
  • Commercial Support Forums (Official)
    • The PMDG Support Forum
    • FS2Crew Support Forum
    • FSFX Packages Support Forum
    • Mindstar Aviation Support Forum
    • The RealityXP Support Forum
    • Fly the MaddogX Support Forum
    • The Official DX10 Scenery Fixer Support Forum
    • Virtual Avionics Support Forum
    • Lorby-SI Support Forum
    • Pilot2ATC Users Forum
    • Icarus Development Forum
    • Remote CDU for Phone / Tablet Official Support Forum
    • Airline2Sim Support Forum
    • SX Airport Design Forum
    • P3D Tweak Assistant (PTA) and RealismShaderPack
    • The simPlugins Support Forum
    • SimSettingsManager Official Support Forum
    • simFDR General Support Forum
    • Blue Sky Star Simulations Support Forum
    • Capt. PERO Support Forum
    • The SkyPilot FSXAssist | P3DAssist Support Forum
    • Flysimware Forum
    • Mid-Atlantic Air Museum Simulations Support
    • Jane Rachel Whittaker - Blue Sock Studios Support Forum
    • FSReborn Series Support Forum
  • Commercial Support Forums (Unofficial)
    • Photo Scenery Support Forum
    • The Carenado Support Forum
    • The Alabeo Support Forum
    • The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support Forum
    • The OpusFSX Forum
    • The FTX | ORBX Support Forum
    • The Multi-Crew Experience (MCE) Support Forum
    • The Captain Sim Support Forum
    • Lionheart Creations Forum
    • The Majestic Software | Dash 8 Support forum
    • The Commercial Level Simulations (CLS)
    • The AeroSim Support Forum
    • The VOXATC Support Forum
    • The I-Fly Support Forum
    • The MILVIZ Support Forum
    • Radar Contact Support Forum
    • The Level D 767 | Wilco PIC 767 Forum
    • Infinite Flight Forum
    • The Wilco B737 Support Forum
    • Night Environment | Black Marble | Blue Marble Forum
    • The SIM720 Forum
    • Infinite Scuba Simulation Forum
  • Virtual Airlines News and Discussion
    • VA News and Announcements
    • VA World!
  • Other Civil Aviation Simulators
    • Terminal Reality's FLY Series
    • FLY! Legacy
    • The Rise of Flight General Forum
    • The AeroFly Simulator
    • The Outerra 3D Planetary Engine
    • The Flight Unlimited Series
    • The ProPilot Forum
    • The FlightGear Forum
  • Digital Combat Simulators (DCS) Forums
    • DCS World!
    • The DCS P-51 Mustang Forum
    • DCS A-10C Warthog
    • DCS Black Shark
  • Combat Flightsims
  • General Combat Flightsims
  • Falcon 4 - Allied Forces
  • Flight Schools
    • The Flight School Hangar
    • So You have Solo'd
    • Preflights
    • Weather - Understanding It and Safe Flight
    • Flight Planning
    • Mountain Flying
    • Float Plane Flying
    • Rotory Winged & Helicopter Flying
  • Freeware Support Forums
    • General Freeware Discussions
    • Ready for Pushback Forum
    • Little Navmap | Little Navconnect | Little Logbook Support Forum
    • The ProController and Squawkbox Support Forum
    • The VATSIM | vPilot | FSInn Support Forum
    • The Sweet FX Support Forum
    • Terminal Procedures Forum
    • The TinMouse Forum
    • The TileProxy Project Forum
    • LINDA
    • Desk Pilot
    • Mario Noriega Designs
    • The FS9 Evolution Forum
    • SimLauncherX
    • FreeMeshX Global Support Forum
    • FSLaunchPad
    • PSXseeconTraffic for FSX | P3D
  • International Language Forums
    • Deutsches Forum fuer die Flusi Gemeinde
    • Türkler için Flight Sim forumu
    • Forum de la Communauté francophone de Simulateur de vol
    • Foro de vuelo virtual en español
    • Forum della Comunità Italiana di Flight Sim
    • O fórum em português
  • Other Forums
    • The Unofficial PSS Forum
    • 777 Studios!
    • Russian Flight Simulation and Aviation
    • Drawbridge Designs Forum
    • VictoriaPlus [Canada] Scenery Forum
    • Other Flight Simulation Software
    • Helicopter and Rotor Head Forum
    • Orbiter and Space Sims
    • Home Cockpit Builders
    • Racing Fools Forum


  • Articles
  • AVSIM News
  • File Library News
  • AVSIM Reviews
    • Hardware
    • Aircraft
    • Scenery
  • Product Announcements & Press Releases
  • What's New @ AVSIM
    • Contests
  • Interviews
  • AVSIM Editorials
  • Guest Editorials
  • Obituaries


  • New Features
  • Other


  • AVSIM Publications


  • Tom Allensworth's Blog
  • Gaiiden's Scroll
  • Brandon's Box
  • Jess B's X-plane blog thingy
  • Tom_Test's Blog
  • Alpha Floor's Logbook
  • GolfPilot
  • adi518's Blog
  • Chase's Blog
  • The Big Tour
  • Tales of a Wannabe Pilot
  • Farmer Looking Skyward


  • I need help with the AVSIM Site...
    • Name
    • E-Mail
    • IP Address
    • Details
  • Submit News or a Press Release
    • Your name
    • Your Email Address
    • Link to URL
    • News Category
    • News Item

Found 20 results

  1. Hello all, Just a little something that I thought I would share with you all. if you're interested in seeing how hard your landings are (for *every* landing!) here's a little Lua script for FSUIPC (I believe you need the payware version for it to work!) I can't take full credit for it, as I found the basic version elsewhere. I just added a few lines here and there. Basically, every time you land a little box will pop up at the side of the screen showing you how hard your touchdown is in Feet Per Minute. The box will then disappear after 15 seconds. Simply copy this code into a text file and save it as "ipcReady.lua" in your FSX/P3D Modules folder. Start the sim and get practicing! ipc.setowndisplay("FPM", 0, 60, 6, 1) function logvs(off, val) if val ~= 0 then -- if on ground flag just set, get VS, convert it and log it vs = ipc.readSD(0x030C) --original was 030C then 31A0 vs = vs * 60 * 3.28084 / 256 ipc.log("Vertical speed at touchdown = " .. math.floor( (vs * 10^2) + 0.5) / (10^2), 5) ipc.display(math.floor( (vs * 10^2) + 0.5) / (10^2), 15) end end -- set to call above routine whenever "on ground" flag changes event.offset(0x0366, "UW", "logvs") Hopefully some people can add some additions and we can improve it together!
  2. Hi. New to Lua and programming in general, am I right in assuming that the function name can be anything I choose that is descriptive of its use? also I am trying to figure out why my code below wont work, nothing happens when I programme a switch on my X-55 with it. I used the LInda Tracer to find the Lvar relevant to opening the cockpit side door on the A2A Spitfire, and (after un-pausing FSX-S) the door opens by a command sent from the Linda Tracer "Set Value" Toggle (Shift+Ctrl+Alt+F10). Any help much appreciated. Linda 2.9.2 (487) Module: - A2A Spitfire (User) FSX-Steam Registered FSUIPC Windows 10 (1607 - Build 14393.693) -- %% Side Door function SPIT_Side_Door_Open () LVarSet = "CockpitSideDoor" ipc.writeLvar(LVarSet, 1) end function SPIT_Side_Door_Close () LVarSet = "CockpitSideDoor" ipc.writeLvar(LVarSet, 0) end -- ## ############### OR put in a simpler way (I think?) -- %% Side Door function SPIT_Side_Door_Open () ipc.writeLvar(CockpitSideDoor, 1) end function SPIT_Side_Door_Close () ipc.writeLvar(CockpitSideDoor, 0) end -- ## ############### Many Thanks Roger
  3. Hallo, ich möchte mir für die Phenom 300 von Carenado ein G1000 MFD- und PFD-Panel bauen. Meine Überlegungen gehen dahin, dass ich z. B. die Softkey12-Taste auf meinem gebauten Panel drücke und dieser Tastendruck so interpretiert wird, als hätte ich mit der Maus auf eben diese Softkey12-Taste im FSX geklickt. Dazu müsste ich aber die Koordinaten des Mauszeigers auf den einzelnen Tasten kennen. Ich stelle mir vor, dass mir die z.B. als Tooltip oder in einem kleinen Fenster beim darauf Klicken angezeigt werden. Das soll u. a. mit LUA gehen. Hier gibt es den "mouse.getpos(x,y)" Befehl. Ich habe damit schon herum probiert, bekomme es aber einfach nicht hin. Es wäre super, wenn mir jemand, der sich mit LUA auskennt dabei helfen könnte. Hier mein Versuchs-Script: --Koordinaten des Mauszeigers printx = 0 printy = 0 function MausKoordinaten(x,y) mouse.getpos(x,y printx = x printy = y end if ==1 then print("PosH: " ..printx, "PosV: " ..printy) end if Alternativ könnte nach betätigen der Taste an meinem gebauten Panel das Ereignis ausgeführt werden, dass sich hinter der Softkey12-Taste im FSX verbirgt. Dazu müsste ich aber herausfinden wie das jeweilige Ereignis heißt, damit ich es dann per LUA-Script aufrufen bzw. anstoßen kann. Ich habe gesehen, dass in den XML-Dateien des Gauges verschiedene Makros enthalten sind. Vielleicht können die ja via Lua und Parametern angestoßen werden. Da es sich hier um ein XML-Gauge handelt, entfällt die Möglichkeit des Mausmakros über FSUIPC. Und über LINDA und Log vars.lua bekomme ich nicht alle LVars heraus. Hat jemand eine Idee wie ich hier vorgehen könnte? Besten Dank im Voraus für Eure Hilfe. Holger
  4. I thought some of you might be interested in this new LUA file that is available for the TFDi 717. The hard work was done by a user called @Skipy, who used the FSUIPC event logging to gain all of the MCP's FSUIPC Event IDs. I just tidied up his work in progress and tested it in FSUIPC. :smile: As long as you own FSUIPC Registered version, with this LUA script you can assign keyboard commands to the 717's MCP - all functions work (mode buttons, -/+ knobs like the heading knob, etc), with the exception of the PROF button. This should also help users who use hardware such as the GoFlight modules, that can work with keyboard commands. Cheers.
  5. I suffered a lot of pain after receiving my very fine Thrustmaster Hotas Warthog - in terms of figuring out how to configure it, how to get FSX to see it even after I had disabled all control surfaces WITHIN FSX, and how to solve difficult problems like separately controlling left versus right engines, achieving proper max and IDLE thrust, and getting the REVERSERS to come on when I lift and then pull back the throttles past their "IDLE" position (and pull them further towards me).So I am beginning this thread as a roundtable for other Warthog drivers to share their experiences and nuances of the control surfaces, and how they interact with FSX and other Flight Sim products.Topic 1 - GETTING the AXES recognized in FSUIPC (after first DISABLING all your controllers within FSX by unticking them on the setup page of FSX) Start FSX Select your typical aircraft (in my case the PMDG 737NGX) From the top menu in FSX, click on OPTIONS, then SETTINGS, then Controls as shown in this picture:You'll see the following image (This picture shows the FSX controls box AFTER I have un-ticked (DE-selected) controllers (Joystick, Throttle, and SAITEK rudders))Plain ENGLISH! Make sure there is NO CHECKMARK in the box next to the words "Enable Controllers" They won't respond now until you set them up in FSUIPC as outlined further on in this topic.From the menu bar across the top of your screen in FSX, click "ADD-ONS" then click FSUIPC (registered version)Tip: There is a MISCELLANEOUS tab in FSUIPC, click on it:I would recommend you check the boxes as I have them (you can take note of what they are before you begin to change them, if you don't like the results it's easy enough to revert them back.After checking the boxes click OK button at bottom of the FSUIPC miscellaneous window to accept your changes. The Control Spike Elimination is particularly important for the Rudder, Elevator and Ailerons.If you use REX for realtime weather, you may want to consider altering the WINDS settings within FSUIPC, but I won't delve into that here as it's a tad off topic.Next, click on the Axis Assignment tab in FSUIPCSplit the throttles on the WARTHOG (pull the silver magnetic switch on the back side of the throttle handle fully left and the two throttle handles will operate independent of each other. Move ONLY the left throttle handle whilst you are in FSUIPC- you see:on the lower left where it says "Type of action required" be sure "Send direct to FSUIPC Calibration" radio button is selected.Then in the drop down box select Throttle 1 and put a checkmark next to it then click OK.After clicking OK FSUIPC will close. Restart it from within FSX and repeat the process with the RIGHT throttle handle. If the JOY# and AXIS# boxes aren't blank, clear them by pressing the CLEAR then the RESCAN buttons in FSUIPC. THis time select Throttle 2 as shown below:Notice the JOY# is the same (JOYSTICK1) but the axis letters are different between LEFT and RIGHT throttle controls!Now that these are selected you can proceed into the calibration tab within FSUIPC and thence to FSUIPC.INI file but more on that in a moment. Note the picture above, the default range for the throttles is -16384 to +16384 That is the rub. If you don't edit these to allow for a dead zone at the bottom end, your thottles will not reach IDLE THRUST properly and you'll experience major pain trying to land at too high a speed!So first go ahead and calibrate them by clicking on the CALIBRATION TABYou see:CRITCALLY IMPORTANT! Put a tick in the checkbox marked "No Reverse Zone" (Why? Because you want the REVERSERS to be controlled by YOU, when you LIFT the throttle handle UP whilst pulling it further back, (after configuring LINDA) your thrusters will work as you want them - NOT come on before you intend them to! Especially important whilst landing and not yet on the runway, yeah? I spent a LOT of time not KNOWING this trick! Hope it helps YOU and if you have a WARTHOG it will!If you don't have a warthog, you'll have to determine some other switches to assign for reversers but that's OFF TOPIC here.Note the ranges above- they are much SMALLER than the default range assigned by FSUIPC. I edited them in the FSUIPC.INI file looks like this: Plain English tip: AFter you first calibrate the controls, then after opening the FSUIPC4.ini file (it is in the MODULES folder of your FSX directory) using NOTEPAD, you will need to MANUALLY change the values (make each of them smaller to create the "DEAD ZONES" i am speaking about. For example, if a control has an existing calibration range of -16384 to +16384 you can select -15500 and +15500 instead then save the file. This will give you some 'headroom' at both the top and bottom range of the given control axis so that things will operate "as expected" - particularly important for THROTTLES and BRAKES. If you fly SAITEK rudders (Combat or regular) you MUST check REVERSE in the configuration window of FSUIPC, because the controls for brakes on Saitek rudder are programmed 'backwards' and when fully depressed your brakes will RELEASE and when fully released they will lock up which is BAD NEWS. You need to enable "REVERSE" operation and then the Saitek brakes will work as you wish. Plus, you also need to create HEADROOM on both the top and bottom ranges of your BRAKES for the same reason... so they fully release and fully engage when you want them to. If you don't create a dead zone, they will sometimes hang up or not move fully up or down, and unexpected results may occur whilst in flight.Worst case you can copy my settings they should work fine for Throttle1 and Throttle 2. You will still get max thust and min thrust, but you'll have headroom (dead zone) at the top and bottom of the throttle throw range so you will achieve full IDLE thrust upon landing and MAX takeoff thrust on takeoff.Many of you have discovered the wonderful interface button assignment tool called LINDA, here are my Linda settings unshifted and shifted (Throttle) and then the Joystick (which I use sparingly, because most of the buttons on the joystick I use to control camera views in EZDOK.Unshifted (2 views to cover all button assingments) Shifted 2 views Joystick 1 view (5 images total)JOYSTICK:What works for me is the LANDING LIGHTS run off ENGL toggle, The Taxi Lights run off FLOW R toggle, ENG OPER L increases all inside dash lights whilst I hold in UP position APU Start switch actually starts the APU (no can of corn, see above programming steps) and when you throw it the opposite way, it swaps from ENGINE GENERATORS to APU GENERATORS (thus allowing you to kill the engines when shutting down and deplaning passengers). Shift the Global Joystick button and lift ENG OPER L switch kills Left engine Lift R switch kills right engine (you must hold the SHIFT button on the joystick down to enable this due to how I programmed - why? Prevent killing engines whilst airborne. Yeah?L/G Warn is Parking Brake toggle. Autopilot engage/disengage does that, the Main A/P. RDR ALTM toggles HUGS display up and down. PATH engages LNAV ALT engages VNAV.The hat switches on the throttle adjust CRSE left and right, ALTITUDE and HEADING. The sliver side switch (left side) gear UP and gear down. The silver slide switch topmost right side pull towards you sounds passenger alert chime push away from you toggles the JETWAY. Middle silver button, pull toward you deploys airbrakes to 50% (max detent during flight) return to center turns off spoilers. Push fully forward ARMS spoilers for landing (but does not deploy them). Red bottom side switch pull towards you toggle A/P CMD A push away from you toggle A/P CMD BThe right rotator grey switch I use FSUIPC to set that axis for FLAPS. On the 737 it works perfectly. Centered is 10 degrees, fully down is 40 and fully up is 0. Try it. AMAZING.You may wish to assign things differently, but the great thing about LINDA is it's simple to use. Get version 1.11 (free from AVSIM). Consider donating to LINDA if you like it. A LOT of work went into it and it now supports up to 10 joysticks.Tip: The Logitech G13 keypad is NOT, repeat NOT recognized or supported by LINDA. It won't work because LINDA sees it as a KEYPAD not as a JOYSTICK.I hope this topic saves some of you a lot of the pain I encountered. Be aware that FSUIPC REGISTERED version is required, the free version won't do what you need it to do AFAIK. They constantly update software, be sure you have the latest versions. FSUIPC and LINDA both "live" in your FSX MODULES folder.It's wise and critically important to do frequent regular "rotating" backups. Get a good backup program, be sure you understand not only how to back up, but how to RESTORE (from your backup) and how to 'test' your backup to be sure your system can "READ IT" (iow, it's not "corrupt"). I personally like ACRONIS True Image Home 2011, they have 2012 out now. It's not super intuitive, but it's pretty strong and it will send you emails to notify when jobs complete, and it can turn your system off after the backup finishes.Keep the blue side up!Robert
  6. Hello, Could you help me please ? How can i use functions who are in actions.lua through FSUIPC ? actions.lua from : Example in FSUIPC : Key presses : SET : CTRL + J >>> NGX_PUMP1_AFT_toggle or Buttons + Switches : SET : 1 >>> NGX_PUMP1_AFT_toggle Thanks for help. PS : i have create a specific FSUIPC macro for the test, but i dont want do this for each function. PMDGBaseVar = 0x00011000 -- 69632 PMDG_ClkL = 0x20000000 -- 536870912 PMDG_ClkR = 0x80000000 -- -2147483648 PMDG_dec = 0x00002000 -- 8192 PMDG_inc = 0x00004000 -- 16384 PMDG_RelL = 0x00020000 -- 131072 PMDG_RelM = 0x00040000 -- 262144 PMDG_RelR = 0x00080000 -- 524288 function NGX_PUMP1_AFT_off () if ipc.readLvar('ngx_switch_37_a') ~= 0 then ipc.control(PMDGBaseVar+37, PMDG_ClkR) DspShow("PMP1", "Aoff") end end function NGX_PUMP1_AFT_on () if ipc.readLvar('ngx_switch_37_a') ~= 100 then ipc.control(PMDGBaseVar+37, PMDG_ClkL) DspShow("PMP1", "A on") end end if ipc.readLvar('ngx_switch_37_a') == 100 then NGX_PUMP1_AFT_off() else NGX_PUMP1_AFT_on() end PS : i have also test an include in lua MACRO file !? But dont still work ? require("scripts.actions") NGX_PUMP1_AFT_toggle() end Thanks for advance; Sky
  7. LINDA employs LUA 5.1 as the engine to interpret the LUA code used my LINDA and its modules (see \modules\linda\lua). The current version is LUA 5.3 which is only available as C++ source code via Are there any LINDA users familiar with C++ who could assist me in creating a new updated LUA distributable package?
  8. Hats Off to Linda!The finest add on since FSUIPC! If you have a set of controllers with mulitple buttons (Joysticks, Throttles, Etc) you want to TRY OUT LINDA!It's the best! Why? Simple to set up and use, easy to debug (if needed) and GREAT online support!My Thrustmaster Hotas is 2x as good because LINDA offers Assignable SHIFT controls, local and entire device. So I can "Shift" the buttons just on my Throttle and the ones on the Joystick are left undisturbed. Thus the 22 buttons on the throttle become 44.In my case I use the shifted throttle buttons to kill Engines 1 and 2 on my 737NGX. Thus I cannot 'accidentally' kill an engine while in flight!It's great to be able to assign toggle switches to put the HUGS up and down, and I use the grey slide lever on the right side of throttle plate to control the PMDG Flaps - works a treat. Other buttons allow quick set of CRSE, ALT and HEADING. Landing Lights (Main) Landing Lights (Taxi) Landing Lights (Runway Turnoff) are all on separate switches on the throttle console. Parking brake, Altimeter reset, Spoilers, and so on.What does this mean to you?The TM HOTAS Warthog can provide a level of immersion that is several notches above the plain vanilla controllers on the market, and at a lot lower price point than the upper-end hardware from PFC and GoFlight.I highly recommend you try LINDA. I am going to donate to them!
  9. I don't know if this is the correct section to post. I'm modifing/editing a LUA plugin in FSX:SE, so when I change and save the .lua file I need to test it in FSX:SE (I use FSUIPC to start .lua plugin via keypress). Every time I want to test modifications I have to exit FSX and reload it, so is there a way to avoid it and test my edited plugin? Thanks a lot
  10. First of all, with MouseClicks you can solve many common problems. Just try with a Lua-Script to Start or Close Engines for the PMDG NGX 737 or try to open the Terrain MAP + Terrain Height on the ND Instrument in automatic. With MouseClicks you can do it. MouseClicks will be available very soon. When MouseClicks Hook-System is activ (intercepting Keyboard) you can still use the Keyboard for other Functions that are not assigned to a Click-File. MouseClicks in NOT connected to any Game or else. You can use it for any Game or else. MouseClicks is including a "Key.txt" File with 47 special Keys/Char you can change for different Keyboards. MouseClicks is executing like the Pilots Hand is moving. Create MouseClicks Files This example is a ClickFile for PMDG NGX 737 The Pilot movements for selecting the Terrain-Data on the ND-Instrument. It seems complicated but it isn't. 1. We create the MouseClickFile or only a Keyboard File Show Terrain_On_Off on the ND Instrument. --- From any actual View switch to the 2D-Panel {F10} --- execute Keyboard Keys --- MouseClicks are executed on the EFIS Control Panel like a Pilot would do. Selecting the MAP ND-View, Selecting Terrain Height(click on center-knob) then click on [Terrain]. --- The ND Instrument is now showing the Terrain Display with the Terrain-Map and the Terrain-Height if both are selected/included. 2. a) We add (View 1) a Joystick-Nr or any Joystick Button Combination. B) We add (View 1) 1 or several Keyboard Keys or Key-Combinations; normally we use a) or B). Joystick number-values are assigned in automatic using 1 or more Joy-Buttons together. 3. With View (2) we can execute any File using the Mouse > click on a Filename. If a File is connected to the Joystick or Keyboard we can execute the File with View(2) or Joystick or KBD. Joystick connection 262144 - Terrain_On_Off is executed. DOORS Using a pure Keyboard File without Mouseclicks included. In this example we open the 2. Door. 1. Door opened (Shift + e) 2. Door is using (Shift + e) then, the delayed Key {2} FSX in Full Screen Just select the Keyboard Keys and save with View (1) Execute as separate File or within another File. Execute via Joystick or 1 Keyboard-Key only or just click on the FileName - View (2) Engine + Lights on Overhead Panel (shift + 6) - From any actual View you switch to any other Panel or Overhead in automatic. - ENGINE Start - ENGINE Stop - Overhead Panel is Fixed. - Execute each Mouseclick x Start or Close engines. Mouseclicks open Switch Covers, click on Switch, close Switch cover. Keyboard Keys a included within the ClickFile. Mouseclicks are executed in sequence like the Pilot Hand is doing. Intrasystem .
  11. Hello! I try to understand why the freewares that are around of Flight Simulator, as many exposes its source code, do not declare open source licenses. There are many scripts to run a same aircraft, and all the works, if were managed publicly in a version control system, Git repositories at GitHub, for example, it would be much better. Perhaps the fact of we are using Microsoft's closed APIs is a disincentive to look for a suitable license model. But I'm sure you can find it. There is the possibility of the Microsoft have interest in guide us about. Projects are already scattered around and she just needs to get more involved with them, taking the opportunity to make her open source marketing. What is my purpose with this topic? Do note that many individual development efforts exists and are being underused by the community. Failure to use licensing and of processes for efficient collaboration in coding are, in my view, the two main impediments. Sending codes in a forum is hugely disadvantageous if compared to having a open projects on GitHub. Projects for which I have looked when thinking these observations: LINDA, FSUIPC, SPAD and some Lua scripts for the aircraft Jetstream 41. Sorry my poor english. I speak portuguese natively. Alexandre Magno from Brazil
  12. I found a couple of great fsuipc LUA scripts to use with the NGX for those who use hardware throttles like the saitek, think one been mentioned before in a posting, but thought I'd create a single thread and republish for those new NGX users or lucky simmers that got hardware for Christmas. The first is a great LUA that allows you to easily set and control reverse thrust. Basically you can assign a throttle lever so that when you bring it all the way down past the detent on the saitek throttle hardware which activates the button it puts the engines into reverse, so now when you push the levers forward you are controlling the amount of reverse thrust, so operating just like a throttle lever but controlling reverse, dropping it back to idle disengages reverse and you have normal throttle control, so it's a more realistic way of having reverse. You can map this to one lever, or two levers if you use multiple levers to control each engine. To me it's a very good way of making use of your throttles to better mirror how it be in real life just without a physical reverse thrust lever to pull. Link Second one which comes with fsuipc and is in the LUA examples file, is a sync one. This is great for helping with correcting the issues that effect the throttle levers especially as they get older where although the physical position of two levers may look the same on your hardware, they haven't sent the same amount of travel to the sim so can find it hard to get your engines in sync. Basically it monitors the engines and if they not quite synced it automatically syncs them, it still allows you to apply different thrust to each engine(say for turns on the ground etc) due to the parameters it uses for out of sync. But it's a great tool for flying manually especially approaches and not finding you have varying thrust on each engine due joystick calibration issues. Combined with the LUA above it again excellent at ensuring you apply symmetrical reverse thrust. These have really enhanced my use of the NGX and hardware.
  13. Here is the first iteration in development of PM/Prosim module. What's done: Display sync with VRi MCP Combo All MCP Dials working (CRS/SPD/HDG/ALT/VS) CRS rotary works for both left and right course (press knob to toggle) Vertical speed indication (not tested, but should work) What's NOT done: NO BUTTONS ACTIONS NO EFIS ROTARIES ACTIONS Instead of that you can use the default FSUIPC assignments for Project Magenta. Go to the FSUIPC Buttons & switches control panel, tap VRi MCP button or turn the knob - it will be detected as joystick button press. Then mark the "Include Project Magenta" checkbox and select th desired action for this button or knob from the drop list. 1. Don't forget, that you should set both "Press" and "Release" actions in this panel for each button (...or else you will need to press each button twice to get action executed). 2. Don't forget, that you should remove any assignments made for VRi MCP dials inside FSUIPC, or LINDA will be unable to catch them. How to use: Assuming you have already installed LINDA and it works properly Download module: LINDA Project Magenta v0.1a (15 aug. 2011) Unzip both folders from Zip into: */FSX/Modules folder Run LINDA Choose "Project Magenta" aircraft from the droplist (switch off the FSX SYNC if it's enabled) Press "Edit" button Select your PM'ed or Prosim'ed aircraft folder from the list Save! (press "Edit") Run FSX and load your aircraft Check LINDA's console - it should say on some line: Module: Project Magenta Started... Now it should work - try to turn VRi MCP knobs and see if PM/Prosim reacts on your input Note: For some reason Prosim doesn't work on my system with FSUIPC offests. So the module was tested and working with time limited Project Magenta modules, but it should work with Prosim too, as they are using the same offsets for data exchange.
  14. Hi Folks I'm working on a mission/job for the airport's Job Boards. I need to inhibit my job from being generated at small airports with short runways I've populated GeneratedAirport - GeneratedAirport_Current with an appropriate MinRunwayLength value. Unfortunately that's not inhibiting my job's generation at small airports. Guessing that only the SimMissionUI.ScenarioMetadata and Career.CareerMissionMetadata are evaluated by the Job Board's script. I also had a brief play with / guess at a LUA script, in Career.CareerMissionMetadata - DisplayRequirements <CareerRequirements>return ( get_runway_length('{8D625BDF-2FF3-4583-9CC7-B70707AE5816}') >= 2743 ) </CareerRequirements> For test purposes - I've forced an increased frequency of generation. by temporarily raising the Career.CareerMissionMetadata - TemplateWeight to 5000. I also noticed a couple of unexpected aspects - - Very small airports consistently generate my jobs as a high proportion of total, whilst larger airports, (blue), only generate one or two. - Some specific airports consistently generate an unusually high number of these jobs. (e.g. Hoonah 7 or 8) Any pointers/tips would be much appreciated. Either by reply, or if required, PM me. ATB Paul
  15. With FSX, F2 is pressed and held to engage reverse thrust. FSUIPC4 can be programmed to assign a joystick or throttle quadrant button (I use the Saitek Throttle microswitch button) to brake the aircraft on landing. However, this cannot be used as a LINDA command as F2 opens the Lua Editor. Is there a FSX Command that can be used in Linda to activate reverse thrust?
  16. Hello everybody, while my FSX Standard King Air or even the Carenado B200 do make clear noises of the wheels while touching down, I did not hear anything with the B1900 - and it is not that I am such a good virtual pilot:) Is there a way to enhance or change the touchdown sounds - I know it is not a PMDG 737 but putting such a bird onto a runway really is confirmed through audio. Thank you! Al
  17. Has anyone written a LUA script for FSUIPC to add elevator trim sounds? I want to add a trim clacking sound to my Dassault Falcon 50 but not sure how to implement this via FSUIPC. Thanks Adam
  18. I have been thinking of building a nav/comm panel with a HD44780 LCD display driven by my Pokeys 56U. Problem is I have no idea how to send a character string to the device. I may be naive but I am sure that there are Lua scripts around to do this. My Googling has not yielded anything obvious. I favour Lua because I can easily run scripts from FSUIPC. Would anybody here know the answer? Thanks, Phil
  19. With Linda loaded and the PMDG 737NGX at the ramp. none of the switches assigned work. All works fine with default FSX aircraft. Looking at the Linda Console, it gives no errors, but I did notice that Linda was loading the Project Magenta Module instead of the PMDG 737 NGX one. There is no double assignement (checked, checked and double checked). If I assign function in the default FSX aircraft Module, it shows up in the Linda Console when the swich is flipped. But when I remove the assignment in the Default aircraft Module, and assign it in the PMDG Module, nothing happens. I have installed: Linda 1.11 PMDG 737NGX SP1c PMDG lua Module version 1.9 FSUIPC v4.91 (purchased) FS2Crew Pilots version for PMDG 737NGX (if that is of importance) Overhead panel switches connected through a Desktop Aviator pcb. I hope someone can shine a light on this. Thanks in advance for any positive feedback Manfred
  20. OK- I'm asking for some help. First, my hat is off and my wallet is about to open (to donate) to LINDA Developers! GREAT program, far better than the drivel that Logitech provides ("T.A.R.G.E.T.") or FSUIPC alone. As a budding PMDG 737NGX pilot I have been steadily climbing the hardware acquisitions ladder. At present Linda is joyfully controlling my 737NGX via my Logitech HOTAS Warthog Throttle and Joystick Combo. As an aside, I would love to have LINDA be able to fully recognize and implement the quite inexpensive Logitech G13 Gamepad. The G13 has 22 G-buttons and 3 Shift modes, that means about 66 buttons in total, plus an LED READOUT! and a mini-joystick. Linda "sees" this as a 1-button 0-hat device (wrong!). If it could be added to the list of supported gamepads for LINDA, I would personally donate $50 to Linda developers! How fair is that?I think LINDA is a very fine product and a HUGE addition to FSX.All encouragement to the developer team - and please add full support for the G13 as you have for the Warthog!Robert