jetsimace Posted July 19, 2024 Posted July 19, 2024 (edited) I am using the two dials at the throttle (front right, please see attached screenshot) to decrease or increase the AH-64 MPD's brightness. Both dials are of "mode encoder" type (set in Virpil's VPC configuration tool sw). Now I would need another 2 dials to act as "video control knob" for the MPDs, so I was wondering if I could use an additional shift state to get another two dials e.g. when pressing the dial+twisting. Unfortunately shift state doesn't seem to work together with "mode encoder" dials (for setting that doesn't work see second attached screenshot - only difference to the one that is working is the additional shift state. The "SHIFT1" state itself is properly recognized) Has anyone been able to get a shift state working for a "mode encoder" dial. If so, how? Edited July 19, 2024 by jetsimace
Nightdare Posted July 19, 2024 Posted July 19, 2024 (edited) Yes, encoders are basically buttons as well make a new logic button # under the same physical (encoder) button and assign it to SHFT2 (Don't forget to set the 5-way to shift function) Edited July 19, 2024 by Nightdare Intel I5 13600k / AsRock Z790 Steel Legend / MSI 4080s 16G Gaming X Slim / Kingston Fury DDR5 5600 64Gb / Adata 960 Max / HP Reverb G2 v2 Rhino FFB / Virpil MT50 Mongoost T50 Throttle, T50cm Grip, VFX Grip, ACE Rudder / WinWing Orion2 Navy, UFC&HUD, PTO2, 2x MFD1, PFP7 / Logitech Flight Panel / VKB SEM V / 2x DIY Bodnar Button Panels
jetsimace Posted July 20, 2024 Author Posted July 20, 2024 (edited) Thanks. I already had that assignement, but I tried again (including assignment of a new "SHFT2" state to the 5-way dial): new logic button #71 under the same physical (encoder) button #62 and assigned it to SHFT2 - please see below (2nd screenshot). That doesn't work either, while the first one without any shift state (here logical button #51, see first screenshot) works fine. Shift state "SHFT2" itself works fine. Have you tried yourself or was that just your assumption that it should work? Strange thing is, that already if I assign a second logical button without any shift state to the same encoder dial (see 3rd screenshot), this already does not work...maybe "encoder" only works for one logical button and/or for one "mode encoder" dial / physical encoder button? Edited July 20, 2024 by jetsimace
Nightdare Posted July 21, 2024 Posted July 21, 2024 (edited) I have the V1 Mongoost, but it works with the same software First off: what happens if you uncheck the "Turbo/Delay" option? This is my setup: Profile page: Button Page: null S1 Same settings for Physical 065 - Disregard 053, that's the push function S2 In VPC Joystick tester, this results in this: Edited July 21, 2024 by Nightdare Intel I5 13600k / AsRock Z790 Steel Legend / MSI 4080s 16G Gaming X Slim / Kingston Fury DDR5 5600 64Gb / Adata 960 Max / HP Reverb G2 v2 Rhino FFB / Virpil MT50 Mongoost T50 Throttle, T50cm Grip, VFX Grip, ACE Rudder / WinWing Orion2 Navy, UFC&HUD, PTO2, 2x MFD1, PFP7 / Logitech Flight Panel / VKB SEM V / 2x DIY Bodnar Button Panels
jetsimace Posted July 22, 2024 Author Posted July 22, 2024 (edited) Thanks for your help! My settings look the same (of course button numbers are different), but in VPC Joystick tester (as well as DCS in-game) logical button 71 will not be triggered. "Delay" on or off has no noticable effect (at least for me). Shift state works fine with other (non-dial / encoder) buttons. Strange is that even if I set Shift state for logical button # 71 (of type dial/encoder) to "OFF", logical button 71 will not be triggered. Only my first assigned logical button to this dial/encoder (#51 with same settings) will be triggered. In contrast to that, a three-way physical switch I am able to use twice. Then I have assigned the shift state to my original logical button (#51) and the non-shift state to the new logical button (#71) - don't ask me why, but this setup now works !! Edited July 22, 2024 by jetsimace
Nightdare Posted July 22, 2024 Posted July 22, 2024 (edited) Hm, I do notice you don't set Shift 1 while setting Shift 2 functions, this might be a reason If things go wonky again, try to assign a shift# at all times (So if you have a button under shift 2, all others should have shift 1 checked), see if that solves any issues, it could be setting shift off while there are other shift states used, it does not see non-state (Shift Off) buttons Edited July 22, 2024 by Nightdare Intel I5 13600k / AsRock Z790 Steel Legend / MSI 4080s 16G Gaming X Slim / Kingston Fury DDR5 5600 64Gb / Adata 960 Max / HP Reverb G2 v2 Rhino FFB / Virpil MT50 Mongoost T50 Throttle, T50cm Grip, VFX Grip, ACE Rudder / WinWing Orion2 Navy, UFC&HUD, PTO2, 2x MFD1, PFP7 / Logitech Flight Panel / VKB SEM V / 2x DIY Bodnar Button Panels
Blackhawk163 Posted December 25, 2024 Posted December 25, 2024 (edited) Okay I’m glad I stumbled on this thread. I was curious if there’s a way to set shift states for any and all buttons. any help with this would be greatly appreciated. So in the VPC software there are currently only 5 shift states with buttons already populated in these states (67-71) in order to set the encoders to a shift state I have to sacrifice a push button that’s been shifted? Can I just turn the encoders to normal buttons and have them be shifted? lol I’m so confused. Oh wow, it really was simple to do this. I’m pleasantly surprised at how versatile this throttle is. Edited December 25, 2024 by Blackhawk163 My first assigned aircraft is in my profile name Ryzen 9800x3d/64gb DDR5 amd expo/RTX 5090/4tb m2/ Win11 pro/Pimax crystal light Winwing Orion F16ex (Shaker kit)/Skywalker pedals/Orion 2 F15EX II Throttle/3 MFD units/Virpil CM3 Mongoose Throttle/Trackir 5 F-16/A10II A/C /F-18/F-15E/F-15C/F-14/F5E II/F-4/Ah64/UH60/P51-D/Super Carrier/Syria/Sinai/Iraq/Persian Gulf/Afghanistan/Nevada/Normandy 2.0
Recommended Posts