737Andi

Thank you! Its working perfectly 🙂

Hi John, thanks for your reply. I'm using the hardware tiller from Skalarki, which has a push button for the pedals disc. My intention would be to have the pedals disconnected as long as the button is being pressed down and to reconnect them as soon as I release the button. I think this is the way as it works in the real plane. When releasing the button on the hardware the software button on the Fenix A320 sometimes stays in. Any idea how to realize that? Thank you! Best regards Andi

Hi, I would like to assign the Tiller Pedals Disconnect function to my hardware button. Unfortunately, it is not working decently with the following setting (please see also attached image). 17=RH,14,CPFNX320_Misc_Tiller_Pedal_Disconnect_Captain_Press,1 -{Preset Control}- 18=UH,14,CPFNX320_Misc_Tiller_Pedal_Disconnect_Captain_Release,1 -{Preset Control}- About 50% of the time it is working fine, but the rest of the time the button gets stuck in the pressed position after release. So the release command does not always seem to work. I suppose that this could be solved by either setting a delay between the press command and the following release command or by initiating the release command 2 or more times at the end. Hopefully someone has a solution here. Thank you! Best regards Andi

Hi John, I'm so happy that everything is working as usual after I restored my whole windows SSD yesterday. I'm quite positive that the FSUIPC update to 7.3.15 was the reason for the problem because I installed no other software in between. Nevertheless since it is no solution for the future I would like to try another install of 7.3.15. This time I would however like to make sure that I can easily get my old FSUIPC back in case the problem occurs again. Which folders do I need to save for a 100% roll back to an older version? Definetely the main FSUIPC folder under C:/ and the fsuipc-lvar-module in the Community folder. Is there anything else that the new install will change? Maybe some settings in the registry or under AppData, Documents etc.? Thank you! Best regards Andi

Hi John, I noticed a strange thing. I recently installed the newest FSUIPC version 7.3.15 and successfully configured the custom control offset "L_Clock" in the PMDG 737-800 under this specific FSUIPC version. Offset is 69632 + 890 = 70522. Left mouse click would be 0x20000000 without the 0 in front of the x. After some time I did however notice some strange connection problems between the CPFlight driver and the most recent FSUIPC version, which forced me to do a complete roll back of my whole windows system. Now I'm currently using the old FSUIPC version 7.3.8 again and the connection problems have gone. I tried to configure the L_Clock custom offset here as well, but it does not work? I made sure that the code line under v7.3.8 FSUIPC.ini is the same as under version 7.3.15 where it worked absolutely fine, which is the case. Is it possible that this offset is only working under FSUIPC 7.3.15 ? Thanks! Best regards Andi

Hi John, thank you again! Please do not ask me why I did not understand it initially. Very embarassing. I thoroughly read through the provided documentation and misunderstood it anyway, although everything is described very clearly. It is working now! :) I noticed an interesting thing though. When using the DOME light custom control the action itself is working. But beside that the custom control action does also move the parking brake and the rudder pedals inside the plane for a very short time simultaneously. I'm quite sure that the rudder pedals and the parking brake are not assigned with FSUIPC. Maybe there is an explanation for it? Thanks! Andi

Hi John, I suppose I was unclear regarding my problem. Where do I find the value of THIRD_PARTY_EVENT_ID_MIN ? Example given... // equals to 69632 There are no remarks in the PMDG 737.h SDK file like e.g. 69632. Thanks! Best regards Andi

Hi John, thanks for your reply 🙂 I have found the entry you mentioned in the 737 SDK --> #define EVT_OH_DOME_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 258) But unfortunately I do not know how to find the custom control offset to which I need to add 258. From where can I get this value? I read everything from the provided link but the information there says that the offset value can be found behind some slashes in the SDK which is however not the case for the PMDG 737 SDK file under MSFS. Can I somehow log the offset myself with the console? If yes, how would this work in detail? Thank you very much! Best regards Andi

No one? 😞 Andreas Vavra

Hi, I'm unfortunately not able to find the right setting under FSUIPC 7 to assign the Dome light bright or dim switch of the newest PMDG 737-800 under MSFS to a joystick button. I tried it the usual way by going to assign buttons, clicking the joystick button (which is recognized fine) and then by clicking the FS Control checkbox and looking for the right Control command from the drop down list. I have tried every command that makes sense somehow but none was successful. Can anyone please give me a hint which command is working under MSFS and the newest PMDG738. Thanks! Best regards Andi

Hi John, thanks for your info. I found out that the program Multi Crew Experience overwrote the latest WASM installed by FSUIPC7 with an older version, which made FSUIPC's WASM unusable. I reinstalled FSUIPC and now its working again. Downside is that Multi Crew Experience is not usable for me for now. I have already spoken to the developer and they will have a look at the problem soon. Regarding the log file. I made that one shorter by hand because I only thought that the beginning might be of interest for you.

