Jump to content
The simFlight Network Forums
Sign in to follow this  
snp227

Another Compound Function Help Request

Recommended Posts

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...

2019-06-16_10-22-39.jpg.2f33af8eb590fbb450d5d1797cb14e27.jpg

 

 

2019-06-16_10-39-47-2.jpg

2019-06-16_10-40-05-3.jpg

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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}-

😠

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.