NovemberUniform

I have a similar question. I made a lua plugin that I also shared with a limited number of users from the community. It needs the WAPI to run, because there is interaction with LVARs of the add-on aircraft it was made for. On my computer, everything is running fine. In the log file, I can see the WAPI loading and connecting on startup. There are users, where the loading of WAPI is apparently not happening (not in the log), altough they tell me it is installed and presumably running, if they go to the FSUIPC "Add-ons" tab -> "WASM". What can prevent the WAPI from loading? If it is listed as running in the "Add-ons" tab -> "WASM", why it doesn't show in the log? Is there more to it? Thanks for helping.

I did, and with another addition, this is working fine now. With mouse clicks between or during data entry, MSFS could regain focus. So I put the line ipc.control(1156) -- set focus in a event.timer(20, "callback_fcn") callback function, to keep the focus on FSUIPC during data entry. This works very good now! Yes, 100%. Also, no problems with long key presses anymore. I'm happy, and I can now concentrate on other parts of my plugin. 👏

Sounds excellent. Your efforts are very much appreciated. I will have a look as soon as possible.

Sure, thank you.

Well, this is essentially the same thing that I did. It won't bring me any further, I guess. I then tried to create events for mouse actions to more or less dial in my values with the mousewheel, instead of typing them with the keyboard, but the events didn't get triggered. Is this a known issue? event.mousewheeltrap("fMouseWheelScroll") -- event for mouse-wheel movement event.mouselefttrap("fMouseLeftClick") -- event for mouse-click left

I sent you the files. I think the biggest problem lies in the MSFS keys not being trapped. Whatever the problem is with longer key presses, I can live with that. Just don't press the keys longer than usual. In the meantime, I will have a look at your proposed alternative for ipc.ask(). Maybe it works better for what I need.

