Kuky

See screenshots -lake east of Buckeburg has bad terrain mesh/elevation

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

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!

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

Standard joystick button presses Each step in rotary switch sends separate/unique button press

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.

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.

Isn't that being done by ED in this case? I mean you used 1 thing, this manual, to model MiG-29's SPO-15 this way while there are more than 1 thing - Yugoslav pilots (also more than 1) and other manual which contradict it.

That is just wrong. REAL WORLD events stomp your manuals/papers esp when in addition there are other manuals/papers which also contradict them. Have you not ever come across reading something, some instructions only to find that it does not function in the same way when you try it? I know I have, so pardon me for saying, you are just blindly trusting (and I can taste a hint of bias) what you are presented. As a tester, you should know to TEST the claims before you decide if something is right or wrong.

Yeah, Slovenia never had MiG-29

Sorry but witnesses of real world events, such as pilots who flew the very aircraft, are not opinions. Those pilots are also SMEs on the subject as again, they flew the aircraft as a profession. Also documents can not only be written with mistakes but can also be interpreted incorrectly, which is most likely what happened in this case, esp when manuals from other sources do not back the info from the one ED used and relied on.

Nah, its not fixed, its still there

ah, didn't see it. Thanks

dreams coming true after soooo many years.... the MiG-29, and now Yugoslavia map also... I'll be flying over my own city, country... at least I should be able to navigate easier visually

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?