johnk515

The only things I've been able to do is the exterior lights I.E. landing taxi... They use the fsuipc standards. I can also do the autobrakes, and toggle the efb and the fmc to make it easier to use. It would be nice if they did like PMDG has their's.

It turns out that the wxr tilt that I had used was for the standard 744. Then the section that said for the 744f and 747-8 had the left and right wxr tilt, and that one worked. I have three 3-way toggle switch which springs back to center like the switches I have on my Saitek x52. So when I push up the tilt inc. and when I push down it dec. It works very well. And the control number for the left wxr tilt was 71034.

I've got one control I've been trying to get working. I want to use a 3-way switch to inc/dec the wrx tilt. For the 747 the control number is 70756 from the sdk. I've tried the mouse flag left single and right single, and the mouse wheel up / down parameters. Yet none work. I have other controls that work, and my 737 and 777 all work fine. Any one have this problem?

Thanks Pete

I have wilco's tecnam p2006t. I've been trying how to assign the chokes to buttons. I have L:tecnam_lever_choke1_number, and L:tecnam_lever_choke2_number. I know how to use trim up/down or inc dec with buttons. But the chokes just have a number. I have lua files, but I want to use the T1,T2,T3, and T4 to move the chokes. T1 would be left engine up and T2 would b left engine down. Then T3/4 would be for the right engine. I don't know how to make the numbers go higher or lower with the buttons.

Turns out I was trying to use the wrong control. Now it works. It's AP VS Var Inc & Dec.

I have the Flysimware C402 Cessna. I'm trying to assign the AP alt pitch wheel to my Saitek x52 stick. On the Flysimware's site they said use (>K:AP_PITCH_REF_INC_UP) and (>K:AP_PITCH_REF_INC_DN) to change the pitch when autopilot's on. In FSUIPC you have the control numbers for the ap pitch ref inc up and down. So I assigned C66584 to R0, 8 and C66583 to RO, 9, but it doesn't work. I still have to use the mouse to adjust the pitch when climbing or descending. The pitch wheel is on the pedestal below the throttles, making it difficult to use the mouse and watching out side. That's why I want to use buttons. I have the latest registered FSUIPC for FSX: SE.

I'll do that. Finding out new things every day.

Here's the file. MJC_acol.lua

I got it all fixed. I removed a lot of stuff not needed. So, it works fine with only 3 actions, -1 up, 0 off, 1 down. Works great, thanks for the help Pete.

Here's the settings in FSUIPC for mjc D8-400: 25=P2,22,CL13:R,0 -{Lua acol}- 26=P2,21,CL13:R,-1 -{Lua acol}- 27=P2,23,CL13:R,1 -{Lua acol}-

I was trying it in the mjc84.ini file, but that didn't work. Some one on their site suggested using lua to change it. They said "There I use the LVar L:OHD_EXT_LT_ACOL_SW with -1, 0 and +1." My problem is that when I look at lua, it can get confusing. I have a 3 way switch J2:21, 22, 23. Just trying to tell it, if I have the switch in the middle 22 and switch to 21 it flips the switch up or I switch it down to 23, the switch in the plane flips down. I attached a lua file that works some what. I start with the switch in the middle b22. when I flip the switch to b21 the red beacon light comes on, but when I switch back to b22, it doesn't switch back to off. I have to flip up again and it goes off and flip back down to the off position. It does the same thing when flipping down to b23, the anti-collision lights come on, but stay on if I flip the switch back to b22. I have to flip down, then up again. Can some one look and tell me what I'm missing? acol.lua

I'm trying to add mjc's anti collision lights to a 3 way switch. The name is OHD_EXT_LT_ACOL_SW. I tried using -1, 0, 1 to move the switch on the panel to have just the beacon on , off, or anti collision / beacon on. That didn't do. I'm not very good with LUA, how to have the switch go down when flipping my switch down or flipping the switch up add the anti collision, or off when switch is in the middle. Some one said to try a mouse macro, but no luck with that either. Any one have away to put this in a macro or LUA file? This is FSUIPC 4. FSX:SE

If you go to https://www.myhomecockpit.de/index.php/en/ From the main menu look at tips & tricks then PMDG event ID's. There he has the 737 and 777 pdf files that have the correct <custom control> number for each offset. I'm just waiting for the 747. He also has the parameters to use. This way you don't have to go through the PMDG_NGX_SDK.h file and fine the (THIRD_PARTY_EVENT_ID_MIN + ) and add it to the control events number, which is 69632. He did that for you at his website.

Well, it works now. Thanks Bruce.

Here is the file and log file. Luacmds.log Luacmds.lua