Hi, I tried several settings to get the best Tiller and Rudder Steering on my PMDG 737, but for some reason it does not feel as fluid as with the PMDG 737 NGXu under Prepar3d 😞 I played a lot with the sensitivities of MSFS, slopes of FSUIPC and so on. At the moment I'm using "Steering Tiller" over Send direct to FSUIPC calibration and "Rudder" also over send direct to FSUIPC calibration. Using Rudder of MSFS and Tiller function of FSUIPC does somehow not work. Both axis seem to work against each other very unnaturally. So I decided to stay with having both axis assigned to FSUIPC. Does anyone have a recommendation what works really well? Thank you! Best regards Andi

Hi John, I tried it with the delay function and it actually worked yesterday. Unfortunately today it has stopped working and I cannot figure out why 😞 It is not even possible to see the LVars List at all at the moment?! If I load the PMDG 737-700 and load FSUIPC and click Addon - Wasm , I can only see "Disable" as option. All the other options are greyed out (not selectable). Toggling between disable and enable does not help. The other WASM options (List Lvars, list hvars, set lvars,...) stay non selectable. I tried so many things. I e.g. removed the delay entry from the FSUIPC_WASM.ini again. Checked that the FSUIPC.ini has not changed. I reinstalled the latest FSUIPC version. I'm on 7.3.6. now. For some strange reasons the List LVars cannot be clicked anymore. Here are my files...hopefully you have an idea whats wrong here? Thank you! Best regards Andi FSUIPC7.log FSUIPC_WASM.ini FSUIPC7.ini

Hi John, just added the line to my General section (see bottom of section) but it still does not work 😞 I also reloaded the cpflight driver after 60s. Any ideas? Thank you! [General] UpdatedByVersion=7304 UseSystemTime=No JoystickTimeout=20 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No UseProfiles=Yes WideLuaGlobals=Yes InvokeFSUIPCOptionsKey=70,12 AxesWrongRange=No TCASid=Flight TCASrange=40,3 AxisCalibration=No DirectAxesToCalibs=No AxisIntercepts=No DontResetAxes=No ThreadAffinityMask=x0 LuaAffinityMask=x0 LogOptionProtect=Yes AutoConnectToSim=Yes AutoExitWithSim=Yes TimeForLuaClosing=2 TrafficStallTime=1 InitialStallTime=30 NormalStallTime=1 LuaRerunDelay=66 ComReadLoopTime=20 ControlsListBuild=999 Window=298,1377,848,1622 Console=No ConsoleWindowTopMost=No ConsoleWindow=260,260,1253,779 EnableExtraButtons=Yes LogEvents=Yes LvarScanDelay=60 FSVersionUsed="KittyHawk",11.0.282174.999 SimConnectUsed=11.0.62651.3

Hi John, I'm using the CPFlight driver for my MCPPro3 MCP panel. They have a fully working driver for the MCP module, which is needing the WASM - LVars to run. Unfortunately there is a small problem. The MCP hardware annunciator lights do not work until I go manually into the FSUIPC program and click Addon - Wasm - List LVars. Only if I do that also the hardware lights (e.g. HDG SEL button light, V/S button light,..) on my MCP light up. Is there any way to autoload the List LVars on FSUIPC startup, so that I do not need to make these steps manually each time when starting up the CPFlight driver? The developer from CP Flight already responded and it seems that this is a fix that would need to be done in FSUIPC, because he does not have any control over that feature with his driver. Hopefully my problem was explained half-way understandable. Please let me know if you need further infos and I will be happy to deliver them to you. Thank you very much! Best regards Andi

Hi John, sorry! Thanks again for writing it!

Awesome thank you so much! I was still on 7303. By the way..Petes lua is working too if WASM is enabled 🙂

Thank you very much! I enabled WASM and searched for the PMDG_B737-7_ANTISKID_OFF_POS_SW,0 command under FSControl. Unfortunately I could not find it there 😞

