Controls -> Inputs -> Radar Target Elevation Knob (Please add separate entries for each value)

[Kuky]

I have built 2 button boxes for the MiG-29A, one of which is for radar management, in particular the Radar Target Elevation Knob, which right now only has CW & CCW input settings which requires use of digital encoder, however as digital encoders have unlimited turns I did not use it, instead I used rotary switch which I have set to exact number of positions (-6, -4, -2, -1, 0, 1, 2, 4, 6, 8 & 10 deltaH ) but I cannot use this due to lack of distinct inputs in DCS for this knob.... so... can you please add it?

[YoYo]

This topc exists:

For merging.

[Kuky]

ah, didn't see it. Thanks

[Pavlin_33]

I know it's not much of an advice, but perhaps you can program in the clicks. So for example, +4 switch position would be three clicks and so on. Come to think of it your every switch position could be one click, since you can't really skip positions.

Edited Saturday at 07:55 AM by Pavlin_33

[Kuky]

1 hour ago, Pavlin_33 said:

I know it's not much of an advice, but perhaps you can program in the clicks. So for example, +4 switch position would be three clicks and so on. Come to think of it your every switch position could be one click, since you can't really skip positions.

Can't do it that way because the input board is not programmable and can't distinguish the direction. I am using one of the LeoBodnar's board BBI-32 I think it was, which is just button inputs only.

Edited Saturday at 09:32 AM by Kuky

[Pavlin_33]

2 hours ago, Kuky said:

Can't do it that way because the input board is not programmable and can't distinguish the direction. I am using one of the LeoBodnar's board BBI-32 I think it was, which is just button inputs only.

I see. Well if the board can't be programmed, you could use some sort of intermediary software solution to bridge the gap, but this now becoming  somewhat complex.

Determining direction should be easy, because you know the current switch position and you can compare that to the new one.

Let me know if you would like to take this further, maybe I could come up with a solution for you.

[Kuky]

16 minutes ago, Pavlin_33 said:

I see. Well if the board can't be programmed, you could use some sort of intermediary software solution to bridge the gap, but this now becoming  somewhat complex.

Determining direction should be easy, because you know the current switch position and you can compare that to the new one.

Let me know if you would like to take this further, maybe I could come up with a solution for you.

Thank you for the offer but I really don't want to bother you with this  I think its just too much hassle because most likely won't work because I am using normal rotary switch, not special one from LedoBodnar here (http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=207) which probably can be configured to do something like that.

Edit: just checked his BBI-32 configuration tool and its for rotary encoders, so it can't solve my issue. I'll just have to wait for ED to hopefully add separate inputs for radio elevation knob.

Edited Saturday at 12:16 PM by Kuky

[Pavlin_33]

What outputs does your board make when you make selections on your rotary switch? Joystick button presses or something else?

Edited Saturday at 02:20 PM by Pavlin_33

[Kuky]

29 minutes ago, Pavlin_33 said:

What outputs does your board make when you make selections on your rotary switch? Joystick button presses or something else?

Standard joystick button presses

Each step in rotary switch sends separate/unique button press

Edited Saturday at 02:50 PM by Kuky

[Kuky]

My humble button boxes for MiG-29A Fulcrum weapons and radar panel

[Pavlin_33]

7 hours ago, Kuky said:

Standard joystick button presses

Each step in rotary switch sends separate/unique button press

I could set up a NodeJS / vJoy combination for you.

NodeJS would be a executabble app that would read your Leo-board's button presses and convert that to repetative button presses for vJoy, which is a programmable virtual joystick.

For example, you move your switch to -6 dH and vJoy sends 4 quick successive button presses. I am assuming that DCS uses one joystick button to increment and one to decrement the radar elevation.

Let me know if this would be acceptable solution for you.

[AeriaGloria]

7 hours ago, Kuky said:

My humble button boxes for MiG-29A Fulcrum weapons and radar panel

Very jealous! What do you think of MiG-29 human interface/weapon controls ergonomics now? Any revelations? 

[Kuky]

12 hours ago, Pavlin_33 said:

I could set up a NodeJS / vJoy combination for you.

NodeJS would be a executabble app that would read your Leo-board's button presses and convert that to repetative button presses for vJoy, which is a programmable virtual joystick.

For example, you move your switch to -6 dH and vJoy sends 4 quick successive button presses. I am assuming that DCS uses one joystick button to increment and one to decrement the radar elevation.

Let me know if this would be acceptable solution for you.

Thanks heaps for wanting to help but that looks like to much hassle and I don't really want to install/run any more extra software, and ED will fix the inputs eventually.

Cheers!

[Kuky]

12 hours ago, AeriaGloria said:

Very jealous! What do you think of MiG-29 human interface/weapon controls ergonomics now? Any revelations? 

While not 100% in right location (but still its good approximate) it does ease up workload compared to remembering many different buttons/HATs on throttle or stick, so ergonomics is easier this way. It does get little confusing to reach for right switch as they are all fairly close together when in rush to change settings when getting into the merge, I think it needs lot of practice to get it right, but also knowing which switch needs to be in what position depending on scenario, at least I do