ESzczesniak

Had a chance to test this now and it all seems to work. Thank you for your help!

I may not have explained this well. The same button pressed just once registers first under the physical hardware device, then a moment later under the virtual device created by the LUA. I have tested on the ramp, and it does not seem to matter if it's programmed through the physical hardware device or the virtual device. The only thing I haven't tested yet is trim, which is a repeat while held scenario. I will have to test this later and see.

Thank you! This is working now! What I think will be one last question. Now with this LUA running, buttons 1-32 register briefly as H 31 (H just happens to be the letter for this Yoke) and then 65 61 (65 I presume to be the virtual device). I currently have buttons 1-32 programmed under the "H" device, with only 33-35 under "65". Does it matter which device they are programmed under? For momentary contact buttons, it seems probably not. But what about "repeat while held" buttons? At least watching through FSUIPC, it seems there's a small, but noticeable delay from when H X is displayed to 65 Y populates through the LUA. Perhaps none of this matters, but I was just curious what the recommended process would be to avoid problems.

Thank you, and in short, no I had not found that section of the manual. Nor do I think the LUA is running still. To FSUIPC5.ini, I hadded [Auto] 1=Lua AlphaYoke The file AlphaYoke.lua is in the P3D\Modules folder. I do not get any effect utilizing these buttons over 32. My FSUIPC log file is below and I see the LUA referenced, but it says "malformed number" near the vendor ID: ********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFA1F600000 Windows 10 Pro 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0) Prepar3D.exe version = 4.4.16.27077 Reading options from "F:\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="Eric Szczesniak" User Addr="eszczesniak@gmail.com" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 0 System time = 21/10/2019 20:40:38 0 FLT path = "C:\Users\Eric Szczesniak\Documents\Prepar3D v4 Files\" 0 Using DialogMode 0 FS path = "F:\Prepar3D v4\" 78 ---------------------- Joystick Device Scan ----------------------- 78 Product= Saitek Pro Flight Quadrant 78 Vendor=06A3, Product=0C2D (Version 2.2) 78 GUIDs returned for product: VID_06A3&PID_0C2D: 78 GUID= {F308E0B0-E99E-11E8-8002-444553540000} 78 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 78 GUID= {F94A49A0-E99E-11E8-8003-444553540000} 78 Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 78 Product= vJoy - Virtual Joystick 78 Manufacturer= Shaul Eizikovich 78 Serial Number= 2.1.8 78 Vendor=1234, Product=BEAD (Version 2.24) 78 GUIDs returned for product: VID_1234&PID_BEAD: 78 GUID= {B47CD7A0-57D2-11E9-8002-444553540000} 78 Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 78 Product= Saitek Pro Flight Quadrant 78 Manufacturer= Saitek 78 Vendor=06A3, Product=0C2D (Version 2.2) 94 Product= MFG Crosswind V2 94 Manufacturer= MFG 94 Serial Number= MFG500001 94 Vendor=16D0, Product=0A38 (Version 33.1) 94 GUIDs returned for product: VID_16D0&PID_0A38: 94 GUID= {5D1C51B0-E843-11E8-8006-444553540000} 94 Details: Btns=2, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4096,U0,V0,X4096,Y4096,Z0 157 Product= Alpha Flight Controls 157 Manufacturer= Honeycomb Aeronautical 157 Serial Number= 96BB380E061A3B00 157 Vendor=294B, Product=1900 (Version 0.16) 157 GUIDs returned for product: VID_294B&PID_1900: 157 GUID= {3571F1B0-E9F5-11E9-8001-444553540000} 157 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 157 Product= Throttle - HOTAS Warthog 157 Manufacturer= Thrustmaster 157 Vendor=044F, Product=0404 (Version 1.0) 157 GUIDs returned for product: VID_044F&PID_0404: 157 GUID= {6B1B22B0-E8E7-11E8-8002-444553540000} 157 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y1023,Z16383 157 ------------------------------------------------------------------- 157 Device acquired for use: 157 Joystick ID = 1 (Registry okay) 157 1=Saitek Pro Flight Quadrant 157 1.GUID={F308E0B0-E99E-11E8-8002-444553540000} 157 Device acquired for use: 157 Joystick ID = 5 (Registry okay) 157 5=Saitek Pro Flight Quadrant 157 5.GUID={F94A49A0-E99E-11E8-8003-444553540000} 157 Device acquired for use: 157 Joystick ID = 3 (Registry okay) 157 3=vJoy Device 157 3.GUID={B47CD7A0-57D2-11E9-8002-444553540000} 157 Device acquired for use: 157 Joystick ID = 0 (Registry okay) 157 0=MFG Crosswind V2 157 0.GUID={5D1C51B0-E843-11E8-8006-444553540000} 157 Device acquired for use: 157 Joystick ID = 4 (Registry okay) 157 4=Alpha Flight Controls 157 4.GUID={3571F1B0-E9F5-11E9-8001-444553540000} 157 Device acquired for use: 157 Joystick ID = 2 (Registry okay) 157 2=Throttle - HOTAS Warthog 157 2.GUID={6B1B22B0-E8E7-11E8-8002-444553540000} 157 ------------------------------------------------------------------- 172 LogOptions=00000000 00000001 172 ------------------------------------------------------------------- 172 SimConnect_Open succeeded: waiting to check version okay 172 Opened separate AI Traffic client okay 172 ### PDKmodeHelper callback registered! 6250 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0) 6250 Initialising SimConnect data requests now 6250 FSUIPC Menu entry added 6250 ... Using Prepar3D with Academic License 6282 C:\Users\Eric Szczesniak\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 6282 F:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 13000 ### The user object is 'F-22 Raptor - 525th Fighter Squadron' 13000 ### Mode is NORMAL 13516 ### Mode: PAUSE on 51438 Loading Complete ... 51532 ### Mode is NORMAL 52235 User Aircraft ID 1 supplied, now being used 52250 Aircraft loaded: running normally now ... 53110 System time = 21/10/2019 20:41:31, Simulator time = 20:40:46 (01:40Z) 53110 Aircraft="F-22 Raptor - 525th Fighter Squadron" 66266 F:\Add-ons\A2A\SimObjects\Airplanes\A2A_C182\C182.air 66844 Aircraft="C182_VH-DLL" 68407 -------------------- Starting everything now ---------------------- 68453 *** LUA Error: F:\Prepar3D v4\Modules\AlphaYoke.lua:14: malformed number near '294B' 68469 ASN active function link set 68469 Ready for ActiveSky WX radar with additional data 69532 Advanced Weather Interface Enabled 88594 === Closing session: waiting for DLLStop to be called ...

