-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
AH-64D Both Pilot and Gunner Signal Light (color) is 0-1 should be 0-65535 #135
Comments
Pls test |
the problem is that these vales were nowhere in the code, they were guessed from the model itself. |
can you give me the name oft the Poti? the Panel lighting readout from your screenshot is only the light intensity. |
Yes I can only try to figure out the problem. The complexity of your work grow with the number of modules and with the complexity of that particular module. |
Pilot Primary Lights Control Knob Remember the CPG cockpit have those controls as well =b Potentiometer: |
i checked the code. BIOS works with the Model Arguments and these 2 are linear in the Cockpit Model. booth work from 0 to 1. so something in the code must be strange. Needs more investigation. since to late for today i look into it when i have more time |
Take your time, and happy holydays |
@flanker0ne Looks like this is a quirk of the module itself in DCS. The panel light (primary lights) knob models a logarithmic potentiometer (well rheostat probably) in that you gotta turn past 50% to get to just 10% intensity and then it takes off towards the end. I have not seen this modeled in any other module in this way. The cockpit animation goes all the way from 0-100% in the model itself but this is not reachable in the sim as you point out. This may be similar to the pressure setting counter on the F18 that had part of the range outside of user reach. Strange way to implement it - perhaps a bug in DCS, but not really in DCS-BIOS I'd say. If you want linear output for your LEDs you could: |
Hi guys, thanks for your attention |
The text was updated successfully, but these errors were encountered: