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

Notifications

Clear all

Increase/Decrease command for Input Event

MD82 · 2026-08-18T14:47:01Z

Hello, I'm trying my best to find out the bindings for the new 707. I have managed to sort out quite some things. However, I'm stuck on the A/P Pitch Wheel. From Dev. Mode I can see that the wheel has 3 Input Events (..._Set, ..._Inc and ..._Dec). When I access the Input Events in FSUIPC, I can see the same initial name of the event "AP PITCH CONTROL WHEEL 1/2". If I manipulate the wheel in the VC, the values change in units of 10° up or down all the way around 360° (since it's a round wheel). When I assign this to a button, in FSUIPC and I set a parameter, it seems that it SETS a wheel position. (e.g. Parameter 1 gives 50°, Parameter 3.6 gives 180°, Parameter 0 gives 0°, etc., etc.) Since there is no separate Input Event to distinguish between increasing or decreasing, is there a way to still achieve that using this input event? Thanks, Xander

Page 2 / 2 Prev

Posts: 9

MD82

Registered

Topic starter

August 19, 2026 4:55 pm

(@md82)

Joined: 4 months ago

I've tried the "1 (<B:AP_PITCH_CTRL_WHEEL1)" calculator code in MSFS 2024 without success (Any value). I've tried adding the offset, even though I can manipulate values with some of the _Inc _Dec values, I can't let it jump 10° at a time like the VC mouse control does. Changing the parameter values changes what values present in Dev. Mode, but instead of increasing 10° at a time, I get random values. Leading me to believe it jumps more than 180° per click. But it's OK. The plane is still new, and I'll wait until someone with more knowledge than me makes the connection. Unfortunately, I've reached my limit LOL.

Thanks anyways

Posts: 350

FSUIPC

Admin

August 19, 2026 5:24 pm

(@fsuipc)

Joined: 1 year ago

Posted by: @md82
↑
I've tried the "1 (<B:AP_PITCH_CTRL_WHEEL1)" calculator code in MSFS 2024 without success (Any value).

That is because the calc code is incorrect - it should use '>' and not '<', i.e. '1 (>B:AP_PITCH_CTRL_WHEEL1').

Also, that is the wrong input event name. I asked you to try the inc/dec input/B events (maybe AP_PITCH_CTRL_WHEEL1_INC and AP_PITCH_CTRL_WHEEL1_DEC?) - the ones you saw in the MSFS debug windows (not the Input Events as seen by FSUIPC. Input Events (as seen by FSUIPC) and B-type variables are related but not exactly the same.

Posted by: @md82
↑
I've tried adding the offset, even though I can manipulate values with some of the _Inc _Dec values, I can't let it jump 10° at a time like the VC mouse control does. Changing the parameter values changes what values present in Dev. Mode, but instead of increasing 10° at a time, I get random values.

I won't be random. You just need to work out the value range it is expecting.

But please try with the correct calc code and correct B-vars first.

Posts: 350

FSUIPC

Admin

August 19, 2026 5:30 pm

(@fsuipc)

Joined: 1 year ago

Just checked your image in the initial post, and the B-type variables you should use (in calccode) are:

AP_PITCH_CTRL_WHEEL_1_INC

AP_PITCH_CTRL_WHEEL_1_DEC

AP_PITCH_CTRL_WHEEL_1_SET

i.e. you also missed the '_' character and had WHEEL1 instead of WHEEL_1, and need to use either _INC, _DEC or _SET at the end of the variable name.

You need to get the names correct!

This post was modified 35 minutes ago by FSUIPC

MD82

Registered

(@md82)

Joined: 4 months ago

Posts: 9

August 19, 2026 6:01 pm

Reply to FSUIPC

@fsuipc Sorry, yes. I was experimenting a bit. The post above was more a typo when editing the post. In my profile and calculator code attempts, I think I had them right. I had an epiphany when I noticed I did not have the _INC, _DEC mapped to the offset. So, I went in thinking surely, I would finally crack it and changed the offset to include that bit. But nothing moved when I included the INC or DEC. Without them, at least the wheel would move. But I'll re-check all my text. Hopefully it was a case of having too much open at the same time.

Have fun on the vacation!

Page 2 / 2 Prev