Joan A

Solved! An end was missing.

Hi, I'm trying to run a Lua automatically without key press. The lua name is 737AutoOps, the ini file looks like this: [LuaFiles] 1=737AutoOps [Auto] 1=Lua 737AutoOps and the lua file script: function ATRST () var = ipc.readSW(0x088C) if var < 1390 then ipc.macro("737NGXU:ATRST") end event.timer(500, "ATRST") I want to run a macro file (which works ok if assigned to a key) when thrust levers are less than 1390. I don't know what I'm missing here. Thanks in advance.

Ok. I can confirm after one leg, (2 hours sim total) that the problem is gone. The solution was to send the exact steps through the Lua script. I attach the Lua plugin in case someone else come across the problem in the future. FSUIPC wins again! Thanks Pete Throttle.lua

Nothing, in fact, the last tests I opened P3D with no controller and tested standard F3,F2 and F1 to be recorded in the log and waited for one exact hour and voila the increments changed. Tested then the same keys which gave me the same entries that the first ones. Tried the same test with default "standard.xml" and "standard.xmlx", the same files with "read only", my own modified files with "read only", tried the three options INCREASE_THROTTLE, THROTTLE_INCR and THROTTLE_INCR_SMALL and the result is always the same. Very strange, really, I never had this problem with FSX, P3D V3... and across the internet I found only two posts from years ago. So I believe it's something difficult to be tracked. 2013 https://www.flightsim.com/vbfs/showthread.php?279421-Throttle-unresponsive 2016 https://www.prepar3d.com/forum/viewtopic.php?t=119494 I know, but I hope that instead of sending the THROTTLE INCR directly which even with the keyboard sends different steps, (I guess that smaller or higher depending on the time being pressed), sending an exact number of steps could bypass the culprit. I don't know, I'll try later a flight EBCI-LGAV with the NGXu and see if when on final approach I found the solution and get the throttles working as expected. Thanks!

Ok, got it working finally! I really hope i do not get ever again the increments problem.

Ok, revised code. Still no luck

Hi, unfortunately the problem is back. No matter what I try the problem persists. One exact hour and the increments are changed for gamepad buttons and keyboard keys. I tried to make an xml code to set the exact steps whe throttle lever position is inside a range, but as the GENERAL ENGINE THROTTLE POSITION is in percent and the values sent THROTTLE_SET are in 16383 range it's not as easy as I thought. So as a last resource, is there a possibility to set a Lua for exact steps when THROTTLE_INC is pressed? One additional problem is that I need the lua code to be made to use it with "flags" through LuaToogle because in my system the standard lua plugins stutter when the action is performed, something which does not happens with flags. Never mind, I came across a Lua plugin I use for Aerosoft rudder which works perfectly for that purpose. Then, I thought it could be modified to do the same but with throttle set steps. Here is the rudder lua code which works ok: And here is the modified one which I tried with no luck. I used the Engine 1 offset to try, but the main idea is to couple both engines with the same flag. Any help wold be appreciated!

Ok. Many thanks Pete. The problem seems to be solved for now. I’ll report if I find something else.

Ok, so it seems I solved the problem. I'm not sure what the culprit was because before logging the events I removed all asssignments from P3D and send those through FSUIPC. And voila, no problem after more than an hour. Then I saw that in the previous Standard.xml controls file there were double assignments for the same actions between two different controllers with different GUIDS. I always use the same controller, but sometimes P3D reads it as a Logitech model and other times as an Xbox controller. I was aware of that, the change is when I start the controller before starting P3D or starting it once P3D already started. Also, I came across the option of "USB Selective Suspend", which I did not know, and I disabled. So could the two GUIDS and the double entries (two of them Throttle Inc and Dec) be the culprit here? Could be that P3D read a different controller when W10 power off the USB (after an hour)? The controller still working but with another GUID, hence the increments change? Thanks!

Hi Pete, thanks. I explained myself wrong, just for comparing the proportion. In fact, the usual setting I use is “Throttle Increase” internal P3D with the Repeat slider in the middle, which gives me the typical 512 increments I guess. When the throttle decides to change the increments itself after an hour I can revert to the initial setting by putting the Repeat slider to the right. So, it is like P3D half-sizing the throttle steps after an hour. Really strange, I’ts driving me crazy. I’ll take a look at the log to see if there’s something that sheds some light on this. Thanks again

Thanks Thomas. I’ll do it, I’ll take a look if it gives me an idea of what is going on.

