-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some KA-50 gauges showing too small values #791
Comments
I did some more digging and fixed this with small code change. There's nonlinearity in gauge. Here's lookout table I made:
With this, fix is:
If this is the proper way for fix, I can put changes to git. |
@usagiyon Thanks for "rolling up your sleeves" and getting stuck in. It is great to seek folk helping the project and themselves. What you've shown in calibration filter changes above is the (or at least one) way of correcting this. Typically you would make the changes in your fork on GitHub, and then create a Pull Request to get your changes considered for inclusion in Helios. |
Pull Request: #794 |
Shipped in 1.6.606. Many thanks for the contribution to Helios |
Some gauges provided for KA-50 by Helios (Profile Editor's Toolbox / KA-50 Gauges) displays too small values.
I haven't checked all gauges. The most distinct are Rotor RPM gauge, QFE and Rotor Blade Angle gauge. There might be more.
The rotor rpm gauge is off about 4-5% at high rpm's (around 100% rpm). The error will go smaller as rpm value goes down.
I figured out that if I use factor 1.05 for TriggerValue in Helios Editor, then gauge will display quite accurate values:
In screenshot above I used Custom gauge along with 'baked in' gauge as I cross checked their behavior. Both had same issue.
What I have checked is that routines itself in KA-50 plugin seems to work properly (did small test program to get values).
When https://github.com/HeliosVirtualCockpit/Helios/blob/master/Aircraft%20Ka-50%20Plugin/Gauges/RotorRPM/RotorRPM.cs receives a value, it will calculate proper value for needle.
I also tried to fiddle with json interface and changed it's values from:
to
Which also works as it's essentially same as 110 * 1.05
My guess is that something happens for value received from DCS before it is passed to KA-50 plugin.
The engine RPM-% gauge which is similar to rotor rpm works fine and has almost 1:1 code in plugin.
The text was updated successfully, but these errors were encountered: