FSUIPC Compound Commands - Joysticks ?

[scottb613 1,188]

Hi Folks,

Any advanced FSUIPC users out there ?

Since Win10 - I stopped using my proprietary CH Control Manager software as it seemed to cause more problems than it solved (BSOD) - and support of said program seems to have stopped completely - so I've lost the old designated [shift] button to allow a single button on a joystick have multiple functions when used with the [shift] button...

I've read through the "Advanced FSUICP User Guide" and I gather the designation of the [shift] button is possible - but cannot be done in the interface as it needs to be done by editing the config file...

I'd simply like to designate a single button on my joystick to act as a [shift] button - for all other button presses - effectively doubling the number of buttons available... Ideally - I'd like to define the [shift] button - then be able to hold two buttons down while assigning functions via the FSUIPC interface...

I haven't sussed it all out yet but I don't think that can be done as once I start using a [shift] button - I need to specify all assignments that use it in the config file manually - which is complicated by the fact that I use "Aircraft Specific" profiles... So each profile will need to be manually entered in the config file...

Has anyone been down this road and perhaps share some information that might be helpful ?

I'm kind of surprised that Pete never added this to the interface - as it seems to me a fairly useful feature...

Thanks...

Regards,

Scott   
 

[jmig 100]

I don't think you can do what you want in FSUIPC without writing a Lua script to code the keys.  However, I would just ask Peter, provided he isn't on a holiday. ;) He is very good at responding.

[spokes2112 179]

It can be done with forethought -
1) Map out everything you would like to do in a drawing.
2) Get the controller number & button numbers for reference, add to the drawing.
3) Get a list of the control numbers wanted from "The 2016 List of FSX and P3D Controls", add to the drawing.
4) Reread the "Advanced FSUIPC User Guide" - repeat, repeat again, and again and again....
5) Keep in mind that going this route you can no longer use the buttons page - ever. Once you get the hang of it, it becomes a no-problem.
6) Make a backup of your now current .ini 

Ex..

29=CR(-0,8)0,5,C65615,0 ;Trim Up     -{ELEV_TRIM_UP}-
30=CP(+0,8)0,5,C65759,0 ;Flaps Up     -{FLAPS_DECR}-
31=;SPARE FOR 5
32=;SPARE FOR 5
33=CR(-0,8)0,6,C65607,0 ;Trim Down     -{ELEV_TRIM_DN}-
34=CP(+0,8)0,6,C65758,0 ;Flaps Down     -{FLAPS_INCR}-
35=;SPARE FOR 6
36=;SPARE FOR 6

A semi-colon is a "comment out". To keep spares is a good idea for each button otherwise renumbering can become tedious.
CR equals "compound repeat"
CP equals "compound press"
from entry # 29
(-0,8) equals the shift button, minus equals unpressed, 0 equals the controller number, 8 equals the shift button
0,5, equals the button being affected by the shift - controller #0, button #5
C65615 equals the control number from "The 2016 List of FSX and P3D Controls"
0 equals the parameter, if needed, most cases zero will suffice
from entry #29 & #30
29=CR(-0,8)0,5,C65615,0     equals compound repeat, while the shift button #8 is unpressed (-) & while button #5 is pressed, trim up is performed
30=CP(+0,8)0,5,C65759,0     equals compound press,  while the shift button #8 is pressed (+) & while button #5 is pressed, a single flaps up command is performed

I don't use profiles since my 12 button stick now has over 27 commands. Basically if a button is different than the base entries only add that different button to the profile.

Here's an example of my hat switch that uses "double shifts" using compounds of buttons 8 & 11 with the hat -