Hi John, thanks for taking the time to write this script. Unfortunately it does not work for me 😞 I placed it inside the main FSUIPC7 folder and added the following part to my fsuipc7.ini file. [Auto] 1=Lua PMDGAutoBrake Then I changed the script header to the following.. -- ## Auto Brake local PMDG_EVT = 66587 -- -- Change the following to match your joysyick and button numbers -- local myJoynum = A local myRtoButton = 0 local myOffButton = 1 local my1Button = 3 local my2Button = 4 local my3Button = 5 local myMaxButton = 7 Since my joynames section contains this I tried it with letter "A" and number "0". The name of the rotary device is BU0836-LC Interface [JoyNames] 0=BU0836-LC Interface 0.GUID={C66388B0-0C9E-11EB-8001-444553540000} 4=T-Pendular-Rudder 4.GUID={0F828800-228C-11EA-8004-444553540000} 6=UnoJoy Joystick 6.GUID={E424C0B0-1AEC-11EB-8001-444553540000} A=BU0836-LC Interface A.GUID={C66388B0-0C9E-11EB-8001-444553540000} B=Alpha Flight Controls << MISSING JOYSTICK >> B.GUID={0F81EBC0-228C-11EA-8001-444553540000} C=SideWinder Force Feedback 2 Joystick C.GUID={E2BE39C0-D661-11E9-8006-444553540000} D=JoyWarrior A8-16 D.GUID={71EE1820-F9FE-11EA-8001-444553540000} E=T-Pendular-Rudder E.GUID={0F828800-228C-11EA-8004-444553540000} F=8AI-36DI-01 F.GUID={298609A0-8683-11EB-8001-444553540000} G=UnoJoy Joystick G.GUID={E424C0B0-1AEC-11EB-8001-444553540000} H=BU0836-LC Interface H.GUID={0856FD90-3014-11EB-8001-444553540000} 5=Controller (XBOX 360 For Windows) 5.GUID={0B9569C0-D4E6-11EB-8002-444553540000} J=Controller (XBOX 360 For Windows) J.GUID={0B9569C0-D4E6-11EB-8002-444553540000} 2=Button Box Interface 2.GUID={09EEC740-1D77-11EC-8001-444553540000} K=Button Box Interface K.GUID={09EEC740-1D77-11EC-8001-444553540000} 3=JoyWarrior A8-16 3.GUID={71EE1820-F9FE-11EA-8001-444553540000} 1=AGRONN Yoke P V1.0 1.GUID={96FE7D00-A48C-11EC-8001-444553540000} L=AGRONN Yoke P V1.0 L.GUID={96FE7D00-A48C-11EC-8001-444553540000} With both I get this result in the logging console. 510704 *** EVENT: Cntrl= 67276 (0x000106cc), Param= 0 (0x00000000) AUTOBRAKE_LO_SET 510719 *** EVENT: Cntrl= 67276 (0x000106cc), Param= 0 (0x00000000) AUTOBRAKE_LO_SET 510750 *** EVENT: Cntrl= 67276 (0x000106cc), Param= 0 (0x00000000) AUTOBRAKE_LO_SET 510766 *** EVENT: Cntrl= 67276 (0x000106cc), Param= 0 (0x00000000) AUTOBRAKE_LO_SET 510782 *** EVENT: Cntrl= 67276 (0x000106cc), Param= 0 (0x00000000) AUTOBRAKE_LO_SET 510813 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511204 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511235 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511250 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511266 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511297 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511313 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511344 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511360 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511375 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511407 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511422 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511438 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511469 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511485 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511500 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511532 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511547 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511579 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511594 *** EVENT: Cntrl= 67277 (0x000106cd), Param= 0 (0x00000000) AUTOBRAKE_MED_SET 511610 *** EVENT: Cntrl= 67278 (0x000106ce), Param= 0 (0x00000000) AUTOBRAKE_HI_SET 512016 *** EVENT: Cntrl= 67278 (0x000106ce), Param= 0 (0x00000000) AUTOBRAKE_HI_SET 512047 *** EVENT: Cntrl= 67278 (0x000106ce), Param= 0 (0x00000000) AUTOBRAKE_HI_SET 512063 *** EVENT: Cntrl= 67278 (0x000106ce), Param= 0 (0x00000000) AUTOBRAKE_HI_SET Any idea what might be wrong? Thank you! Best regards Andi

I tried it with these presets..I assigned them to the different switch positions via fs control and Parameter "1". Unfortunately it did not work 😞 Any idea what Ive done wrong? //PMDG737/Autobrake PMDG_B737_AUTOBRAKE_RTO#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) PMDG_B737_AUTOBRAKE_OFF#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) PMDG_B737_AUTOBRAKE_1#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) PMDG_B737_AUTOBRAKE_2#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) PMDG_B737_AUTOBRAKE_3#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) PMDG_B737_AUTOBRAKE_MAX#46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46001 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE) 46002 (>K:ROTOR_BRAKE)

Hi, thanks for your replies. I'm not that familiar with programming and scripting so I'm very unsure how this will work and what I need to do now. I have a 6 position hardware rotary knob, where all 6 positions can be individually assigned. So if I put this lua file in my modules folder, have it automatically loaded via an entry in the FSUIPC.ini under [Auto] section and assign it to each position of my hardware rotary as .lua script it will work? Sorry. I fear there is a long way for me to go.

My idea was to simply ignore the current rotary position by going to decrease as much as possible (6 times should be enough but I could also do 10 times or more). This way I can be sure that the rotary is at RTO each time before I do the defined increase step afterwards. Would that work?

I'm unfortunately not familiar with lua scripts 😞 Is there the possibility to assign several actions to be performed when the rotary is set to one specific position? E.g. rotary to second position and FSUIPC does the following commands: 6 times.... PMDG_B737-7_AUTOBRAKE_DEC#46001 (>K:ROTOR_BRAKE) 2 times PMDG_B737-7_AUTOBRAKE_INC#46001 (>K:ROTOR_BRAKE) I have heard somewhere that you can do multiple actions by editing the FSUIPC ini file. Thank you! Best regards Andi

Thanks for your reply and for testing it out 🙂 I assume I will only be able to increase or decrease the Autobrake rotary this way but it will not be possible to set a specific autobrake value like "2" or "RTO", correct? Or is there a workaround? Maybe decreasing it by 6 increments each time and then increase it "1" time for RTO, 2 times for "OFF", 3 times for "1" and so on.

Hi John, thanks for your reply! Ok I will try it. Not sure if the old P3D NGXU custom controls will work though. Or are there already some new custom controls for the MSFS 737 out?