Jump to content

Search the Community

Showing results for tags 'LUA'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • Flight Planning
    • Virtual Reality (VR) Hardware and Games
    • Letters to the Editorial Staff of AVSIM
    • 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 Reviews Feedback
    • The File Library General Forum
    • Flight Sim & Aviation User Stories
    • In Memoriam of Tom Allensworth
    • In Memoriam
  • Microsoft Flight Simulator Forums
    • Microsoft Flight Simulator (2020)
    • MS FSX | FSX-SE Forum
    • The Microsoft Flight (2012) 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
    • FSX | P3D Missions Forum - How To
    • FSX/FSX-SE Aircraft and Panel Design Forum - How To
    • FSX | FSX-SE Scenery Design Forum - How To
    • The Paint Shop - The Aircraft Painter's Forum - How To
    • Mesh Scenery Design - How To
    • 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
    • The X-Plane General Discussions Forum
    • X-Plane Tips and Tricks
  • The IPACS Aerofly Forums
    • IPACS AeroFly FS2
  • Helicopter and Rotor Head Forum
    • Rotor Head Archive
    • Rotory Winged & Helicopter Flying
  • Simulator Screen Shots, Real Aviation Photos, & Videos
    • The AVSIM Screen Shots Forum
    • Real Aviation Photos
    • Aviation and Flight Sim Video Forum
  • Hardware & Operating Systems Discussions
    • WIN11 OS Forum
    • WIN10 OS Forum
    • WIN8 OS Forum
    • The Win7 OS Forum
    • System Hardware: PC | MOBO | RAM | CPU | HDD | SSD | PSU etc
    • Video Hardware: Monitors | Multi-Monitors | Video Cards | Drivers etc
    • Hardware Controllers: Joysticks/Yokes | Throttle Quads | Rudder Pedals | Drivers etc
    • Networks | WIFI | Routers | Ethernet | DSL | Cable Modems
  • Commercial Support Forums (Hosted by AVSIM)
    • FS2Crew Support Forum
    • Mindstar Aviation Support Forum
    • The RealityXP Support Forum
    • The Official DX10 Scenery Fixer Support Forum
    • The Multi-Crew Experience (MCE) Support Forum
    • Lorby-SI Support Forum
    • Pilot2ATC Users Forum
    • The Carenado Support Forum
    • The Alabeo Support Forum
    • Aviasoft Remote CDU for Phone / Tablet Official Support Forum
    • Airline2Sim Support Forum
    • SX Airport Design Forum
    • SimSettingsManager Official Support Forum
    • simFDR General Support Forum
    • Blue Sky Star Simulations Support Forum
    • Capt. PERO Support Forum
    • Flysimware Forum
    • Mid-Atlantic Air Museum Simulations Support
    • FSReborn Series Support Forum
    • Desk Pilot - Shared Cockpits
    • PhotoSim Labs - Bahamas sceneries
    • Fulcrum Simulator Controls
    • The PILOT'S Support Forum
    • Stick and Rudder Studios
    • Honeycomb Aeronautical
    • SimFly Pad Support Forum
  • User-to-User Support Forums
  • Freeware Support Forums
  • Virtual Airlines News and Discussion
  • Home Cockpit Builders
  • Other Civil Aviation Simulators
  • International Language Forums
  • Other Forums

Categories

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

Blogs

  • Tom Allensworth's Blog
  • Gaiiden's Scroll
  • Brandon's Blog
  • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


About Me


About Me

Found 7 results

  1. Hi all, I am currently in the process of building a LINDA Module for the new Captain Sim 757 III. I have recorded all LVAR data and have been able to use it for switches and buttons with the VRInsight MCP Combo 2 (Boeing). However, my problem lies with displaying SPD/IAS, HDG, ALT and V/S information on the VRInsight LCD Display and using the various rotary dials. When I try to add code for them, the dials don't respond and nothing appears on the LCD Display. I've been able to display SPD/IAS, HDG and ALT when LINDA is first loaded and the MCP boots up, but that's it. Does anybody have any example script they can give me to start me off? I'm a fast learner! I've been looking at other modules to help get an idea of things, but still need someone to identify and explain certain things. Many thanks for any help - I'm eager to write it all as soon as possible! Pete
  2. Hello, I made a Cessna Home cockpit and to make it works with A2A C182 & C172 I need to make a LUA Script with A2A LVAR. Because I don't know how to code on LUA, I'm cherching a developper for a LUA mission. You can contact me on MP to discuss the modality and the prices. Waiting for your answer Ludo
  3. Hey there. Having copied the HDG Bug code (hdg plusfast & hdg minusfast) which allows a fast spin of a physical encoder and works a treat, I am completely baffled why the Fast Spin code below for VOR1 - VOR2 & ADF will not work, any ideas / help please. I confirm that the normal calls work (VOR1_plus (and minus) | VOR2_plus (and minus) ADF_plus (and minus) but they are painfully slow. I have used the User.lua to enter the code in to Linda 3.0.9 v2 (FSUIPC is up to date) Shut Linda down and restarted no luck. Many Thanks Roger PS Sorted now - I had forgotten to set the variables.. see below -- ## Rotaries functions -- ## VOR1 --Orignal function _VOR1_OBI_DEC (p) ipc.control( 65662, p ) end --Orignal function _VOR1_OBI_INC (p) ipc.control( 65663, p ) end function VOR1_plus (a, b, c) if c == nil then _VOR1_OBI_INC () return end sync_vor1 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor1) end function VOR1_plusfast (a, b, c) if c == nil then for i = 1, fast_vor1 do _VOR1_OBI_INC () end return end sync_vor1 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor1) end function VOR1_minus (a, b, c) if c == nil then _VOR1_OBI_DEC () return end sync_vor1 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor1) end function VOR1_minusfast (a, b, c) if c == nil then for i = 1, fast_vor1 do _VOR1_OBI_DEC () end return end sync_vor1 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor1) end -- ## VOR2 -- Orignal function _VOR2_OBI_DEC (p) ipc.control( 65664, p ) end -- Orignal function _VOR2_OBI_INC (p) ipc.control( 65665, p ) end function VOR2_plus (a, b, c) if c == nil then _VOR2_OBI_INC () return end sync_vor2 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor2) end function VOR2_plusfast (a, b, c) if c == nil then for i = 1, fast_vor2 do _VOR2_OBI_INC () end return end sync_vor2 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor2) end function VOR2_minus (a, b, c) if c == nil then _VOR2_OBI_DEC () return end sync_vor2 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor2) end function VOR2_minusfast (a, b, c) if c == nil then for i = 1, fast_vor2 do _VOR2_OBI_DEC () end return end sync_vor2 = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_vor2) end -- ## ADF -- Orignal function _ADF_CARD_DEC (p) ipc.control( 65882, p ) end -- Orignal function _ADF_CARD_INC (p) ipc.control( 65881, p ) end function ADF_plus (a, b, c) if c == nil then _ADF_CARD_INC () return end sync_adf = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_adf) end function ADF_plusfast (a, b, c) if c == nil then for i = 1, fast_adf do _ADF_CARD_INC () end return end sync_adf = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_adf) end function ADF_minus (a, b, c) if c == nil then _ADF_CARD_DEC () return end sync_adf = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_adf) end function ADF_minusfast (a, b, c) if c == nil then for i = 1, fast_adf do _ADF_CARD_DEC () end return end sync_adf = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_adf) end -- ## DUPLICATE HDG BUG function HDG_plus (a, b, c) if c == nil then _HEADING_BUG_INC () return end sync_hdg = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_hdg) end function HDG_plusfast (a, b, c) if c == nil then for i = 1, fast_hdg do _HEADING_BUG_INC () end return end sync_hdg = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_hdg) end function HDG_minus (a, b, c) if c == nil then _HEADING_BUG_DEC () return end sync_hdg = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_hdg) end function HDG_minusfast (a, b, c) if c == nil then for i = 1, fast_hdg do _HEADING_BUG_DEC () end return end sync_hdg = round(c / 360 * 65536) ipc.writeUW(0x07CC, sync_hdg) end
  4. 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
  5. 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!
  6. I would like to request for consideration to the next 737NGX SP that there be put in place programmable keys to operate each door on the airplane. Yes, you can do it from within the 2 page "DOORS" area on the FMC/CDU unit. That's convoluted as opposed to being able to assign key commands to operate each door separately, and why not include a "close all doors" and "open all doors" while we're dreaming?Folks who use one way or another to control the airplane with hardware could then assign button commands using Linda or FSUIPC or simply manually hit the key combos to open the doors, instead of having to plow through the FMC/CDU and mouse-click.It's a "LITTLE" thing that could make a "BIG" improvement for those of us with older eyes who prefer to press an actual button or switch in lieu of precisely placing the mouse on the FMC.Just hoping, is all.That said, doff of the cap to the NGX. AMAZING airplane, only one I fly. Stunning achievement in every way.Robert
  7. 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
×
×
  • Create New...