John Dowson

First, you posted in the sub-forum for FSUIPC7 / MSFS - please use the main forum for all other versions of FSUIPC, not the specific sub-forum for FSUIPC7. You also attached the trial license/key file for FSUIPC7 for some reason...I have removed that. Yes, that is the correct control/event, but be aware that the parameter for that control is in BCD16 format (Binary-encoded decimal), so to set to 120.80 you would use: ipc.control(66371, 0x2080) (the leading 1 is assumed). That is the difficult bit. You would need to register a function to receive key presses (using the event.key function) for the keys 'C'. 'O', 'M'. '1', ' ', 'S', 'B', ',' , and all the digits, then keep track of everything entered and in the correct order....I really can't recommend doing it this way.... Maybe take a look at this user' contribution, which is a lua script to allow keyboard entry for radios (as well as obs and AP). Its for FSUIPC4, but should work with FSUIPC5, although some small modifications may be needed: John

Well, its not going to be anything to do with the throttle itself - that will just be sending an axis value, as with all other throttles... Doesn't matter - and you don't have to. As the flaps are working for the user in the other post, it would be interesting to find out how this is assigned. If its not using LINDA, you can just copy that. if it is using LINDA, I can maybe take a look at what LINDA is using and replicate that (LINDA is just a fancy wrapper around FSUIPC's Lua functionality). The Rotor Brake control is another method of sending custom controls for PMDG aircraft - see That is strange...be careful though, as I think there were some issues when using the regular flpas assignments that could cause a loss of power when climbing...but that may have been for the 737 or for the MSFS version, not sure without checking... Was that with the standard flaps control? Could it either be due to a failure or maybe they are being controlled by the FMS? I am no expert on airliners and only fly these occasionally for test purposes, so better off asking about this on the PMDG forums, and check the 777 documentation.

You don't create them - they are either provided or not. Just try listing what is available: Log -> List Input Events and Add-ons->WASM->List Lvars. For Input Events, you can also log these in real time (Log->Input Events), so set that and then move the twist throttle and see if anything is logged. The FSUIPC7 main window also indicates how many Input Events and Lvars are available (as well as Presets and Hvars). No problem - sorry I can't help more, but its difficult not having the aircraft. I can only advise on the various techniques to try, and how to use those if you find anything. Regards, John

Note that another user also had issues with flaps in the PMDG 777, in the following thread: I have asked if he can share his settings, although he way be using LINDA for this... John

@Edmundo Could you maybe share your flaps settings as another user is also having issues, in this thread; Thanks, John

By the way, saw this on the flightsim forums (https://forums.flightsimulator.com/t/cowan-simulation-md-500-e-helicopter/572344/15😞 That was quite old (for V1 in Jan 2023, but maybe worth checking if this has been fixed... John

Very strange that it logs the throttle inc/dec commands - but you shouldn't use these on an axis/potentiometer. Not all axis that work when assigned in MSFS work when assigned by 3rd party apps - this is a known issue. For "set helicopter throttle axis", try using Helicopter Throttle Set - these are the specific 'helicopter' controls: If the standard controls don't work, lcheck for available Input Events and lvars. It is difficult for me to advise on this as I don't have this aircraft, and all add-on aircraft work in different ways. Maybe try asking on the aircraft developers support forum. You can also just assign this in MSFS - no problem mixing and matching assignments between FSUIPC and MSFS, as long as you don't have the same button/switch/axis assigned in both. John

Depending on what to control you are using, it could take a parameter, usually 0 for off and 1 for on... If the PMDG 777 custom flaps controls are not working, then maybe ask about this on the PMDG support forums.

Then I do not know why this PMDG custom control is not working. Maybe try the same control via the Rotor Brake method... I do not have the PMDG 777, but I can check this in the 737...however, I am currently away/travelling. I will look into this further when I return on the 23rd October (Wednesday next week). Sounds very strange though...are any of the PMDG 777 custom controls working for you? These have worked without issues for many years for most user.... John

Ok. Be aware that FSUIPC populates offsets for data based upon the standard simvars, which used to be used by most aircraft (but not all!). With MSFS2020, many more aircraft, some default and many add-ons, don't use or respect the standard simvars, and may use lvars, bvars (input events) or hvars (html variables) instead. If this is the case, then the default offsets won't work / hold the correct data. What you can do for such aircraft is determine what holds the correct data, add this to an offset, and then you can instruct FSUIPC to 'spoof' the reading of the original offset (that the 3rd party app is reading) to read the value of the correct value and supply this instead. If you want to do this, you need to know what offset is being read by the third-party app, and what holds the correct value. If you know this, I can help you with the rest... John

First, if this is a charity or not-for-profit organisation, I will give you a free license - no need to purchase. If this is the case, please PM me the details so that I can verify, and I will generate a free license for you. You also mention FSX - you need FSUIPC4 for FSX. This is the forum for MSFS2020 / FSUIPC7. Please clarify which simulator you are using - FSX or MSFS2020? They are very different beasts... With FSUIPC, you use a system called 'profiles' to have different settings/assignments for different aircraft. Just download and install the relevant FSUIPC version for the simulator you are using. The FSUIPC documentation will also be installed, which will tell you how to use profiles. And if you are using FSUIPC7/MSFS2020, start with the trial license which you can download from a sticky-topic at the top of this sub-forum. There is no trial license available for FSUIPC4 / FSX. John

Then you have a UserCfg.opt file in your user' AppData\Roaming\Microsoft Flight Simulator folder for some reason (did you previously have a Steam version installed?). Delete or rename that file and re-install. If that file is present in that folder, the installer (and FSUIPC) will think you are using a Steam install, hence the issue. John

You need to determine what to use for these controls. To do this, use FSUIPC's logging facilities. For the Twist Throttle, first try logging Axes Controls, open the logging console window (Log -> Open Console...), then twist the throttle in the VC and see if anything is logged. If so, try assigning to that. if not, try logging Input Events and again twist the throttle in the VC and see if anything is logged, and if so you can use that (I can help you in assigning an axes to an Input Event if you don't know how to do that). If there are no standard controls or Input Events, the next thing to try is lvars - try listing them (Add-ons -> WASM -> List Lvars) to see if any look appropriate, and if so try setting it (again using the Add-ons ->WASM menu entries) and you need to determine the value range of the lvar. If there is an lvar, I can also help you assign an axis to control this if needed. Not sure I fully understand this...you cannot easily map different ranges of an axis to different controls. To do this, you would need a lua script. Alternatively, you can just assign your axis to the twist throttle control (whatever that is!) and just send the throttle Cut control in an axis range (using the right-hand side of the axis assignment dialog). Throttle Cut is a standard control and should be available for button assignments and for axes range assignments. You cannot use this control as an axis assignment as this makes no sense - axis assignments take a parameter (the axis value) but Throttle Cut takes no parameter - it is usually assigned to a button (and usually a detent button on a throttle). Note I am currently travelling so support will be intermittent until Wednesday next week. John

Sorry but i have no idea what your issue is.... Be aware that FSUIPC is aircraft agnostic (generally, although it does have specific offsets for PMDG aircraft). If any offsets or controls are not working for a given aircraft, it is because the aircraft does not use that event or simvar. It will only detect these if the aircraft you are using uses the standard simvars for these data points. I have no idea what APLv2 is... What is wrong? Proof (i.e. logs)? Explain what you mean by 'gets data'? I think you are either mistaken, or the aircraft you are using is not implemented correctly...there has been no change in the lights offsets (0x0D0C) for many years (if that is what you are talking about). If they are reporting the wrong data, then the aircraft is setting the wrong data and needs to be reported to the aircraft provider. But I think it is more likely you are either misunderstanding something or have an error somewhere. What do you mean by ' If you have an issue, please show me your files - your FSUIPC7.ini and FSUIPC7.log files, the latter with appropriate logging activated for your issue...whatever that is... But what has this got to do with FSUIPC? FSUIPC just reports and responds to the events seen/received.... Sorry, but I really have no idea what you are talking about...please explain more clearly, if you think this is an issue with FSUIPC... Maybe.... PS: I am now on holiday/away for a long weekend, back on Wednesday....

First, please change this: to this: That won't make any functional difference, but you should understand why the other entries aren't needed.... I don't have the PMDG 777 so cannot test/try these controls to see if they work correctly. Please do the following: - start the sim and load the 777 - open FSUIPC7, and activate logging for both Events and Axis Controls - make sure you also check to Send to console window, so you can see the events when logged - move the assigned flaps axis through its full range, from 0 to 30 and then back again. - exit P3D, and then show me/attach your FSUIPC6.ini and FSUIPC6.log files and tell me what, if anything happened when you moved the flaps lever I don't have the PMDG 777 so cannot test those controls here. And I can only help you confirm if the correct controls are being sent as assigned (which i am sure they are, if assigned correctly). Also, please test/try those custom controls to see if they actually work, e.g. assign a button or key press (temporarily) to one of the flaps settings and see if triggering that moves the flaps. If not, then maybe something else is preventing these controls from taking effect... John

By moving your axis and clicking the From and To buttons - as described in the User manual: Change the file either with FSUIPC not running, or with the Axis assignment panel open, and click Reload all assignments when done, otherwise it will get overwritten with the current settings.

👍 No, not necessary with MSFS - you can have assignments in both MSFS and FSUIPC7 - just make sure you don't have assignments to the same button/switch/axis in both. John

Then this sounds like the lvar only controls the switch position, and something else actually changes the lights. Is anything logged when you switch the lights on/off? If so, you can try using that. You can also try offset 0x0D0C to see if that holds the correct light state, and you can also try writing to that offset (bit 8 for logo lights). Otherwise, see the following article on how to determine how a switch/button functions: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ What type of variable is this? To toggle an lvar, use, e.g (L:VC_Logo_Light_SW_VAL) ! (>L:VC_Logo_Light_SW_VAL) But that toggles between 0 and 1, not 10... The events.txt file is provided by MobiFlight. See https://hubhop.mobiflight.com/presets/. For question or help with defining presets, try the MSFS2020 channel on the MobiFlight Discord server. The events.txt use calculator code, which is in Reverse Polish Notation - see the following: https://docs.flightsimulator.com/flighting/html/Additional_Information/Reverse_Polish_Notation.htm Also please don' modify or add anything to the events.txt file (as this will get overwritten the next time toy update). you should use the myevents.txt file. See the Advanced User guide on using the events.txt file in FSUIPC (in WASM section). John

You don't do things like that really... There are two choices: - capture the key press/release event using event.key. The lua script needs to be running to do this - such scripts are usually auto-started, - have two lua scripts, and assign one to be called/ran on the key press, and the other to be ran on the key release Using events is the preferred method and will be quicker than having two separate scripts,

Did you not understand my last comment? It is obvious what is wrong if you actually look at the panel or at you ini file... You are again NOT using the correct control numbers: - your first range is using control number 16000 with a parameter of 74703, when it should be using control 74703 (and no parameter needed) - your second range is using control 11319 with a parameter of 74704, when it should be using control 74704 with no parameter needed - similar issues with your 3rd and 4th ranges Try deleting the addition parameter you have added, highlighted in bold below: i.e. Remove those 0,

Just took a look at both the stable and dev versions and I see the same in both - this lvar stays at 1 regardless of the position of the switch. You should maybe report this to FBW. So try the simvar instead. Once you have added it to an offset, log/monitor that offset (using FSUIPCs offset logging facilities) and see if that changes value when you change the switch position. I have checked that in the dev version and it works there - this is the entry in the myOffsets.txt file that I use to add the simvar to offset 0x66C0: // offset, size, simvar, type, units [, w] 0x66C0, 1, CABIN SEATBELTS ALERT SWITCH,I32, Bool This should also work in the stable, but please test. John

In your first ini, you are using the standard controls, which won't work. In your second ini, you are using custom control numbers 70607m 60608, etc, whuch do not exist. For EVT_CONTROL_STAND_FLAPS_LEVER_0, which is THIRD_PARTY_EVENT_ID_MIN + 5071, use 69632 + 5071 = 74703. Flaps 1 (5072) would be 74704, etc. You are also are not using ranges but specific points: you need to use a range around the detent value, as entering a detent will not always give a specific value., and entry 9 has the same range defined as entry 6. Try a range of around 400 around the detent value. e.g.

Hmm..what version of the FBW A320 are you using (release or dev)? It should hold the correct value, according to the MF presets... That is a simvar that is currently not held in any offsets. To be able to read the value of this simvar, you first need to add it to a free/spare FSUIPC offset. You can do this via the myOffsets.txt file - please see the Advance User guide, section Adding Simulator variables (simvars) to FSUIPC offsets on page 35 of the Advanced User guide, Once it is in an offset, you can read the value using the lua ipc library to read offset values. John

First, this topic is for requesting a trial license only. If you want to try FSUIPC7 for your issue, please download the trial license, available in the first post in this topic, and at least try assigning to the steering controls/events (Steering Set or Axis Steering Set, or the FSUIPC-added Steering Tiller control) , and see if that works, Please also see/read the section on the Steering Tiller axis (in the box) on page 33 of the FSUIPC7 User guide. If you still need help after trying, then post again for assistance - in a new topic please (or one that is already for steering tiller issues), And also please state which aircraft you are using - a steering tiller assignment in one aircraft may not work in another. John

For the position of the overhead seatbelt switch in the FBW A320, just read the lvar L:XMLVAR_SWITCH_OVHD_INTLT_SEATBELT_Position, i.e. seatBeltSwitch = ipc.readLvar("L:XMLVAR_SWITCH_OVHD_INTLT_SEATBELT_Position") John