John Dowson

Try activating logging for Axis Controls and Events. Open the logging condole (Log -> Open Console) and see what (if any) events are logged when you move the throttle/flaps in the cockpit UI. If you see any events logged, you can try assigning to those. John

Or maybe better to wait 250ms (for example) for the first key repeat, and then 50ms for subsequent repeats? I think it is necessary to have a longer repeat interval for the first repeat as this will affect all current key assignments (when 'no repeats' has not been selected). This is implemented in the attached version, v7.3.5b: FSUIPC7.exe John

@NovemberUniform I have looked into the key repeat issue...I don't think this has ever been working properly in FSUIPC7! The problem is that only the initial key press is received from the FS - no repeats are received, and later the key release. I've checked in 7.3.3 and repeats were not working in that version, and I doubt that they were in any previous version. It is strange that this issue has not been reported previously... I have added some code to enable repeat key presses to be detected. Basically I generate these internally and send repeat key presses until the key release is received. In the attached version, I have set repeats to be send every 50ms. I can adjust this (if needed), or maybe add a new ini parameter so that this can be set/changed by the user. What do you think? Anyway, please try the attached version, v7.3.5a. I can adjust the repeat rate, or make this adjustable, as you prefer. Let me know. FSUIPC7.exe John

You could do this but you would have to write a lua script and control your axis assignments in lua, monitor for the button press and switch the control used when you receive the button press event. You would need to assign your axis to write its value to an FSUIPC offset, monitor that offset in lua (using event.offset) and then either send the appropriate control (for either manifold pressure or propeller RPM) depending upon whether the shift key has been pressed or not. John

You need WideFS6 - it is available from www.fsuipc.com - it is no longer supported but a free license is available. John

Your EXE.xml looks fine - I do not know why MSFS is not starting FSUIPC7 as it should. Is your vdgs-util.exe program started? You could try changing the order in which these programs are started - to do this, try the attached EXE.xml: EXE.xml If that doesn't work, I can only re-iterate what has already been said on this topic: - check that you have not set FSUIPC7 to run as admin - check folder permissions are set correctly - if all else fails, go back to the old method of starting FSUIPC7 via the MSFS.bat file - instructions on how to do this are posted earlier in this thread. John

There are issues using the Xbox One and Xbox 360 controllers with FSUIPC as they are XInput devices. You need to install additional software for these to work correctly. Please see the README.txt included in the zip file you downloaded: John

Then this is a problem with Foreflight - I cannot help you with this. As FSUIPC4 is installed and running correctly, I don't see how I can help - you need Foreflight support really... Your log is large as you have logging of IPC Reads/Writes activated - turn that off. John

