Adri1 Posted February 23, 2022 Report Share Posted February 23, 2022 Hello ! I'm facing to a strange issue with FSUIPC7 that i don't really understand. Well, i have bought FSUIPC7 for MFS2020 a few weeks ago, in order to bind my own button box to FS2020. All work fine (or almost) except 4 of my 5 encoders... . So here is the point: I would like to bind my encoders to AP x var inc / dec (x = alt/hdg/vs etc). Each direction event of encoders is see like a push button. For example, for my first encoder, if I turn it in CW, my software send button 52 = 1,0,1,0 etc.. and if I turn it in CCW it send button 51 = 1,0,1,0 etc... . All of encoders works like that. On FSUIPC side, all of my encoders events are well logged in the FSUIPC log interface. But when after binding to a AP_x_Var_dec/incr, 4 of my encoders event are not visible anymore in the log interface and nothing move into the cockpit. Only the 5th encoder event is well logged and is able to set the AP target value... . Moreover, if for exemple, my working encoder is binded on AP_alt_var_dec / incr and then I swap this variable to bind it on a not working encoders it doesn't work too. So we can conclude that it come from my software, but if i run my own debug interface i cannot see any issue, and FSUIPC7 see my encoders events before binding them, so i cannot really believed that it come from my software. Morover, if I bind them directly into MFS2020, all work ! I dont really understand. Another stuff is that all of my swichs/push button/encoder ID are see by FSUIPC with the button ID from my SW + offset of 100. For example, my software send button 42 = 1 then FSUIPC see button 142 = 1, maybe it's normal, i dont know. Thanks a lot for your support !! BR Adrien Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now