johnk515

I think I had hit the wrong button. I removed the key and ran the update again and did the register again, and now I'm back in business. Thanks

I've tried to update several times, but it doesn't give me the option to register. I don't get the field between options and logs. I have a lot of binding on here and won't be able to fly until I get it fixed. Help! FSUIPC7.log

I used the preset in FSUIPC for the ignition switch with a 3 way switch, but when switching the switch in the plane just wiggles. I do have the starter switch working using the presets. I have a spring back 3way switch and have it control to repeat while held, and it works good. It's the ignition I'm having problem with.

I bound a 3-way switch for the TBM 930 using the presets in FSUIPC. It works good, however, the switch in the plane doesn't move. How can I get the switch to move? When I switch from off to max then auto, I get the messages on the PDF that it's working. Just no switch moving in the panel. John K

In my P3D 4.5 PMDG 737, I have a spreadsheet that has to control codes for all the PMDG 737 events. Unfortunately I can't get them to work in msfs 737. In P3D I could either use a toggle switch or on/off switch I.E. anti coalition lights event ID 69757. It works great there, only if they would work in msfs.

I have the same problem. It started with mod 6.3 and 6.3.1. Mugz had changed the tbm930_interior.xlm file. I attached it, and about 1/3 down he added some binding_set lines that are on the right side. If I go back to mod 6.2 everything works fine, but 6.3.1 you have to use msfs binding just for the throttle, the prop works with FSUIPC or msfs, it's not affected. TBM930_interior.zip

John Would this lua work with a three way switch? I've made some boards with toggle switches, buttons and three way switches. I have some planes in P3D v4.5 that I use lua files to turn on/off taxi lts, and landing lights when on one switch. But I don't know about MSFS. I just want one of my switches to be down: off, middle: taxi lights, up: landing lights, then middle; landing lights off, taxi lights on, then down: all off. Or is there an easier way.

I updated to the new FSUIPC5. I also ran a repair on my P3D v4.5. Then when I loaded up my PMDG 737, the taxi lights were now working. I believe that doing the repair was what fixed the lights. I don't know if the update of FSUIPC did it, all I now is all is working. Oh, and if you still want the log I can send it to you, but by then they were working.