62=CR(-0,11)(-0,8)0,32,C65734,0 ;HAT VIEWS     -{PAN_UP}-
63=CR(-0,11)(-0,8)0,33,C65856,0     -{PAN_RIGHT_UP}-
64=CR(-0,11)(-0,8)0,34,C65672,0     -{PAN_RIGHT}-
65=CR(-0,11)(-0,8)0,35,C65857,0     -{PAN_RIGHT_DOWN}-
66=CR(-0,11)(-0,8)0,36,C65735,0     -{PAN_DOWN}-
67=CR(-0,11)(-0,8)0,37,C65855,0     -{PAN_LEFT_DOWN}-
68=CR(-0,11)(-0,8)0,38,C65671,0     -{PAN_LEFT}-
69=CR(-0,11)(-0,8)0,39,C65854,0     -{PAN_LEFT_UP}-
70=CP(+0,11)(-0,8)0,32,C65674,0 ;HAT VIEWS - Look     -{VIEW_FORWARD}-
71=CP(+0,11)(-0,8)0,33,C65675,0     -{VIEW_FORWARD_RIGHT}-
72=CP(+0,11)(-0,8)0,34,C65676,0     -{VIEW_RIGHT}-
73=CP(+0,11)(-0,8)0,35,C65677,0     -{VIEW_REAR_RIGHT}-
74=CP(+0,11)(-0,8)0,36,C65678,0     -{VIEW_REAR}-
75=CP(+0,11)(-0,8)0,37,C65679,0     -{VIEW_REAR_LEFT}-
76=CP(+0,11)(-0,8)0,38,C65680,0     -{VIEW_LEFT}-
77=CP(+0,11)(-0,8)0,39,C65681,0     -{VIEW_FORWARD_LEFT}-
78=CP(-0,11)(+0,8)0,32,C66137,0 ;HAT VIEWS - Look Up     -{VIEW_FORWARD_UP}-
79=CP(-0,11)(+0,8)0,33,C66138,0     -{VIEW_FORWARD_RIGHT_UP}-
80=CP(-0,11)(+0,8)0,34,C66139,0     -{VIEW_RIGHT_UP}-
81=CP(-0,11)(+0,8)0,35,C66140,0     -{VIEW_REAR_RIGHT_UP}-
82=CP(-0,11)(+0,8)0,36,C66141,0     -{VIEW_REAR_UP}-
83=CP(-0,11)(+0,8)0,37,C66142,0     -{VIEW_REAR_LEFT_UP}-
84=CP(-0,11)(+0,8)0,38,C66143,0     -{VIEW_LEFT_UP}-
85=CP(-0,11)(+0,8)0,39,C66144,0     -{VIEW_FORWARD_LEFT_UP}-

It is very powerful what you can do by hand editing the .ini. This only scratches the surface.
BTW you can reload and check the button(s) operations while in the sim, after hand editing, by going to the buttons page and hitting reload. Depending on the text editor (notepad ++ is a good one) you use and it's settings, if there is a problem, FSUIPC will make a note of it in the .ini on the line where it occurred after a reload of the editor.

Good luck!

[hs118 707]

4 hours ago, jmig said:

I don't think you can do what you want in FSUIPC without writing a Lua script to code the keys.  However, I would just ask Peter, provided he isn't on a holiday. ;) He is very good at responding.

I gonna agree with John, it would probably be easier to do with Lua AND give you much greater capability.

Here is a package of FSUIPC Lua scripts I did for Dino's T-45C that you could look at. Check our the previous post mentioned as well.

https://uchisworld.wordpress.com/2016/02/06/this-game-of-ghosts/

 

 

[spokes2112 179]

It makes no difference for compounds (shifts), effectively doubling or tripling the amount of commands per controller.  Doing it via lua just makes a confusing mess.. Yes, lua has it's advantages but not for compounds.

[scottb613 1,188]

Hi Folks,

Hah - plenty to digest - thanks so much for all the great responses - let me read through this and get a grasp of what everyone is saying...

Honestly - though - probably only an extremely small percentage of people ever get into modifying FSUIPC config files - it's such a useful feature doubling the amount of joystick buttons a user has available - it would probably benefit so many - it would sure be nice to have a "simple" setup via the interface - so more users could leverage the feature...

Regards,
Scott 

[scottb613 1,188]

Hi Folks,

Just a follow up - I plan on trying to set this up over the weekend as a trial to see if I can get something working...

 

I did broach the topic in the form of a suggestion on Pete's forum - as a modification to the FSUIPC GUI...

Basically...

Request [shift] button to be specified via FSUIPC GUI to allow all button presses to support two modes of operation - which effectively doubles the number of buttons a user has available for assignment:

• Normal Mode [button press] - - - what we have now...
• Shifted Mode [button press] + [shift button]

Pete seemed receptive to the idea - if you have any input I'd suggest joining the conversation...

http://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Regards,
Scott

[Tom_L 533]

Hi Scott,

did you ever try LINDA? I have disabled Joysticks in P3D, my axes are set via FSUIPC and all buttons are set with LINDA. You get a >double< shift function and advanced features for certain airplanes via downloadable LINDA modules. Just a thought...

https://www.avsim.com/forums/forum/424-linda/

 

Rgds

Tom