Hi, I'll copy the same post I leaved on P3D Froum, in case of someone else had the problem or if anyone have a clue. Thanks. I use gamepad buttons to control throttle, but the problem also happens if I use the standard F2 & F3 keys. I have a problem with the throttle sensitivity. After an hour or so, (never less than an hour) the throttle sensitivity reduces to more than a half. So, for example if you start the flight there are let’s say 10 increments from idle to full thrust, after an hour flying you’ll need 25-30 increments from 0 to 100. It happens with every aircraft (default or not) except with Aerosoft Airbus, which I believe it has a custom throttle code for detents. I tried default aircraft, PMDG NGXu, QW 787, VRS F-18... The problem persists with and without any addons, with and without FSUIPC, tried “throttle increase” and “throttle decrease” P3D controls, I did the same through FSUIPC... no luck. I have no idea from where the problem could come from. Using P3D 4.5 Hf3 (but it also happened with older versions). The FSUIPC log does not show anything strange or relevant when it happens. Any advice would be appreciated. Thanks in advance

Hi Roman, Yes, it works! It does work with default aircraft without stuttering, but it behaves strangely with the AS Airbus, it works "partly", with FBW doing its stuff. Strange, because without events was working well despite stuttering. I'll keep testing anyway. Many thanks Roman, I really appreciated all of your help.

Hi Roman, Thank you again, I tried it but it does not do anything. Maybe I'm doing something wrong, but after replacing the script, and adding the plugin to the [Auto] section the plugin does not work. No action is shown in the FSUIPC console when buttons pressed. Just to add that with the original script the stutters were also happening with default aircraft. In fact I tried with one of the Lua plugin that comes with FSUIPC, the gradual braking and it also stutters when I trigger the button. This is happening in fresh install of Win10 with last updates and fresh install of P3D 4.3. It seems that all the Lua Plugins I try I have massive stuttering when applied. I'm going mad with this. Thank you.

Hi Roman, Many thanks, I didn't expect such a detailed explanation, even taking the time to modify the script. I would never have been able to do it myself. I really appreciate your help. I've been using FSUIPC for some time and I experimented with offsets but I really do not know anything about deeper knowledge of the coding capabilities that it offers. But I get what you are saying about the new efficient way of invoking it with events. I'll try tomorrow the script and let you know. Thank you!

Hi, After installing the new AS Airbus for P3D V4, I tried to load a Lua file to move the rudder with a joystick. This Lua plugin was made years ago by Enrique Vaamonde for the 32bit version of this aircaft. The plugin works well, but every time I press the buttons and the plugin is working I have hard stutters, (tried with gamepad and with keyboard keys also) only when it is applied. It has something to do with the change of 32 to 64 environment? It needs some kind of modification inside the Lua file? Many thanks

An update to the topic. Problem is solved. After looking around here and there I found some topics where Pete suggested that wxstationlist.bin could be the problem. Deleted the file, let P3d generate a new one and voilà. Everything is working back again. Thanks for the quick support anyway!

Yes. I tried that. Everything goes well with all addons activated (uninstalled and installed again) one by one. The problem starts when FSUIPC (last addon installed) works with Latin Vfr Barcelona, and only in that scenery or close to it. If I uninstall FSUIPC all works fine again. And also if I am at an airport far from LEBL no problem at all. Don’t know, seems like LEBL and FSUIPC don’t get along with each other. PMDG is brand new ngx for v4 released today. But it happens with default aircraft also, in fact my default flight is with default Beech King Air, wich is with the one I reproduce the CTD. (I tried other aircraft of course). I’ll keep 5.103e and try tomorrow again. Thanks

Hi Thomas, Yes, I tried with 5.103e with no luck. Here is the Crash report. I attach you two of them, as the error dll is different sometimes. Menus.dll, KERNELBASE.dll, facilities.dll... Many thanks in advance.

Hi, I have a really odd problem. I bought FSUIPC5 for v4 some days ago. I have flown without problems until then with GSX, Active Sky and LatinVFR LEBL, default and PMDG aircraft. But since I installed FSUIPC 5.103 I get a CTD every time I am or I get close to LEBL. If I start from let's say KJFK or LIRF there's no problem at all, the problem is with both FSUIPC and being at LEBL. I tried several things, reinstalled LEBL, GSX and FSUIPC with no luck. I attach the log and files if it helps. Many thanks in advance. Joan FSUIPC5.ini FSUIPC5.log