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
Harware Throttle B737 via FSUIPC7
MSFS2024
FSUIPC7 latest version
Aircraft: ASOBO B737 MAX
My original B737 Throttle Quadrant (Engine1) writes the lever position via FSUIPC to offset 0x088C (also tried 0x089A). The offset is loaded, but the virtual throttle lever no longer moves (this worked with MSFS2020).
This wouldn't be a problem in itself. However, when I monitor the offset, I can see that the value from the hardware lever appears but is immediately overwritten by the value of the virtual lever! This causes the engine to constantly wobble back and forth. I can disable the hardware lever with offset 0x310A, but I should actually be able to disable the virtual one. Is there a possible solution to my problem?
Regards,
H.P. Roth
Can you check your assignments in MSFS2024 and make sure that your throttle is not also assigned there.
It could also be possible that the ASOBO B737 MAX is using a different throttle control than the one supported by offsets 0x088C / 0x089A. I will check that here... If this is the case, you cannot use those offsets, and would have to use a different assignment method.
Regards,
John
Hello John
As I already described: On the Displacement 310A, it's possible to either close the levers together or block them:
Controls the joystick connection to the main flight controls.
Normally all zero, set the following bits to actually disconnect
the specific joystick axes (from least significant bit = 0):
0 Elevator
1 Aileron
2 Rudder
3 Throttles (all).
4 See below (throttle sync control)
5 Elevator trim
6 Throttle #1
7 Throttle #2 (see next byte for others)
By the way, the B737 MAX is available in 2020, but it's probably not from ASOBO. The description doesn't mention anything about that either.
Posted by: @cockbitAs I already described: On the Displacement 310A,
Offset 310A will not disconnect joysticks assigned in MSFS - it disconnects from FSUIPC. As advised, please check your MSFS assignments and if assigning in FSUIPC you MUST remove assignments in MSFS.
Posted by: @cockbitBy the way, the B737 MAX is available in 2020, but it's probably not from ASOBO.
Maybe, but you said this was working with the same aircraft in MSFS2020. If it is a different aircraft, although still a B737 max, you need to specify in which aircraft this was working with so that I can compare - if I have this aircraft for MSFS2020.
A side note - better to add a new comment than replying to each individual comment - this makes the conversation timeline difficult to track. I will look into removing this feature in these forums...
Posted by: @fsuipcIt could also be possible that the ASOBO B737 MAX is using a different throttle control than the one supported by offsets 0x088C / 0x089A. I will check that here... If this is the case, you cannot use those offsets, and would have to use a different assignment method.
No, it looks to be using the same axes controls. If I assign my throttle lever to offset 0x088C here, it works. However, when doing this the lever controls both throttle1 and throttle2...not sure why this is. I will investigate further.
John
Interesting, which aircraft exactly did you load?
Where did you make the assignment?
I thought that if I write directly to the offset, I don't need to assign anything else. That's always worked for me with FSUIPC so far.
H.P.
Posted by: @cockbitInteresting, which aircraft exactly did you load?
The Asobo B737 Max in MSF2024.
Posted by: @cockbitWhere did you make the assignment?
In FSUIPC7, assigning a spare axis to offset 0x088C, and also removing/checking no assignments in MSFS.
Posted by: @cockbitI thought that if I write directly to the offset, I don't need to assign anything else. That's always worked for me with FSUIPC so far.
You don't. But you MUST remove any assignments in MSFS. MSFS recognises most devices and will apply default assignments. Again, please check your MSFS assignments.
Hi
I've naturally removed all keyboard and axis assignments related to power control.
I'll create log files from 2020/24 for both the hardware and virtual levers tomorrow and send them to you.
Regards,
H.P.
Posted by: @cockbitI've naturally removed all keyboard and axis assignments related to power control.
Well, nothing 'natural' about this - I am plagued with issues due to users assigning in FSUIPC and not removing the default assignments in MSFS. This is always the first thing I ask users to check, and it has taken quite a while for you to confirm this. Also, as MSFS2024 has various different asignment levels/profiles, it is quite a bit harder to check and remove such assignments.
Posted by: @cockbitI'll create log files from 2020/24 for both the hardware and virtual levers tomorrow and send them to you.
Ok, that may help - make sure you are logging the offsets and have logging for /axes Controls activated. Also a good idea to remove any events flooding the log using the DontLogThese ini parameter. I will take a look next week - I do not have time this weekend.
And please stop replying to individual messages, and use the red Add Reply button instead. Makes things far easier to follow. I will remove the facility to reply to old comments as it is a pain to follow the conversation with this, and to find the latest comment added.
John
By the way, the B737 MAX is available in 2020, but it's probably not from ASOBO. The description doesn't mention anything about that either.
Posted by: @cockbitBy the way, the B737 MAX is available in 2020, but it's probably not from ASOBO. The description doesn't mention anything about that either.
Your description sai:
Posted by: @cockbitthis worked with MSFS2020
It may have worked with a B737 Max in MSFS2020, but not from Asobo so there isn't one. This information is therefore useless unless you provide further details. That is all I am trying to say - give me more information, the vendor for example....