if that's the case try re-seating the grip & extension
if that's the case try re-seating the grip & extension
Awhat grip do you have? i have the alpha, and that's the trigger lever, which defaults to pressed when extended. If i pull the trigger switch in, it then becomes unpressed
APressed
AUnpressed
TOk - removed the 20cm extension and now no errant button pushes, so ready to go into dcs and see if I can set up force trim in the apache
TThis extension has been a dick for some time, and basically stopped me swapping grips for different planes - I have four grips - CM2, F14, TMF18 and TM-A10. Used to be able to swap in a couple of minutes, but the extension was so picky, once I got it working I just left it alone.
TYes when the guard is down get a press on btn6, which goes away when I unsafe it.
THere goes force trim!
TGetting closer - you available - going to voice in case you are
Poh shit sorry m8, give me a min
SI don't know why it is like that but you can invert the button from VPForce configurator's button mapping tab. It should solve the problem not being able to map buttons in DCS.
PSo is there any way to configure the Virpil & Winwing grips via the VPforce config app? Or if I buy Virpil & Winwing grips will I still need to buy the bases too?
WWhat do you mean to configure? They're plug and play
PI just mean how with the Virpil software you get the options to do different things with the buttons/axis etc. can we do the same sort of configuration in the vpforce app?
Plike if this was with my vkb (I don't own virpil/WW atm) I can change the flip trigger to act differently depending how I set it, I imagine that virpil/WW have similar configurability & can we do the same thing with vpforce?
Psorry if I'm making this confusing 
WThere's limited stuff you can manipulate with the Rhino software. Since there's tools (such as joystick Gremlin) that can do the more advanced stuff, I haven't put in much effort to cover all the edge use cases 
Pyeah nice, I kinda forgot about JG
PHey Walmis, just wondering what's going on here? This might be normal I might need to run the debug to get a proper log for you, I'm getting motor vibration/shudder occasionally when going to full x deflection, I'm also using software endstops, this hasn't happened during flight but can happen when between flights & the stick has gone 'limp' & I move it to the x endstop. Is this the motor's doing their self protection thing? the motor temp was around 34° is this too hot? I wouldn't think it was especially with the fans & as I say it's not happening when flying. Does it just not like touching the endstop while in the 'limp' state it's in between flights & I just need to be careful not to be tempted to move the stick unless flying? Sorry for the txt wall.
Si had the same thing last night with XPForce.. i made a post here but deleted since it cleared up after a reboot
Smy motors were dead cold though and the repeating disconnects happened right away. not sure what the problem was, it was only with the joystic not the pedal single axis.
Si made sure the joystick was the "master device" in xpforce config also
WYeah, I have a fix committed for the next firmware update.
WI've noticed the author of XPforce started working on better multi device support
Sit mostly works.. kinda finicky though
Ahere's a random thing -- i've been playing some IL2, and all a sudden the LEDs on my virpil alpha grip, attached to the rhino, turned on 
A(is that something to be worried about? like, they've never worked before... and I assume if i disconnect and re-connect, the LEDs will stop working)
AProof that I’m not crazy…
TWith a lot of messing around with my virpil 200mm extension, I got it to send a constant push on button 1, which then upset DCS as I could not configure any controls without them being overwritten by button 1, which does not exist. Tried the invert to no effect, so just set it to zero and nothing seen by DCS.
T
AYour bug is so weird, cause even with the button constantly activating for me when I have the lever pushed out, it doesn’t fight when attempting to create other binds with the grip
ADCS only activates the bind if there’s a state change from off to on for me, I have lots of switches on my virpil button boxes that are toggles that are always on and never had problems with binds in DCS
T@amadeus Which stick grip do you have plugged in ?
AIn the photo I just posted above? It’s the Virpil Alpha grip
T@.durham
Tmy question was meant for @.durham but I also have the alphas and the button he is referring to as number 1 is the flip trigger in front of the actual trigger...If it is pushed forward then it sends a constant button 1 signal to windows and DCS.. the fix is to pull the flip lever back so it doesn't send the button 1 signal and then you can program the other hats and buttons....I also have the virpil panels 1 and 2 and sharka 50 and they do not do this....only the stick forward flip trigger.
TGrip is VPC T-50CM2
TI have not found button 1 per the rhino responsive to any button press. My thought is that it is a "I am here now" signal from the grip.
TI will go and change to their F-14 grip and see what happens.
Ahere's screenshots from my different button panels, notice all the red buttons that show constant switch presses, i have no idea what your setup is to not have this
A
A
Aand of course, my rhino: that's with the lever out, and also with the lever returned to center
ATo be clear tho — this does not cause a problem when binding in DCS. My guess in Durham’s case, his device must be spamming multiple button presses very quickly, unlike the holds that you see with the button panels and my rhino,
TYeah, but once I am using the VPForce base I lose the virpil software, which talks to the virpil base, which is no longer connected, unless I am missing something?
TOkay the tester tool works, but just repeats what I get from the Rhino tool, which is button 1 stuck on send, like my mother:
T
T@.durham VPC T-50CM2 is not a grip
WIt is
TI stand corrected..confusion is that there is a base and grip both with that designation...Mongoose
Aso it stays on and never goes away regardless of that lever state, eh?