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
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
Posted by: @md82I'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: @md82I'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.
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!
@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!
Posted by: @md82I would finally crack it and changed the offset to include that bit.
But you cannot use the B variables (ending in _INC, _DEC and _SET) - they can only be used via calculator code.
As I said, B-type variables and Input Events are related but NOT the same. For FSUIPC offsets (and assignments to Input Events), you use the Input Event names as seen by FSUIPC. When using calculator code, you need to use the name of the B-type variable as shown in MSFS debug windows.
The B-events will/must work...providing you have the FSUIPC WASM installed and working correctly (which I am assuming you do!).
To test these, all you need to do is use the Add-ons->WASM->Execute Calculator Code option, and try executing the following:
1 (>B:AP_PITCH_CTRL_WHEEL_1_INC)
Execute that 2 or 3 times and see what happens. If you only see small movements, try:
10 (>B:AP_PITCH_CTRL_WHEEL_1_INC)
and see what that does.
Then also try the same but using AP_PITCH_CTRL_WHEEL_1_DEC
You can also add the Input Event AP_PITCH_CTRL_WHEEL to an FSUIPC offset, and add logging for that offset (Log->Offsets) and make sure you check to log to the FSUIPC log file. Also set WAPI Debug level logging (Log->WAPI->Debug), then test those b-variables by executing the calculator code I gave above. Then show me / attach both your FSUIPC7.ini and FSUIPC7.log files.