I got a lua file from Bruce Buckley in the Carenado Phenom 100 so I could the taxi/landing light switch to a button. -- Parameters by Number -------------------------------------------- -- 1 Move Ldg_Taxi Lt SW UP one position -- E50P -- 2 Move Ldg_Taxi Lt SW DN one position -- E50P -- 3 Turn ON NAV & STROBE Lts -- E50P, PA28, C172 -- 4 Turn OFF NAV & STROBE Lts -- E50P, PA28, C172 -- 5 Turn ON Fuel Pump -- PA28, C172 -- 6 Turn OFF Fuel Pump -- PA28, C172 -------------------------------------------- ---- Variables -------------------------------------------- SW_Pos = "L:ASD_SWITCH_LANDING_TAXI_EMB500" -------------------------------------------- ---- Scripts -------------------------------------------- -- Move Ldg_Taxi Lt SW UP one position if ipcPARAM == 1 then SWPos = ipc.readLvar(SW_Pos) if SWPos == 0 then ipc.writeLvar(SW_Pos, 1) ipc.setbitsUW(0x0D0C, 8) end if SW_os == 1 then ipc.writeLvar(SW_Pos, 2) ipc.clearbitsUW(0x0D0C, 8) ipc.setbitsUW(0x0D0C, 4) end end -- Move Ldg_Taxi Lt SW DN one position if ipcPARAM == 2 then SWPos = ipc.readLvar(SW_Pos) if SWPos == 2 then ipc.writeLvar(SW_Pos, 1) ipc.clearbitsUW(0x0D0C, 4) ipc.setbitsUW(0x0D0C, 8) end if SWPos == 1 then ipc.writeLvar(SW_Pos, 0) ipc.clearbitsUW(0x0D0C, 8) end end This is the script that I got. I left out the ones for variable 3-6. But nothing happens when I try it. Here's the lua log that comes up. ********* LUA: "Luacmds" Log [from FSUIPC version 4.971] ********* 314391 System time = 30/08/2017 14:42:02, Simulator time = 14:37:27 (21:37Z) 314391 LUA: beginning "D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua" 314391 *** LUA Error: D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua:1: unexpected symbol near ' ' 314391 >>> Thread forced exit (ipc.exit or os.exit) <<< 314391 System time = 30/08/2017 14:42:02, Simulator time = 14:37:27 (21:37Z) ********* LUA execution terminated: Log Closed ********* ********* LUA: "Luacmds" Log [from FSUIPC version 4.971] ********* 315188 System time = 30/08/2017 14:42:03, Simulator time = 14:37:28 (21:37Z) 315188 LUA: beginning "D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua" 315203 *** LUA Error: D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua:1: unexpected symbol near ' ' 315203 >>> Thread forced exit (ipc.exit or os.exit) <<< 315203 System time = 30/08/2017 14:42:03, Simulator time = 14:37:28 (21:37Z) ********* LUA execution terminated: Log Closed ********* ********* LUA: "Luacmds" Log [from FSUIPC version 4.971] ********* 347766 System time = 30/08/2017 14:42:36, Simulator time = 14:37:42 (21:37Z) 347766 LUA: beginning "D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua" 347766 *** LUA Error: D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua:1: unexpected symbol near ' ' 347766 >>> Thread forced exit (ipc.exit or os.exit) <<< 347766 System time = 30/08/2017 14:42:36, Simulator time = 14:37:42 (21:37Z) ********* LUA execution terminated: Log Closed ********* ********* LUA: "Luacmds" Log [from FSUIPC version 4.971] ********* 349000 System time = 30/08/2017 14:42:37, Simulator time = 14:37:43 (21:37Z) 349000 LUA: beginning "D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua" 349000 *** LUA Error: D:\Steam\steamapps\common\FSX\Modules\Luacmds.lua:1: unexpected symbol near ' ' 349000 >>> Thread forced exit (ipc.exit or os.exit) <<< 349000 System time = 30/08/2017 14:42:37, Simulator time = 14:37:43 (21:37Z) ********* LUA execution terminated: Log Closed ********* Bruce says it works for him and many others. I'm using steam, but I have other lua files that work just fine. Any ideas what the problem is?

Demon, I installed Lekseecon_f 8.4. But when I run it I get an error :51 lekseecon_f.ini can't be found. I've uninstalled then reinstalled, but still the same error. Should it create an ini file? I've installed it on my D:\ drive. And at his site, there's no place to contact him. Do you know where it should be located?

I was given a web site that had the control numbers for the pmdg 737 and 777 along with the parameters to use. It works great, and since I have the registered version of FSUIPC, I do it all in FSUIPC.

I was given away to use offset mapping for PMDGs 737, 747 v2, 777 in FSX:SE using custom controls. It works some what. I have the desktop aviators model 2120 and model 2630 usb boards for adding switches. I have 20 dual pulse switches. The 2630 has 10 DP3T switches. The 3 way switches work fine, but the on/off switches will turn on but not off. Is there something I'm missing? JohnK

You shouldn't install flight simulator in the C:\Program Files (x86)\. You should have a separate folder outside of the program files. I.E. c:\fsx\ or I have d:\steam\steamapps\common\fsx\.

Would I get a discount since I did buy the se version. I don't know why Steam says it can't use FSUIPC. I've been using it long before steam. It works fine, but steam uses the FSUIPC excuse for not having the wxr radar. I have it in the feelthere 737.

I bought E-Jets v2 from steam the other day. After getting it all installed and setup, there was no weather radar. I looked in their forum and the ejets v2 (official) discussion was that fsx:se doesn't use fsuipc so they didn't have the weather radar included. The thing is I've been using fsuipc since fs2000 and have the registered version for fsx. I use it with all my addons i.e. pmdg, level-d wilcos 737 and others with no problem. I have the fswxr2100.gau, but I don't have the coordinates in the panel.cfg to add it to my ejet 175 & 195.

I've updated what terminals are used by what airlines, like the north terminal has all asa and qxe. And added new parking spots. I just started KLAX and it started fine and I had made changes to adding some new spots. Does tower have problems with gates that have letters after the gate number? That's what C2L is. For that gate I have terminal_C and the name of the gate is C2L. There is also C2M and others. In the north terminal I added N12A, N12B... But that's the name, the terminal filter is Terminal_North, just like C2L has Terminal_C for that gate. And C2L was there when I had used ksea before. That was about 8 to 11 months ago. John K

Here's the log. I didn't see anything with ksea with the airfield editor. tower.log