Severity:High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description: The Asobo H125 has a rotor brake handle that applies the rotor brake in percentages. There is a corresponding simvar called A:ROTOR BRAKE HANDLE POS which is not settable. So I am wondering how can the rotorbrake be applied partially in percentages? The available key events just allow for a ON/OFF control.
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
In my sdk samples I only have the cabri files in terms of helicopters, not the H125.
Yes, the lever of the H125 will only remain active, when it is fully pulled, below that it will go back to zero if you let go. But that should be related to the template and not the axis.
I have set up my own lever template, when moving the lever there is a lvar being set to values between 0 and 100. Based on that lvar I have tried to use the axis key event but without success. The handle pos simvar reads 0 no matter how my lever is positioned.
As you can see in my screenshot I am dividing my custom lvar that is set with the lever by 100 to ensure that the key event is being set with values between 0 and 1.
The documentation says that the axis is set with 1 and 0 which is confusing to me as well since I would usually expect values between 0 and 16383 for an axis. I was under the impression that the H125 rotorbrake is less strong when only pulled slightly compared to having it fully pulled, but that would mean the axis is not just on/off.
I am not sure where you saw the axis key event being used, this is what I could find. It seems to be setting the handle with values between 0 and 16k. But I am not sure how that would be translated to a regular key event so I can use it in my update template. Maybe you have an idea? Otherwise we’ll wait until someone from Asobo might provide us with some help.
So in the end the mistake there is that the AXIS_ROTOR_BRAKE_SET key event does not take a boolean as a parameter but a 16K position, which makes more sense for an axis and is more in accordance with other axis events.
Unless you have identified another issue, I’ll add a ticket in our backlog so the documentation is fixed.
Are you sure you don’t have a rotor brake input event somewhere already that conflicts with what you are trying to set directly through the K event in your custom component?
You can use the behaviors tool to make sure your component is correctly evaluated, or even hardcode a test value to send to the K event.
But if it doesn’t work, I suspect that same K event is sent from somewhere else.
I can have a look if you are willing to share a version of your package.
I have never used the axis key event before. I will set up the update template again as shown in my screenshot and check what the behaviors tool tells me.
Problem solved. I just tried it exactly like I did back then and this time it works. Maybe the live reload had some kind of hickup back then.
Thanks a lot for your support.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
