Now that I was finally able to get the engines started, I dug into solving the problem of getting the throttles bound. The Boeing 247 implementation uses LVARS for throttle control, so binding via FSUIPC isn’t completely straightforward. What is required is to select FSUIPC offsets to bind the LVARs to and then bind the throttle axes to those offsets. Since the throttle axis ranges over a signed 16-bit value, a scalar is applied to change the range from 0-100, which will fit easily in an unsigned byte. Additionally, you must enable WASM via Add-ons->WASM->Enable. You may need to restart FSUIPC for this to take effect. If you don’t have that option in your menu, be sure to download the latest version of FSUIPC (7.3.2, released March 20, 2022).
Anyway, here are the FSUIPC7.ini settings to bind the throttles to a two-axis controller:
[Profile.Boeing 247D]
1=Boeing 247D United Air Lines (1941)
[LvarOffsets.Boeing 247D]
1=L:ENG THROTTLE 1=UB0xA000
2=L:ENG THROTTLE 2=UB0xA001
[Axes.Boeing 247D]
…
3=BX,256,F,x0100A000,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A000 }-
4=BY,256,F,x0100A001,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A001 }-
A couple of notes:
- This assumes a separate profile for the 247. Mine is called “Boeing 247D,” but any name can be used.
- Under the axes settings I just included the throttle binds, so don’t wipe out your other existing axes when copying and pasting.
- I used offsets 0xA000 and 0xA001 (scaled down to byte values). If these offsets are already in use for other reasons, choose new ones.
- To bind to a single throttle axis, just assign both LVARS to a single FSUIPC offset and then bind the throttle to that offset.