No. You would have to use the lua ipc.createLvar() function (or create it via offsets), and then issue an ipc.reload() to reload all lvars (although I'm not sure that is necessary as it may be done by the function itself - I would need to check). I'm also not sure the the [LvarOffset] sections is reprocessed on a reload() command...they should be, but if not then you would need to add an event.Lvar function to and add/update the offset in the handling function.

The ini you attached is from 7.3.3, and looks fine and loads ok here. Do you have a problem now or not? Not sure if I am supposed to be looking into anything... That's not possible as calculator code runs in the FS and offsets are part of FSUIPC (and in a separate process). However, if you want the value of a calculator code expression to go into an offset, you can create your own lvar, asddthat to an offset, and then update the calculator code to write the value to that lvar.

This is not correct. Why don't you consult the documentation if you do not know how to use a facility before posting.... The correct format should be: [Auto.PMDG 737-700] 1=Lua PMDGAutoBrake In your lua file,why didn't you just change the variables at the top of the file? Doesn't really matter, but you didn't change the last event.button call: That last one should probably be: event.button(4, 135, "PMDG_MPNL_AUTOBRAKE_MAX")\ Any further issues, try looking at the documentation first, and also check your log file (you can add appropriate logging) which should tell you what is happening.

Sorry, but I so not understand your issue or what this has to do with FSUIPC4... WideFS is for use on a client PC, and all your licenses will be available from your SimMarket account. Is FSUIPC4 installed correctly? Can you access the FSUIPC4 main window from the add-ons menu? Can you please explain your issue, and if you are having problems with installation then show me your FSUIPC4 installation log file. If FSUIPC4 is installed and running, show me your FSUIPC4.log file. John

Do @NovemberUniform or @roland_lfor have your throttle's set-up for the Fenix A320? If so, maybe toy could help the user in this post: John

So repeat isn't working when MSFS has the focus? I will check this. Key repeats should be sent to the sim. There were some changes to processing key assignments and sending keys in the latest release (v7.3.4). I'm pretty sure this was working in earlier versions, so I will look into it... The OP's problem is with key repeats - button repeats are working as expected. John

Then why post here - I think you need support for FSeconomy - I know nothing about that program, sorry.

That sounds strange. Do you not have any assignments? I see you are not using the events.txt file but have 2 events in your myevents.txt file. Maybe try again with your previous ini to see if that still gives issues and if so post it here and I will take a look.

First, use the number for your device - I suspect that it is 0, but you can confirm by looking at the joy letter / id mapping in the [Joy\names] section of your FSUIPC7.ini. Second, the lua must be auto-ran - add it to your [Auto] section, or, better still, your [Auto.xxx] section (where xxx is the name of the profile you use for the PMDG 737). You do not need to make any assignments to the lua. Anu issues, activating logging for Lua Plugins and show me your FSUIPC7.ini and FSUIPC.log files. Not 100% sure what this means, but looks ok to me. keep this thread updated if you hear anything, thanks.

You should check if the calculator code for the preset is working or not first (as explained). Also check that it is being sent - activate logging for Buttons * Keys as well as events, and check your FSUIPC7.log file to confirm that it is being sent. You can also post your FSUIPC7.log file here and I can check it.

I'm not sure and cannot really help as I don't have this aircraft...maybe it is a timing issue? What happens if/when the gear is UP and you send the gear-off calculator code e.g. using Add-ons->WASM->Execute Calculator code using 30 (L:switch_455_73X) - 10 div s0 :1 l0 0 > if{ 45501 (>K:ROTOR_BRAKE) l0 -- s0 g1 } l0 0 < if{ 45502 (>K:ROTOR_BRAKE) l0 ++ s0 g1 } ? Try that to confirm the preset actually works. If so, you may need to add a delay, to allow time for the Gear-up to complete. before sending the gear-off ccode. If the calc code doesn't work, I cannot help with that - maybe ask on the MF discord channel. John

You need to have the WASM installed and enabled to use presets - check the Advanced User guide, un the WASM section. If the WASM is enabled correctly, you should see the menu entries active under the Add-ins->WASM menu - try listing lvars to confirm the WASM is installed and connected. Note that you need an aircraft loaded and ready-to-fly (i.e. not in the MSFS menu). Also check that you are using the latest version of FSUIPC7, v7.3.4 - if not, update. John

That would be good, thanks. The best place for this would be to create a topic in either the FAQ sub-forum or the User Contributions sub-forum. It would be better to do this as a post, rather than a document. But if you prefer to do this in Word 2003, you could export this as a pdf and attach it to a post in one (or both) of those sections. John

No. If the lua is auto-running, why assign a button to start it? You cannot assign a button to a function in a lua script. To use the lua, you need to add some event.button calls which would call the appropriate lua function when one of your rotary buttons was detected. I have put together a script for you to try this - download to your FSUIPC7 installation folder and change the following variables to match your hardware: The script should be auto-started, preferably from a PMDG profile section: PMDGAutoBrake.lua (NB. script not tested as I don't have this aircraft!] What happened? Did you look at the log or try logging *Buttons & Keys + Events) to see what is happening? There is no point just saying 'it doesn't work'... Also, if writing your own presets, you should test the calculator code first using the Add-ons->WASM->Execute Calculator Code menu option, to check that it has the desired affect. Otherwise you could follow the advice of @mtjoeng and install LINDA...

What list? Check that you are using the latest version of FSUIPC7, v7.3.4. If so, there should be a preset you can use for this: Preset: PMDG B737-7 GEAR OFF John

Ok, that is interesting....but I can't see any changes between these versions that would cause this... Could you show me an FSUIPC7.log file from both versions please. John

All the FSUIPC documentation is installed under your Documents folder, as well as a README.txt that is contained in the zip file you downloaded. You should at least read the README,txt and the Installation and Registration guide, which will tell you what is installed and where. However, if you are using an unregistered version for use by an FSUIPC client application, you don't normally need to do anything, and any config needed should be specified in the documentation for your client program. I cannot see how this can be related to FSUIPC7. As a test, uninstall FSUIPC7 (using the uninstallFSUIPC7.exe that will be in your FSUIPC7 installation folder) and see if you get the same problem. John