The PMDG support team had me start the 737 in the default mode with engines running. I have been using a start that had just the ground power running. When I did, it still does the same thing, comes on 1 second later turns off. Here's the log: ********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FF8978E0000 Windows 10 Pro 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0) Prepar3D.exe version = 4.5.11.29713 Reading options from "D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="John Kramer" User Addr="snookums.51@gmail.com" FSUIPC5 Key is provided WIDEFS7 not user registered, or expired 16 System time = 10/09/2019 15:37:57 16 FLT path = "C:\Users\Dad\Documents\Prepar3D v4 Files\" 16 Using DialogMode 31 FS path = "D:\Lockheed Martin\Prepar3D v4\" 187 ---------------------- Joystick Device Scan ----------------------- 187 Product= Saitek X52 Flight Control System 187 Manufacturer= Saitek 187 Vendor=06A3, Product=075C (Version 1.0) 562 GUIDs returned for product: VID_06A3&PID_075C: 562 GUID= {6CD7B660-EDE8-11E5-8001-444553540000} 562 Details: Btns=34, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X2047,Y2047,Z255 562 Product= Model 2238-CON 578 Manufacturer= Desktop Aviator 578 Serial Number= 1TA018E0 578 Vendor=16D0, Product=0621 (Version 0.1) 578 GUIDs returned for product: VID_16D0&PID_0621: 578 GUID= {8B580F80-AF53-11E7-8001-444553540000} 578 Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 578 Product= Model 2120/2125 578 Manufacturer= Desktop Aviator 578 Serial Number= DTpc03d9 578 Vendor=16D0, Product=0480 (Version 0.1) 578 GUIDs returned for product: VID_16D0&PID_0480: 578 GUID= {40B196F0-6FBA-11E7-8002-444553540000} 578 Details: Btns=20, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 578 Product= Saitek Pro Flight Rudder Pedals 594 Manufacturer= Saitek 594 Vendor=06A3, Product=0763 (Version 1.0) 594 GUIDs returned for product: VID_06A3&PID_0763: 594 GUID= {D27F8600-EDE3-11E5-8001-444553540000} 594 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 594 Product= DP3T Emulator 594 Manufacturer= Desktop Aviator 594 Serial Number= zzA0dxxx 594 Vendor=16D0, Product=0747 (Version 0.2) 594 GUIDs returned for product: VID_16D0&PID_0747: 594 GUID= {40B16FE0-6FBA-11E7-8001-444553540000} 594 Details: Btns=30, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 594 ------------------------------------------------------------------- 625 Device acquired for use: 625 Joystick ID = 0 (Registry okay) 625 0=X52 H.O.T.A.S. 625 0.GUID={6CD7B660-EDE8-11E5-8001-444553540000} 625 Device acquired for use: 625 Joystick ID = 4 (Registry okay) 625 4=Model 2238-CON 625 4.GUID={8B580F80-AF53-11E7-8001-444553540000} 625 Device acquired for use: 625 Joystick ID = 3 (Registry okay) 625 3=Model 2120/2125 625 3.GUID={40B196F0-6FBA-11E7-8002-444553540000} 625 Device acquired for use: 625 Joystick ID = 1 (Registry okay) 625 1=Mad Catz Pro Flight Rudder Pedals 625 1.GUID={D27F8600-EDE3-11E5-8001-444553540000} 625 Device acquired for use: 625 Joystick ID = 2 (Registry okay) 625 2=DP3T Emulator 625 2.GUID={40B16FE0-6FBA-11E7-8001-444553540000} 625 ------------------------------------------------------------------- 1422 LogOptions=00000000 00000001 1422 ------------------------------------------------------------------- 1422 SimConnect_Open succeeded: waiting to check version okay 1422 Opened separate AI Traffic client okay 1422 ### PDKmodeHelper callback registered 242922 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.11.29713 (SimConnect: 4.5.0.0) 242937 Initialising SimConnect data requests now 242937 FSUIPC Menu entry added 242937 ... Using Prepar3D with Professional License 242984 C:\Users\Dad\Documents\Prepar3D v4 Files\KAVC.fxml 242984 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Carenado Commander 114\Car_Commander114.air 329031 ### The user object is 'AC11 Commander 114 - Deep Blue' 329031 ### Mode is NORMAL 329578 ### Mode: PAUSE on 527453 Loading Complete ... 527516 ### Mode is NORMAL 530500 Aircraft loaded: running normally now ... 530547 User Aircraft ID 1 supplied, now being used 530812 System time = 10/09/2019 15:46:48, Simulator time = 15:43:25 (22:43Z) 531594 Aircraft="AC11 Commander 114 - Deep Blue" 536812 -------------------- Starting everything now ---------------------- 536859 ASN active function link set 536859 Ready for ActiveSky WX radar with additional data 538000 Advanced Weather Interface Enabled 700922 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air 700922 PMDG 737 offsets enabled 711453 Aircraft="Boeing 737-8K2NGX KLM Royal Dutch Airlines Winglets" 745687 **** Restarting traffic scanning due to non-reception **** 751953 Sim stopped: average frame rate for last 40 secs = 22.8 fps 751953 Max AI traffic was 41 aircraft (Deleted 0) 751953 ------------------------------------------------------------------- 914516 Sim stopped: average frame rate for last 109 secs = 29.1 fps 914516 Max AI traffic was 42 aircraft (Deleted 0) 914516 ------------------------------------------------------------------- 918344 === Closing session: waiting for DLLStop to be called ... 947031 === DLLStop called ... 947031 === Closing external processes we started ... 948031 === About to kill any Lua plug-ins still running ... 948172 === Closing global Lua thread 949187 === About to kill my timers ... 949391 === Restoring window procs ... 949391 === Unloading libraries ... 949391 === stopping other threads ... 949391 === ... Button scanning ... 949484 === ... Axis scanning ... 949594 === Releasing joystick devices ... 949594 === Freeing macro memory 949594 === Removing any offset overrides 949594 === Clearing any displays left 949594 === NOTE: not calling SimConnect_Close ... 949594 === AI slots deleted! 949594 === Freeing button memory ... 949594 === Deleting wxstationlist.bin file ... 949594 === Closing my Windows ... 949594 === Freeing FS libraries ... 950594 === Closing devices ... 950594 === Closing the Log ... Bye Bye! ... 950594 System time = 10/09/2019 15:53:47, Simulator time = 15:45:41 (22:45Z) 950594 *** FSUIPC log file being closed Minimum frame rate was 9.7 fps, Maximum was 29.9 fps Average frame rate for running time of 164 secs = 27.6 fps Maximum AI traffic for session was 42 aircraft Memory managed: 71 Allocs, 70 Freed ********* FSUIPC Log file closed *********** By the way the landing lights are working fine now. So it's just the taxi lights. Which worked just fine in FSX:SE and my PMDG 777 works fine using it's custom controls. I'm at a loss. And if I use the mouse to turn on and off the taxi lights, when I turn it on the lights go on then off, but the switch is still on. I attached my ini file. FSUIPC5.ini

I've been flying my PMDG 737 for sometime in P3D v4.5 with the latest FSUIPC 5. Haven't done any night flights until lately. I discovered that when I turned on the taxi lights, they weren't showing on the ground. From the external view, when I turned on the taxi lights, they came on for about a second then went off. My other lights work fine. My PMDG 777 all exterior lights work. I use the control number 69749 from the pmdg pdf file for the 737. I've also, turned off that switch and just clicked on the switch in the ovh in vc, but still goes off after a second. Over at the PMDG forum they said I should move the FSUIPC temp to see it works then. The thing is that I use FSUIPC for all my commands. So would I need to activate the controlers in p3d v4 and would all I have to move temporally the ini file? Or would I need to move any others to test it without FSUIPC. I just thought that having the taxi lights unassigned to FSUIPC would be enough without basically removing. Or do you have anything I could check that could fix the problem.

I guess I need my eyes check also. I had looked all over the file and couldn't see anything wrong until now. Well both the tcas and the autobrake works now. Thanks for all the help.

Where should the } be. I'm still getting that error.

I logged the test and here's what I got. 706062 ------------------------------------------------------------------- 798890 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\QualityWings 787-9\Boeing 787-9 RR.air 803078 Aircraft="QualityWings 787-9 Virgin Atlantic Airways -SATCOM" 890219 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 891156 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 891750 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 892172 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 900859 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 901375 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 901781 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 902094 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 906422 Sim stopped: average frame rate for last 97 secs = 27.9 fps 906422 Max AI traffic was 15 aircraft (Deleted 0) 906422 ------------------------------------------------------------------- 961156 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 962703 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 963656 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 964469 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 964922 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 965312 *** LUA Error: D:\Lockheed Martin\Prepar3D v4\Modules\QWTcasAutobrake.lua:25: ')' expected near '}' 972625 Sim stopped: average frame rate for last 29 secs = 29.4 fps 972625 Max AI traffic was 15 aircraft (Deleted 0) 972625 ------------------------------------------------------------------- [Log closed by user request, and continued in new file] Roman, I changed the Max and Min around since like the tcas inc the max was 4. tcas was 0-4 and I didn't want it to go higher. I don't know what the error means ')' expected near ')' or what needs to change.

The thing is, it didn't work.

Here's what I came up with for the TCAS and autobrake in 1 lua file. --------------------------------------------- --Parameters by Number --------------------------------------------- --1 Turn TCAS Clockwise one position --2 Turn TCAS Counter Clockwise one position --3 Turn Autobrake clockwise one position --4 Turn Autobrake Counter Clockwise one postion --------------------------------------------- ----Variables --------------------------------------------- "L:QW_AFT_Transponder_Knob" "L:auto_brake_switch" -------------------------------------------- ---- Scripts -------------------------------------------- --Inc TCAS if ipcPARAM == 1 then n = ipc.readLvar("L:QW_AFT_Transponder_Knob") n = n + 1 If n > 4 end else ipc.writeLvar(L:QW_AFT_Transponder_Knob", n) end end --Dec TCAS if ipcPARAM == 2 then n = ipc.readLvar("L:QW_AFT_Transponder_Knob"} n = n - 1 if n < 0 end else ipc.writeLvar("L:QW_AFT_Transponder_Knob" n) end end --Inc Autobrakes if ipcPARAM == 3 then n = ipc.readLvar("L:auto_brake_switch") n = n + 1 if n > 6 end else ipc.writeLvar("L:auto_brake_switch", n) end end --Dec Autobrakes if ipcPARAM == 4 then n = ipc.readLvar("L:auto_brake_switch") n = n - 1 if n < -1 end else ipc.writeLvar("L:auto_brake_switch", n) end end I had it read the value of the switch, then add 1 or subtract 1. And check to see if n was more than 4 or less than 0 for the tcas, and more than 6 or less than -1 for the autobrake.