snp227 Posted June 16, 2019 Report Share Posted June 16, 2019 I've been using FSUIPC for some time, but have not delved into the advanced functions beyond separate profiles for aircraft, etc. I'd like to have two sets of functions for certain joystick buttons. I've read the 'COMPOUND BUTTON CONDITIONS' text in the advanced manual, and also perused some threads here on the topic but I"m doing something wrong! I am using a Gladiator MKII stick, and to start I would like to same buttons to move the heading bug left, right and the OBS needle left, right depending on whether or not another button is pressed. The modifier button is #29 on my joystick, identified by FSUIPC with the number '3' (see first screenshot). I want to use buttons 2 and 8 for my actions. Only the VOR OBS INCR and DEC is defined in the 'Options and Settings' dialog box (see screenshots 2, 3). Everything else is in the .INI file; here are the relevant lines: 45=CR(-3,29)R3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)R3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)R3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)R3,8,C65662,0 -{VOR1_OBI_DEC}- The OBS needle moves left and right, regardless of the position of the modifier button. The Heading bug does not move, at all. Could anyone please help me clean this up and close my knowledge gap? Thanks in advance... Link to comment Share on other sites More sharing options...
spokes2112 Posted June 16, 2019 Report Share Posted June 16, 2019 For the first part - 1 hour ago, snp227 said: The OBS needle moves left and right, regardless of the position of the modifier button. It looks like you may have a syntax error that FSUIPC doesn't catch, you are using a "repeat" modifier in the second half of the compound code. None of my compounds have this. Perhaps having this negates the original "CR" in the first part of the compound code. 45=CR(-3,29)R3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)R3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)R3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)R3,8,C65662,0 -{VOR1_OBI_DEC}- Maybe (?) this will work - 45=CR(-3,29)3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)3,8,C65662,0 -{VOR1_OBI_DEC}- For the second part - 1 hour ago, snp227 said: The Heading bug does not move, at all. I see that you are using profiles and that particular profile is for the 310, perhaps the Milviz C310? I do not have that model from them so cannot test. I can bet apples to oranges that they are not using standard FS type coding, rather using L:Vars instead. (many designers do use L:Vars, specially for heading) My advice? Try your compound code with something stock and non-complex such as the 172 or Baron. If it works for the 172 / Baron then further investigation will need to be done, possibly using a lua file will need to be done to interface with it. Roman Link to comment Share on other sites More sharing options...
snp227 Posted June 16, 2019 Author Report Share Posted June 16, 2019 9 minutes ago, spokes2112 said: For the first part - It looks like you may have a syntax error that FSUIPC doesn't catch, you are using a "repeat" modifier in the second half of the compound code. None of my compounds have this. Perhaps having this negates the original "CR" in the first part of the compound code. 45=CR(-3,29)R3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)R3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)R3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)R3,8,C65662,0 -{VOR1_OBI_DEC}- Maybe (?) this will work - 45=CR(-3,29)3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)3,8,C65662,0 -{VOR1_OBI_DEC}- For the second part - I see that you are using profiles and that particular profile is for the 310, perhaps the Milviz C310? I do not have that model from them so cannot test. I can bet apples to oranges that they are not using standard FS type coding, rather using L:Vars instead. (many designers do use L:Vars, specially for heading) My advice? Try your compound code with something stock and non-complex such as the 172 or Baron. If it works for the 172 / Baron then further investigation will need to be done, possibly using a lua file will need to be done to interface with it. Roman Roman, Thank you for your reply, and for fixing my issue. It is clear to me now, of course. I am using the Milviz C310; your advice on testing with stock aircraft FIRST is noted. Link to comment Share on other sites More sharing options...
Fielder Posted June 16, 2019 Report Share Posted June 16, 2019 45=CR(-3,29)3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)3,8,C65662,0 -{VOR1_OBI_DEC}- Yes, I 🤓 too have been guilty of this: 45=CR(-3,29)R3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)R3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+3,29)R3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+3,29)R3,8,C65662,0 -{VOR1_OBI_DEC}- And this: 45=CR(-3,29)3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-3,29)3,8,C65880,0 -{HEADING_BUG_DEC}- 46=CR(+3,29)3,2,C65663,0 -{VOR1_OBI_INC}- 47=CR(+3,29)3,8,C65662,0 -{VOR1_OBI_DEC}- And this: 45=CR(-29,-3)3,2,C65879,0 -{HEADING_BUG_INC}- 46=CR(-29,-3)3,8,C65880,0 -{HEADING_BUG_DEC}- 47=CR(+29,3)3,2,C65663,0 -{VOR1_OBI_INC}- 48=CR(+29,3)3,8,C65662,0 -{VOR1_OBI_DEC}- 😠 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now