Tutmeister Posted 19 hours ago Report Posted 19 hours ago I am having an issue with throttle_set values only working once unless you move the axis. For a particular custom reverser setup, I have the throttle lever calibrated as normal (no reverse zone set). Then by using a button press I want the throttle to go to a specific value, lets say -100. So, using throttle1_set and putting -100 in the parameter box this seems to work. It engages reverse but doesn't throttle up. i.e idle reverse. Then using another button configured to throttle1_decrease I can increase the amount of reverse thrust, and when this is released it activates throttle cut which kills the reverser and returns the engine to idle. The above works ok, but the problem I have is, if I now press the button for throttle set -100 again then nothing happens. The lever does not move and I have to move the throttle axis forwards a bit then back. Then I can use throttle set again. I have tested with multiple aircraft (PMDG 737, 777, default 747, multiple GA propellor aircraft) in msfs2020 and 2024 and even simplified the testing by setting up 2 buttons, one sets the throttle to a specific parameter (2000) and the other sets throttle cut. If you cycle between these 2 then the throttle should move from idle to 2000 and then back to idle. After pressing throttle cut you cannot use the throttle set again without cycling the axis lever. I know this is quite a specific problem but does anyone know why this might be? It is needed for a very specific hardware setup I have. Could someone verify by using 2 buttons to switch back and forth between throttle cut and a set value? Hope this makes sense and thanks. Chris
John Dowson Posted 10 hours ago Report Posted 10 hours ago 8 hours ago, Tutmeister said: I have tested with multiple aircraft (PMDG 737, 777, default 747, multiple GA propellor aircraft) in msfs2020 and 2024 and even simplified the testing by setting up 2 buttons, one sets the throttle to a specific parameter (2000) and the other sets throttle cut. If you cycle between these 2 then the throttle should move from idle to 2000 and then back to idle. After pressing throttle cut you cannot use the throttle set again without cycling the axis lever. I know this is quite a specific problem but does anyone know why this might be? It is needed for a very specific hardware setup I have. Could someone verify by using 2 buttons to switch back and forth between throttle cut and a set value? I have looked into this and can confirm this issue. It looks to be an issue with MSFS, but I will investigate further and report back, and will also raise an issue with Asobo. However, there is a workaround - you can use presets instead. I have tested this in a few aircraft and it works with presets - I have only tested in MSFS2020 but should also work in MSFS2024. Define two presets in your myevents.txt file (create this file if you do not have one): Quote //General Throttle_Set#$Param (>K:THROTTLE_SET) Throttle_Cut#(>K:THROTTLE_CUT) Then assign to these, giving the required parameter to the Throttle Set preset. Note that I have moved your post to the FSUIPC7 / MSFS subforum. John
John Dowson Posted 10 hours ago Report Posted 10 hours ago This is an FSUIPC issue. Successive axis control events that are masked (i.e. can be calibrated in FSUIPC) using the same parameter are currently ignored. I am not sure why this is (probably for performance issues with some devices), but I have removed this in the attached version. So please try the attached version, 7.5.5e. John FSUIPC7.exe
Tutmeister Posted 6 hours ago Author Report Posted 6 hours ago Hi John, Thanks for the fast response! I've been a long time customer of fsuipc and just wanted to say how much I appreciate it. I've tested this in 2024 and can cycle between a set value and cut multiple times without issue. Can I ask, is this going to be rolled into all future versions of fsuipc? It has bearing on a future product of mine. Thanks again. Chris
John Dowson Posted 5 hours ago Report Posted 5 hours ago Yes, this will be included as default in the next release, hopefully mid-October or before. As the code that caused this must be for some reason (but well before my time and difficult to deduce why), I tthink I will also add an ini parameter that, when set, will revert to previous behavior. Please also let me know about your product. I am currently working on a new FSUIPC website and support forums (as these will be closing soon). I would like to add a page, with links, to all software that uses/relies/depends on FSUIPC, but that will come post-launch. Cheers, John
Tutmeister Posted 4 hours ago Author Report Posted 4 hours ago That's great, thanks John. My product is actually hardware and is a set of throttle levers with integrated reverser levers that activate microswitches and I needed to be able to use the set function to allow selection of idle reverse as well as max reverse and then throttle cut when the levers are closed. What was happening previously was that you couldn't use the reversers again until you cycled the axis. Chris
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now