I found this topic, but am having some difficulties. The only LUA have used before is from the Aerosoft F-14 that automatically installed the files. I have the new Honeycomb Yoke that has >32 buttons, with the buttons over 32 being Magneto Left, Magneto Both, and Starter. I am using FSUIPC 5 in P3D v4.4 I copied the file HidDemo.lua from the Modules\FSUIPC Documents\Example LUA Plugins to the Modules folder. I renamed this AlphaYoke. From the FSUIPC5 file opened in Notepad, the relevant section is: 156 Product= Alpha Flight Controls 156 Manufacturer= Honeycomb Aeronautical 156 Serial Number= 96BB380E061A3B00 156 Vendor=294B, Product=1900 (Version 0.16) 156 GUIDs returned for product: VID_294B&PID_1900: 156 GUID= {3571F1B0-E9F5-11E9-8001-444553540000} 156 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 I edited only new AlphaYoke.lua file to: ... Vendor = 294B Product = 1900 Device = 0 -- Multiple devices of the same name need increasing Device numbers. -- Logging on or off (to see when numbers you are getting) Logging = false -- Polling rate in number of polls per second Pollrate = 25 ... If I understood correctly, I should now see buttons 32-35 registers in the Buttons + Switches tab when I pressed them. Am I misunderstanding something, or doing something wrong?

Thank you both. Of all things, it turned out to be a “reverser” button from a Saitek quadrant that was plugged in at the same time.

While I'm a long time user, I'm no super user and am guessing there's some work around to this problem. I run all controls through FSUIPC in P3D v4.4 to allow for completely custom profiles for any aircraft. I've just received Honeycomb Yoke a few days ago and just got in to FSUIPC to try and program the buttons. There are a hand full of lights, battery, avionics, and magneto switches. The problem is that each position of the switch is a separate "button". This means a handful of buttons are always pressed. The problem this leads me to is that when I press a button I wish to program, call it button x, some other button press registers almost immediately changing the button to be programmed to button y. How can I go through one button at a time without some other "pressed" button immediately overriding the one I just selected?

Hello, I was hoping someone could help me with a controller problem I am having in P3D v4 and FSUIPC 5. I fly both jetliners and tactical military craft. As such, I have the following controller options: Connected all the time: 1. MFG Crosswind Rudder pedals Connected for military flying: 1. Thrustmaster HOTAS Joystick 2. Thrustmaster HOTAS Throttle Connected for jetliners: 1. Saitek Proflight Yoke 2. Saitek USB Throttle Quadrant #1 3. Saitek USB Throttle Quadrant #2 Back with FSUIPC v4.x, I had these all recognized perfectly and setup through FSUIPC. Now with P3D v4 and FSUIPC v5, I have one Saitek USB Throttle Quadrant not recognized in FSUIPC. Both are recognized in Windows 7 x64 and the P3D v4 controller settings. I suspect my problem is that they have a duplicate entry (as well as the yoke) with the same ID's. This is my JoyNames section: [JoyNames] AutoAssignLetters=Yes 0=MFG Crosswind V2 0.GUID={F50B58C0-E564-11E5-8001-444553540000} 1=vJoy Device 1.GUID={312D5C00-BFDE-11E6-8002-444553540000} A=MFG Crosswind V2 A.GUID={F50B58C0-E564-11E5-8001-444553540000} B=vJoy Device B.GUID={312D5C00-BFDE-11E6-8002-444553540000} C=Throttle - HOTAS Warthog << MISSING JOYSTICK >> C.GUID={CA539D20-3F6D-11E4-8002-444553540000} D=Joystick - HOTAS Warthog << MISSING JOYSTICK >> D.GUID={CA537610-3F6D-11E4-8001-444553540000} 3=Saitek Pro Flight Quadrant 3.GUID={C405EE40-3F64-11E4-8002-444553540000} 4=Saitek Pro Flight Yoke 4.GUID={4090D2F0-3F64-11E4-8001-444553540000} E=Saitek Pro Flight Quadrant E.GUID={C405EE40-3F64-11E4-8002-444553540000} F=Saitek Pro Flight Yoke F.GUID={4090D2F0-3F64-11E4-8001-444553540000} Can I delete the duplicate Saitek Yoke? And can I delete device 0 and 1 from before I started the AutoAssignLetters? And most importantly, what should be edited to get both quadrants recognized? Currently it's the one assigned letter E that is recognized and D is not. Thanks for any help!

I know PMDG does not recommend using FSUIPC with the NGX. However, I know that many people are in fact successfully using FSUIPC with this bird. Personally I am able to use it fine for spoilers, throttles (as long as I don't calibrate throttles axes within FSUIPC), reversers, gear and a number of button pushes. I however am not getting the flaps to work well. I have assigned an axis on one of my Saitek quadrants to the flap axis as a normal FSX axis. I've tried using detents, straight axis calibration and so forth. However, I do not get the flaps to smoothly progress. Typically, I find that the flaps don't retract fully using this axis, flaps 2 or 5, flaps 15 are skipped and I don't get all the way to flaps 40 at the end of the range. So, has anyone gotten this working? Would using the direct axis control work (I don't truly understand the difference between direct and normal FSX axes yet)? If anyone has them working, please share how you did it. Thanks for any help.

Thanks for the reply Quite true. Believe it or not I've read the manual through a couple times. Problem is I don't necessarily realize the usefullness of a certain utility until I need it...

I'm using a Saitek yoke and throttle quadrant x 2 to control my aircraft. I have a standard airleron, elevator, throttle, mixture and pitch settings in FSUIPC, but almost all of my aircraft are programmed indepedently (using teh specific aircraft check box) to make better use of all the axes and buttons (i.e., adding spoilers, flaps, etc.). The problem with this is that each different paint of an aircraft needs to be programmed individually this way. Is there anyway to apply or copy the control settings to all the different paints of a single aircraft? For example, I was just programming my Captain Sim C-130 using the basic C-130E USAF model. However, if I open the Blue Angels, Coast Guard, KC-130 or AC-130's that I also like to fly, I'm back with all of my "default" controls. I'd like to tell the sim somehow that any version of the Captain Sim C-130 uses the same controls. If important in this matter, I am using FSX+acceleration, FSUIPC 4.53 registered.