These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Throttle axis conflict, stays at idle while axis working
MSFS2024, latest FSUIPC version. The aircraft is HondaJet. VKB STECS throttle
I did not have this problem before and dont know what changed.
MSFS assignments are clear/deleted for throttle everywhere.
In FSUIPC the throttle is configured ok (see pics below).
When i use the throttles they briefly respond but the engine marker remains at idle. It is like something is keeping the the engine at idle. If i close FSUIPC and assign the axis in MSFS it works fine. So it must be something in FSUIPC.
I also include the fsuipc.ini
Also here are my honda custom events:
//FLIGHTFX/HONDAJET
e4-hdjt-baro-push#(>H:AS3000_PFD_1_BARO_PUSH) 1013.25 16 * (>K:2:KOHLSMAN_SET) l0 (>L:INSTRUMENT_Altimeter_1)
e4-hdjt-baro-inc#(>H:AS3000_PFD_1_BARO_INC) 2 (>K:KOHLSMAN_INC)
e4-hdjt-baro-dec#(>H:AS3000_PFD_1_BARO_DEC) 2 (>K:KOHLSMAN_DEC)
e4-hdjt-throttle-right-idle#0 (>L:THROTTLE2_SET) 50 (>L:HA420_ThrottlePos_R)
e4-hdjt-throttle-left-idle#0 (>L:THROTTLE1_SET) 50 (>L:HA420_ThrottlePos_L)
e4-hdjt-throttle-right-cutoff#-1 (>L:THROTTLE2_SET) 0 (>L:HA420_ThrottlePos_R)
e4-hdjt-throttle-left-cutoff#-1 (>L:THROTTLE1_SET) 0 (>L:HA420_ThrottlePos_L)
e4-hdjt-external-power-on#1 (>L:GROUNDPOWER)
e4-hdjt-cabin-power-on#(L:CPOW Pushed, Bool) ! (>L:CPOW Pushed, Bool)
e4-hdjt-eadi-baro-hp#1 (>L:useHpaUnits)
e4-hdjt-eadi-baro-in#0 (>L:useHpaUnits)
e4-hdjt-engine-anti-ice-toggle#(L:HJET_ENGINEAI_L, bool) ! (>L:HJET_ENGINEAI_L, bool) (L:HJET_ENGINEAI_R, bool) ! (>L:HJET_ENGINEAI_R, bool) (L:TAILDEICE_KNOB, Number) 1 == if{ 0 } els{ 1 } (>L:TAILDEICE_KNOB, Number)
e4-hdjt-zoom-inc#(>B:AS3000_TSC_Vertical_1_Joystick_Range_Zoom_In)
e4-hdjt-zoom-dec#(>B:AS3000_TSC_Vertical_1_Joystick_Range_Zoom_Out)
The standard FS throttle controls do not work with the HondaJet. There are already some MF presets defined to control the HondaJet throttle: e.g.
However, those presets are for a potentiometer - for use with a standard axis range of -16384 to + 16384 you would need to define your own preset with correct calibration for your axis (define this preset in your myEvents.txt file) and then assign to that. You probably just need to divide by 327.68 rather than 20.46, so you could try the following presets:
My HA420 Throttle 1 Set#@ 327.68 / 50 + 50 max 100 min d (>L:HA420_ThrottlePos_L,number) 50 - 2 * 100 / (>L:THROTTLE1_SET) My HA420 Throttle 2 Set#@ 327.68 / 50 + 50 max 100 min d (>L:HA420_ThrottlePos_R,number) 50 - 2 * 100 / (>L:THROTTLE2_SET)
Alternatively, you could use lua - there is already a post on how to control the HondaJet throttle via lua - see https://fsuipc.com/community/user-contributions-user-contributions/honda-hjet-throttle-control-fsuipc7/#post-44
Your ini file does show some issues:
1. You have assignments to joystick letters (joyletters) that no longer exist:
A=<< MISSING JOYSTICK >> B=<< MISSING JOYSTICK >> C=<< MISSING JOYSTICK >> D=<< MISSING JOYSTICK >>
To correct this, you need to remove/delete all axis and button assignments to these joyletters, or (alternatively) change the axis/button assignment to use the correct letter for that joystick.
2, You should use substrings for your profile aircraft names so that they match all variants. For example, you can change this:
[Profile.HONDA] 1=HJET HA420 hgi2 2=HJET HA420 Red 3=HJET HA420 HGI 4=HJET HA420 HB-JRA REGA 5=HJET HA420 AEROSOAR - Lite 6=HJET HA420 Blue - Lite 7=HJET HA420 Black - Lite 8=HJET HA420 Yellow 9=mg hjet ha420 (Preset Default)
to this:
[Profile.HONDA] 1=HJET HA420 2=hjet ha420
(and you may not even need that second entry, but I can't remember if the match is case insensitive or not!).
You should do something similar for all your aircraft profile names - use a substrings that will match all variants that you want to catch in the profile.