DCS-BIOS potentiometer input issue

[Extranajero]

I'm trying to set up the lighting controls for the Viggen but I've run into an issue I can't solve.

The three cockpit light rotary controls work fine when I have them connected to potentiometers via DCS-BIOS. The radar brightness and Hud brightness aren't working though.

If I watch the in game radar brightness rotary it tries to turn with the potentiometer, but then snaps right back to the default position. Hud brightness rotary doesn't move at all.

The rotaries work fine with the mouse and also with the keyboard, just not DCS-BIOS.

What's going on ? anyone know ?

[lesthegrngo]

I have had a similar issue in driving sims, and it almost always is a conflict between two different controllers. Make sure you have cleared any other mapping of those items to anything else, even if they are not present

 

Hope this helps

 

Les

[Extranajero]

Now you mention it that's what it seems like, but the only mapping I've got for those rotaries is the default keyboard bindings. I'll remove them and check again.

 

Edit, nope, still not working right. If I turn it down with the mouse I can turn it back up with the pot, but it's very sensitive, uses only a fraction of the travel. And it'll only go one way - up.

I think I need to reduce the range of values that is being sent and make them negative as well as positive. How I do that I don't know though.

Edited August 7, 2019 by Extranajero

[Hansolo]

Can you start communication's program and check whether you get indications similar to this

 

 

If your potentiometer is wired correctly then you should be able to read numbers from 0-65535.

 

cheers

Hans

[Extranajero]

I do have numbers from 0 to 65535 in the console.

 

I took a look at the Viggens clickable.lua - now bear in mind that I really don't know much about coding at all, except for a basic understanding of C from years ago - but one thing I have noticed is that all the rotaries I am having this problem with are called default_axis_limited rather than default_axis and are used with slightly different arguments. I don't know if that might be a part of the issue ?

 

I can work around this - I've already got the Radar brightness and the Hud brightness working, but that's by binding them to the keyboard and then using a joystick axis and JoyToKey - which is a bit of a mess, I don't want to do that unless I have to