Masterius

Try this: 1) Unplug the joystick and throttle 2) Uninstall in device manager 3) reboot 4) Edit your FSUIPC6.ini file [Joynames] as follows: [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Stick << MISSING JOYSTICK >> A.GUID={20AEA380-71FE-11EB-8001-444553540000} B=Saitek Pro Flight X-55 Rhino Throttle B.GUID={20AEA380-71FE-11EB-8003-444553540000} 0=Saitek Pro Flight X-55 Rhino Stick 0.GUID={20AEA380-71FE-11EB-8002-444553540000} 1=Saitek Pro Flight X-55 Rhino Throttle 1.GUID={20AEA380-71FE-11EB-8003-444553540000} A=Saitek Pro

Not sure if this will work, but look in your FSUIPC(x).ini file for the following: [Buttons] PollInterval=25 See if decreasing the poll Interval helps. From the Advanced User Guide: PollInterval=25: This parameter tells FSUIPC how often to read (“poll”) the joystick buttons. The time is in milliseconds, and the default, as shown, is 25 (40 times a second). A polling rate of 0 will stop FSUIPC looking at buttons altogether, and in fact this will remove the Buttons & Switches tab from the FSUIPC options. This may come in useful for checking whether a rogue

There was a lua script that I hadn't been using since I'd switched from FSX to P3Dv5. It had been located in the directory--and thus listed in fsuipc6.ini under [LuaFiles]--since the changeover, but due to mission requirements (basically I'll be using it this weekend to operate our Norden bombsight) I'd updated the [Auto] to have it autoload. The lua script in question contained the following: function VAS(control, vas) vas_in = ipc.readUD(0x024C) ipc.writeLvar("L:VAS", vas_in) if vas_in < 500000 then ipc.display("VAS = "..vas_in,2)

P3Dv5 (5.1.12.26829) LINDA3.2.6.1111 FSUIPC 6.0.12 Starting yesterday, I've started getting a cyclical message popping up in a window. It's a SimConnect Window, stating that "VAS=0". I've disabled all my addons, and restarted using just the stock, default-provided aircraft. I do not get that message until I've re-enabled FSUIPC6. No other addon triggers the message window. Checking the FSUIPC6.log does not show any errors. I've been running the same conditions for weeks now without problems of this sort, and am clueless as to why this has suddenly started. Also have noted tha

Fixed and working >Update: Still working, with the script variables identical as before. Only change being the repositioning of function MixAdj_1 to allow for it being defined.

I have four identical scripts that differ only in their numeration, one each for engines 1 thru 4. All four have worked just fine this last week. All four stopped dead at the same time yesterday evening. All four have the same time stamp, dated last week. I assure you, they did run, and they haven't changed. I'll agree that something has to have changed. I meant that script. It auto loads using fsuipc6.ini, and is called using FSUIPC6 axis definition offsets. LINDA has nothing to do with these scripts. I'll update that right now.

P3Dv5 LINDA3.2.6 FSUIPC 6.0. 11 For over a week this lua has been working just fine. It was working fine this morning. And now it's not. When trying to load I get the following error message in the LINDA2.log: [E] *** LUA Error: C:\Prepare3D v5 Add-ons\FSUIPC6\A2AB17_MixAdj_1.lua:7: attempt to call global 'adjust_mix_1' (a nil value) The main script is set to autoload and run in FSUIPC6.ini. I have no idea why it ran without a hitch for days and now suddenly is faulting. function MixAdj_1(offset, input) MixAdj_1_in = ipc.readSW(0x66DB) n = (MixAdj_1_in +

Problem is, FSUIPC doesn't recognize them. Nor, for that matter, does LINDA or FSX:SE. Windows USB game controller sees them, but for some reason nothing else does. ~Masterius

Thanks! I'll go and give that a whirl! ~Masterius

Pinkie Trigger [6] (stick): Button 6 Mouse Button [31] (throttle): Button 31 Mouse Button 2 [32] (throttle): Button 32 ~Masterius

FSX:SE LINDA 3.1.1 FSUIPC 4975A First off, not complaining. FSUIPC is an awesome tool, and I enjoy it--and use it--immensely. I've recently begun using my old Saitek X-52 H.O.T.A.S., and unlike in the past, when I used Saitek's (ugh) profiler, this time I've used LINDA and FSUIPC to assign controls and functions. Having done so, I've discovered controls that neither LINDA nor FSUIPC recognize. The specific buttons, switches and axis are: Mode Switch [MODE] (stick), Pinkie Trigger [6] (stick) Mouse Button [31] (throttle) Mouse Button 2 [32] (throttle

OK, I'm admitting I've no idea what I'm doing. I've torn apart every .lua existing in the various folders, and after having done so I've no idea how DspShow is defined. I've specifically looked for "Fthr" to see where and how that is defined, and simply can't find it. I'm at a loss here. I've also read all the support manuals and instructions and have exhausted Google, and again come up short with an explanation for DspShow. Care to take pity on an ignoramous?

I've found the issue, but no idea how to fix it. I get this error when trying to run it: [E] *** LUA Error: ...am\steamapps\common\FSX\Modules\B17_Eng1_restart.lua:61: attempt to call global 'DspShow' (a nil value) It runs fine in LINDA, but I suspect that's because it's run within the larger file lib-user.lua function B17_Eng1_restart () ipc.writeLvar("L:Feather1Switch", 0) DspShow("Fthr", "1 off") ipc.sleep(500) ipc.clearbitsUB("2434", 1) ipc.sleep(2000) ipc.writeLvar("L:FuelValvesSafe",1) ipc.sleep(750) ipc.writeLvar("L:Eng1FuelCutOffSwitch",1) i

Oddly enough, had I searched for Lua in controls, I highly doubt I would have asked this question. Since I was going to be conditionally programming the .lua, and as you can't directly assign that through the GUI interface but are required to manually program that, I was trying to do so using the instructions found in pages 18 thru 28 of the FSUIPC4 for Advanced Users.pdf. The examples used there for control definitions are the typical Cxxxxx format, such as C65570. I'm familiar with that, and extensively use them in my scripts. I hadn't encountered the "CL" definition before, and since I

Can a button be programmed to run a .lua? It appears that buttons can be programmed for keypresses, controls, and macros, but not a .lua.