Hi John, here is what happened. If I click on the window prior to data entry, neither the window itself nor the sim receive any key presses. Strange... If I click on the FSUIPC window prior to data entry, the lua window receives the correct inputs and the sim keys are successfully trapped. So this is good, minus the FSUIPC window... If I click on the sim window prior to data entry (or just don't click anywhere, same result), the lua window receives the correct inputs but the sim keys are not trapped and their actions are triggered. I also tried this. I told you, duration of the key press has an impact on the way it is received. This is with scenario 2 (clicking FSUIPC window prior to data entry). If I press the keys very quickly, only keyUp is being listed in the log as not programmed. If I hold the keys down for longer, the keydown is being listed repeatedly as programmed in FSUIPC keys options. If I then release the keys, their preset is being performed. I hope that makes sense. I will also send you a stripped down version of the lua via PM. It should run under any circumstances for you to try out. Working on it right now.

Hi John, and thanks for your reply. Well, the keys I also use in MSFS are not trapped. They trigger the functions they are assigned to in MSFS. That's also the case, if I add LuaTrapKeyEvent=Yes to the ini. I guess, if I open the window like this, it has the focus. The keys I press get added to the window text... w = wnd.open("mywindow", WND_FIXED, 50, 50, 410, 220) -- (pos x, pos y, size x, size y) wnd.show(w, WND_TOPMOST) -- window always on top It's difficult to describe. I found out, that part of the problem is the duration the keys are pressed. I discovered it by mistake. I have assigned (via FSUIPC Key menu) all the numerical keys of my keyboard (the ones above the letters) to custom event presets for the Fenix A320. Those keys are no longer assigned in MSFS itself. If I run my lua plugin, the window is presented to me and asks me to enter numerical values and confirm with enter key. If I press the keys quickly, all is good. The keys are entered in the window and their assigned FSUIPC function is not triggered. If I hold a key for a longer duration, they also get entered into the window, but their FSUIPC fuctions are triggered on top of that. There is actually no reason to hold a key for a longer duration, but I will maybe release this plugin to a wider audience and it must be more or less fool proof for that. To make things more complicated, if one key was pressed for a longer duration, after that, even a quick press of other keys trigger their FSUIPC functions. Thanks, I might have a look at this if there is no way to get the stability with what I've tried so far. I would gladly show you my plugin but I would prefer to send it with a PM. Is this okay for you? Thanks!

Hi experts, due to lack of alternatives I'm using the WND library to enter data into my little lua plugin. I declared key events for certain keys, that are allowed to be pressed for data entry. Generally, it works as expected. The data goes where it should. But there is the problem, that the keys that I press to enter the data into the window, also trigger the action that they are assigned to (either by fsuipc or the the sim itself). This is not desirable, at least not in my case. I found out, that keys, which are assigned in the sim itself, always seem to "go through". Keys, which are assigned in FSUIPC, show different results. Some go through, some seem to be blocked. Is there a way to only allow the data entry into the window and block all other functions the keys might have? Thanks in advance.

I can confirm everything works with the latest version downloaded today. Thanks again! 🤗

Thanks John, much appreciated. It will take me a few days, maybe a week, until I can test it myself. I don't have access to my computer til then.

FSUIPC still going strong after all those years! Excellent service as usual. Thanks a lot.

Hi John, I can confirm the repeat does now work with hidden FSUIPC window. Good job and thanks very much! If the repeat rate would be adjustable (ini), that would give all the options. For my taste, with the Fenix A320, 50ms is slightly too fast. Related question: I have UseProfiles = Files enabled. Could I have a repeat rate specifically for each profile? That would be extra useful.

I will have a look in the late afternoon / evening. Thanks for taking care, John. Sounds very promising.

Hello Sehadi, what you quoted is all I can share at the moment. I haven't looked much further, as I ran into troubles with using keys. That's what this topic is about. You can look there. Just google it.

Same with me. All axes except throttle and tiller (nose wheel steering) worked. I had to assign these two in the MSFS own controls menu. It's not a big problem for me, though.

Yes, that's the correct LVar. I do it like this in the myevents.txt // FENIX A32X FNX32X_FCU_SPD_DECR# (L:E_FCU_SPEED, 1) -- (>L:E_FCU_SPEED) FNX32X_FCU_SPD_INCR# (L:E_FCU_SPEED, 1) ++ (>L:E_FCU_SPEED) FNX32X_FCU_HDG_DECR# (L:E_FCU_HEADING, 1) -- (>L:E_FCU_HEADING) FNX32X_FCU_HDG_INCR# (L:E_FCU_HEADING, 1) ++ (>L:E_FCU_HEADING) FNX32X_FCU_ALT_DECR# (L:E_FCU_ALTITUDE, 1) -- (>L:E_FCU_ALTITUDE) FNX32X_FCU_ALT_INCR# (L:E_FCU_ALTITUDE, 1) ++ (>L:E_FCU_ALTITUDE) FNX32X_FCU_VS_DECR# (L:E_FCU_VS, 1) -- (>L:E_FCU_VS) FNX32X_FCU_VS_INCR# (L:E_FCU_VS, 1) ++ (>L:E_FCU_VS) I don't have to specify a format in this case and it works. I just found out there is a database also including presets for the Fenix over at Hubhop by Mobiflight. That's handy. If only I knew where to read about the syntax of these calculator codes for presets. They can be very powerful it seems.

Correct. Thanks for checking, John. Indeed. Thanks anyway Roland.

Hi there, I want to bind some FCU rotary knobs of the newly released Fenix A320 to keys of my keyboard. For example, I want to decrease the ALT while holding the "9-key" (not Numpad) and I want to increase the ALT while holding the "0-key" (again not Numpad). For that, I created custom presets of the appropriate LVars in the myevents.txt. Then I assigned the keys with the FSUIPC Key Assignment, choosing my custom presets from the drop down. So far so good. My ALT is increasing and decreasing only by one increment, if the keys are pressed, but the keys are somehow not repeated, if I keep the keys pressed. I found out, this only works, if the FSUIPC window has the focus, which it naturally has not, while simming as usual. The sim window has the focus. I tried different key of the keyboard, not just numbers, but it didn't change the situation. I tried the same presets assigned to buttons of my controllers. Here the button press is repeated while held, even if the sim has the focus and the FSUIPC window is in the background. Is there a way to achieve what I want with repeating key presses, or is this a limitation of the sim SDK? Thank you very much! Nils

I used the simple notepad provided by windows 7 to edit the ini file and I don't know another way to type " than pressing SHIFT+2 buttons on my keyboard. Moreover, I would still run into problems if my " were not the correct ones, as the path to the exe still contains spaces now as it is. I can not see where I am doing something wrong... Anyway my problem is solved, I just wanted to let you know in case there is something that needs to be fixed. Regards Nils

Hi Pete, first, as this is the first time for me writing in these forums, let me start by saying thanks for your ongoing work for our community. Much appreciated. Second, I used the search function but could't find topics related to the problem I came across. Now, my finding is the following. I wanted to run Fiber Accelerator (FA) together with FSX using the help of FSUIPC (V 4.934 in this case). In the beginning I didn't install FA in the proposed directory but in another I freely chose. The entry in the ini file looked like that: Run1=CLOSE,"C:\FSX\FSX Fiber Accelerator\FSX Fiber Accelerator.exe" When I started FSX I always got an error popup telling me, that FSX is already running. Apperently FSUIPC tried to start FSX again instead of FA. Only after deinstalling and installing Fiber Accelerator in the default location C:\Program Files (x86)\FSPS\FSX Fiber Accelerator\FSX Fiber Accelerator.exe I got it working. It's no big deal, but something seems to be wrong here. I just wanted to let you know. Greetings, Nils