mastercosta Posted July 25, 2020 Posted July 25, 2020 some btns in right TM MFD dont work in F16 and AV8B, in printscreen i put the bttns that dont work (in red) and work perfectly in A-10c and F18.(all buttons) the left MFD work perfet in all planes. i realy dont understand... try to delete all MFD controlls and make manually assign, unplugn diferent usb... and still not work in game. OZOMASTER A10C||F-14C||F-16C||F/A-18C||AV-8B||ASJ37||M-2000C||MIG15||MIG19||MIG21||F5-E||F86||FC3||P51D||Fw190||Fw190 A8||Bf109 D9||Spitfire||UH-1H||Mi8||GAZELLE||BShark2||CA||YAK52||CEagle2||L39||C101||i16||Supercarrier|| ---------------------------------------------------------------------------------------------- WINDOWS10 HOME ||asus GTX 1080|| 3440x1440 34' ||sixcore i7-3930k 3.2GHz || asus sabertooth x79 || 32GbRAM 2133Mhz || TM warthog || saitek cessna pedals || trackIR 5
Flappie Posted July 25, 2020 Posted July 25, 2020 In the Controls option menu, the UI layer category bindings have top priority above all other bindings. Please ensure you have not bound any of these unworking buttons in the UI layer category. It might be the same for the General category, but I'm not quite sure. ---
mastercosta Posted July 25, 2020 Author Posted July 25, 2020 i check "Ui Layer" i check general... no duplicate bindings :( but one correction to my printscreen ... in AV8b osb 6-7-8- work.. like in f16... one thing constante, at least. but still strange OZOMASTER A10C||F-14C||F-16C||F/A-18C||AV-8B||ASJ37||M-2000C||MIG15||MIG19||MIG21||F5-E||F86||FC3||P51D||Fw190||Fw190 A8||Bf109 D9||Spitfire||UH-1H||Mi8||GAZELLE||BShark2||CA||YAK52||CEagle2||L39||C101||i16||Supercarrier|| ---------------------------------------------------------------------------------------------- WINDOWS10 HOME ||asus GTX 1080|| 3440x1440 34' ||sixcore i7-3930k 3.2GHz || asus sabertooth x79 || 32GbRAM 2133Mhz || TM warthog || saitek cessna pedals || trackIR 5
mastercosta Posted July 25, 2020 Author Posted July 25, 2020 SOLVED ::: it was conflit binding with NS430... i have it but dont even remender that i bind NS430 into MFD 2 and that i can use it in 2d in almost evry plane, exect a-10c and F18 ... just delete lua input of NS430, and unchek NS430 special tab no this planes..DONE ;) my Bad, DCS is working fine... sorry. back to the air ;) OZOMASTER A10C||F-14C||F-16C||F/A-18C||AV-8B||ASJ37||M-2000C||MIG15||MIG19||MIG21||F5-E||F86||FC3||P51D||Fw190||Fw190 A8||Bf109 D9||Spitfire||UH-1H||Mi8||GAZELLE||BShark2||CA||YAK52||CEagle2||L39||C101||i16||Supercarrier|| ---------------------------------------------------------------------------------------------- WINDOWS10 HOME ||asus GTX 1080|| 3440x1440 34' ||sixcore i7-3930k 3.2GHz || asus sabertooth x79 || 32GbRAM 2133Mhz || TM warthog || saitek cessna pedals || trackIR 5
Flappie Posted July 26, 2020 Posted July 26, 2020 Thank you very much for your feedback! Does that mean the N430 bindings category can contain conflicting bindings without any warning, just like the UI layer and General categories? ---
mastercosta Posted July 26, 2020 Author Posted July 26, 2020 yes, i guess so... i was thinking that NS430 keybiding it only aplly in 3D , like in mi8 . but it is always present, even if you dont use it (if you have airplane boxcheck in NS430 special TAB in settings ) OZOMASTER A10C||F-14C||F-16C||F/A-18C||AV-8B||ASJ37||M-2000C||MIG15||MIG19||MIG21||F5-E||F86||FC3||P51D||Fw190||Fw190 A8||Bf109 D9||Spitfire||UH-1H||Mi8||GAZELLE||BShark2||CA||YAK52||CEagle2||L39||C101||i16||Supercarrier|| ---------------------------------------------------------------------------------------------- WINDOWS10 HOME ||asus GTX 1080|| 3440x1440 34' ||sixcore i7-3930k 3.2GHz || asus sabertooth x79 || 32GbRAM 2133Mhz || TM warthog || saitek cessna pedals || trackIR 5
Recommended Posts